Hello,
I am working on a custom board that uses the TI DRA74x SoC.
I have configured the scan chain to expose the A15 and IPU0 M4 cores; however I can only successfully debug the A15.
dra74x.JLinkScript.zip
I have attached the working A15 JlinkScript. Altering the last line to SetCore(2) exposes the M4.
The M4 is being correctly initialised by the A15 and is executing code when I try to connect and I can use the "mem" command in JLinkExe.
For some reason, JLink thinks that the core is not halted, yet the code is paused (display animation output halts).
Is there a step that I am missing to tell JLink about the M4 in order to debug it correctly?
Any help is much appreciated.
I get the following error when using GDB:
Display All
The debug output from JLinkExe:
Display All
I am working on a custom board that uses the TI DRA74x SoC.
I have configured the scan chain to expose the A15 and IPU0 M4 cores; however I can only successfully debug the A15.
dra74x.JLinkScript.zip
I have attached the working A15 JlinkScript. Altering the last line to SetCore(2) exposes the M4.
The M4 is being correctly initialised by the A15 and is executing code when I try to connect and I can use the "mem" command in JLinkExe.
For some reason, JLink thinks that the core is not halted, yet the code is paused (display animation output halts).
Is there a step that I am missing to tell JLink about the M4 in order to debug it correctly?
Any help is much appreciated.
I get the following error when using GDB:
Source Code
- $ JLinkGDBServer -ScriptFile dra74x.JLinkScript -device CORTEX-M4 -speed 8000
- SEGGER J-Link GDB Server V6.12a Command Line Version
- JLinkARM.dll V6.12a (DLL compiled Dec 2 2016 17:00:59)
- -----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: yes
- 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: dra74x.JLinkScript
- J-Link settings file: none
- ------Target related settings------
- Target device: CORTEX-M4
- Target interface: JTAG
- Target interface speed: 8000kHz
- Target endian: little
- Connecting to J-Link...
- J-Link is connected.
- Firmware: J-Link V9 compiled Dec 2 2016 15:35:20
- Hardware: V9.30
- S/N: 59305236
- Feature(s): GDB
- Checking target voltage...
- Target voltage: 3.38 V
- Listening on TCP/IP port 2331
- Connecting to target...
- J-Link found 4 JTAG devices, Total IRLen = 18
- JTAG ID: 0x4BA00477 (Cortex-M4)
- ERROR: Could not connect to target.
- Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
- Shutting down...
- Could not connect to target.
- Please check power, connection and settings.
The debug output from JLinkExe:
Source Code
- $ JLinkExe -JLinkScriptFile dra74x.JLinkScript -device CORTEX-M4 -speed 8000 -if jtag
- SEGGER J-Link Commander V6.12a (Compiled Dec 2 2016 17:01:07)
- DLL version V6.12a, compiled Dec 2 2016 17:00:59
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link V9 compiled Dec 2 2016 15:35:20
- Hardware version: V9.30
- S/N: 59305236
- License(s): GDB
- VTref = 3.380V
- Type "connect" to establish a target connection, '?' for help
- J-Link>con
- Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
- JTAGConf>
- Device "CORTEX-M4" selected.
- DRA74x J-Link script
- Could not measure total IR len. TDO is constant high.
- Selected M4 Core #0
- TotalIRLen = 18, IRPrint = 0x001111
- AP-IDR: 0x24770011, Type: AHB-AP
- Start searching for Cortex-M ROM table with ROMTable[0] @ 0xE00FF000.
- ROMTable[-317433376]: Cortex-M ROM table found.
- Found Cortex-M4 r0p1, Little endian.
- FPUnit: 6 code (BP) slots and 2 literal slots
- CoreSight components:
- ROMTbl 0 @ E00FF000
- ROMTbl 0 [0]: FFF0F000, CID: B105E00D, PID: 000BB000 SCS
- ROMTbl 0 [1]: FFF02000, CID: B105E00D, PID: 003BB002 DWT
- ROMTbl 0 [2]: FFF03000, CID: B105E00D, PID: 002BB003 FPB
- ROMTbl 0 [3]: FFF01000, CID: 00000000, PID: 00000000 ???
- ROMTbl 0 [4]: FFF41000, CID: 00000000, PID: 00000000 ???
- ROMTbl 0 [6]: FFF43000, CID: 00000000, PID: 00000000 ???
- Found 4 JTAG devices, Total IRLen = 18:
- #0 Id: 0x3BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
- #1 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
- #2 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
- #3 Id: 0x0B99002F, IRLen: 06, IRPrint: 0x1, TI ICEPick
- Cortex-M4 identified.
- J-Link>mem 0x48975500 0x10
- 48975500 = 00 00 00 00 0A A1 40 00 D0 02 80 07 00 00 00 00
- J-Link>h
- **************************
- WARNING: CPU could not be halted
- **************************
- J-Link>mem 0x48975500 0x10
- Could not read memory.
- J-Link>
The post was edited 1 time, last by richt123 ().