Flash erase for LPC55S69-EVK fails

Showing results for 
Search instead for 
Did you mean: 

Flash erase for LPC55S69-EVK fails

Contributor II


I recently got a LPC55S69-EVK. I was trying out some sample programs and it worked fine. Recently, though the flashing procedure is failing. I have power-cycled the board several times but the situation did not improve. Am I missing something. Thank you.

Please see the logs below:

MCUXpresso IDE RedlinkMulti Driver v10.3 (Feb  7 2019 22:50:02 - crt_emu_cm_redlink build 760)
Found chip XML file in C:/MCUXpressoIDE_10.3.1_2233/workspace/lpcxpresso55s69_hello_world_s/Debug\LPC55S69.xml
Reconnected to existing link server
Connecting to probe 1 core 0 (using server started externally) gave 'OK'
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.224 (NXP Semiconductors)
Serial Number:  XXXXXXXX <Serial number masked>
VID:PID:  1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&1b84f72f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
processor is in secure mode
debug interface type      = Cortex-M33 (DAP DP ID 6BA02477) over SWD TAP 0
processor type            = Cortex-M33 (CPU ID 00000D21) on DAP AP 0
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
DAP stride is 1024 bytes (256 words)
Inspected v.2 On chip Flash memory using IAP lib LPC55xx_S.cfx
Image 'LPC55xx (Secure) Feb 14 2019 11:15:00'
Opening flash driver LPC55xx_S.cfx
Sending VECTRESET to run flash driver
AFTER driver startup timeout (302 5ms retries)
Driver Addresses
Start:  14000000
Entry:  14000035
End:    140003C4
Stack:  30000800
Driver Register State
R0:     300007E0
R1:     14000034
R2:     00000004
R3:     0000BEAB
R4:     00000000
R5:     00000000
R6:     00000000
R7:     00000000
R8:     00000000
R9:     00000000
R10:    00000000
R11:    00000000
R12:    00000000
SP:     300007E0
LR:     FFFFFFF9 (exception from main thread)
PC:     10002D80
xPSR:   89000003
MSP:    300007E0
PSP:    30000800
CFBP:   00000001 (CONTROL=0x0, FAULTMASK=0x0, BASEPRI=0x0, PRIMASK=0x1)
Stacked Exception information at MSP
300007FC:  xPSR:   89000000
300007F8:  VECTPC: 14000034
300007F4:  LR:     14000035
300007F0:  R12:    00000000
300007EC:  R3:     00000000
300007E8:  R2:     00000000
300007E4:  R1:     00000000
300007E0:  R0:     30006800
Exception registers
E000ED04:  ICSR:   00400803 (ISRPENDING, VECTPEND=0(none), RETTOBASE, VECTACTIVE=3(hard fault))
E000ED08:  VTOR:   10000000 TBLBASE=0(INCODE), TBLOFF=0x200000
E000ED28:  MMFSR:  00
E000ED29:  BFSR:   01 (IBUSERR)
E000ED2A:  UFSR:   0000
E000ED2C:  HFSR:   C0000000 (DEBUGEVT, FORCED)
E000ED30:  DFSR:   00000001 (HALTED)
E000ED3C:  AFSR:   00000000
E000ED24:  SHCSR:  00000004 (HARDFAULTACT)
E000ED34:  MMAR:   0103E9F0
E000ED38:  BFAR:   0103E9F0
E000EDFC:  DEMCR:  01100000 (TRCENA)
VECTPC instructions near 89000000
88FFFFFC:  (can't read - Nn(05). Wire ACK Fault in DAP access)
88FFFFFE:  (can't read)
Flash Driver V.2 startup failed - rc Ef(34): Timed-out initializing flash.
chip initialization failed - Ef(34): Timed-out initializing flash.
failed to initialize flash driver LPC55xx_S.cfx
can't find a flash driver called ''

Labels (1)
0 Kudos
2 Replies

NXP TechSupport
NXP TechSupport

Hi Romit Dasgupta

What's your LPC55s69 EVK board version?

Some early pre-release version of LPC55s69 EVK has on board Flash defect.  but if you purchased the board from NXP web site, the mass erase should work without problem. Besides Romit's suggestion, please check attached video of how to do mass erase with the tool.

Have a great day,


- If this post answers your question, please click the "Mark Correct" button. Thank you!


- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.

0 Kudos

Contributor II

I found the solution to this via mass erase.  Please see the thread on how to mass-erase the flash. 


0 Kudos