Hello,
I am testing a custom board based on LCP54018J2MET180. I am trying to flash a simple helloworld program using MCUXpresso and MCU-Link pro as programmer. I have downloaded the SDK for the LPC54018J2, this device has an internal QSPI flash of 2M.
Whenever I try to flash the program I get stuck always on the flash drivver loading, since it doen't detect the flash from the device. I have tied IS0 and ISP1 high and ISP2 low so the system boots checking for the flash.
I have double checked that the lines regarding the SPIFI driver are not used in the board.
The output of the MCUXpresso is as follows:
MCUXpresso IDE RedlinkMulti Driver v11.5 (Dec 16 2021 12:47:27 - crt_emu_cm_redlink build 2)
Found chip XML file in ~/Documents/MCUXpresso_11.5.0_7232/workspace/Trial/Debug/LPC54018J2M.xml
Reconnected to existing LinkServer process.
Probe Firmware: MCU-LINK Pro (r0CF) CMSIS-DAP V2.241 (NXP Semiconductors)
Serial Number: C5UFCSNDLYZKR
VID:PID: 1FC9:0143
USB Path: /dev/hidraw3
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 = 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: 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: LPC54018J2M
DAP stride is 4096 bytes (1024 words)
Inspected v.2 External Flash Device on SPI LPC540xx_SPIFI_SFDP.cfx
Image 'LPC540xx_JEDEC_SFDP Dec 16 2021 12:43:33'
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)
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
I have seen one similar case in the forum with a custom board based on LPC54018 IoT board and using also an LPC54018J2MET180 chip with similar problem, but without solution.
Any help or idea will be wellcome.
Luis
Hi @luimarma
Did you find a solution for your problem?
I am using the LPC54018J4M with 4MB internal SPIFI flash and i am also facing problems. In my case, I can flash but the program will not start but hang somewhere in BOOT ROM....
my ticket is the follwing:
Re: XIP, program not starting on LPC54018J4M custo... - NXP Community
best regards
Ron
Hi Ron,
I didn't find a solution yet. I switched in the meantime to LPC54606J512 that uses normal internal flash rather than QSPI flash. I have lost some features but in the other hand I could probe that my original design was fully working. I will dig more on LCP54018 using Segger J-Link probe in SWD mode, since it is said to be compatible for LPC54018JMET180 but yest have to test.
It is a pity that I could not get anymore backup on LCP54018 since I am infinally interested on the S series with enhanced security features.
Already replaced with another LCP54018J2MET180.
I have also made a version of the same board but using LCP54608 that has on-chip flash, but not attached to SPIFI. With that one flashing works well, but not with LCP54018J2MET180.
With LCP54018J2MET180 I always get the following error.
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
I have checked in the documentation and LCP54018J2MET180 has internally a flash marked as Winbond W25Q32JV. The LPC540xx_SPIFI_GENERIC.cfx has support for W25Q32FV chip, but it looks that they share the same ID codes. I tried to recompile the driver setting the size of the W25Q32FV to 2Mb but still no success, the chip cannot be programmed.
Can anyone help here? How is it possible there is no way to program the internal Flash?
Where's my mistake?
Hi,
Pls try to select the flash driver LPC540xx_SPIFI_GENERIC.cfx and have a try.
If it does not work, I suppose it is complex, you have to check the user manual of your own spifi flash on custom board, and develop the driver yourself.
Hope it can help you
BR
XiangJun Rong
The spifi flash is not a custom one, it is the internal spifi flash of LCP54018J2MET180.
Using LPC540xx_SPIFI_GENERIC.cfx driver doesn't help also.
Any help would be wellcome.
Thanks in advance
Hi,
Pls try to replace with another LCP54018J2MET180 and have a try.
BR
XiangJun Rong
Ok, I will test with another unit, but this will take long time since this needs a new board assembly.