topic Re: Failed on connect: Ee(42) Could not connect to core. No connection to chips debug port in i.MX RT Crossover MCUs

Failed on connect: Ee(42) Could not connect to core. No connection to chips debug port

dparth — Sat, 12 Mar 2022 15:49:18 GMT

I have been facing this issue when I try to load any code on i. MX RT1064 eval board. Can you please help me to clear this error? Already tried to change cable and usb port but did not work.

Re: Failed on connect: Ee(42) Could not connect to core. No connection to chips debug port

kerryzhou — Mon, 14 Mar 2022 03:48:29 GMT

Hi @dparth

Do you connect the USB to J41, and can you find the CMSIS DAP debugger?

If yes, and previously, you can download code, just now can't download code, you need to do the flash mass erase at first.

Please follow me to test it.

1. Power off the board, SW7:1-OFF,2-OFF,3-OFF,4-ON, enter serial download mode.

2. Download the MCUbootUtility tool:

https://github.com/JayHeng/NXP-MCUBootUtility/archive/refs/tags/v3.4.0.zip

the related user manual is:
https://github.com/JayHeng/NXP-MCUBootUtility

3. find another USB connect to J9, then

Connect the board, and erase the chip flash.

Then exit,

4. power off, SW7:1-OFF,2-OFF,3-ON,4-OFF

Use your CMSIS DAP connect again, you can test the SDK led_blinky simple code, it should works Ok now.

Best Regards,

Kerry

Re: Failed on connect: Ee(42) Could not connect to core. No connection to chips debug port

dparth — Mon, 14 Mar 2022 11:05:36 GMT

Hello,

Many thanks for the response.

Yes I am connecting the board through J41.

My PC would not let MCUbootUtility tool run- blocked by security software. Is there any other source to download/install it?

Re: Failed on connect: Ee(42) Could not connect to core. No connection to chips debug port

kerryzhou — Tue, 15 Mar 2022 01:54:18 GMT

Hi @dparth ,

1. About tool download in serial download mode, you also can try this nxp.com tool:

https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools-/mcuxpresso-secure-provisioning-tool:MCUXPRESSO-SECURE-PROVISIONING?tab=Design_Tools_Tab

2. Please try whether you can download code to internal RAM in serial download with the onboard CMSIS DAP debugger.

If yes, you can use my attached code to test your internal flash, whether erase, program and read can work successfully.

When this can work, then you can change the erase location from 0x60000000.

Just do the mass erase.

Please try it on your side, any updated information, please kindly let me know.

Best Regards,

Kerry