IMXRT1021-evk Could not connect to core.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

IMXRT1021-evk Could not connect to core.

1,021 Views
swapna_b
Contributor I

We were trying to run zephyr OS sample program on MIMRT1021-EVK. Successfully flashed the code on MIMRT1021-EVK. After this step we were not able to debug the device, not even erase it. We tried to flash hello world code from SDK still failed. We have tried with DAP-Link following is the error message

Executing flash operation 'Erase' (Erase flash) - Thu Sep 12 16:34:41 IST 2019
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.0 (May 22 2019 13:50:00 - crt_emu_cm_redlink build 6)
(  0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in /home/xxx/Documents/workspace/MCUXpresso_11.0.0_2516/RT1020/evkmimxrt1020_hello_world/Debug/MIMXRT1021xxxxx.xml
(  5) Remote configuration complete
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
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

Even we tried with JTag/J-Link following is the error message

Executing flash operation 'Erase' (Erase flash) - Thu Sep 12 17:56:06 IST 2019
Checking MCU info...
Scanning for targets...
Executing flash action...
SEGGER J-Link Commander V6.44i (Compiled May 17 2019 17:37:38)
DLL version V6.44i, compiled May 17 2019 17:37:26
J-Link Command File read successfully.
Processing script file...
J-Link Commander will now exit on Error
J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
Hardware version: V8.00
S/N: -1
License(s): RDI,FlashDL,FlashBP,JFlash,GDB
VTref=3.287V
Target connection not established yet but required for command.
Device "MIMXRT1021DAG5A" selected.
Connecting to target via SWD
Found SW-DP with ID 0x0BD11477
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map seems to be reached
Iterating through AP map to find AHB-AP to use
**************************
WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
**************************
Found SW-DP with ID 0x0BD11477
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map seems to be reached
AP[0]: AHB-AP (IDR: 0x04770041)
Iterating through AP map to find AHB-AP to use
AP[0]: Skipped. Could not read AHB ROM register
****** Error: Could not find core in Coresight setup
**************************
WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
**************************
**************************
WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
**************************
Found SW-DP with ID 0x0BD11477
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map seems to be reached
AP[0]: AHB-AP (IDR: 0x04770041)
Iterating through AP map to find AHB-AP to use
AP[0]: Skipped. Could not read AHB ROM register
Cannot connect to target.
Script processing completed.
Unable to perform operation!
Command failed with exit code 1

Please guide us, what should we do to access? Is there any way to go into ISP Mode?

Labels (1)
Tags (1)
0 Kudos
2 Replies

820 Views
swapna_b
Contributor I

We have successfully resolved the issue by changing boot mode. It was in qspi mode changed to sdcard and then tried erasing flash from IDE.

Thank you so much for help.

0 Kudos

820 Views
oleglavrukhin
Contributor IV

Hello!

as You can see, RESET (pin 15) high, but should be low. Please check target hardware.

try to check a jumper connection on board!

I could not start my board for 3 days due to poor contact on J37!

regards

0 Kudos