PN7462 Debugging Error in MCUXpresso IDE – Need Root Cause and Resolution

[Vignesh_Venkatesan123]

Hello All,

I am using the PN7462 Development Kit with MCUXpresso IDE version 12.24.148. While attempting to debug code on the PN7462, I am encountering the error shown below.

I have included the debug log and attached a screenshot of the error for your reference.

Could you please help identify the root cause of this issue and suggest a possible solution?

Thank you in advance for your support.

Error Log:

LinkServer RedlinkMulti Driver v24.12 (Dec 18 2024 18:34:07 - crt_emu_cm_redlink build 869)

Found part description in XML file PN74xxAU.xml

Reconnected to existing LinkServer process.

============= SCRIPT: PN7xxxxx_Connect.scp =============

DpID = 0BB11477

APID = 0x04770021

============= END SCRIPT ===============================

Probe Firmware: LPC-LINK2 CMSIS-DAP V5.224 (NXP Semiconductors)

Serial Number:  PUDQPZIU

VID:PID:  1FC9:0090

USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&31d1711e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

Using memory from core 0 after searching for a good core

debug interface type      = CoreSight DP (DAP DP ID 0BB11477) over SWD TAP 0

processor type            = Cortex-M0 (CPU ID 00000C20) on DAP AP 0

number of h/w breakpoints = 4

number of flash patches   = 0

number of h/w watchpoints = 2

Probe(0): Connected&Reset. DpID: 0BB11477. CpuID: 00000C20. Info: <None>

Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.

Content of CoreSight Debug ROM(s):

RBASE E00FF000: CID B105100D PID 04000BB471 ROM (type 0x1)

ROM 1 E000E000: CID B105E00D PID 04000BB008 Gen SCS (type 0x0)

ROM 1 E0001000: CID B105E00D PID 04000BB00A Gen DWT (type 0x0)

ROM 1 E0002000: CID B105E00D PID 04000BB00B Gen FPB (type 0x0)

NXP: PN7462AU-C3-00

DAP stride is 1024 bytes (256 words)

Inspected v.2 On-chip Flash Memory PN7xxxxx_158k.cfx

Image 'PN7xxxxx_158k Mar  8 2016 16:35:06'

( 65) Chip Setup Complete

Connected: was_reset=true. was_stopped=false

Awaiting telnet connection to port 3330 ...

GDB nonstop mode enabled

FreeRTOS stack backtrace is disabled

Opening flash driver PN7xxxxx_158k.cfx

VECTRESET requested, but not supported on ARMv6-M CPUs. Using SOFTRESET instead.

Using SOFT reset to run the flash driver

Flash device supported (158KB = 79*2K at 0x203000)

Writing 120260 bytes to address 0x00203000 in Flash

driver "ProgramPage" timeout (500 ms)  PC: FFFFFFFE

Closing flash driver PN7xxxxx_158k.cfx

Target error from Commit Flash write: Ec: Flash driver "ProgramPage" timeout (500 ms)  PC: FFFFFFFE

GDB stub (C:\NXP\LinkServer_24.12.21\binaries\crt_emu_cm_redlink) terminating - GDB protocol problem: Pipe has been closed by GDB.

[KaiLi]

Hello @Vignesh_Venkatesan123 

Try turning the power off and then on again. In principle, EVK+example project should not have any problems. It works on my side.

[Vignesh_Venkatesan123]

Hello KaiLi,

I am working on below example code "NfcrdlibEx10_MIFAREDESFire_EVx". I could able to progress for certificate read/write and flash. Now i am facing this issue in board side. there are no changes made to SW which worked earlier.

Probe used : LPC-LINK2 CMSIS-DAP V5.224

Best regards,

Vignesh Venkatesan

[KaiLi]

Hello @Vignesh_Venkatesan123 

Please try updating the LPC-Link2 firmware. Normally, the EVK board and software code haven't been modified, so there shouldn't be any problems.

Please update firmware by going LPC-Link2 | NXP Semiconductors

[Vignesh_Venkatesan123]

There is no problem with LPC-Link2. As i connected another EVK board with the same LPC-Link2 and same probe, debug flashing is happening properly. Problem is with EVK board.

[Vignesh_Venkatesan123]

Hi @KaiLi 

Can you please explain the process of how to do full erase ?