Dear community,
I'm trying to debug my Amlogic A113X SoC using JLink v10.1 adapter via JTAG. This is quad Cortex-A53 SoC. This is what I get in JLinkExe under Linux:
Display All
It says "Specific core setup failed". I had another output some time ago (did not change anything in my debug setup):
Display All
Now it says "EDSCR[HDE]: Cannot enable halting debug mode" and missing CPU features list.
Looks like it can read registers but cannot execute commands, like "halt" command.
I have prepared device to JTAG debug using SoC vendor instructions. I cannot understand what's going on - is it incomplete vendor's instructions, faulty connection or what? Please help me figure this out.
JLink adapter firmware is up to date.
I'm trying to debug my Amlogic A113X SoC using JLink v10.1 adapter via JTAG. This is quad Cortex-A53 SoC. This is what I get in JLinkExe under Linux:
Source Code
- SEGGER J-Link Commander V7.62a (Compiled Feb 23 2022 17:02:50)
- DLL version V7.62a, compiled Feb 23 2022 17:02:35
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link V10 compiled Nov 2 2021 12:14:50
- Hardware version: V10.10
- S/N: 50125191
- License(s): GDB
- VTref=3.300V (fixed)
- Type "connect" to establish a target connection, '?' for help
- J-Link>connect
- Please specify device / core. <Default>: CORTEX-A53
- Type '?' for selection dialog
- Device>
- Please specify target interface:
- J) JTAG (Default)
- S) SWD
- T) cJTAG
- TIF>
- Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
- JTAGConf>
- Specify target interface speed [kHz]. <Default>: 4000 kHz
- Speed>
- Device "CORTEX-A53" selected.
- Connecting to target via JTAG
- TotalIRLen = 4, IRPrint = 0x01
- JTAG chain detection found 1 devices:
- #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
- DPv0 detected
- Scanning AP map to find all available APs
- AP[1]: Stopped AP scan as end of AP map has been reached
- AP[0]: APB-AP (IDR: 0x44770002)
- Iterating through AP map to find APB-AP to use
- AP[0]: APB-AP found
- Scanning ROMTbl @ 0x80000000
- [0]Comp[0] @ 0x00000000: ROM Table
- Scanning ROMTbl @ 0x00000000
- [1]Comp[0] @ 0x00001000: CSTF
- [1]Comp[1] @ 0x00002000: TPIU
- [1]Comp[2] @ 0x00003000: ETB
- [1]Comp[3] @ 0x00004000: ATBR
- [1]Comp[4] @ 0x00005000: CTI
- [1]Comp[5] @ 0x00006000: TSG
- [1]Comp[6] @ 0x00400000: ROM Table
- Scanning ROMTbl @ 0x00400000
- [2]Comp[0] @ 0x00410000: Cortex-A53
- [2]Comp[1] @ 0x00420000: CSS600-CTI
- Core found. Stopped ROM table scan: https://wiki.segger.com/ROMTableScan
- Cortex-A53 @ 0x00410000 (detected)
- CoreCTI @ 0x00420000 (detected)
- Debug architecture: ARMv8
- 6 code breakpoints, 4 data breakpoints
- Processor features:
- EL0 support: AArch64 + AArch32
- EL1 support: AArch64 + AArch32
- EL2 support: AArch64 + AArch32
- EL3 support: AArch64 + AArch32
- FPU support: Single + Double + Conversion
- Add. info (CPU temp. halted)
- CPU could not be halted
- Failed to temporarily halt CPU
- TotalIRLen = 4, IRPrint = 0x01
- JTAG chain detection found 1 devices:
- #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
- DPv0 detected
- Scanning AP map to find all available APs
- AP[1]: Stopped AP scan as end of AP map has been reached
- AP[0]: APB-AP (IDR: 0x44770002)
- Iterating through AP map to find APB-AP to use
- AP[0]: APB-AP found
- Scanning ROMTbl @ 0x80000000
- [0]Comp[0] @ 0x00000000: ROM Table
- Scanning ROMTbl @ 0x00000000
- [1]Comp[0] @ 0x00001000: CSTF
- [1]Comp[1] @ 0x00002000: TPIU
- [1]Comp[2] @ 0x00003000: ETB
- [1]Comp[3] @ 0x00004000: ATBR
- [1]Comp[4] @ 0x00005000: CTI
- [1]Comp[5] @ 0x00006000: TSG
- [1]Comp[6] @ 0x00400000: ROM Table
- Scanning ROMTbl @ 0x00400000
- [2]Comp[0] @ 0x00410000: Cortex-A53
- [2]Comp[1] @ 0x00420000: CSS600-CTI
- Core found. Stopped ROM table scan: https://wiki.segger.com/ROMTableScan
- Cortex-A53 @ 0x00410000 (detected)
- CoreCTI @ 0x00420000 (detected)
- Debug architecture: ARMv8
- 6 code breakpoints, 4 data breakpoints
- Processor features:
- EL0 support: AArch64 + AArch32
- EL1 support: AArch64 + AArch32
- EL2 support: AArch64 + AArch32
- EL3 support: AArch64 + AArch32
- FPU support: Single + Double + Conversion
- Add. info (CPU temp. halted)
- CPU could not be halted
- Failed to temporarily halt CPU
- ****** Error: Specific core setup failed.
- Cannot connect to target.
- J-Link>
It says "Specific core setup failed". I had another output some time ago (did not change anything in my debug setup):
Source Code
- SEGGER J-Link Commander V7.62a (Compiled Feb 23 2022 17:02:50)
- DLL version V7.62a, compiled Feb 23 2022 17:02:35
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link V10 compiled Nov 2 2021 12:14:50
- Hardware version: V10.10
- S/N: 50125191
- License(s): GDB
- VTref=3.300V (fixed)
- Type "connect" to establish a target connection, '?' for help
- J-Link>connect
- Please specify device / core. <Default>: CORTEX-A53
- Type '?' for selection dialog
- Device>
- Please specify target interface:
- J) JTAG (Default)
- S) SWD
- T) cJTAG
- TIF>
- Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
- JTAGConf>
- Specify target interface speed [kHz]. <Default>: 4000 kHz
- Speed>
- Device "CORTEX-A53" selected.
- Connecting to target via JTAG
- TotalIRLen = 4, IRPrint = 0x01
- JTAG chain detection found 1 devices:
- #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
- DPv0 detected
- Scanning AP map to find all available APs
- AP[1]: Stopped AP scan as end of AP map has been reached
- AP[0]: APB-AP (IDR: 0x44770002)
- Iterating through AP map to find APB-AP to use
- AP[0]: APB-AP found
- Scanning ROMTbl @ 0x80000000
- [0]Comp[0] @ 0x00000000: ROM Table
- Scanning ROMTbl @ 0x00000000
- [1]Comp[0] @ 0x00001000: CSTF
- [1]Comp[1] @ 0x00002000: TPIU
- [1]Comp[2] @ 0x00003000: ETB
- [1]Comp[3] @ 0x00004000: ATBR
- [1]Comp[4] @ 0x00005000: CTI
- [1]Comp[5] @ 0x00006000: TSG
- [1]Comp[6] @ 0x00400000: ROM Table
- Scanning ROMTbl @ 0x00400000
- [2]Comp[0] @ 0x00410000: Cortex-A53
- [2]Comp[1] @ 0x00420000: CSS600-CTI
- Core found. Stopped ROM table scan: https://wiki.segger.com/ROMTableScan
- Cortex-A53 @ 0x00410000 (detected)
- CoreCTI @ 0x00420000 (detected)
- Debug architecture: ARMv8
- 6 code breakpoints, 4 data breakpoints
- Add. info (CPU temp. halted)
- CPU could not be halted
- Failed to temporarily halt CPU
- TotalIRLen = 4, IRPrint = 0x01
- JTAG chain detection found 1 devices:
- #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
- DPv0 detected
- Scanning AP map to find all available APs
- AP[1]: Stopped AP scan as end of AP map has been reached
- AP[0]: APB-AP (IDR: 0x44770002)
- Iterating through AP map to find APB-AP to use
- AP[0]: APB-AP found
- Scanning ROMTbl @ 0x80000000
- [0]Comp[0] @ 0x00000000: ROM Table
- Scanning ROMTbl @ 0x00000000
- [1]Comp[0] @ 0x00001000: CSTF
- [1]Comp[1] @ 0x00002000: TPIU
- [1]Comp[2] @ 0x00003000: ETB
- [1]Comp[3] @ 0x00004000: ATBR
- [1]Comp[4] @ 0x00005000: CTI
- [1]Comp[5] @ 0x00006000: TSG
- [1]Comp[6] @ 0x00400000: ROM Table
- Scanning ROMTbl @ 0x00400000
- [2]Comp[0] @ 0x00410000: Cortex-A53
- [2]Comp[1] @ 0x00420000: CSS600-CTI
- Core found. Stopped ROM table scan: https://wiki.segger.com/ROMTableScan
- Cortex-A53 @ 0x00410000 (detected)
- CoreCTI @ 0x00420000 (detected)
- Debug architecture: ARMv8
- 6 code breakpoints, 4 data breakpoints
- Add. info (CPU temp. halted)
- CPU could not be halted
- Failed to temporarily halt CPU
- ****** Error: EDSCR[HDE]: Cannot enable halting debug mode
- Specific core setup failed.
- Cannot connect to target.
Now it says "EDSCR[HDE]: Cannot enable halting debug mode" and missing CPU features list.
Looks like it can read registers but cannot execute commands, like "halt" command.
I have prepared device to JTAG debug using SoC vendor instructions. I cannot understand what's going on - is it incomplete vendor's instructions, faulty connection or what? Please help me figure this out.
JLink adapter firmware is up to date.