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.
-
Submitted as a ticket: Inquiry#60145122
-
Just to show you that this problem is intermittent, I tried again this morning, with the same board, same everything, just restarting JLinkGDBServer and arm-non-eabi-gdb, and it's currently working, so somehow it gets into a bad state: (gdb) x 0x8888 0x8888: 0xffffffff (gdb) set *0x8888 = 0x12345678 (gdb) x 0x8888 0x8888: 0x12345678 (gdb) x 0x2000 0x2000: 0xffffffff (gdb) set *0x2000 = 0x1234 (gdb) x 0x2000 0x2000: 0x00001234
-
I have been having trouble in the past few weeks using JLInkGDBServer, in which it appears to write to flash memory on a SAMD21G18, but the writes don't actually happen. Example A: (gdb) set *0x2000 = 0x1234 (gdb) x 0x2000 0x2000: 0xffffffff # write did not happen?! JLinkGDBServer output: Downloading 4 bytes @ address 0x00002000 Reading all registers Read 4 bytes @ address 0x00000288 (Data = 0x49214820) # (this is the PC location, not important to this example) Read 2 bytes @ address 0x00000288 …
-
Apologies: I thought this was the official support channel. I have resubmitted this via the contact form at segger.com/about-us/contact-us.
-
I upgraded from JLink V6.30i to V6.32, and JLInkGDBServer no longer communicates properly with arm-none-eabi-gdb. (OS is Ubuntu 16.04.4 LTS 64-bit). JLinkGDBServer starts up fine: $ JLinkGDBServer -device ATSAMD51J19 -if SWD SEGGER J-Link GDB Server V6.32 Command Line Version JLinkARM.dll V6.32 (DLL compiled Apr 20 2018 17:34:47) Command line: -device ATSAMD51J19 -if SWD -----GDB Server start settings----- GDBInit file: none GDB Server Listening port: 2331 SWO raw output listening port: 2332 Ter…