Dear Segger Community
I'm using a JLink Pro to flash a STM32G031G8 device via SWD with JLinkExe under Ubuntu. Downloading works and the software starts _after a power cycle_. Resetting the MCU, either by issuing the 'r' command or by pulling the RESETn pin low does not start the program. After a power cycle, the RESETn pin works as expected.
This is not ideal, but I can life with it.
However, note that the JLink recognizes this device as 'active write protected' and performs a device erase when connecting to it. This is a problem for RTT: When I connect the RTT-Viewer it also erases the device. (See screen shot). This prevents me from using RTT, which is a problem for me.
Any ideas why this device appears as protected? Using JLinkExe's 'mem' command check the Option Bytes of the STM32 shows them in their default state, which is not locked.
Best Regards,
Lukas
I'm using a JLink Pro to flash a STM32G031G8 device via SWD with JLinkExe under Ubuntu. Downloading works and the software starts _after a power cycle_. Resetting the MCU, either by issuing the 'r' command or by pulling the RESETn pin low does not start the program. After a power cycle, the RESETn pin works as expected.
This is not ideal, but I can life with it.
However, note that the JLink recognizes this device as 'active write protected' and performs a device erase when connecting to it. This is a problem for RTT: When I connect the RTT-Viewer it also erases the device. (See screen shot). This prevents me from using RTT, which is a problem for me.
Any ideas why this device appears as protected? Using JLinkExe's 'mem' command check the Option Bytes of the STM32 shows them in their default state, which is not locked.
Best Regards,
Lukas
The post was edited 1 time, last by ls_technokrat ().