Hi all,
I hope someone can help me with this issue. For a long time now, I have experienced an issue where after flashing a read protected program, J-link commander errors out trying to reset protection. To get around this, I have been using an ST-link debugger to reset the option bytes through another utility and then I can reconnect using the J-link debugger; however, this is pretty inconvenient as the ST-link debugger does not provide power so I have to use an alternate method for power the device.
I've attached the response from the command window in J-link commander. If anyone knows why the STM32G0 is having an issue resetting the options bytes, please let me know. It has no problem connecting when the read protection is disabled.
Also should note, I connect to the device over SWD using the recommended connections in the manual.
Thanks!
I hope someone can help me with this issue. For a long time now, I have experienced an issue where after flashing a read protected program, J-link commander errors out trying to reset protection. To get around this, I have been using an ST-link debugger to reset the option bytes through another utility and then I can reconnect using the J-link debugger; however, this is pretty inconvenient as the ST-link debugger does not provide power so I have to use an alternate method for power the device.
I've attached the response from the command window in J-link commander. If anyone knows why the STM32G0 is having an issue resetting the options bytes, please let me know. It has no problem connecting when the read protection is disabled.
Also should note, I connect to the device over SWD using the recommended connections in the manual.
Thanks!