LPC54113 no acces via SWD

Showing results for 
Search instead for 
Did you mean: 

LPC54113 no acces via SWD

Contributor II


we use the LPC54113 within our custom Board.

But we can't acces the µC via SWD.

We strip down the PCB up to only the µC and the capacitor.

So there are no other connections, beside the SWD Signals.

Via the Segger j-link we can connect to the µC, but any further acces is not possible.

We teted 4 Boards and 3 different j-links.

The Voltage is 3.3V and there is no ripple.

Here you can see the Log from the j-link:

Connecting ...
- Connecting via USB to probe/ programmer device 0
- Probe/ Programmer firmware: J-Link EDU Mini V1 compiled Jun 24 2021 14:29:39
- Device "LPC54113J256_M4" selected.
- Target interface speed: 100 kHz (Fixed)
- VTarget = 3.291V
- Found SW-DP with ID 0x2BA01477
- DPIDR: 0x2BA01477
- Scanning AP map to find all available APs
- AP[1]: Stopped AP scan as end of AP map has been reached
- AP[0]: AHB-AP (IDR: 0x24770011)
- Iterating through AP map to find AHB-AP to use
- AP[0]: Core found
- AP[0]: AHB-AP ROM base: 0xE00FF000
- CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
- Found Cortex-M4 r0p1, Little endian.
- FPUnit: 6 code (BP) slots and 2 literal slots
- CoreSight components:
- ROMTbl[0] @ E00FF000
- ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
- ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
- ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
- ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
- ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
- Executing init sequence ...
- Initialized successfully
- Target interface speed: 100 kHz (Fixed)
- CPU clock frequency: 5981 kHz (Auto detected)
- Found 1 JTAG device. Core ID: 0x2BA01477 (None)
- Connected successfully
Blank checking target ...
- 8 of 8 sectors selected, 1 range, 0x0 - 0x3FFFF
- Start of preparing flash programming
- ERROR: Failed to download RAMCode.
- ERROR: Failed to prepare for programming.
Failed to download RAMCode!
- End of preparing flash programming
- Start of restoring
- End of restoring
- ERROR: Failed to check blank target
Disconnecting ...
- Disconnected


Any hints, what is going wrong?

Is there any protection preprogrammed ?

What else should i check?


thanks Andreas


0 Kudos
1 Reply

NXP TechSupport
NXP TechSupport

Hi andreasruetten

I suggest you testing your custom board SWD connection on one more computer. if same connection error, we need to check SWD interface design. Thus refer this article please



Have a nice day

Jun Zhang

0 Kudos