LPC54018 driver Init provided no flash parameters

[KTech]

Hallo everyone,

I recently created a new project in MCUXpresso to work with FreeRTOS on my LPC54018 on the OM40003 Bord. Sadly, every attempt to start a debugging session ends in an “Driver V.2 dynamic startup failed - driver Init provided no flash parameters” Error. (detail below)

Even with the example Projects / clean FreeRTOS I encounter the same problem. As an older example Project worked on my Controller, I started to test different SDK versions. In version 2.8.2 and 2.6.0 neither new Projects nor examples worked. On the 2.3.0 Version only example Projects could run.

I also noticed the default SPIFI driver was changing from LPC540xx_SPIFI_GENERIC.cfx to LPC540xx_SPIFI_SFDP.cfx. sadly, I found no further information about those.

As I tried to flash the controller directly with the MCUExpresso flashing tool and the good version from the 2.3.0 SDK, I got another error: “File 'lpcxpresso54018v2.3_shell.axf' load failure: Ef(11). No flash configured.” Flash attempts with the other non debugable version got me back to the old error. But this time with a minor variation. “Terminate (0x0, 0x0, 0x0) status 0x40 - driver reports init failure - EXTSPI driver rc 15 (0xF)” instead of the former “Terminate (0x0, 0x0, 0x0) status 0x40 - driver reports init failure - EXTSPI driver rc 13 - No supported SPIFI device found”

It’s probably also worth mentioning, that I have to boot the controller into a non-default boot state (ISP-Mode) or end up with an “Cannot halt processor” error.

Also, I tried vector catch as mentioned in the various other posts with a similar problem.

Thanks,

                Karl

MCUXpresso IDE v11.3.1 [Build 5262] [2021-04-02]

SDK: LPCXpresso54018 version 2.8.2/ 2.6.0 / 2.3.0

Board: OM430003 with LPC54018 Rev E

破坏者

MCUXpresso IDE RedlinkMulti Driver v11.3 (Mar 30 2021 16:50:12 - crt_emu_cm_redlink build 18)

Found chip XML file in C:/dev/MCUXpressoIDE_11.3.1_5262/Workspace/bare metal_v2.3/Debug\LPC54018.xml

(  5) Remote configuration complete

Reconnected to existing LinkServer process.

Probe Firmware: LPC-LINK2 CMSIS-DAP V5.361 (NXP Semiconductors)

Serial Number:  LSAUAQBQ

VID:PID:  1FC9:0090

USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#8&13ccc672&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

Using memory from core 0 after searching for a good core

debug interface type      = CoreSight DP (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: Disabled.

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)

XML Error - no license-type XML file 'crt_common.xme' on path.

note - part information contained no product license-type data

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

Image 'LPC5460x Generic SPIFI Mar 22 2021 08:18:07'

Opening flash driver LPC540xx_SPIFI_GENERIC.cfx

Sending VECTRESET to run 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 13 - No supported SPIFI device found

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

failed to initialize flash driver LPC540xx_SPIFI_GENERIC.cfx

[Alice_Yang · Accepted solution]

Hello KTech,

Try to erase chip based on ISP mode:

pressing ISP button and do not release,  and click erase button as below:

Pay attention, open a new workspace and import new led project to try.

BR

Alice

[KTech]

Hallo Alice

thank you very much, after the Mass erase I can now debug again. Pressing the ISP buttons for the entire time when using the chip tool was the solution.

PS: for everyone with the same problem ISP button 0 was the one to press.  

Thanks,

                Karl

[Alice_Yang]

Hello,

Please first use a simple demo project LED to test.

If still can't work, please take a video or screenshots show your steps.

Does your board can work well before?

BR

Alice

[KTech]

Hallo Alice,

yes my board worked well bevor, using mainly test projects from the 2.3.0 SDK Version.

Now I cannot get anything to work being created from the newer SDK versions, while the old 2.3 examples are still running fine.

Gpio_led_out SDK version 2.8.2

1. I click import SDK example.
2. I select the LPC54018 Board.
3. I select the LED-project. (See image)
4. I reset the LPC-Bord by pressing reset and Button 1 for SPI Boot mode. Otherwise, I get the cannot hold processor error
5. I start Debugging.
6. I confirm the Probe selection.
7. Error (See images)

This very exact process works fine with v2.3.0 examples but fails as soon as I try the same with a new project.

Thanks,

                Karl