IMXRT685-AUD-EVK debugging issue with JLink

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

IMXRT685-AUD-EVK debugging issue with JLink

Jump to solution
1,166 Views
e_matthews
Contributor II

it is the first time i use IMXRT685-AUD-EVK, i meet two issues blocking in setup stage by following the Tutorial steps.

First Issue:

when debugging the example, error message popups as followng snapshot:

 

Spoiler
e_matthews_0-1730352309148.png

the logs from output is captured in attached text file: MCUxpresso_err.txt

The environment and versions of IDE is as following list:

 

MCUXpressoIDE: 24.9.25

JLink: V810 (installed with MCUXpressoIDE)

Windows 10 Pro x64 22H2

 

Second Issue:

failed when use xt-ocd to connect EVB through JLink, "Error: SWD Wait time-out expired!" printed.

the template topology.xml is from here , and the modified version (with my serial number) is in attached

whole log is as following:

Ubuntu 22.04:

edmond@ed-ubuntu:/opt/Tensilica/xocd-14.11$ ./xt-ocd -c ./topology.xml
XOCD 14.11 2023-04-06 14:43:30
(c) 1999-2024 Cadence Design Systems Inc. All rights reserved.
[Debug Log 2024-10-31 10:12:33]
Loading module "gdbstub" v2.0.0.12
Loading module "jlink" v2.0.2.0
Using JLINK lib v.69600
Jlink USB Serial Number: 722949484
Connected to Jlink Device:
Name:'J-Link LPCXpresso V2 compiled May 2 2023 17:39:56'
S/N:722949484
Firmware: J-Link LPCXpresso V2 compiled May 2 2023 17:39:56
Requested/Set TCK: 1000kHz/65534kHz
Jlink: Select pipelined SWD
SWD-DP with ID 0x6BA02477
Loading module "jtag" v2.0.0.20
Loading module "xtensa" v2.0.0.48
Starting thread 'GDBStub'
Listening for GDB connection on port 20000
Initialize XDM driver
Error: SWD Wait time-out expired!
SWD-DP with ID 0x6BA02477
SWD-DP with ID 0x6BA02477
SWD-DP with ID 0x6BA02477
SWD-DP with ID 0x6BA02477
Error: XDM initialization failed
ERROR: Couldn't initialize, exit...

other logs from Win11:

PS C:\Program Files (x86)\Tensilica\Xtensa OCD Daemon 14.07> .\xt-ocd.exe -c .\topology.xml
XOCD 14.07 2021-06-01 19:00:49
(c) 1999-2024 Cadence Design Systems Inc. All rights reserved.
[Debug Log 2024-10-30 16:35:38]
Loading module "gdbstub" v2.0.0.12
Loading module "jlink" v2.0.2.0
Using JLINK lib v.69600
Jlink USB Serial Number: 722949484
Connected to Jlink Device:
Name:'J-Link LPCXpresso V2 compiled May 2 2023 17:39:56'
S/N:722949484
Firmware: J-Link LPCXpresso V2 compiled May 2 2023 17:39:56
Requested/Set TCK: 1000kHz/65534kHz
Jlink: Select SWD
SWD-DP with ID 0x6BA02477
Loading module "jtag" v2.0.0.20
Loading module "xtensa" v2.0.0.48
Starting thread 'GDBStub'
Opened GDB socket at port 20000
Initialize XDM driver
Error: SWD Wait time-out expired!
SWD-DP with ID 0x6BA02477
SWD-DP with ID 0x6BA02477
SWD-DP with ID 0x6BA02477
SWD-DP with ID 0x6BA02477
Error: XDM initialization failed
ERROR: Couldn't initialize, exit...

Have tried different combination with OS, xtensa ocd versions and JLink versions:

Win10, Win11 and Ubuntu 22.04

xtensa ocd version: 14.07, 14.08, 14.11

JLink version: V810, V810C, V696(in another topic, this version fixed similar error, but not mine)

 

Also checked the jumps as default:

MVIMG_20241031_113202.jpg

Labels (1)
0 Kudos
Reply
1 Solution
598 Views
mayliu1
NXP Employee
NXP Employee

Hi @e_matthews ,

 

Hi , I 'm glade that your project " hello world example" from SDK is well debugging through JLink.

Question1: Does it mean JLink connecting to CPU is OK on IDE?

Answer: Yes,  If you can debugging, It means CPU is OK on IDE.

Question2: But JLink connection from xt-ocd still doen't work, it always show "Error: SWD Wait time-out expired!". Does it mean DSP still not work?

Answer:  To reduce power consumption, The DSP core will do not power on  when the RT600 boots. If you want debug a DSP code, the RT600 Arm kernel need execute some code .

For the detail description, you can refer to the guide sheet.

mayliu1_0-1730972190494.png

Wish it helps you.
If you still have question about it, please kindly let me know.
If your question is solved, please tell me to close this case, thanks.

 

Best Regards

mayliu

 

View solution in original post

0 Kudos
Reply
8 Replies
1,130 Views
mayliu1
NXP Employee
NXP Employee

Dear @e_matthews ,

 

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

Please tell me your SDK information, It must be consistent to your Board.

From image you post I know your board is MIMXRT685-AUD EVK board , so you should import MIMXRT685-AUD-EVK SDK, not MIMXRT685-EVK SDK, It is very import.

Also, I suggest you can refer to this link

https://www.nxp.com/document/guide/getting-started-with-imxrt685-aud-evk-development-platform:GS-MIM...

Wish it helps you.
If you still have question about it, please kindly let me know.

Best Regards

mayliu

0 Kudos
Reply
1,128 Views
e_matthews
Contributor II

Dear @mayliu,

Thank you for your kindly advice, I will follow your guide to check the toturial from the correct link.

On the other hand, I double checked the wrong link that I jumped in:

https://www.nxp.com.cn/document/guide/getting-started-with-imxrt685-aud-evk-development-platform:GS-... 

the only difference between two links: mine is "www.nxp.com.cn" and the video content in the first section are different:图片.png

And then checking for the SDK version, what i used was for MIMXRT685-AUD-EVK as following:

图片.png

I also rebuild the SDK from the new link. The new downloaded SDK package are identical with my old one:

图片.png

 

Thank you again for replying! But there is still issue No.2 blocking, and it is not related with SDK. Only Jlink and xt-ocd are involved.

0 Kudos
Reply
1,111 Views
mayliu1
NXP Employee
NXP Employee

Dear @e_matthews ,

 

I use MIMXRT685-EVK debug, It is similar to  MIMXRT685-AUD-EVK.

1: Please make sure that modify usbser ID in  topology.xml file according to your JLINK.

2: the command is xt-ocd.exe -c topology.xml,  but I see your command is xt-ocd.exe -c .\topology.xml.  

mayliu1_1-1730456909701.png

Wish it helps you.
If you still have question about it, please kindly let me know.

 

Best Regards

mayliu

0 Kudos
Reply
1,104 Views
e_matthews
Contributor II

Thanks! @mayliu

For 1, the "./" means the current path, just inditate where's the topology exist. It should be the same if without it.

For 2, i double checked the usbser ID which I used, it was correct and was retrieved from JLink log print as tortuial: 722949484

图片.png

图片.png

if I typed the wrong ID, the log was like the following instead of what i've got:

图片.png

0 Kudos
Reply
1,060 Views
mayliu1
NXP Employee
NXP Employee

Hi @e_matthews ,

 

Hi, I have consulted with a RT600 series expert. He give some advices.

1: Please pay attention to the "Getting Started with Xplorer for EVK-MIMXRT685".

The path of the "Getting Started with Xplorer for EVK-MIMXRT685" file is in XXX\SDK_2_16_000_EVK-MIMXRT685\docs.

Especially, check  chapter 2.6 "2.6 Program LPC-Link2 with SEGGER J-Link", and update JLINK firmware.

2: Try to use J-link-commander to connect the board, whether It can connected.

3: Try to use MCUXpresso IDE create a simple project "mimxrt685audevk_hello_world" , using JLINK to debug, whether the project can run normally.

Wish it helps you.
If you still have question about it, please kindly let me know.

Best Regards

mayliu

 

 

0 Kudos
Reply
601 Views
e_matthews
Contributor II

Dear @mayliu1 

Thank you for advices.

For 1, JLink firmware is updated with guide, log as:

e_matthews_0-1730968162906.png

For 2, JLink commander connection is verified:

e_matthews_2-1730968488017.png

For 3, hello world example from SDK is well debugging through JLink:

e_matthews_3-1730968898136.png

e_matthews_4-1730969450653.png

Does it mean JLink connecting to CPU is OK on IDE?

But JLink connection from xt-ocd still doen't work, it always show "Error: SWD Wait time-out expired!". Does it mean DSP still not work?

 

Best Regards!

Edmond

0 Kudos
Reply
599 Views
mayliu1
NXP Employee
NXP Employee

Hi @e_matthews ,

 

Hi , I 'm glade that your project " hello world example" from SDK is well debugging through JLink.

Question1: Does it mean JLink connecting to CPU is OK on IDE?

Answer: Yes,  If you can debugging, It means CPU is OK on IDE.

Question2: But JLink connection from xt-ocd still doen't work, it always show "Error: SWD Wait time-out expired!". Does it mean DSP still not work?

Answer:  To reduce power consumption, The DSP core will do not power on  when the RT600 boots. If you want debug a DSP code, the RT600 Arm kernel need execute some code .

For the detail description, you can refer to the guide sheet.

mayliu1_0-1730972190494.png

Wish it helps you.
If you still have question about it, please kindly let me know.
If your question is solved, please tell me to close this case, thanks.

 

Best Regards

mayliu

 

0 Kudos
Reply
589 Views
e_matthews
Contributor II

Thanks! @mayliu1 

It can work after i upload a hello world demo with DSP enabled through IDE (mimxrt685audevk_dsp_hello_world_usart_cm33)

The xt-ocd can connect to DSP now.

So I guess that because i bought a new board which was burned with the factory default image (without DSP enabled), but I want to debug DSP directly and ignore running IDE demo in toturial video, then it causes the communication failure.

Just an advice to add a tip in guide document that to run hello world with DSP first then to try debugging DSP.

Thank you again for your kindly support and your time! That's really helpful to me.