Issue when S32DS using Jlink to debug

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

Issue when S32DS using Jlink to debug

Jump to solution
978 Views
GavinLi1
Contributor III

Hi NXP experts,

I follow the S32 Design Studio for S32 Platform V3.4/V3.5 + SEG... - NXP Community to using Jlink to connect S32K324(since there is no S32K324 example found in RTD, I use the S32K344 example instead) but meet issue.

My steps shown as follow:

1.

GavinLi1_0-1704704989635.png

2.

GavinLi1_1-1704705028773.png

3.

GavinLi1_0-1704705549788.png

 

4.

GavinLi1_3-1704705074772.png

Any steps I miss?

Thanks in advance!

Gavin

0 Kudos
Reply
1 Solution
931 Views
GavinLi1
Contributor III
Hi Julian,
Thanks for the reply.
I've fixed the issue by removing the step-3 above.
As you can see the error report in step-4 "another server is running...". Since we have set the Jlink serverCL.exe in the setp-2 and the server will be started when do the debug, so the Step-3 should not be done.

Hope it works for your side.

BR,
Gavin

View solution in original post

3 Replies
945 Views
Julián_AragónM
NXP TechSupport
NXP TechSupport

Hi @GavinLi1

Adding to what Jiri said, please consider porting the example from the K344 to the K324, as there are some differences between devices that may come with issues.

Best regards,
Julián.

0 Kudos
Reply
932 Views
GavinLi1
Contributor III
Hi Julian,
Thanks for the reply.
I've fixed the issue by removing the step-3 above.
As you can see the error report in step-4 "another server is running...". Since we have set the Jlink serverCL.exe in the setp-2 and the server will be started when do the debug, so the Step-3 should not be done.

Hope it works for your side.

BR,
Gavin
951 Views
jiri_kral
NXP Employee
NXP Employee

Hi, 

did you check with Windows Task Manager if there is really not running another J-Link gdb server instance ? 

Other possibility is that Firewall/network policy or other application is blocking port 2331.

0 Kudos
Reply