Cannot debug after upgrading to JLink software 5.10q

Sysprogs forums › Forums › VisualGDB › Cannot debug after upgrading to JLink software 5.10q

Log In Register Lost Password
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • March 8, 2016 at 23:08 #7739
    mlower
    Participant

    After upgrade to JLink software 5.10q I cannot start debug session using VisualGDB. After successfully programming my nRF51822 VisualGDB halts without any error message. It looks like a breakpoint but I’m unable to hit “continue”. The same program can be debugged in Keil without any problems Below please find attached JLink logs from “JLinkGDBServerCL” window.

     

    SEGGER J-Link GDB Server V5.10q Command Line Version

    JLinkARM.dll V5.10q (DLL compiled Mar 4 2016 16:03:41)

    —–GDB Server start settings—–
    GDBInit file: none
    GDB Server Listening port: 2331
    SWO raw output listening port: 2332
    Terminal I/O port: 2333
    Accept remote connection: localhost only
    Generate logfile: off
    Verify download: off
    Init regs on start: off
    Silent mode: off
    Single run mode: off
    Target connection timeout: 0 ms
    ——J-Link related settings——
    J-Link Host interface: USB
    J-Link script: none
    J-Link settings file: none
    ——Target related settings——
    Target device: nRF51822_XXAC
    Target interface: SWD
    Target interface speed: auto
    Target endian: little

    Connecting to J-Link…
    J-Link is connected.
    Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 8 2016 11:17:15
    Hardware: V1.00
    S/N: 681310085
    Checking target voltage…
    Target voltage: 3.30 V
    Listening on TCP/IP port 2331
    Connecting to target…Connected to target
    Waiting for GDB connection…Connected to 127.0.0.1
    Reading all registers
    Read 2 bytes @ address 0x000223CC (Data = 0xA805)
    Read 4 bytes @ address 0x0001C110 (Data = 0xE7FEE7FE)
    Read 2 bytes @ address 0x0001C10C (Data = 0x4700)
    Resetting target
    Downloading 4096 bytes @ address 0x00000000
    Downloading 4096 bytes @ address 0x00001000
    Downloading 4096 bytes @ address 0x00002000
    Downloading 4096 bytes @ address 0x00003000
    Downloading 4096 bytes @ address 0x00004000
    Downloading 4096 bytes @ address 0x00005000
    Downloading 4096 bytes @ address 0x00006000
    Downloading 4096 bytes @ address 0x00007000
    Downloading 4096 bytes @ address 0x00008000
    Downloading 4096 bytes @ address 0x00009000
    Downloading 4096 bytes @ address 0x0000A000
    Downloading 4096 bytes @ address 0x0000B000
    Downloading 4096 bytes @ address 0x0000C000
    Downloading 4096 bytes @ address 0x0000D000
    Downloading 4096 bytes @ address 0x0000E000
    Downloading 4096 bytes @ address 0x0000F000
    Downloading 4096 bytes @ address 0x00010000
    Downloading 4096 bytes @ address 0x00011000
    Downloading 4096 bytes @ address 0x00012000
    Downloading 4096 bytes @ address 0x00013000
    Downloading 4096 bytes @ address 0x00014000
    Downloading 4096 bytes @ address 0x00015000
    Downloading 4096 bytes @ address 0x00016000
    Downloading 4096 bytes @ address 0x00017000
    Downloading 4096 bytes @ address 0x00018000
    Downloading 4096 bytes @ address 0x00019000
    Downloading 4096 bytes @ address 0x0001A000
    Downloading 4096 bytes @ address 0x0001B000
    Downloading 192 bytes @ address 0x0001C000
    Downloading 4096 bytes @ address 0x0001C0C0
    Downloading 4096 bytes @ address 0x0001D0C0
    Downloading 4096 bytes @ address 0x0001E0C0
    Downloading 4096 bytes @ address 0x0001F0C0
    Downloading 4096 bytes @ address 0x000200C0
    Downloading 4096 bytes @ address 0x000210C0
    Downloading 4096 bytes @ address 0x000220C0
    Downloading 1016 bytes @ address 0x000230C0
    Downloading 8 bytes @ address 0x000234B8
    Downloading 4 bytes @ address 0x000234C0
    Downloading 4 bytes @ address 0x000234C4
    Downloading 8 bytes @ address 0x000234C8
    Writing register (PC = 0x00021a00)
    Read 2 bytes @ address 0x000223CC (Data = 0xB510)
    Read 4 bytes @ address 0x00021A00 (Data = 0x68024812)
    Resetting target
    Read 2 bytes @ address 0x000223D0 (Data = 0xF7FF)
    Read 2 bytes @ address 0x000223D0 (Data = 0xF7FF)
    Read 4 bytes @ address 0x20007FFC (Data = 0x00021A35)
    Downloading 4 bytes @ address 0x20007FFC
    Reading all registers
    Read 4 bytes @ address 0x000006D0 (Data = 0x4C174916)
    Read 2 bytes @ address 0x000006D0 (Data = 0x4916)
    Read 4 bytes @ address 0xFFFFFFFF (Data = 0x4C174916)
    Read 2 bytes @ address 0xFFFFFFFF (Data = 0x4916)
    Read 4 bytes @ address 0xFFFFFFFF (Data = 0x4C174916)
    Read 2 bytes @ address 0xFFFFFFFF (Data = 0x4916)
    Read 4 bytes @ address 0x20007FFC (Data = 0x0A91D9CD)
    Setting breakpoint @ address 0x000223CC, Size = 2, BPHandle = 0x0001
    Setting breakpoint @ address 0x000223D0, Size = 2, BPHandle = 0x0002
    Starting target CPU…
    …Breakpoint reached @ address 0x000223CC

    March 11, 2016 at 19:28 #7755
    support
    Keymaster

    Hi,

    We have just retested it with the latest Segger J-Link v5.10s and could not find any problem.

    We have tested the LEDBlink (BSP) project and tried stepping through the main() function and setting breakpoints – everything worked as expected.

    On the first run the J-Link server prompted to update the firmware and we did that. Could you please verify that the problem still exists with 5.10s and after the firmware update?

    March 12, 2016 at 10:38 #7765
    mlower
    Participant

    Version 5.10s works. Firmware update crashes Visual Studio but this happens only once so it’s not a big problem.

    March 13, 2016 at 19:08 #7767
    support
    Keymaster

    Wow, strange. It did not crash on our side. If anyone else can confirm the crash, please send us dump file and we’ll gladly fix it.

  • Author
    Posts
Log In Register Lost Password
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.