I am trying to set up a script for Jlink Commander to program STM32F051 parts. The script I have been using is:
device STM32F051C8
r
h
erase
Sleep 1000
r
h
loadfile "lccomp.hex"
Sleep 1000
r
g
Sleep 1000
qc
When it encounters a device that has already had read protection enabled, it brings up the 'Active read protected STM32 device detected' dialog box. Clicking 'Yes' in the dialog does correctly erase the whole part, however nothing beyond that point in the script works. Running the script one line at a time, I find that the dialog comes up as soon as the device STM32F051C8 line is executed. At this point the only way I have found to proceed with the device is to power it down and back up again, now the script works with the device as if it were a new blank device. For what its worth, running IAR embedded workbench to program the device and then start the debugger brings up the same dialog box, however it succeeds in programming the device and proceeds into the debugger when 'Yes' is clicked on in the dialog box. Have tried with a few recent versions and am currently on V5.02f. This script seems to work just fine on unprotected blank parts.
On an only partially related note, is there somewhere that the changes for the little sub versions such as going from 5.02e to 5.02f are documented? It seems that release notes on the web page are a bit behind what is being posted for download.
Gus
device STM32F051C8
r
h
erase
Sleep 1000
r
h
loadfile "lccomp.hex"
Sleep 1000
r
g
Sleep 1000
qc
When it encounters a device that has already had read protection enabled, it brings up the 'Active read protected STM32 device detected' dialog box. Clicking 'Yes' in the dialog does correctly erase the whole part, however nothing beyond that point in the script works. Running the script one line at a time, I find that the dialog comes up as soon as the device STM32F051C8 line is executed. At this point the only way I have found to proceed with the device is to power it down and back up again, now the script works with the device as if it were a new blank device. For what its worth, running IAR embedded workbench to program the device and then start the debugger brings up the same dialog box, however it succeeds in programming the device and proceeds into the debugger when 'Yes' is clicked on in the dialog box. Have tried with a few recent versions and am currently on V5.02f. This script seems to work just fine on unprotected blank parts.
On an only partially related note, is there somewhere that the changes for the little sub versions such as going from 5.02e to 5.02f are documented? It seems that release notes on the web page are a bit behind what is being posted for download.
Gus