PNEV7462C examples don't debug

[Juergen_Abel]

As a new developer in the field of NXP boards, I would like to test some sample programs for DESFire.
For the development board PNEV7462C I have added the examples from SW3683.zip to a new workspace, having "copy projects into workspace" unchecked during import.
The examples can be compiled without any error for debug configuration ReleasePN7462AU and for debug configuration DebugPN7462AU.
The PNEV7462C board is connected with the LPC-Link2 as shown in fig. 34 p. 32 of UM10883, both boards are connected via USB cables to a WINDOWS 10 pc.
VCOM drivers are installed, board is recognized as VCOM_PN7462AU.

The problem is, that when trying to debug a sample program, e.g. PN7462AU_exphExMain with debug configuration DebugPN7462AU, the process stops with errors listed below.

Is there any more config to be set in order to debug a sample program?

Cheers,

Juergen

#########################################################
Error message in "MCUXpresso IDE: Exception" dialog:
-----------------------------
IOExeption

Read timed out

Read timed out
at com.nxp.mcuxpresso.core.debug.support.linkserver.redlink.client.RedlinkServerClient.receive(RedlinkServerClient.java:978)
at com.nxp.mcuxpresso.core.debug.support.linkserver.redlink.client.RedlinkServerClient.sendReceive(RedlinkServerClient.java:1068)
at com.nxp.mcuxpresso.core.debug.support.linkserver.redlink.client.RedlinkServerClient.sendReceive(RedlinkServerClient.java:1053)
at com.nxp.mcuxpresso.core.debug.support.linkserver.redlink.client.RedlinkServerClient.sendReceive(RedlinkServerClient.java:1040)
at com.nxp.mcuxpresso.core.debug.support.linkserver.redlink.client.RedlinkServerClient.wireConnect(RedlinkServerClient.java:1189)
at com.nxp.mcuxpresso.core.debug.support.linkserver.emulators.jtag.AbstractJtagDiscovery.ideConnect(AbstractJtagDiscovery.java:207)
at com.nxp.mcuxpresso.core.debug.support.linkserver.emulators.jtag.AbstractJtagDiscovery.connect(AbstractJtagDiscovery.java:187)
at com.nxp.mcuxpresso.core.debug.support.linkserver.emulators.jtag.AbstractJtagDiscovery.discover(AbstractJtagDiscovery.java:146)
at com.nxp.mcuxpresso.core.debug.support.linkserver.emulators.TargetDiscovery.jtagDiscovery(TargetDiscovery.java:445)
at com.nxp.mcuxpresso.core.debug.support.linkserver.launch.LaunchScriptUtils.getEmulatorInfo(LaunchScriptUtils.java:248)
at com.nxp.mcuxpresso.core.debug.support.linkserver.launch.LaunchScriptUtils.init(LaunchScriptUtils.java:488)
at com.nxp.mcuxpresso.core.debug.support.linkserver.launch.LaunchScriptUtils.<init>(LaunchScriptUtils.java:156)
at com.nxp.mcuxpresso.core.debug.support.linkserver.launch.LaunchScriptUtils.<init>(LaunchScriptUtils.java:143)
at com.nxp.mcuxpresso.core.debug.support.linkserver.services.TargetDiscoveryService.getTargetDiscovery(TargetDiscoveryService.java:138)
at com.nxp.mcuxpresso.core.debug.support.linkserver.override.LSFinalLaunchSequence$TargetDiscoveryJob.run(LSFinalLaunchSequence.java:124)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

#########################################################
Error message in console log:
-----------------------------

MCUXpresso IDE RedlinkMulti Driver v11.5 (Dec 16 2021 12:38:31 - crt_emu_cm_redlink build 2)
Found part description in XML file PN74xxAU.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
Connecting to probe 1 core 0 (using server started externally) reports:
'Ee(42). Could not connect to core.'
Retrying...
Reconnected to existing LinkServer process.
Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
============= SCRIPT: PN7xxxxx_Connect.scp =============
============= END SCRIPT ===============================
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port

[Juergen_Abel]

Hello Daniel,
thanks for the hint, after programming the LPC-Link2 with Segger J-Link firmware, the sample programs run and debug.
Before, I have used the CMSIS-DAP firmware, which didn't work.

Cheers,
Juergen

[danielchen]

thank you for your good news.

[danielchen · Accepted solution]

Hi @Juergen_Abel :

I would suggest you update the firmware image.

Available firmware images include:

J-LINK On-board by Segger

CMSIS-DAP

Please try with J-LINK.

Please refer to below link for more details

https://www.nxp.com/design/microcontrollers-developer-resources/lpc-link2:OM13054