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, every now and then we have the problem that when the debugger is started, it does not jump into the main routine and stops there. Together with this problem, the error message that the readout protection is activated, comes up every now and then. We don't know why the readout protection should be activated. We don't use this feature. For a first test we want to disable the readout protection in the GDB startup script. This is the actual startup script. Source Code (37 lines) How can I unlock…
-
It works. Thank you for the link. Thank you Alex.
-
Windows 7 Atollic 9.3 Debug hardware: j-link ULTRA+ GDB: V680c JLinkGDBServerCL.exe Micro controller: STM32F091RC If we delete the flash with the command "FlashStatus = FLASH_ErasePage( address )" the flash in this page should be 0xFF. But the whole flash content is not updated in the memory browser. I have tried it with other versions of the JLinkGDBServerCL.exe with no success. If I make the same procedure with the ST-Link/V2 is works perfectly. I would be grateful for any hint.