-
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
STM32F072CBU: ST-Flash fails randomly on Raspberry Pi 2 #556
Comments
I must say, this is a very weird situation. I have seen people having trouble with a half broken USB cable. Not connected reset to target. You should try to upgrade the firmware of your programmer to V2J27 I have seen better results with this. |
Hi thanks for the suggestion. Have upgraded the firmware of the programmer to V2J27 but the problem still persists randomly. |
To bad this didn't help. The difficult part is it happens "random", hopefully other people will spot this and can reproduce. Currently I have no idea or fix. |
Is this reproducible with a STM32F072 or any similar MCU in a comparable environment? |
Since the flashing fails randomly and occurs on a RPI2, where undervolt occurs from time to time when it is connected with peripherals or running at a heavy load, I would suggest checking the volt of the ST MCU. |
Apart from the advice from @chenguokai this is also related to #356. |
st-flash
I have a bug which appears on Raspbian (For info, it works perfectly on Windows 10 and Ubuntu 16.04). The st-flash will sometimes fail to program my target chip with either of the error messages:
home/pi/stlink/src/flash_loader.c: flash loader run error
ERROR /home/pi/stlink/src/common.c: stlink_flash_loader_run(0x8000000) failed! == -1
OR:
INFO /home/pi/stlink.git/src/common.c: Loading device parameters....
WARN /home/pi/stlink.git/src/common.c: unknown chip id! 0xa05f0000
I have tried erasing the Flash before programming as detailed in the README but this does not prevent the problem, only makes it less prevalent. Have seen the other closed issues but none of them seem to present both messages at the same time.
Thank you for your awesome tool.
Output:
The text was updated successfully, but these errors were encountered: