lpc55s69 can't be programmed

cancel
Showing results for 
Search instead for 
Did you mean: 

lpc55s69 can't be programmed

119 Views
steffen_norbert
Contributor II

We have produced a custom board for the lpc55s69 chip (100 pin HLQFP). For power supply , USB and connectivity, reset, the JTAG connector and quarz oszillators we reproduced the design from the EVK development board. The processor seems to run, but we are not able to program it (using MCUxpresso 11 and the Link Probe from the EVK board). From several tries ("Debug" with the Hello world example) 2 times the programming went through and we ended up at the breakpoint (first line in main). we never managed to get "Hello World" over FC0.
The error messaged whch where shown in the Console window of MCUXpresso are shown below. We felt that using the GUI Flash tool doing a mass erase helped some how, but did not really solve th problem.

Any help how to get more information what happened and why is very much appreciated.

Protocol of a typical Debug session:
MCUXpresso IDE RedlinkMulti Driver v11.3 (Jan 11 2021 16:41:13 - crt_emu_cm_redlink build 9)
Found chip XML file in C:/Users/H.Mielke/Documents/MCUXpressoIDE_11.3.0_5222/workspace/lpcxpresso55s69_hello_world/Debug\LPC55S69.xml
Reconnected to existing LinkServer process.
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.183 (NXP Semiconductors)
Serial Number: JRAVBQCQ
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&37997ba1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 1 after searching for a good core
Cannot halt processor
Request debug reset of DAP
Cannot halt processor
Request debug reset of DAP
( 40) No Halt
debug interface type = CoreSight DP (DAP DP ID 6BA02477) over SWD TAP 0
processor type = Cortex-M33 (CPU ID 00000D21) on DAP AP 1
number of h/w breakpoints = 8
number of flash patches = 0
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 6BA02477. CpuID: 00000D21. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FE000: CID B105100D PID 0000095000 ROM (type 0x1)
ROM 1 E00FF000: CID B105100D PID 04000BB4C9 ROM (type 0x1)
ROM 2 E000E000: CID B105900D PID 04000BBD21 CSt ARM ARMv8-M type 0x0 Misc - Undefined
ROM 2 E0001000: CID B105900D PID 04000BBD21 CSt ARM DWTv2 type 0x0 Misc - Undefined
ROM 2 E0002000: CID B105900D PID 04000BBD21 CSt ARM FPBv2 type 0x0 Misc - Undefined
ROM 2 E0000000: CID B105900D PID 04000BBD21 CSt ARM ITMv2 type 0x43 Trace Source - Bus
ROM 1 E0040000: CID B105900D PID 04000BBD21 CSt type 0x11 Trace Sink - TPIU
request to clear DAP error failed - status 5
request to clear DAP error failed - status 5
request to clear DAP error failed - status 5
Failed on chip setup: Nn(05). Wire ACK Fault in DAP access
request to clear DAP error failed - status 5
request to clear DAP error failed - status 5
error closing down debug session - Nn(05). Wire ACK Fault in DAP access

0 Kudos
3 Replies

101 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

Hi

Thank you for contacting us.

Your custom board can't be connected with LPC-Link2. The problem may be in either PC side or board side:

1. test your LPC-Link2 with another board. make sure your LPC-Link2 is in good condition.

2. create a NEW project in a NEW workspace, make sure the problem is not due to SW association.

3. refer this article to check your debug interface design.

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

 

Hope this helps,

Jun Zhang

 

0 Kudos

74 Views
steffen_norbert
Contributor II

Hi,

thanks for the suggestions. Meanwhile we found a hardware Problem. Once we solved this we hope our custom board will work. If not we will come back.

tx & regards,

Steffen

0 Kudos

64 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

Welcome!

Have a nice day,

Jun Zhang

0 Kudos