LPC55S69 Flash Initialization & reset/erase failing

cancel
Showing results for 
Search instead for 
Did you mean: 

LPC55S69 Flash Initialization & reset/erase failing

483 Views
Contributor I

Flash Driver V.2 startup failed - rc Ef(34): Timed-out initializing flash.
chip initialization failed - Ef(34): Timed-out initializing flash.

Flash startup failed when i am trying to run default hello world and gpio led output applications. 

Please find the full error below. Also i tried erasing the flash which failed (hanging after a while) as well

MCUXpresso IDE RedlinkMulti Driver v11.0 (May 22 2019 13:46:40 - crt_emu_cm_redlink build 6)
Found chip XML file in C:/Users/aslput01/Documents/MCUXpressoIDE_11.0.0_2516/workspace/lpcxpresso55s69_gpio_led_output/Debug\LPC55S69.xml
Reconnected to existing LinkServer process.
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
NXP: LPC55S69
DAP stride is 1024 bytes (256 words)
Inspected v.2 On chip Flash memory using IAP lib LPC55xx.cfx
Image 'LPC55xx May 22 2019 12:27:16'
Opening flash driver LPC55xx.cfx
Retask watch 0 <NONE> address 0x0 (unused) for boot rom stall
Sending SYSRESETREQ to run flash driver
AFTER driver startup timeout (302 5ms retries)
Driver Addresses
Start: 14000000
Entry: 14000035
End: 140003B8
Stack: 30000800
Mailbox:30006800
Driver Register State
R0: 03800000
R1: 30000820
R2: FFFFFFE0
R3: AB2A43D0
R4: 00000000
R5: 00000000
R6: 00000000
R7: 00000000
R8: 00000000
R9: 00000000
R10: 00000000
R11: 00000000
R12: 00000000
SP: 30000800
LR: 10002A0B
PC: 10002A18
xPSR: 01000007
MSP: 30000800
PSP: 30000F40
CFBP: 00000000 (CONTROL=0x0, FAULTMASK=0x0, BASEPRI=0x0, PRIMASK=0x0)
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.cfx

Flash Reset Error:

C:\nxp\MCUXpressoIDE_11.0.0_2516\ide\binaries>crt_emu_cm_redlink.exe --flash-erase --rst -pLPC55S69 -v
Ns: MCUXpresso IDE RedlinkMulti Driver v11.0 (May 22 2019 13:46:40 - crt_emu_cm_redlink.exe build 6)

C:\nxp\MCUXpressoIDE_11.0.0_2516\ide\binaries>crt_emu_cm_redlink.exe --flash-erase --rst -pLPC55S69
Ns: MCUXpresso IDE RedlinkMulti Driver v11.0 (May 22 2019 13:46:40 - crt_emu_cm_redlink.exe build 6)
Wc(03). No cache support.
Nc: Found chip XML file in C:/nxp/MCUXpressoIDE_11.0.0_2516/ide/binaries\LPC55S69.xml
Nc: Restarted LinkServer process (PID 21804).
Nc: Using memory from core 0 after searching for a good core
Pc: ( 30) Emulator Connected
Nc: processor is in secure mode
Pc: ( 40) Debug Halt
Pc: ( 50) CPU ID
Nc: debug interface type = Cortex-M33 (DAP DP ID 6BA02477) over SWD TAP 0
Nc: processor type = Cortex-M33 (CPU ID 00000D21) on DAP AP 0
Nc: number of h/w breakpoints = 8
Nc: number of flash patches = 0
Nc: number of h/w watchpoints = 4
Nc: Probe(0): Connected&Reset. DpID: 6BA02477. CpuID: 00000D21. Info: <None>
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Ns: Content of CoreSight Debug ROM(s):
Nc: RBASE E00FE000: CID B105100D PID 0000095000 ROM (type 0x1)
Nc: ROM 1 E00FF000: CID B105100D PID 04000BB4C9 ROM (type 0x1)
Nc: ROM 2 E000E000: CID B105900D PID 04000BBD21 CSt ARM ARMv8-M type 0x0 Misc - Undefined
Nc: ROM 2 E0001000: CID B105900D PID 04000BBD21 CSt ARM DWTv2 type 0x0 Misc - Undefined
Nc: ROM 2 E0002000: CID B105900D PID 04000BBD21 CSt ARM FPBv2 type 0x0 Misc - Undefined
Nc: ROM 2 E0000000: CID B105900D PID 04000BBD21 CSt ARM ITMv2 type 0x43 Trace Source - Bus
Nc: ROM 1 E0040000: CID B105900D PID 04000BBD21 CSt type 0x11 Trace Sink - TPIU
Nc: NXP: LPC55S69
Nc: DAP stride is 1024 bytes (256 words)
Nc: Inspected v.2 On chip Flash memory using IAP lib LPC55xx.cfx
Nc: Image 'LPC55xx May 22 2019 12:27:16'
Nc: Opening flash driver LPC55xx.cfx
Nc: Sending VECTRESET to run flash driver
Nc: Flash variant 'LPC55xx (608KB)' detected (608KB = 19*32K at 0x0)
Nc: Closing flash driver LPC55xx.cfx
Nt: Reset target (system)
Nc: Starting execution using system reset and halt target
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Nc: Waiting for target to stop...
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
Xs:
Xc:
^C
C:\nxp\MCUXpressoIDE_11.0.0_2516\ide\binaries>

Labels (1)
0 Kudos
7 Replies

101 Views
NXP TechSupport
NXP TechSupport

HI ASLAM SYED

I wonder how I can reproduce your issue.

You use MCUXpressoIDE_11.0.0.

- What's your SDK version?

- do you use NXP demo board or your own designed PCB?

- What emulator interface do you use?

- Your board can't connect MCUXpresso IDE when debug lpcxpresso55s69_gpio_led_output. please send me screenshot about that.

Thanks.


Have a great day,
Jun Zhang

-------------------------------------------------------------------------------
Note:
- 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

101 Views
Contributor I

Hi Jun Zhang,

Please find the details below:

- What's your SDK version?

1. I am using SDK_2.6.2_LPCXpresso55S69

- do you use NXP demo board or your own designed PCB?

1. I am using NXP LPC55S69 EVK board

- What emulator interface do you use?

1. I am using CMSIS-DAP

- Your board can't connect MCUXpresso IDE when debug lpcxpresso55s69_gpio_led_output. please send me screenshot about that.

1. Please find the screenshots attached

Regards

Aslam Syed

0 Kudos

101 Views
NXP TechSupport
NXP TechSupport

HI

1. first I would suggest you refresh your LPCXPresso55s69 CMSIS-DAP firmware with LPCScrypt. Make sure your board is in DFU mode during updating. Thus we can make sure the on board debugger firmware is in good.

pastedImage_1.png

2. remove DFU jumper, reconnect board. you should be able to see LPC-Jlink2 appears in device manager:

pastedImage_2.png

then create a NEW project under a NEW workspace, test how it works. if still can't connect. test it on another computer.

3. If above can not help you, I suggest you try latest MCUxpresso IDE v11.0.1+ SDK2.6.3.  I have tested these combination, it works well.

I was told SDK2.6.3 will be released on 25,Sept.

 


Have a great day,
Jun Zhang

-------------------------------------------------------------------------------
Note:
- 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

101 Views
Contributor I

Hi Zhang,

Please find my comments inline below

Regards

Aslam Syed

0 Kudos

101 Views
NXP TechSupport
NXP TechSupport

I don't see your comments.

0 Kudos

101 Views
Contributor I

Hi Zhang

After updating to the latest NXP SDK 2.6.3, I am able to flash successfully without any errors. So it must have been some issue with old SDK 2.6.2

Hence my issue is now resolved. Thanks again for your support

Regards

Aslam Syed

0 Kudos

101 Views
NXP TechSupport
NXP TechSupport

Good to know your problem has been resolved. 

You are welcome!


Have a great day,
Jun Zhang

-------------------------------------------------------------------------------
Note:
- 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