Search Results
Search results 1-5 of 5.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
I close this thread as I found a solution for the issue. I am using the Cortex-M plugin in a docker container to connect to the GDB server running natively on my host. In order to "keep" the settings in the device I added the following to the launch.json (specific for the Cortex-M Plugin): "overrideLaunchCommands": [ "monitor reset 0", "dump memory ./settings.bin 0x000f8000 0x000fffff", "-target-download", "restore ./settings.bin binary 0x000f8000", "monitor reset 0" ], This dumps the settings a…
-
Ok, I am not getting it: According to the log in localhost:19080/flash.htm the area with persistent data is not touched at all... Where the heck is the stored data?
-
It might not be the solution for your setup, but I am using JLink GDB Server and RTT Viewer on the host and connect to the GDB Server on the host from within the docker container. The marked line in the launch.json shows the connection to the GDB server for downloading and debugging, RTT is done on the host side. Hope that helps. "configurations": [ { "type": "cortex-debug", "request": "launch", "servertype": "external", >> "gdbTarget": "host.docker.internal:2331", << "name": "Jlink", "device": …
-
Add "memory.region add ro 0x000f8000 0x2000" does not help... The persistent data is erased after the download. Received monitor command: exec memory.region add ro 0x000f8000 0x2000 Executed memory.region add ro 0x000f8000 0x2000 Received monitor command: reset 0 Resets core & peripherals via SYSRESETREQ & VECTRESET bit. Downloading 16128 bytes @ address 0x00000000 Downloading 11676 bytes @ address 0x00003F00 Downloading 16080 bytes @ address 0x00008000 Downloading 16112 bytes @ address 0x0000BE…
-
Hello, I am using the J-LINK GDB server V7.98a for downloading and debugging my firmware on a Nordic nrf9160. Recently I added a flash area for storing persistent data in the firmware. This data is located in the area 0x000f8000-0x000f9fff. When I download my full application, this persistent area gets erased. This is an excerpt of the log I see in the GDB server log (you can see my attempts to define which areas to erase and to enable the RWM feature): Received monitor command: exec erase 0x000…