Error in SDK v3.0.1 when flashing: unexpected argument --x-ext-mem-config-file found

[Marko W]

When flashing with SDK v3.0.1 the following error occurs:

-- west flash: using runner nrfutil
-- runners.nrfutil: mass erase requested
-- runners.nrfutil: reset after flashing requested
-- runners.nrfutil: Flashing file: *****\firmware\observer\build\merged.hex
error: unexpected argument '--x-ext-mem-config-file' found

  tip: a similar argument exists: '--x-qspi-config-file'

Usage: nrfutil device <--json|--json-pretty|--skip-overhead> <--json|--json-pretty> <--x-qspi-config-file <PATH>>

For more information, try '--help'.
-- runners.nrfutil: Board with serial number 1050202762 flashed successfully.

If I use Toolchain and SDK v2.9.1 it works without problems:

-- west flash: using runner nrfjprog
-- runners.nrfjprog: mass erase requested
-- runners.nrfjprog: reset after flashing requested
-- runners.nrfjprog: Flashing file: *****\firmware\observer\build\merged.hex
[ #################### ]   0.304s | Erase file - Done erasing                                                          
[ #################### ]   0.544s | Program file - Done programming                                                    
[ #################### ]   0.553s | Verify file - Done verifying                                                       
Enabling pin reset.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050202762 flashed successfully.

[Menon]

Hello Marko,

I am able to see the same error as you, but as mentioned by Libor Votocek, the nrfutil upgrade device command resolved my issue. I am also on Windows 11. I am sharing the logs where I saw the error message and then succeeded in flashing after running the command.

Flashing build to 683816873
C:\WINDOWS\system32\cmd.exe /d /s /c "west flash -d c:\ncs\v3.0.0\zephyr\samples\basic\blinky\build --dev-id 683816873 --erase"

-- west flash: rebuilding
[0/5] Performing build step for 'blinky'
ninja: no work to do.
[2/5] No install step for 'blinky'
[3/5] Completed 'blinky'
[4/5] cmd.exe /C "cd /D C:\ncs\v3.0.0\zephyr\samples\basic\blinky\build\_sysbuild && C:\ncs\toolchains\0b393f9e1b\opt\bin\cmake.exe -E true"
-- west flash: using runner nrfutil
-- runners.nrfutil: mass erase requested
-- runners.nrfutil: reset after flashing requested
-- runners.nrfutil: Flashing file: C:\ncs\v3.0.0\zephyr\samples\basic\blinky\build\merged.hex
error: unexpected argument '--x-ext-mem-config-file' found

Usage: nrfutil device <--json|--json-pretty|--skip-overhead> <--json|--json-pretty>

For more information, try '--help'.
-- runners.nrfutil: Board with serial number 683816873 flashed successfully.
* Terminal will be reused by tasks, press any key to close it.

* Executing task: nRF Connect: Flash: blinky/build (active)

Flashing build to 683816873
C:\WINDOWS\system32\cmd.exe /d /s /c "west flash -d c:\ncs\v3.0.0\zephyr\samples\basic\blinky\build --dev-id 683816873 --erase"

-- west flash: rebuilding
[0/5] Performing build step for 'blinky'
ninja: no work to do.
[2/5] No install step for 'blinky'
[3/5] Completed 'blinky'
[4/5] cmd.exe /C "cd /D C:\ncs\v3.0.0\zephyr\samples\basic\blinky\build\_sysbuild && C:\ncs\toolchains\0b393f9e1b\opt\bin\cmake.exe -E true"
-- west flash: using runner nrfutil
-- runners.nrfutil: mass erase requested
-- runners.nrfutil: reset after flashing requested
-- runners.nrfutil: Flashing file: C:\ncs\v3.0.0\zephyr\samples\basic\blinky\build\merged.hex
-- runners.nrfutil: Erasing non-volatile memory (ERASEALL)
-- runners.nrfutil: Programming image
-- runners.nrfutil: Verifying image
-- runners.nrfutil: Reset
-- runners.nrfutil: Board with serial number 683816873 flashed successfully.
* Terminal will be reused by tasks, press any key to close it.

Kind Regards,

Abhijith

[jay]

yes, its completely worked for me  

[RogerC60]

After reading this I tried nrfutil upgrade device again, and got the same response that it was already at the newest version (2.3.6). Then I discovered the self-upgrade command, and ran that, It did update. After that, nrfutil upgrade device did upgrade to 2.10.2. Again, this is on Windows 11.

[jay]

i was facing issue is like 

Fullscreen nrf52840 flashing failed log.txt Download

logs : 


Flashing build_nrf54840dk to 1050266177
C:\WINDOWS\system32\cmd.exe /d /s /c "west flash -d c:\Users\J\Downloads\ncs-inter-main\l9\l9_e5\build_nrf54840dk --dev-id 1050266177"

-- west flash: rebuilding
[0/10] Performing build step for 'l9_e5'
ninja: no work to do.
[1/10] Performing build step for 'mcuboot'
ninja: no work to do.
[4/10] cmd.exe /C "cd /D C:\Users\J\Downloads\ncs-inter-main\l9\l9_e5\build_nrf54840dk\_sysbuild && C:\ncs\toolchains\0b393f9e1b\opt\bin\cmake.exe -E true"
[6/9] No install step for 'mcuboot'
[7/9] Completed 'mcuboot'
[8/9] cmd.exe /C "cd /D C:\Users\J\Downloads\ncs-inter-main\l9\l9_e5\build_nrf54840dk\_sysbuild && C:\ncs\toolchains\0b393f9e1b\opt\bin\cmake.exe -E true"
-- west flash: using runner nrfutil
-- runners.nrfutil: reset after flashing requested
-- runners.nrfutil: Flashing file: C:\Users\J\Downloads\ncs-inter-main\l9\l9_e5\build_nrf54840dk\merged.hex
error: unexpected argument '--x-ext-mem-config-file' found

tip: a similar argument exists: '--x-qspi-config-file'

Usage: nrfutil device <--json|--json-pretty|--skip-overhead> <--json|--json-pretty> <--x-qspi-config-file <PATH>>

For more information, try '--help'.
-- runners.nrfutil: Board with serial number 1050266177 flashed successfully.
* Terminal will be reused by tasks, press any key to close it.

 


my issue resolved after this execution.



if you facing same then will work for you...
share your logs..