RT685 and LPC4322 custom board can't debug

[MkingWang]

Hi  NXP FAE,

We using LPC4322 to debug RT685 on our custom board,SCH  is  based on RT685-EVK Board, now we get a problom, seem's LPC4322 cant debug RT685, log shows as:

ERROR: Could not connect to target.
SEGGER J-Link GDB Server V7.54b Command Line Version
JLinkARM.dll V7.54b (DLL compiled Sep 14 2021 16:07:10)
Command line: -nosilent -swoport 2332 -select USB=729396258 -telnetport 2333 -singlerun -endian little -noir -speed auto -port 2331 -vd -device MIMXRT685S_M33 -if SWD -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: none
J-Link settings file: none
------Target related settings------
Target device: MIMXRT685S_M33
Target interface: SWD
Target interface speed: auto
Target endian: little
Connecting to J-Link...
J-Link is connected.
Device "MIMXRT685S_M33" selected.
Firmware: J-Link LPCXpresso V2 compiled Apr 4 2019 16:54:03
Hardware: V1.00
S/N: 729396258
Checking target voltage...
Target voltage: 3.30 V
Listening on TCP/IP port 2331
Connecting to target...
InitTarget() start
ERROR: Wrong DM-AP IDCODE detected: 0x00000000
InitTarget() end
InitTarget() start
ERROR: Wrong DM-AP IDCODE detected: 0x00000000
InitTarget() end
InitTarget() start
ERROR: Wrong DM-AP IDCODE detected: 0x00000000
InitTarget() end
InitTarget() start
ERROR: Wrong DM-AP IDCODE detected: 0x00000000
InitTarget() end
ERROR: Could not connect to target.

SEGGER J-Link GDB Server V7.54b Command Line Version

JLinkARM.dll V7.54b (DLL compiled Sep 14 2021 16:07:10)

Command line: -nosilent -swoport 2332 -select USB=729396258 -telnetport 2333 -singlerun -endian little -noir -speed auto -port 2331 -vd -device MIMXRT685S_M33 -if SWD -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: none
J-Link settings file: none
------Target related settings------
Target device: MIMXRT685S_M33
Target interface: SWD
Target interface speed: auto
Target endian: little

Connecting to J-Link...
J-Link is connected.
Device "MIMXRT685S_M33" selected.
Firmware: J-Link LPCXpresso V2 compiled Apr 4 2019 16:54:03
Hardware: V1.00
S/N: 729396258
Checking target voltage...
Target voltage: 3.30 V
Listening on TCP/IP port 2331
Connecting to target...
InitTarget() start
ERROR: Wrong DM-AP IDCODE detected: 0x00000000
InitTarget() end
InitTarget() start
ERROR: Wrong DM-AP IDCODE detected: 0x00000000
InitTarget() end
InitTarget() start
ERROR: Wrong DM-AP IDCODE detected: 0x00000000
InitTarget() end
InitTarget() start
ERROR: Wrong DM-AP IDCODE detected: 0x00000000
InitTarget() end
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.

Server has been shut down.

I use Jlink to connect borad, error screenshot as：

can someone give me any suggestion?

[jingpan]

Hi @MkingWang ,

Please at first check if the RT600 is power up correctly. You can try to connect RT600 boot ROM in ISP mode, via uart/usb.

If it's correct, please share the related schematic.

Regards,

Jing

[MkingWang]

Hi jingpan,

Thanks for reply。My question is how to check RT600 is power up corroct? When i set boot mode switch"ON OFF ON"(custom board flows EVK desgin), the uart has no out-put.

BR,

Mking

[jingpan · Accepted solution]

Hi @MkingWang ,

You can use MCUBootUtility  which can be found in https://github.com/JayHeng/NXP-MCUBootUtility.

Select RT685 and click connect if it can find uart/usb. The tool will use blhost.exe to connect.

Regards,

Jing

[MkingWang]

Thanks for your help, there is something wrong with reset circiut. Now RT685 is bootup.