AnsweredAssumed Answered

RT1020-EVK Debug error

Question asked by Carlos Candido on Jan 5, 2019
Latest reply on Jan 19, 2019 by Carlos Candido

Hi,

MCUxpresso 10.3

RT1020EVK - A3

Intall all, testing debug ok,

 

now, error debug or flasher.

Update: k20dx_mimxrt1020_evk_qspi_if_crc20180312.bin

error.

 

see Logs.

//-----------------------Debug error:
Error in final launch sequence
Error: Unable to configure core for probe index 1.
Wire not connected

LinkServer has been terminated and will be restarted.
Please restart your debug session.
If the problem recurs, please power cycle your debug probe and restart MCUXpresso IDE.
//----------------------------DETAILS
# DAPLink Firmware - see https://mbed.com/daplink
Unique ID: 0226000040214e4500521018c89200399e11000097969900
HIC ID: 97969900
Auto Reset: 0
Automation allowed: 0
Overflow detection: 0
Daplink Mode: Interface
Interface Version: 0244
Bootloader Version: 0244
Git SHA: 28f80751691ef703ab87355e5f42a6065de1cf4c
Local Mods: 1
USB Interfaces: MSD, CDC, HID
Bootloader CRC: 0x44eadb90
Interface CRC: 0xb309c6d0
Remount count: 0

 

//---------------------------FLASHER ERROR
Executing flash operation 'Program' (Program file into flash: RT20OSLCD.axf) - Sat Jan 05 11:28:28 BRST 2019
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v10.3 (Nov 28 2018 02:33:57 - crt_emu_cm_redlink.exe build 748)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in C:/HDsource/workspace/RT20OSLCD/Debug\MIMXRT1021xxxxx.xml
( 5) Remote configuration complete
Reconnected to existing link server
Connecting to probe 1 core 0 (using server started externally) gave 'Ee(42). Could not connect to core.'
Connecting to probe 1 core 0 (using server started externally) gave 'Ee(42). Could not connect to core.'
Connecting to probe 1 core 0 (using server started externally) gave 'Ee(42). Could not connect to core.'
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
//--------------------------------------------------------

 

how to?

 

thanks,

Carlos.

Outcomes