LPC LINK-2 error in connecting to LPC54606 using JTAG

[hemanthvasista]

Hello ,

I am using LPC54606 based custom board. I am unable to program using the LPC Link-2 using JTAG.

Attached is the error message in MCUexpresso and the log of the error in Redink server.

Error in MCUexpressoSchematic

Also could you confirm the schematic attached?

LPC LOG:

[Started server]
[Connected on port 3025]
redlink> ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.361
Serial Number = KXBUAWIV
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&26531d9c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink> ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.361
Serial Number = KXBUAWIV
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&26531d9c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink> ProbeIsOpen 1
FALSE
redlink> ProbeOpenByIndex 1
Probe Handle 1 Open
redlink> WireIsConnected 1
FALSE
redlink> WireSwdConnect 1
Error: Wire Ack Fault - target connected?
redlink> WireIspReset 1
redlink> ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.361
Serial Number = KXBUAWIV
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&26531d9c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = TRUE
WireInitialized = FALSE
WireProtocol = SWD
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink> quit
[Closed]

Executing flash operation 'Program' (Program file into flash: INTG_TIMER_DELAY_LED.axf) - Mon Dec 07 17:53:32 IST 2020
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.2 (Sep 22 2020 13:23:35 - crt_emu_cm_redlink.exe build 19)
( 0) Reading remote configuration
Wc(03). No cache support.
Found part description in XML file LPC54606_internal.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

Thanks!!

Hemanth

[converse · Accepted solution]

As common with all ARM Cortex-M parts, JTAG is not used for debug - only boundary scan. Instead it uses SWD. See

https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/Design-Considerations-for-Debug/m-p/469565

[hemanthvasista]

Are there any way I can use JTAG in LPC54606? I remember to have used JTAG in LPC1768/88 controllers

In case of SWD,

I would need following pins:

1. SWCLK

2. SWDIO

3. SWO

Could you confirm? Also these pins are not overlapped with JTAG pin?

[converse]

There is no way to use JTAG, for debug, in LPC54606.

The document I linked in my first reply, should give you all the information you require to create your debug circuit.