MCUxpresso debugger failing to connect to RT 1062 (MIMXRT1060-EVK) - Probe Index 1

graham_taylor-j — Mon, 07 Oct 2019 22:03:47 GMT

Error: Unable to configure core for probe index 1

I have tested this with a number of sample / experimental projects and they all exhibit the same issues. I need a reliable / repeatable method to recover from this. I am using the MIMXRT1060-EVK with External PSU 5V and the USB cable connected from PC to J41. I am running version DAP 0244.

Daplink Mode: Interface
Interface Version: 0246
Bootloader Version: 0244
Git SHA: 51140ef2aa7be53bca9e15ca7ef7acef05ff6527
Local Mods: 1
USB Interfaces: MSD, CDC, HID, WebUSB
Bootloader CRC: 0xe493996b
Interface CRC: 0xf7f2f5dd

I have followed: MCUxpresso debugger failing to connect to RT 10... | NXP Community as closely as possible.

Trying to debug through DAP I get:

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

Setting SW7 to 0000 and using GUI flash tool mass erase, gave:

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

Tried using J-Link. Removed J47 and J48

Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:2331
Error message from debugger back end:
localhost:2331: No connection could be made because the target machine actively refused it.
Could not connect to target.
SEGGER J-Link GDB Server V6.44a Command Line Version
JLinkARM.dll V6.44a (DLL compiled Mar 8 2019 17:31:48)
Command line: -nosilent -swoport 2332 -select USB=59304533 -telnetport 2333 -singlerun -endian little -noir -speed auto -port 2331 -vd -device MIMXRT1062xxx6A -if SWD -halt -reportuseraction
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2331
SWO raw output listening port: 2332
Terminal I/O port: 2333
Accept remote connection: localhost only
Generate logfile: off
Verify download: on
Init regs on start: off
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: MIMXRT1062xxx6A
Target interface: SWD
Target interface speed: auto
Target endian: little
Connecting to J-Link...
J-Link is connected.
Device "MIMXRT1062XXX6A" selected.
Firmware: J-Link V9 compiled Oct 25 2018 11:46:07
Hardware: V9.30
Feature(s): GDB
Checking target voltage...
Connecting to target failed. Connected correctly?
GDB Server will be closed...
Shutting down...
Could not connect to target.

Also tried going into different flash modes: SW7-0001 serial download; SW7-0000 and SW7-0010 internal flash

Re: MCUxpresso debugger failing to connect to RT 1062 (MIMXRT1060-EVK) - Probe Index 1

ErichStyger — Tue, 08 Oct 2019 05:36:39 GMT

The message

Checking target voltage...
Connecting to target failed. Connected correctly?

indicates that there might be a problem with the power supply. The J-Link senses the target voltage using pin 1 (VTRef):

Can you check that this pin really has 3V?

As for the external power supply: that supply needs to be *very* stable and able to provide the needed current. I had problem with a bad/cheap one. Using a very good lab/desk power supply solved that problem for me. Additionally I had to have the power supply grounded.

I hope this helps,

Erich

Re: MCUxpresso debugger failing to connect to RT 1062 (MIMXRT1060-EVK) - Probe Index 1

graham_taylor-j — Tue, 08 Oct 2019 15:49:08 GMT

SOLVED: Touch Controller on attached LCD was dragging supply. Remove / replace LCD.

ThanksErichS‌

Checked the 3.3v reference to JTAG. This was overloaded resulting in 0.8v to pin even when J-Link removed. Also listen closely for switched mode regulators working too hard. Buzzing / whining sound.

MCUXpresso GeneralのトピックRe: MCUxpresso debugger failing to connect to RT 1062 (MIMXRT1060-EVK) - Probe Index 1

MCUxpresso debugger failing to connect to RT 1062 (MIMXRT1060-EVK) - Probe Index 1

Re: MCUxpresso debugger failing to connect to RT 1062 (MIMXRT1060-EVK) - Probe Index 1

Re: MCUxpresso debugger failing to connect to RT 1062 (MIMXRT1060-EVK) - Probe Index 1