west flash --runner=jlink failes with runner.jlink not found

[emmdaniel]

Hi All,
This is more of a question as maybe I'm doing something wrong.
I setup my zephyr environment yesterday on an Ubuntu 22.04, following the provided user guide, all worked fine, I was able to compile and flash an ESP32 and RPI4B.
I setup also the JLink as I have a dongle around and saw it can be used, so I downloaded the JLinkExe from Segger and installed it.
Tried to see if the connection with the dongle is fine and although I didn't have a target connected to Jlink I could see all went well as it was failing when trying to detect the target.
Today I got my hands on a RPI Pico and tried to flash the blinky example.
Compilation went fine, but, when trying to flash I get the following error:

╰$ west flash --runner jlink                                                                                                                                                          
-- west flash: rebuilding
[1/11] Performing build step for 'second_stage_bootloader'
ninja: no work to do.
[2/2] cd /home/mdaniel/zephyrproject/zephyr/build/zephyr && /home/mdaniel/zephyrproject/.venv/bin/pyt.../build/check_init_priorities.py --elf-file=/home/mdaniel/zephyrproject/zephyr/build/zephyr/zephyr.elf
-- west flash: using runner jlink
-- runners.jlink: JLink version: 7.94b
-- runners.jlink: Flashing file: /home/mdaniel/zephyrproject/zephyr/build/zephyr/zephyr.hex
FATAL ERROR: command exited with status 1: /opt/SEGGER/JLink_V794b/JLinkExe -nogui 1 -if swd -speed auto -device RP2040_M0_0 -CommanderScript /tmp/tmprktku0xojlink/runner.jlink -nogui 1

So I ran manually that command and saw it fails because it can't find the /tmp/tmprktku0xojlink/runner.jlink
The /tmp is not restricted to non sudo users, so it's not an access issue. I see the folder name changes with every west flash command, so I'm assuming the runner.jlink is generated every time. But for some reason it fails and no other error is generated.
I reinstalled the entire setup once again, not helping.

Any suggestion much appreciated.
Thanks.

[DerekSnell]

Hi @emmdaniel ,
The JLink commander script is generated, and is removed after the west flash command, so it is expected that commander script will be missing afterwards. When I have issues with the JLink runner, I run the West command in verbose mode by adding the -v argument to the command below. That should display all the output from the JLink commander tool directly, and help identify the issue.

west -v flash --runner jlink

Hope that helps

[emmdaniel]

Thanks @DerekSnell , I didn't write in my original post that I tried already the verbose mode:

╰$ west -v flash --runner jlink
-- west flash: rebuilding
cmake version 3.22.1 is OK; minimum version is 3.13.1
Running CMake: /usr/bin/cmake --build /home/mdaniel/zephyrproject/zephyr/build
[1/11] Performing build step for 'second_stage_bootloader'
ninja: no work to do.
[2/2] cd /home/mdaniel/zephyrproject/zephyr/build/zephyr && /home/mdaniel/zephyrproject/.venv/bin/pyt.../build/check_init_priorities.py --elf-file=/home/mdaniel/zephyrproject/zephyr/build/zephyr/zephyr.elf
-- west flash: using runner jlink
runners.jlink: JLINKARM_GetDLLVersion()=79402
-- runners.jlink: JLink version: 7.94b
runners.jlink: JLink commander script:
ExitOnError 1
r
loadfile "/home/mdaniel/zephyrproject/zephyr/build/zephyr/zephyr.hex"
g
writeDP 1 0
readDP 1
q
-- runners.jlink: Flashing file: /home/mdaniel/zephyrproject/zephyr/build/zephyr/zephyr.hex
runners.jlink: /opt/SEGGER/JLink_V794b/JLinkExe -nogui 1 -if swd -speed auto -device RP2040_M0_0 -CommanderScript /tmp/tmpipvbivnyjlink/runner.jlink -nogui 1
SEGGER J-Link Commander V7.94b (Compiled Dec 13 2023 17:05:47)
DLL version V7.94b, compiled Dec 13 2023 17:05:24


J-Link Command File read successfully.
Processing script file...
J-Link>ExitOnError 1
J-Link Commander will now exit on Error
J-Link>r
J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
Hardware version: V8.00
J-Link uptime (since boot): N/A (Not supported by this model)
S/N: 58000399
License(s): FlashBP, FlashDL, GDB
VTref=0.000V
Target connection not established yet but required for command.
Device "RP2040_M0_0" selected.


Connecting to target via SWD
Cannot connect to target.

Script processing completed.

FATAL ERROR: command exited with status 1: /opt/SEGGER/JLink_V794b/JLinkExe -nogui 1 -if swd -speed auto -device RP2040_M0_0 -CommanderScript /tmp/tmpipvbivnyjlink/runner.jlink -nogui 1

The only thing I can notice from this output is that the commander script file is not generated, I might need to debug that python script, but other than that this doesn't tell me anything.

Regards.

[thedjnK]

VTref=0.000V

No device is connected

[emmdaniel]

@thedjnK That was the issue, thanks!