about secure jtag for 1176

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

about secure jtag for 1176

Jump to solution
938 Views
hhh
Contributor III

i am working on an custom board of i.mx1176, from an13133 i burned the fuse and using the jlink script , from command line i connect to the mcu without any problem. but when i use the mcuxpresso, it does not seem i can use jtag to download my code.  in the jlink script already specified the script i used in command line. is there any  one knows why?

 

thanks.

0 Kudos
1 Solution
897 Views
hhh
Contributor III

we found out issue.

there is monitor reset in startup. after remove that, everything went well.

 

View solution in original post

0 Kudos
7 Replies
898 Views
hhh
Contributor III

we found out issue.

there is monitor reset in startup. after remove that, everything went well.

 

0 Kudos
823 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @hhh ,

  Which detail part you remove, do you mean this part?

kerryzhou_0-1685089829137.png

 

  Thanks for your experience sharing.

 

Best Regards,

Kerry

 

0 Kudos
812 Views
hhh
Contributor III

here is the place i remove monitor resetmonitor_reset.png

897 Views
hhh
Contributor III

[10-5-2023 12:09:10] Executing Server: "C:\Program Files\SEGGER\JLink\JLinkGDBServerCL.exe" -SettingsFile "C:\Users\eric\Documents\MCUXpressoIDE_11.7.1_9221\workspace\evkmimxrt1170_flashloader_cm7\Debug\evkmimxrt1170_flashloader_cm7 JLink Debug SettingsFile.jlink" -nosilent -swoport 2332 -select USB=XXXXXXXX -jlinkscriptfile D:\FM01\NXP_RT1170_SecureJTAG.JlinkScript -telnetport 2333 -singlerun -endian little -noir -speed 50 -port 2331 -vd -device MIMXRT1176xxxA_M7 -if JTAG -halt -reportuseraction
SEGGER J-Link GDB Server V7.86e Command Line Version

JLinkARM.dll V7.86e (DLL compiled Mar 22 2023 16:27:41)

Command line: -SettingsFile C:\Users\eric\Documents\MCUXpressoIDE_11.7.1_9221\workspace\evkmimxrt1170_flashloader_cm7\Debug\evkmimxrt1170_flashloader_cm7 JLink Debug SettingsFile.jlink -nosilent -swoport 2332 -select USB=XXXXXXXX -jlinkscriptfile D:\FM01\NXP_RT1170_SecureJTAG.JlinkScript -telnetport 2333 -singlerun -endian little -noir -speed 50 -port 2331 -vd -device MIMXRT1176xxxA_M7 -if JTAG -halt -reportuseraction
-----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: on
Init regs on start: off
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: D:\FM01\NXP_RT1170_SecureJTAG.JlinkScript
J-Link settings file: C:\Users\eric\Documents\MCUXpressoIDE_11.7.1_9221\workspace\evkmimxrt1170_flashloader_cm7\Debug\evkmimxrt1170_flashloader_cm7 JLink Debug SettingsFile.jlink
------Target related settings------
Target device: MIMXRT1176xxxA_M7
Target device parameters: none
Target interface: JTAG
Target interface speed: 50kHz
Target endian: little

Connecting to J-Link...
J-Link is connected.
Device "MIMXRT1176XXXA_M7" selected.
Firmware: J-Link Pro V5-1 compiled Mar 15 2023 11:22:04
Hardware: V5.10
S/N: 175102228
Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
Checking target voltage...
Target voltage: 2.54 V
Listening on TCP/IP port 2331
Connecting to target...
InitTarget() start
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
#0 Id: 0x088C601D, IRLen: 04, JTAG-DP
Challenge UUID0:0x828F2C4F
Challenge UUID1:0x260D480E
InitTarget() end - Took 128ms
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
#0 Id: 0x088C601D, IRLen: 04, JTAG-DP
DPv0 detected
Scanning AP map to find all available APs
AP[3]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x84770001)
AP[1]: AHB-AP (IDR: 0x24770011)
AP[2]: APB-AP (IDR: 0x54770002)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FD000
CPUID register: 0x411FC272. Implementer code: 0x41 (ARM)
Cache: L1 I/D-cache present

Found Cortex-M7 r1p2, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ E00FD000
[0][0]: E00FE000 CID B105100D PID 000BB4C8 ROM Table
ROMTbl[1] @ E00FE000
[1][0]: E00FF000 CID B105100D PID 000BB4C7 ROM Table
ROMTbl[2] @ E00FF000
[2][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[2][1]: E0001000 CID B105E00D PID 000BB002 DWT
[2][2]: E0002000 CID B105E00D PID 000BB00E FPB-M7
[2][3]: E0000000 CID B105E00D PID 000BB001 ITM
[1][1]: E0041000 CID B105900D PID 001BB975 ETM-M7
[1][2]: E0042000 CID B105900D PID 004BB906 CTI
[0][1]: E0043000 CID B105900D PID 001BB908 CSTF
I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way

J-Link found 1 JTAG device, Total IRLen = 4
JTAG ID: 0x088C601D (Cortex-M7)
Halting core...
Connected to target
Waiting for GDB connection...Connected to 0000:0000:0000:0000:0000:0000:0000:0001
GDB client (conn. 832) requested target.xml from GDB Server
Reading common registers: Read register 'r0' (4 bytes) from hardware: 0xB0C0CA40
Read register 'r1' (4 bytes) from hardware: 0x0000000A
Read register 'r2' (4 bytes) from hardware: 0x00000080
Read register 'r3' (4 bytes) from hardware: 0x00F00000
Read register 'r4' (4 bytes) from hardware: 0x00ED00E0
Read register 'r5' (4 bytes) from hardware: 0x6D942200
Read register 'r6' (4 bytes) from hardware: 0xCD401600
Read register 'r7' (4 bytes) from hardware: 0xC87D2000
Read register 'r8' (4 bytes) from hardware: 0x80AE2420
Read register 'r9' (4 bytes) from hardware: 0x84AE2420
Read register 'r10' (4 bytes) from hardware: 0x0C1C2100
Read register 'r11' (4 bytes) from hardware: 0x33000000
Read register 'r12' (4 bytes) from hardware: 0x00000000
Read register 'sp' (4 bytes) from hardware: 0x981D2420
Read register 'lr' (4 bytes) from hardware: 0xF3152000
Read register 'pc' (4 bytes) from hardware: 0x04312200
Read register 'xpsr' (4 bytes) from hardware: 0x00000081
Read 4 bytes @ address 0x00223104 (Data = 0xF7DEE7FE)
Read 2 bytes @ address 0x00223104 (Data = 0xE7FE)
Connected to 0000:0000:0000:0000:0000:0000:0000:0001
GDB client (conn. 1052) requested target.xml from GDB Server
Reading common registers: Read register 'r0' (4 bytes) from hardware: 0xB0C0CA40
Read register 'r1' (4 bytes) from hardware: 0x0000000A
Read register 'r2' (4 bytes) from hardware: 0x00000080
Read register 'r3' (4 bytes) from hardware: 0x00F00000
Read register 'r4' (4 bytes) from hardware: 0x00ED00E0
Read register 'r5' (4 bytes) from hardware: 0x6D942200
Read register 'r6' (4 bytes) from hardware: 0xCD401600
Read register 'r7' (4 bytes) from hardware: 0xC87D2000
Read register 'r8' (4 bytes) from hardware: 0x80AE2420
Read register 'r9' (4 bytes) from hardware: 0x84AE2420
Read register 'r10' (4 bytes) from hardware: 0x0C1C2100
Read register 'r11' (4 bytes) from hardware: 0x33000000
Read register 'r12' (4 bytes) from hardware: 0x00000000
Read register 'sp' (4 bytes) from hardware: 0x981D2420
Read register 'lr' (4 bytes) from hardware: 0xF3152000
Read register 'pc' (4 bytes) from hardware: 0x04312200
Read register 'xpsr' (4 bytes) from hardware: 0x00000081
Read 4 bytes @ address 0x00223104 (Data = 0xF7DEE7FE)
Read 2 bytes @ address 0x00223104 (Data = 0xE7FE)
Received monitor command: reset
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Reset: SYSRESETREQ has confused core.
DPv0 detected
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0x00
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
Reset: Using fallback: VECTRESET.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.VECTRESET.
Reset: VECTRESET has confused core.
DPv0 detected
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0x00
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
Reset: Using fallback: Reset pin.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
Reset: Reconnecting and manually halting CPU.
DPv0 detected
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0x00
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
CPU could not be halted
Reset: Core did not halt after reset, trying to disable WDT.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
Reset: Reconnecting and manually halting CPU.
DPv0 detected
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24]

0 Kudos
900 Views
hhh
Contributor III

jlinksetting.pngjlinkdebug.pngjlinkdebug1.png

0 Kudos
900 Views
hhh
Contributor III

jtagsecure.pngcommand line.png

this is the command line i use to connect with jlink tool.

0 Kudos
919 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @hhh ,

  Thank you for your interest in the NXP MIMXRT product, I would like to provide service for you.

  1. Please share your JLINK Script connection result which is correct

  2. Please also share me your mcuxpresso related log, do you already add the secure jlink script to the mcuxpresso JLINK debugger, please share some debug result pictures and the log, thanks.

 

Best Regards,

Kerry

0 Kudos