Closed rzbrk closed 3 years ago
@Amerlander : Can you reproduce it on your system?
Mmmh, this problem seems to occur only sometimes ...
I think it is related to the high data rate on the serial port using burst.hex
.
Okay, I think I found the problem. This is how the .data file looks like, when the testcase 08a fails:
...
2000/01/01-00:00:00.000000 plzkillme!
2000/01/01-00:00:00.000000 plzkillme!
2000/01/01-00:00:00.000000 plzkillme!
2000/01/01-00:00:00.000000 plzkillme! me!
2000/01/01-00:00:00.000000 plzkillme!
2000/01/01-00:00:00.000000 plzkillme!
2000/01/01-00:00:00.000000 plzkillme!
2000/01/01-00:00:00.000000 plzkillme!
...
One line contains additional characters that will spoil the md5 checksum test.
I already speed down burst.hex
by introducing a control.waitMicros(1000)
after the serial.writeLine()
.
I increased control.waitMicros()
to 100 ms and now it seems to work. made multiple runs, all successful! :)
Can be closed if PR #75 is merged.
Output says: