Actions
Forum Thread Details
  • State Not Answered
  • Replies 5 replies
  • Subscribers 39 subscribers
  • Views 90 views
  • Users 0 members are here
Related

NO connection to chips debug port on the MCXN236?

skruglewicz

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

image

 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

Parents
  • 0

    1. Close every other projects, and select debug option.

    2. Sometimes the IDE will hang trying to open the linkserver. In that case, close the IDE, locate the axf or hex file and flash it using standalone link flash application.

  • 0 in reply to balajivan1995
    balajivan1995 said:
    Close every other projects, and select debug option.
    balajivan1995 said:
    Sometimes the IDE will hang trying to open the linkserver. In that case, close the IDE, locate the axf or hex file and flas

    hello  

    Thanks a lot for your suggestions! I tried closing every other project and selecting the debug option, but unfortunately that did not resolve my connection issue.

    For flashing with standalone link flash—could you clarify how you locate the .axf or .hex file from the IDE? Any tips for using the utility reliably would be great.

    Also, do you think I need to update the MCU-Link firmware using the firmware update utility for my board? Wondering if that might be causing problems with the debug port not connecting.

    Here is my tool chain: 
    IDE: MCUXpresso IDE V25.6 [Build 136] [2025-06-27]]
    SDKs:
    SDK_2.x_FRDM-MCXA153 SDK Version: 25.09.00 Manifest Version: 3.15.0
    SDK_2.x_FRDM-MCXN236 SDK version: 25.09.00 Manifest Version: 3.15.0

    Thanks again for all your help!

Reply
  • 0 in reply to balajivan1995
    balajivan1995 said:
    Close every other projects, and select debug option.
    balajivan1995 said:
    Sometimes the IDE will hang trying to open the linkserver. In that case, close the IDE, locate the axf or hex file and flas

    hello  

    Thanks a lot for your suggestions! I tried closing every other project and selecting the debug option, but unfortunately that did not resolve my connection issue.

    For flashing with standalone link flash—could you clarify how you locate the .axf or .hex file from the IDE? Any tips for using the utility reliably would be great.

    Also, do you think I need to update the MCU-Link firmware using the firmware update utility for my board? Wondering if that might be causing problems with the debug port not connecting.

    Here is my tool chain: 
    IDE: MCUXpresso IDE V25.6 [Build 136] [2025-06-27]]
    SDKs:
    SDK_2.x_FRDM-MCXA153 SDK Version: 25.09.00 Manifest Version: 3.15.0
    SDK_2.x_FRDM-MCXN236 SDK version: 25.09.00 Manifest Version: 3.15.0

    Thanks again for all your help!

Children
No Data