2011-05-08 10:31 PM
STM32 ST-LINK v1 problem in IAR EWARM v5.50.x-v6.x
2011-05-17 05:34 AM
I'd suggest you take this up with your support representative at IAR, that's why they have support contracts.
If you've tried the most current ST-LINK firmware, and drivers/dlls, and SWD/JTAG modes, you will have pretty much exhausted the software troubleshooting paths. They will no doubt tell you to try a J-Link JTAG pod. If that doesn't work, look at your hardware.2011-05-17 05:34 AM
Have you succeeded in this issue?
2011-05-17 05:34 AM
Hello,
I have the same problem... Where could I findEWARM v5.41.2-the kickstart version ?
Thank you!2011-05-17 05:34 AM
Not yet. IAR support team won't help. ST-LINK v1 cannot program STM32 in EWARM v6.20.2 also. This is a hard problem, v5.41.2 is very old release...
If needed, I can share v5.41.2 kickstart edition (32K code limited).2011-05-17 05:34 AM
I found a workaround for this... it's not verry elegant, but it works for me...
Step1.
In IAR EWARM project Options->Output Converter :
- generate aditional output (ENABLED)
- output format : binary.
This way, a raw binary is generated when make command is called.
Step2.
You write the generated bin file with the ST-link utility.
Step3.
Going back to the IAR EWARM you launch Download and Debug and everything goes well( of course if you modify anything inside the code you have to go back to step 2).
Hope this is OK for you... until IAR does something about this...
2011-05-17 05:34 AM
The other way is to use command line interface of ST-LINK utility v2.0 and add some commands to IAR Tools/Configure Tools menu.
To program chip: ST-LINK_CLI.exe -P ''ProjName.hex'' To reset chip: ST-LINK_CLI.exe -Rst Once added, we can assign a keyboard shortcut to this new commands and it's a bit convenient to work. But generally, it's good idea to moving to the JetLink Ultra. It's looking like ST-LINK v1 now discontinued and cannot be supported. P.S. ST-LINK v1 also not working in KEIL v4.20. I tested it some days ago...