-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
STM32F030 STM32F051: Flashing fails on first flashing instance (Reliability) #661
Comments
more info: 2018-01-24 DEBUG src/common.c: core_id = 0x0bb11477 2018-01-24 DEBUG src/common.c: *** stlink_write_reg 2018-01-24 DEBUG src/common.c: *** stlink_write_reg 2018-01-24 DEBUG src/common.c: *** stlink_write_reg 2018-01-24 DEBUG src/common.c: *** stlink_write_reg 2018-01-24 DEBUG src/common.c: *** stlink_run *** 2018-01-24 DEBUG src/common.c: *** stlink_read_debug32 8005641 is 0x8000004 2018-01-24 DEBUG src/common.c: *** stlink_run *** |
@ksschwabe @aric1987: Please verify if the problem still exists in Release v1.5.0. |
This problem now seems to have been resolved in v1.6.0. |
Thx for the feedback. Have you also tested v1.5.0 and v1.5.1? |
This should be tested with our |
st-flash
Whenever I flash any of the F0 chips that I have, the flashing fails on the first execution. I have to reset the chip (power off and power back on again) and try to flash the chip again. On the second execution it successfully flashes the chip.
I have included the standard console output below. I am unable to include the debug output, because GitHub won't accept it - it is too long.
This seems to be related to issue #92, but it doesn't look as if simply running st-flash directly works on the first execution.
Initial flashing:
After having reset the chip (power off and power back on):
The text was updated successfully, but these errors were encountered: