Cannot debug with LPC4330

Sysprogs forums Forums VisualGDB Cannot debug with LPC4330

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #8499
    Seidleroni
    Participant

    I’m just starting with Visual GDB and I am trying to debug using the Segger J-Link. When I run the debugger, I get the following in my GDB Server Log. What do I need to do to get this working with my project?

    —————————————

    SEGGER J-Link GDB Server V5.12h Command Line Version

    JLinkARM.dll V5.12h (DLL compiled Jun 29 2016 17:47:05)

    WARNING: Unknown command line parameter (SPIFI) found.
    —–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: LPC4330_M4
    Target interface: SWD
    Target interface speed: auto
    Target endian: little

    Connecting to J-Link…
    J-Link is connected.
    Firmware: J-Link LPC-Link 2 compiled Oct 6 2015 20:18:25
    Hardware: V1.00
    S/N: 611000000
    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
    WARNING: Failed to read memory @ address 0x00000F54
    WARNING: Failed to read memory @ address 0xFFFFFFFE
    Resetting target
    Downloading 276 bytes @ address 0x00000000
    Downloading 3972 bytes @ address 0x00000114
    Downloading 4 bytes @ address 0x00001098
    Downloading 4 bytes @ address 0x0000109C
    Writing register (PC = 0x00000db0)
    Read 2 bytes @ address 0x00000F54 (Data = 0xF7FF)
    Read 2 bytes @ address 0x00000F54 (Data = 0xF7FF)
    Read 2 bytes @ address 0x00000F54 (Data = 0xF7FF)
    Read 4 bytes @ address 0x00000DB0 (Data = 0x4C0D4D0C)
    Read 4 bytes @ address 0x1001FFFC (Data = 0x81000000)
    Downloading 4 bytes @ address 0x1001FFFC
    Reading all registers
    Read 4 bytes @ address 0x00000DB0 (Data = 0x4C0D4D0C)
    Read 4 bytes @ address 0x1001FFFC (Data = 0x42519CFD)
    Starting target CPU…
    …Target halted (DBGRQ, PC = 0xFFFFFFFE)
    Reading all registers
    WARNING: Failed to read memory @ address 0xFFFFFFFE
    WARNING: Failed to read memory @ address 0xFFFFFFFE
    WARNING: Failed to read memory @ address 0xFFFFFFFE
    Read 1 bytes @ address 0x00000000 (Data = 0x00)
    Reading 8192 bytes @ address 0x7FFFFFFF
    WARNING: Failed to read memory @ address 0x7FFFFFFF
    Reading 8192 bytes @ address 0x3FFFFFFF
    WARNING: Failed to read memory @ address 0x3FFFFFFF
    Reading 8192 bytes @ address 0x1FFFFFFF
    GDB closed TCP/IP connection

    #8500
    support
    Keymaster

    Hi,

    It looks like the J-Link software might be getting invalid readings from the chip. Have you checked with Segger whether this chip is officially supported? Perhaps you are missing some configuration option of the J-Link GDB stub?
    You can also try using OpenOCD instead. We can share our experimental script files for LPC4330 if this helps.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.