-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verify slow in reply mode #20
Comments
gicking
added a commit
that referenced
this issue
Dec 26, 2020
- support re-synchronization after return from RAM routine - add option verify via CRC32 checksum (see issue #20) - add parameter to verify option for new CRC32 check
Fixed via v1.4.2 and CRC32 verify option (32kB in 2.4s, 128kB in 4.9s). To use CRC32 check use option "-V 1" |
Thank you, this should prove very valuable! |
Update v1.4.3 fixes an address conflict with STM8L low-density BL v1.0. RAM code now starts at 0x210. For technical details see https://github.com/gicking/stm8gal/blob/master/verify_CRC32/README.md |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reading out and/or verifying data in "UART reply mode" is very slow over 2-wire interface. This is caused by a few ms latency for each byte which must be echoed by the PC. Using a FT232R, reading back 14kB takes ~5min
The text was updated successfully, but these errors were encountered: