This question have been asked several times! But I have found no good answers.
On one computer I could not connect to the target board (LPCExpresso1769/CD.
This is running Windows7/64. And MCUXpresso IDE v11.0.0 [Build 2516] [2019-06-05]
<pre>
Executing flash operation 'Program' (Program file into flash: freertos_blinky.axf) - Sun Aug 25 17:14:06 CEST 2019
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.0 (May 22 2019 13:46:40 - crt_emu_cm_redlink.exe build 6)
( 0) Reading remote configuration
Wc(03). No cache support.
Found part description in XML file nxp_lpc17xx.xme
( 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
</pre>
I also have a laptop (with about the same configuration) - and there it works.
/gh
Hello,
The first thing to try with NXP LPC MCU's to recover debug access is to boot into the ISP bootloader. That is, GND the ISP pin, assert RST, then remove the GND to ISP pin. Once in the ISP bootloader, the target clock configuration is stable, and the debug pins are in their default state - you should be able to connect.
Note: The ISP pin is:
Have a great day,
Sol
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------