Hello,
I have a imx6ull evk and I would like to test the JTAG interface. Executing JLinkExe and starting JLinkGdbServer works fine.
Display All
Display All
My first aim is to load a u-boot image to the RAM and execute it.
Does anyone have a proper docu?
Thanks
I have a imx6ull evk and I would like to test the JTAG interface. Executing JLinkExe and starting JLinkGdbServer works fine.
Source Code
- SEGGER J-Link Commander V6.30k (Compiled Apr 9 2018 18:33:16)
- DLL version V6.30k, compiled Apr 9 2018 18:33:07
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link V10 compiled Mar 29 2018 17:45:34
- Hardware version: V10.10
- S/N: 50105141
- License(s): GDB
- VTref = 3.315V
- Type "connect" to establish a target connection, '?' for help
- J-Link>connect
- Please specify device / core. <Default>: MCIMX6Y2
- Type '?' for selection dialog
- Device>
- Please specify target interface:
- J) JTAG (Default)
- S) SWD
- TIF>
- Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
- JTAGConf>
- Specify target interface speed [kHz]. <Default>: 4000 kHz
- Speed>
- Device "MCIMX6Y2" selected.
- Connecting to target via JTAG
- J-Link script: Setting up AP map
- TotalIRLen = 13, IRPrint = 0x0101
- **************************
- WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
- **************************
- JTAG chain detection found 3 devices:
- #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
- #1 Id: 0x00000001, IRLen: 05, Unknown device
- #2 Id: 0x088C101D, IRLen: 04, JTAG-DP
- AP map detection skipped. Manually configured AP map found.
- AP[0]: AHB-AP (IDR: Not set)
- AP[1]: APB-AP (IDR: Not set)
- Using preconfigured AP[1] as APB-AP
- AP[1]: APB-AP found
- ROMTbl[0][0]: CompAddr: 80001000 CID: B105900D, PID:04-001BB961 TMC
- ROMTbl[0][1]: CompAddr: 80002000 CID: B105900D, PID:04-004BB906 CTI
- ROMTbl[0][2]: CompAddr: 80003000 CID: B105900D, PID:04-004BB912 TPIU
- ROMTbl[0][3]: CompAddr: 80004000 CID: B105F00D, PID:04-001BB101 TSG
- ROMTbl[0][4]: CompAddr: 80020000 CID: B105100D, PID:04-000BB4A7 ROM Table
- ROMTbl[1][0]: CompAddr: 80030000 CID: B105900D, PID:04-005BBC07 Cortex-A7
- Found Cortex-A7 r0p5
- 6 code breakpoints, 4 data breakpoints
- Debug architecture ARMv7.1
- Data endian: little
- Main ID register: 0x410FC075
- I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
- D-Cache L1: 32 KB, 128 Sets, 64 Bytes/Line, 4-Way
- Unified-Cache L2: 128 KB, 256 Sets, 64 Bytes/Line, 8-Way
- System control register:
- Instruction endian: little
- Level-1 instruction cache enabled
- Level-1 data cache disabled
- MMU disabled
- Branch prediction enabled
- Cortex-A7 identified.
- J-Link>
- Unknown command. '?' for help.
- J-Link>
Source Code
- SEGGER J-Link GDB Server V6.30k Command Line Version
- JLinkARM.dll V6.30k (DLL compiled Apr 9 2018 18:33:07)
- -----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: none
- J-Link settings file: none
- ------Target related settings------
- Target device: Unspecified
- Target interface: JTAG
- Target interface speed: 4000kHz
- Target endian: little
- Connecting to J-Link...
- J-Link is connected.
- Failed to set device (Unspecified). Unknown device selected?ERROR : Failed to set device.
- Firmware: J-Link V10 compiled Mar 29 2018 17:45:34
- Hardware: V10.10
- S/N: 50105141
- Feature(s): GDB
- Checking target voltage...
- Target voltage: 3.32 V
- Listening on TCP/IP port 2331
- Connecting to target...ERROR: No CPU core or target device has been selected. Please make sure at least the core J-Link shall connect to, is selected.
- 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.cb82lol@cb82lol:~$ JLinkGDBServer -device MCIMX6Y2
- SEGGER J-Link GDB Server V6.30k Command Line Version
- JLinkARM.dll V6.30k (DLL compiled Apr 9 2018 18:33:07)
- Command line: -device MCIMX6Y2
- -----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: none
- J-Link settings file: none
- ------Target related settings------
- Target device: MCIMX6Y2
- Target interface: JTAG
- Target interface speed: 4000kHz
- Target endian: little
- Connecting to J-Link...
- J-Link is connected.
- Firmware: J-Link V10 compiled Mar 29 2018 17:45:34
- Hardware: V10.10
- S/N: 50105141
- Feature(s): GDB
- Checking target voltage...
- Target voltage: 3.32 V
- Listening on TCP/IP port 2331
- Connecting to target...WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
- J-Link found 3 JTAG devices, Total IRLen = 13
- JTAG ID: 0x5BA00477 (Cortex-A7)
- Connected to target
- Waiting for GDB connection...
My first aim is to load a u-boot image to the RAM and execute it.
Does anyone have a proper docu?
Thanks