failed to initialize flash driver LPC540xx_SPIFI_SFDP.cfx

cancel
Showing results for 
Search instead for 
Did you mean: 

failed to initialize flash driver LPC540xx_SPIFI_SFDP.cfx

299 Views
Contributor II

Just received a lpc54018 eval board with LCD (OM40003).  It powers up with the LCD color draw demo - which works

fine.  Have installed latest MCUxpresso and verified that it works by debugging code on a LPC55S69 board to be used

for the same project.  Also loaded the correct SDK for this board and built (no errors) several LPC54018  projects.

When attempting to debug any of the successfully build demo projects (e.g. both littlevgl demos from the SDK), I get the

following:

MCUXpresso IDE RedlinkMulti Driver v11.1 (Feb 24 2020 13:54:38 - crt_emu_cm_redlink build 11)
Found chip XML file in C:/Users/mcp/Documents/MCUXpressoIDE_11.1.1_3241/GStest_54018/lpcxpresso54018_littlevgl_terminal/Debug\LPC54018.xml
Reconnected to existing LinkServer process.
Using memory from core 0 after searching for a good core
On debug connection - use system reset, stalling when 0x40000040 is accessed
Retask read watchpoint 1 at 0x40000040 to use for boot ROM stall
Waiting for target to stop...
Warning - processor did not halt - gave up waiting
debug interface type      = Cortex-M3/4 (DAP DP ID 2BA01477) over SWD TAP 0
processor type            = Cortex-M4 (CPU ID 00000C24) on DAP AP 0
number of h/w breakpoints = 6
number of flash patches   = 2
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 2BA01477. CpuID: 00000C24. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Enabled.
Content of CoreSight Debug ROM(s):
RBASE E00FF000: CID B105100D PID 04000BB4C4 ROM (type 0x1)
ROM 1 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
ROM 1 E0001000: CID B105E00D PID 04003BB002 Gen DWT (type 0x0)
ROM 1 E0002000: CID B105E00D PID 04002BB003 Gen FPB (type 0x0)
ROM 1 E0000000: CID B105E00D PID 04003BB001 Gen ITM (type 0x0)
ROM 1 E0040000: CID B105900D PID 04000BB9A1 CSt TPIU type 0x11 Trace Sink - TPIU
ROM 1 E0041000: CID B105900D PID 04000BB925 CSt ETM type 0x13 Trace Source - Core
NXP: LPC54018
DAP stride is 4096 bytes (1024 words)
Inspected v.2 External Flash Device on SPI LPC540xx_SPIFI_SFDP.cfx
Image 'LPC540xx_JEDEC_SFDP Feb 17 2020 13:57:06'
Opening flash driver LPC540xx_SPIFI_SFDP.cfx
Using SOFT reset to run the flash driver
rst - Boot ROM stall address was not accessed (but we entered debug on Halt anyway)
Cannot halt processor
warning - failed to halt processor on startup timeout - rc Ep(04). Cannot halt processor.
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 LPC540xx_SPIFI_SFDP.cfx

Have searched this site for similar issues and have tried restarting with several alternate configs -

namely with and without J5 (DFU boot) inserted and powering up with any of the ISP buttons

depressed.  As the saying goes - "no joy".  I don't think I could have possibly bricked the board since

it never gets to loading any code...besides, none of the demos are related to OTP.  As I pointed out

above, this environment works fine with Link2 on a current LPC55S69 board.

Any help getting past this would be appreciated.  I plan to eRPC this board to the LPC55S69 as a HMI interface.

But, can't focus on that until this board starts behaving.

Regards,

Chuck McP

Tags (1)
6 Replies

126 Views
Contributor II

Felipe,

Thanks for your note.  Although I realize its unlikely to be an actual hardware

problem, I need to get this resolved.  I've contacted the vendor I purchased the

board from and they will ship a replacement and work things out w/NXP.  I'll let

you know if a replacement board resolves the issue.  It has be stumped.

Regards,

Chuck

126 Views
NXP TechSupport
NXP TechSupport

Hi Chuck,

Just to continue with the follow-up. Could you please let me know the status of this issue? Did you get the replacement board?

Regards,

Felipe

0 Kudos

126 Views
NXP TechSupport
NXP TechSupport

Hello Chuck,

 

I tried to load same example to see if it was a problem of our SDK example but I could program my board successfully.

 

I would suggest that you try the following:

 

  1. Click on "Clean up debug" button in IDE.
  2. Power your board and debug probe down and back up again
  3. Delete your launch configuration
  4. Try debugging again
  5. If debug still doesn't work, try doing an ISP reset as well as the above :

 

Best regards,

Felipe

0 Kudos

126 Views
Contributor II

Felipe,

Trying to make some progress on this issue.....can you forward any

parameters from load config in IDE

that I can check against my config? I assume that the flash program file

is the correct one and that

it has not been recently updated to match a change (read in one of the data

sheets) of the installed

on-board flash chip. Does "failed to halt processor" have any

significance? I don't think

the demo program has gone amuck since it functions properly and, when I

boot w/ISP buttons, the

LCD screen is blank (indicating, I believe, that it is not running).

If I need to send this board back to Mouser, I'd like to do so sooner than

later. Thanks again for

looking at this.

Regards,

Chuck

On Mon, Jun 8, 2020 at 4:04 PM Charles McParland <cpmcparland@rtisys.org>

0 Kudos

126 Views
NXP TechSupport
NXP TechSupport

Hi Chuck,

 

I am sorry for my late reply. If you have tried all the recommendations and you were not able to program your board out of the box. Then, it certainly can be a defective board.

 

I recommend you to go to the following link.

Returns and Warranty Information | NXP 

Best regards,

Felipe

0 Kudos

126 Views
Contributor II

Felipe,

Thanks for your note. Afraid no good news here. I did a debug cleanup in

the IDE, powered om40003 down and up,

deleted launch config for the project and then started a debug session.

First instance timed out - as expected - during

the link2 to software load. Second instance progressed properly. I

received same response as in first email.

One additional bit from one of the error windows was:

Flash driver v.2 dynamic startup failed - driver init provided no flash

parameters.

Also, a bit more detail from the console:

NXP: LPC54018

DAP stride is 4096 bytes (1024 words)

Inspected v.2 External Flash Device on SPI LPC540xx_SPIFI_SFDP.cfx

Image 'LPC540xx_JEDEC_SFDP Feb 17 2020 13:57:06'

Opening flash driver LPC540xx_SPIFI_SFDP.cfx

Using SOFT reset to run the flash driver

Driver V.2 dynamic startup failed - driver Init provided no flash parameters

Flash Driver V.2 startup failed - rc Ef(55): Dynamic flash driver startup

failed to provide flash parameters.

Terminate (0x0, 0x0, 0x0) status 0x40 - driver reports init failure -

EXTSPI driver rc 15 (0xF)

chip initialization failed - Ef(55): Dynamic flash driver startup failed to

provide flash parameters.

failed to initialize flash driver LPC540xx_SPIFI_SFDP.cfx

Repeated several times, once it selected LPC540xx_SPFI_GENERIC.cfx; but

behaved the same way.

Also booted to ISP and retried (RESET and ISP1/SW3 buttons - demo NOT

executing on LCD). Again,

no success.

Also attempted mass erase using GUI Flash Tool. No luck there either.

Verified that board is loaded with

LPC54018 and that the flash is a winbond w9812G6JB. Sure seems to be a

flash driver problem.

Could it just be a bad board? or defective flash?

Regards,

Chuck

0 Kudos