MCUXpresso IDE can't find CMSIS-DAP probe

[longxing]

MCUXpresso IDE can't find my CMSIS-DAP probe.My MCUXpresso IDE version is:MCUXpresso IDE v11.5.1 [Build 7266] [2022-04-13] and running on WINDOWS 10.

but the J-link command can find my CMSIS-DAP probe,thougth it can't download my program.

These two problems bother me for weeks,I can do nothing with my evaluation board an CMSIS-DAP.

Is any solution to finding no compatiable probe problem?

[Alice_Yang]

Hello ,

Is your board custom board? How about have a look at this thread:

https://community.nxp.com/t5/i-MX-RT/J-Link-fail-to-erase-or-program-RT1052-and-VTref-only-2-608V/m-...   

BR

Alice

[longxing]

Hi 

Alice

I do use a custom board,and it was bought from a third-party vender.The vref is 3.3V as you can see from the console log I posted last time.Also I use SWD interface.

I'm very confused about that why I can download code using J-Flash but failed when use J-commander.

[Alice_Yang · Accepted solution]

Hello 

You said you changed the "JLinkDevices.xml of jlink", how about do not change it, also use the latest J-commander .

About this question “I'm very confused about that why I can download code using J-Flash but failed when use J-commander.”， how about also ask Segger customer support, maybe they know it well.

https://www.segger.com/support/technical-support/  

BR

Alice

[Alice_Yang]

Hello,

How about update the debug firmware, and check whether Debug probe recognized by Device Manger of PC.

Does your board is Demo board from NXP or custom board?

BR

Alice

[longxing]

fist,thanks for your reply.

I already have given up trying to  use the DAP probe,and use a jlink probe instead.But there still one problem:I can't load my program into a QSPI flash using GUI FLASH TOOL while it's OK with Jlink command.

[Alice_Yang]

Hello,

Please show your detail steps with screenshot or vedio.

[longxing]

Also,I have aready modified the JLinkDevices.xml of jlink like:

I can load my program using J-Flash tool.

But it's true that it may be failed when using J-command.Is this the reason to fail to load program using GUI Flash tool of MCUXpresso IDE? 

[Alice_Yang]

Hello,

""But it's true that it may be failed when using J-command.Is this the reason to fail to load program using GUI Flash tool of MCUXpresso IDE? 

->> Maybe, while  there isn't this board , I cant' test on my hand, because we are working at home due to COVID-19. 

Please show the debug log on Console view.

And try change to another new workspace of ide, and open a simple SDK demo, build, check whether can debug well, then test program using GUI. Also pay attention erase flash before program:

BR

Alice

[longxing]

Hi,

you said "pay attention to erase the flash before program",do you means to check the "Enable erase all flash banks" box,like:

The debug log on console view is listed below:

Executing flash operation 'Program' (Program executable into flash weld_power.axf) - Tue May 31 08:16:54 CST 2022
Checking MCU info...
Scanning for targets...
Executing flash action...
SEGGER J-Link Commander V7.54 (Compiled Sep 1 2021 10:47:47)
DLL version V7.54, compiled Sep 1 2021 10:46:27
J-Link Command File read successfully.
Processing script file...
J-Link Commander will now exit on Error
J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link V11 compiled Apr 27 2022 16:36:21
Hardware version: V11.00
S/N: xxxxxxx
License(s): GDB, JFlash, FlashDL, RDI, FlashBP
VTref=3.328V
Target connection not established yet but required for command.
Device "MIMXRT1052XXXXA" selected.
Connecting to target via SWD
Found SW-DP with ID 0x0BD11477
DPIDR: 0x0BD11477
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x04770041)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FD000
CPUID register: 0x411FC271. Implementer code: 0x41 (ARM)
Found Cortex-M7 r1p1, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ E00FD000
ROMTbl[0][0]: E00FE000, CID: B105100D, PID: 000BB4C8 ROM Table
ROMTbl[1] @ E00FE000
ROMTbl[1][0]: E00FF000, CID: B105100D, PID: 000BB4C7 ROM Table
ROMTbl[2] @ E00FF000
ROMTbl[2][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[2][1]: E0001000, CID: B105E00D, PID: 000BB002 DWT
ROMTbl[2][2]: E0002000, CID: B105E00D, PID: 000BB00E FPB-M7
ROMTbl[2][3]: E0000000, CID: B105E00D, PID: 000BB001 ITM
ROMTbl[1][1]: E0041000, CID: B105900D, PID: 001BB975 ETM-M7
ROMTbl[1][2]: E0042000, CID: B105900D, PID: 004BB906 CTI
ROMTbl[0][1]: E0040000, CID: B105900D, PID: 000BB9A9 TPIU-M7
ROMTbl[0][2]: E0043000, CID: B105F00D, PID: 001BB101 TSG
Cache: Separate I- and D-cache.
I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
Cortex-M7 identified.
Reset delay: 0 ms
Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
ResetTarget() start
ResetTarget() end
AfterResetTarget() start
AfterResetTarget() end
PC = 60002360, CycleCnt = 00000000
R0 = 60002361, R1 = 20203A58, R2 = 60002361, R3 = 202051F0
R4 = 60002000, R5 = A63FEB26, R6 = 00200300, R7 = 000000F0
R8 = 401F4470, R9 = 20203A00, R10= A63FEB26, R11= 00000000
R12= 000001FE
SP(R13)= 20020000, MSP= 20020000, PSP= 20020000, R14(LR) = 00211A41
XPSR = 41000000: APSR = nZcvq, EPSR = 01000000, IPSR = 000 (NoException)
CFBP = 00000000, CONTROL = 00, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 00
FPS0 = 00000000, FPS1 = 00000000, FPS2 = 00000000, FPS3 = 00000000
FPS4 = 00000000, FPS5 = 00000000, FPS6 = 00000000, FPS7 = 00000000
FPS8 = 00000000, FPS9 = 00000000, FPS10= 00000000, FPS11= 00000000
FPS12= 00000000, FPS13= 00000000, FPS14= 00000000, FPS15= FFFFFFFF
FPS16= 00000000, FPS17= 00000000, FPS18= 00000000, FPS19= 00000000
FPS20= 00000000, FPS21= 00000000, FPS22= 00000000, FPS23= 00000000
FPS24= 00000000, FPS25= 00000000, FPS26= 00000000, FPS27= 00000000
FPS28= 00000000, FPS29= 00000000, FPS30= 00000000, FPS31= FFFFFFFF
FPSCR= 00000000
Downloading file [E:\XTProj\nxp\weld_power\Debug\weld_power.hex]...
****** Error: Timeout while preparing target, core does not stop. (PC = 0x2000017A, XPSR = 0x41000000, SP = 0x20000B18)!
Failed to initialize RAMCodeTimeout while preparing target, core does not stop. (PC = 0x2000017A, XPSR = 0x41000000, SP = 0x20000B18)!
Failed to initialize RAMCode
Unspecified error -1
Script processing completed.
Unable to perform operation!
Command failed with exit code 1

[longxing]

I just click the GUI FLASH TOOL icon,then a dialog apears:

then click the run button on following picture.