Trouble Connecting to nRF5340 via nRFConnect Extension (WSL Environment)

RE: Trouble Connecting to nRF5340 via nRFConnect Extension (WSL Environment)

Valentin Otte — Tue, 07 Jan 2025 17:14:13 GMT

I also tested downgrading the Jlink Software/Driver version (8.12, 8.10l, 8.10k) just in case this affects the interaction with the microcontroller, and I have the same issue.

RE: Trouble Connecting to nRF5340 via nRFConnect Extension (WSL Environment)

Valentin Otte — Tue, 07 Jan 2025 13:49:05 GMT

Hi Bendik,

Thank you for your quick response!

Before changing the WSL configuration, I tested the Windows version of the SEGGER JLink and nRF Command Line Tools to check if the connection with the device was possible.

I tested JLink separately, and similar to WSL, I couldn’t connect to the device using either JTAG or SWD. (See attached images.)

To rule out potential configuration issues, I attempted to upload firmware to the board using the command line tools but encountered the same problem.

The respective log file is attached here.

devzone.nordicsemi.com/.../3487.log.log

I re-checked the USB cable, tag-connect cable, and other hardware components. Everything appears to be in working order. Interestingly, the board restarts after a failed connection, suggesting a connection attempt is being made.

Are there any additional tests or debugging steps you’d recommend to identify the issue?

I appreciate your support!

Best regards,

Valentin.

RE: Trouble Connecting to nRF5340 via nRFConnect Extension (WSL Environment)

Bendik Heiskel — Fri, 03 Jan 2025 15:06:24 GMT

Hi,

I haven't tested using the linux version of nrfjprog, jlinkexe etc. in WSL with USBPID. Instead when using WSL I have replaced the executables for nrfjprog and JLinkExe in /usr/bin with scripts that instead use the windows versions of the tools from within WSL. This has the benefit of not needing to pass the USB device over to the linux environment to connect to them.

Here's the scripts for replacing nrfjprog and JLinkExe with the windows tools:

/usr/bin/JLinkExe:

#!/bin/bash
 
ARGS=("$@")
JLINKEXE='/mnt/c/Program Files/SEGGER/JLink/JLink.exe'
WSLROOT='\\wsl$\Ubuntu'
 
for IDX in ${!ARGS[*]}; do
        ARG=${ARGS[$IDX]}
        case "$ARG" in
        -*)
                ;;
        *)
                if [ -e "$ARG" ]; then
                        NEW=$(wslpath -aw "$ARG" 2>/dev/null) || \
                        NEW="$WSLROOT"$(readlink -f "$ARG" | sed 's@/@\\@g')
                        ARGS[$IDX]=$NEW
                fi
                ;;
        esac
done
 
exec "$JLINKEXE" "${ARGS[@]}"

/usr/bin/nrfjprog:

#!/bin/bash
 
ARGS=("$@")
NRFJPROG='/mnt/c/Program Files/Nordic Semiconductor/nrf-command-line-tools/bin/nrfjprog.exe'
WSLROOT='\\wsl$\Ubuntu'
 
for IDX in ${!ARGS[*]}; do
        ARG=${ARGS[$IDX]}
        case "$ARG" in
        -*)
                ;;
        *)
                if [ -e "$ARG" ]; then
                        NEW=$(wslpath -aw "$ARG" 2>/dev/null) || \
                        NEW="$WSLROOT"$(readlink -f "$ARG" | sed 's@/@\\@g')
                        ARGS[$IDX]=$NEW
                fi
                ;;
        esac
done
 
exec "$NRFJPROG" "${ARGS[@]}"

The scrips need to be set as a executable using chmod +x /usr/bin/nrfjprog /usr/bin/JLinkExe

I also recommend to rename the existing executables before replacing them, incase you need to revert the changes.

It should be possible to do the same for other CLI tools, but these are the only ones I have tested.

This approach requires nRF-Command-Line-Tools and SEGGER JLink to be installed on the host windows system.

Best regards,

Bendik