Search Results

Search results 1-3 of 3.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Hi Fabian Quick update: I tried different configurations of option bytes - all without success. JLink persistenly consideres this device as 'write protected' even though it is not. As recommended, I tried the JLink tools on Win 10 and they ask me if I want to unlock the device. If I answer no, I can still program the device -> So its a bug in JLink? Btw: On Win 10 the RTT Viewer works if I tell it _not_ to unlock the device. I consider it a bug in your Linux software that you do not provide this…

  • Hi Fabian Thank's for the quick reply! Ok, I tried pulling the BOOT0 pin high without success, but it might actually be disabled per default. I'll look into that. It's custom hardware and I don't have a demo board at hand to see if it happens there as well, but I guess it does. The hex file of my software is attached. BR, Lukas

  • 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 …