LPC54018 Error on programming flash (Ef(11). No flash configured.)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

LPC54018 Error on programming flash (Ef(11). No flash configured.)

3,080 Views
MRenshaw
Contributor I

Hello,

I have been trying to program the external flash on a LPC54018 Dev board (OM40003) and have been unable to get it working. I am using the latest version of MCUXpresso IDE, trying to program on the lwip_udpecho demo from the LPCXpresso54018 SDK. I am using default settings and get the following log in the terminal:

Executing flash operation 'Program' (Program file into flash: lpcxpresso54018_lwip_udpecho_bm.axf) - Mon Nov 15 15:44:27 GMT 2021
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.4 (Sep 13 2021 15:04:52 - crt_emu_cm_redlink.exe build 16)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in C:/s_w_wip/MCUXpresso Workspaces/UDP/lpcxpresso54018_lwip_udpecho_bm/Debug\LPC54018.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.182 (NXP Semiconductors)
Serial Number: JSAVBQER
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#9&19a8ec3e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
( 30) Emulator Connected
( 40) Debug Halt
( 50) CPU ID
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)
( 65) Chip Setup Complete
Connected: was_reset=true. was_stopped=false
( 70) License Check Complete
File 'lpcxpresso54018_lwip_udpecho_bm.axf' load failure: Ef(11). No flash configured.
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

 

I have had success erasing the flash following the same process but selecting "Mass Erase" after connecting to the device using the GUI Flash Tool, this was certainly a success as the pre-loaded program on the dev board no longer run on power on.

Is there something I have missed where I have to configure the flash separately?

 

Many thanks

Michael

Labels (1)
0 Kudos
9 Replies

2,606 Views
NVazquez
Contributor IV

I am getting the same error, I have a custom board with controller lpc540s16. 

 

If I have "Link application to RAM" selected, that means the controller should not touch the ROM and download and execute from RAM, is that right?

 

 

 

I get this error when "link application to RAM" is selected

 

NVazquez_0-1657819131504.png

 

and I get this, when "Plain load image" is selected

NVazquez_1-1657819212893.png

 

 

 

 

0 Kudos

3,014 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello,

 

Use the GUI Flash Tool ease the whole flash firstly.

Alice_Yang_0-1637565716813.png

If still work, please pressing ISP button in the whole erase/program or debug time .

 

 

0 Kudos

1,105 Views
ecollado
Contributor I

Hello there I'm having the same issue that NVazquez had with a mimxrt1020 MCU and a Link to RAM application, I even tried using the GUI Flash Tool and I have the same result. It works when I debug the board but I'm in the process of creating the flashing script for releasing our product, that's why we need to make it work without the MCUxpresso IDE.

I'll appreciate any idea. Thanks in advace.

ERROR:

Executing flash operation 'Program' (Program file into flash: dcdc_pre_bootloader.bin) - Mon Oct 23 09:48:51 EDT 2023
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.7 (Mar 22 2023 09:52:55 - crt_emu_cm_redlink.exe build 13)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in D:/harv/spot_dcdc_arm/bootloader/mimx_pre_bootloader/dcdc_pre_bootloader/Debug\MIMXRT1021xxxxx.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
============= SCRIPT: RT1020_connect.scp =============
RT1020 Connect Script
DpID = 0BD11477
APID = 0x04770041
Disabling MPU
Configure FlexRAM for 128KB OC RAM, 64KB I-TCM, 64KB D-TCM
Finished
============= END SCRIPT =============================
Probe Firmware: MCU-LINK (r0FF) CMSIS-DAP V2.263 (NXP Semiconductors)
Serial Number: DTH4WNFIRYX5I
VID:PID: 1FC9:0143
USB Path: \\?\hid#vid_1fc9&pid_0143&mi_00#7&295a876e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
( 30) Emulator Connected
( 40) Debug Halt
( 50) CPU ID
debug interface type = CoreSight DP (DAP DP ID 0BD11477) over SWD TAP 0
processor type = Cortex-M7 (CPU ID 00000C27) 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: 0BD11477. CpuID: 00000C27. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FD000: CID B105100D PID 000008E88C ROM (type 0x1)
ROM 1 E00FE000: CID B105100D PID 04000BB4C8 ROM (type 0x1)
ROM 2 E00FF000: CID B105100D PID 04000BB4C7 ROM (type 0x1)
ROM 3 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
ROM 3 E0001000: CID B105E00D PID 04000BB002 Gen DWT (type 0x0)
ROM 3 E0002000: CID B105E00D PID 04000BB00E Gen (type 0x0)
ROM 3 E0000000: CID B105E00D PID 04000BB001 Gen ITM (type 0x0)
ROM 2 E0041000: CID B105900D PID 04001BB975 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
ROM 2 E0042000: CID B105900D PID 04004BB906 CSt type 0x14 Debug Control - Trigger, e.g. ECT
ROM 1 E0040000: CID B105900D PID 04000BB9A9 CSt type 0x11 Trace Sink - TPIU
ROM 1 E0043000: CID B105F00D PID 04001BB101 Sys (type 0x0)
NXP: MIMXRT1021xxxxx
DAP stride is 1024 bytes (256 words)
( 65) Chip Setup Complete
Connected: was_reset=false. was_stopped=true
( 70) License Check Complete
File 'dcdc_pre_bootloader.bin' load failure: Ef(11). No flash configured.
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

 

CMD:

crt_emu_cm_redlink --flash-load-exec "D:\harv\spot_dcdc_arm\bootloader\mimx_pre_bootloader\dcdc_pre_bootloader\Debug\dcdc_pre_bootloader.bin" -g --debug 2 --vendor NXP -p MIMXRT1021xxxxx --load-base=0x0 --ConnectScript RT1020_connect.scp --reset SOFT --flash-driver-reset SOFT --probeserial DTH4WNFIRYX5I -CoreIndex=0 -x D:/harv/spot_dcdc_arm/bootloader/mimx_pre_bootloader/dcdc_pre_bootloader/Debug --flash-dir C:/nxp/MCUXpressoIDE_11.7.1_9221/ide/plugins/com.nxp.mcuxpresso.tools.bin.win32_11.7.1.202303220859/binaries/Flash --flash-dir C:/Users/ElvysCollado/Documents/MCUXpressoIDE_11.7.1_9221/workspace/.mcuxpressoide_packages_support/MIMXRT1021xxxxx_support/Flash --flash-hashing

0 Kudos

3,011 Views
MRenshaw
Contributor I

Hi,

 

When attempting a full flash erase I got a similar error to trying to write it:

Executing flash operation 'Erase' (Erase flash) - Mon Nov 22 08:36:58 GMT 2021
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.4 (Sep 13 2021 15:04:52 - crt_emu_cm_redlink.exe build 16)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in C:/s_w_wip/MCUXpresso Workspaces/UDP/lpcxpresso54018_lwip_udpecho_bm/Debug\LPC54018.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.182 (NXP Semiconductors)
Serial Number: JSAVBQER
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#9&19a8ec3e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
( 30) Emulator Connected
( 40) Debug Halt
( 50) CPU ID
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)
( 65) Chip Setup Complete
Connected: was_reset=true. was_stopped=false
( 70) License Check Complete
Mass Erase - can't find a programmable memory area at 0xFFFFFFFF
Failed to erase flash: Ef(11). No flash configured.
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

However I had previously tried a flash erase that was successful and had wiped the built-in demo off the board.

 

0 Kudos

2,995 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello ,

 

I recommend the last try: Change to a new USB line, open a new IDE workspace, open simple hello world project, use "Debug" button :

Alice_Yang_0-1637723694487.png

 

If still can't work. Maybe there is a broken image in your flash, recommend use blhost erase the whole flash , detail steps please refer to:

https://community.nxp.com/t5/LPC-Support/Use-blhost-to-program-erase-LPC540xxM-LPC54S0xxM-flash/ta-p...  

 

BR

Alice

 

0 Kudos

3,051 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello MRenshaw,

How about program hello world or simple LED sdk demo?

Please take a video or screenshots show your steps.

 

BR

Alice

0 Kudos

3,042 Views
MRenshaw
Contributor I

I have tried programming the Hello World demo, it has the same error.

Here is how the board is plugged in:

IMG_20211118_103831__01.jpg

Here is the device selected in the GUI Flash Tool:

FlashTool1.png

Here are the settings used when programming the board:

FlashTool2.png

I have also tried to program using the .bin file generated by the build but also had the same error.

The build settings have not been touched since importing the SKD example projects so are as default.

0 Kudos

3,073 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello MRenshaw,

Please configure board refer to readme. txt under project, and also make you use the right SDK related your board.

 

BR

Alice

0 Kudos

3,060 Views
MRenshaw
Contributor I

Hi Alice,

The SKD is for the correct board and the board is configured as described in the readme.

0 Kudos