AnsweredAssumed Answered

MCUxpresso error Ee(42) Could not connect to core. Fails on Windows 10 - works on OsX

Question asked by James McCartney on Aug 26, 2019
Latest reply on Sep 19, 2019 by Chris Keydel

Trying to get the demo lab setup for the eIQ virtual event. Started with a new RT1060 EVK board. Installed the camera, lcd display and then wanted to do basic checkout before installing any of the lab demos. Board powers up from USB connection and blinky runs (green user led blinks) - first test, load hello world to prove that the board is communicating.

Board fails with the folowing errors displayed in MCUxpresso:

 

Dialog box message:
Error in final launch sequence:

 

Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=51856 -g -mi -2 -pMIMXRT1062xxxxA -vendor=NXP   --reset= -ProbeHandle=1 -CoreIndex=0 -cache=disable --flash-driver= -x C:/Users/James/Documents/MCUXpressoIDE_11.0.0_2516/eIQworkspace/evkmimxrt1060_hello_world/Debug --flash-dir C:/nxp/MCUXpressoIDE_11.0.0_2516/ide/plugins/com.nxp.mcuxpresso.tools.bin.win32_11.0.0.201905221151/binaries/Flash --flash-dir C:/Users/James/Documents/MCUXpressoIDE_11.0.0_2516/eIQworkspace/.mcuxpressoide_packages_support/MIMXRT1062xxxxA_support/Flash --telnet 3330 --no-packed
Error message from debugger back end:
Remote communication error.  Target disconnected.: Success.
Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=51856 -g -mi -2 -pMIMXRT1062xxxxA -vendor=NXP   --reset= -ProbeHandle=1 -CoreIndex=0 -cache=disable --flash-driver= -x C:/Users/James/Documents/MCUXpressoIDE_11.0.0_2516/eIQworkspace/evkmimxrt1060_hello_world/Debug --flash-dir C:/nxp/MCUXpressoIDE_11.0.0_2516/ide/plugins/com.nxp.mcuxpresso.tools.bin.win32_11.0.0.201905221151/binaries/Flash --flash-dir C:/Users/James/Documents/MCUXpressoIDE_11.0.0_2516/eIQworkspace/.mcuxpressoide_packages_support/MIMXRT1062xxxxA_support/Flash --telnet 3330 --no-packed
Error message from debugger back end:
Remote communication error.  Target disconnected.: Success.

 

MCUxpresso console window:

MCUXpresso IDE RedlinkMulti Driver v11.0 (May 22 2019 13:46:40 - crt_emu_cm_redlink build 6)
Found chip XML file in C:/Users/James/Documents/MCUXpressoIDE_11.0.0_2516/eIQworkspace/evkmimxrt1060_hello_world/Debug\MIMXRT1062xxxxA.xml
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.
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port

 

This was with MCUxpresso build "MCUXpresso IDE v11.0.0 [Build 2516] [2019-06-05]" on a Windows 10 Core I7.

SDK build version: RT1060 - 2.6.2 238 2919-07-11 with required eIQ mods as described in  eIQ ML Software Clinic - Lab and Software Files 

 

Reinstalled MCUxpresso over the existing install as this was indicated to solve the problem by one of the community notes. This left MCUxpresso in a state where it would not start correctly. (side note: get you installer guys to fix there installer) .

Next uninstalled MCUxcpresso using control panel/programs/... (uninstaller left the mcu directories however - which were then deleted) Then reinstalled MCUxpresso again. Starts correctly, still has the above problem. Possible driver problem?

 

Considered a possible USB port problem - moved to new USB port - same problem. No USB hubs involved. Also tried both USB3 and USB2 ports. No difference.

 

Installed MCUxpresso build v11.0.0 [Build 2516] [2019-06-05] on to my Mac/OsX system. Installed newly downloaded SDK for RT1060 (build 238 2019-07-11) from the NXP website. Loaded the hello world demo - build, selected debug - app built

and loaded and ran as it should.

 

What is the problem with the windows version of MCUxpresso?

 

Thank you.

Outcomes