NO connection to chips debug port on the MCXN236?

skruglewicz said:

I’m still having problems with the MCXN236 . Can't find the probe 

CONSOLE log:

LinkServer RedlinkMulti Driver v25.6 (Jun 26 2025 19:34:05 - crt_emu_cm_redlink build 1017)
Found chip XML file in C:/nxp/workspace/frdmmcxn236_hello_world/Debug\MCXN236.xml
( 5) Remote configuration complete
Reconnected to the existing LinkServer process.
Connecting to probe 2 core 0 (using server started externally) reports:
'Ee(42). Could not connect to core.'
Retrying...
Reconnected to the existing LinkServer process.
Server OK but no connection to probe 2 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port

 I'm dead in the water with the MCXN236 and can not develop my project without it Does any one know why thus is happening? Is my board defective? 

any help here would be appreciated.

Thanks 

Steve K

I am currently facing a critical and complete standstill in my project development due to a severe and unresolved issue with the MCXN236 device. To be absolutely clear, this development board or component is entirely non-functional; it is, in effect, a useless brick. All attempts to utilize the device have failed, rendering it completely unusable for its intended purpose. Consequently, I am dead in the water, as the lack of a working MCXN236 has created an insurmountable bottleneck, making any further progression on my project impossible until this fundamental hardware issue is resolved. This is not a minor setback; the device is fundamentally broken and cannot be leveraged for any stage of my necessary development work.

Here are the four troubleshooting steps I attempted to fix the "No connection to chip's debug port" error with your NXP FRDM-MCXN236 board, along with the reported status for each:

The persistent error across all attempts was: Ee(42). Could not connect to core. and No connection to the chip's debug port.

Thanks balajivan1995 or all your suggestions, but unfortunately your suggestions di not fix the problem. 

I'm closing my question but the debug Probe is still not working. I cannot use the board. 

skruglewicz said:

I’m still having problems with the MCXN236 . Can't find the probe 

CONSOLE log:

LinkServer RedlinkMulti Driver v25.6 (Jun 26 2025 19:34:05 - crt_emu_cm_redlink build 1017)
Found chip XML file in C:/nxp/workspace/frdmmcxn236_hello_world/Debug\MCXN236.xml
( 5) Remote configuration complete
Reconnected to the existing LinkServer process.
Connecting to probe 2 core 0 (using server started externally) reports:
'Ee(42). Could not connect to core.'
Retrying...
Reconnected to the existing LinkServer process.
Server OK but no connection to probe 2 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port

 I'm dead in the water with the MCXN236 and can not develop my project without it Does any one know why thus is happening? Is my board defective? 

any help here would be appreciated.

Thanks 

Steve K

I am currently facing a critical and complete standstill in my project development due to a severe and unresolved issue with the MCXN236 device. To be absolutely clear, this development board or component is entirely non-functional; it is, in effect, a useless brick. All attempts to utilize the device have failed, rendering it completely unusable for its intended purpose. Consequently, I am dead in the water, as the lack of a working MCXN236 has created an insurmountable bottleneck, making any further progression on my project impossible until this fundamental hardware issue is resolved. This is not a minor setback; the device is fundamentally broken and cannot be leveraged for any stage of my necessary development work.

Here are the four troubleshooting steps I attempted to fix the "No connection to chip's debug port" error with your NXP FRDM-MCXN236 board, along with the reported status for each:

The persistent error across all attempts was: Ee(42). Could not connect to core. and No connection to the chip's debug port.

Thanks balajivan1995 or all your suggestions, but unfortunately your suggestions di not fix the problem. 

I'm closing my question but the debug Probe is still not working. I cannot use the board.