2019-06-03 06:23 AM
Hey guys,
i'm currently struggeling with the STM32 CLI to programm my MCU.
For my (old) STM32F103 i did setup a script wich worked nicely. Going through the documentation a came uo with
ST-LINK_CLI.exe -c SN=xxxxxx SWD UR -TVolt -ME -P ../my_firmware.hex -V -Rst
(See Section 4)
However when i tried to use the same cmommand to flash my STM32F4 it does not work.
The error is
My gues is that the CLI is still looking for the old STM32F103 device. However there's no option to change the MCU type. Could you help me out, do you have any idea how to fix this?
Solved! Go to Solution.
2019-06-03 08:45 AM
Try updating the ST-LINK to the latest version (4.4.0.0). It might recognize newer devices.
2019-06-03 08:22 AM
The error message is not shown on you post. Would you be able to add it again?
Did you try using the JTAG instead of the SWD?
Did you try using the STM32 ST-LINK utility? You might get a more descriptive error message.
2019-06-03 08:41 AM
Sorry my bad. I thought i copied the error into my question:
Here it goes:
When i excecute this cmd the MCU is restarted. So "connect under reset" seams to work.
I did try the same using ST Link. The ST Link tool works fine
Output looks pretty much the same to be, except one is working and the other not. :(
As you said, i tried JTAG (with STM32 Link Utility) but this did not work. I'm not sure if SWD and JTAG are hardware compatible though ?!
2019-06-03 08:45 AM
Try updating the ST-LINK to the latest version (4.4.0.0). It might recognize newer devices.
2019-06-04 01:44 AM
Thx that was indeed the right answer. After upgrading mit ST Link CLI the device was found.
Just FYI:
After that i had to face 2 additional problems
Thx for your fast help :)