west flash on nrf9151dk failed

RE: west flash on nrf9151dk failed

Adam.L — Mon, 03 Aug 2026 06:39:52 GMT

Did you need help setting that up as well, or do you have it? It should not be an issue setting that up. The main goal is to be able to get the USB device to reboot and re-enumerate. You could probably use SCP commands to transfer the binaries over.

RE: west flash on nrf9151dk failed

Skips — Fri, 31 Jul 2026 12:46:31 GMT

Should not be a problem... but I have to setup a shared directory between the Host and the VM
or or better yet transfer the binaries via ssh.

RE: west flash on nrf9151dk failed

Adam.L — Fri, 31 Jul 2026 06:54:00 GMT

Would you be open to getting the J-link software on your host? It seems like the device is in recovery fallback, and if we try to update it through the VM it will likely give you the "Emulator did not re-enumerate" again. After that, try rebinding and reattaching after the update.

RE: west flash on nrf9151dk failed

Skips — Thu, 30 Jul 2026 14:14:28 GMT

I have not J-Link installed on the Win10 Host..
Before to execute the west flash on the ubuntu guest, on the Win10 host the
usbipd list showed:

Also on Ubuntu guest the lsusb -t command reported:

After executing west flash on the ubuntu guest (that failed trying to reload fw on J-Link OB)
the usbipd list -u reported instead this information:

And on Ubuntu gurst lsusb -t showed that the nordic board is no more present as USB device:

I'm stuck..

RE: west flash on nrf9151dk failed

Adam.L — Thu, 30 Jul 2026 13:08:07 GMT

Strange. Unbind the device from the VM for now and check J-link commander on your host and see if there are any updates. If it does not try rebinding and reattaching the device to the VM.

RE: west flash on nrf9151dk failed

Skips — Thu, 30 Jul 2026 12:51:08 GMT

I tried to reproduce the fix you suggested, but this time the flashing command
fails with the following errors:

It seems this time it trying to upload a new firmware in the J-Link OB component
on the nRF9151DK board.

RE: west flash on nrf9151dk failed

Adam.L — Thu, 30 Jul 2026 10:37:54 GMT

That is expected, usbip attach hands over the USB device over to the VM, which is why the ports disappeared.
You can view the COM ports through the serial interfaces or RTT in the VM. If that does not work for you, I can look for an alternative solution.

RE: west flash on nrf9151dk failed

Skips — Thu, 30 Jul 2026 10:18:07 GMT

Well,

From the qemu-system-x86_64 invokation, I removed the argument

-device usb-host,bus=xhci.0,vendorid=0x1366,productid=0x1069

Next I ran on the Ubuntu VM guest the command

sudo usbip attach --remote=<HOST> --busid=3-2

but it failed because of vhcd-hcd driver was not loaded.

So I executed the command

sudo modprobe vhci-hcd

Loading the toochain with

nrfutil sdk-manager toolchain launch --ncs-version=v3.4.0 --shell

and entering the scratch project directory executing the command

west -v flash --build-dir scratch/build

produces the following output:

This seems to work...
But after the above operation, in the Window host machine, I can not see anymore COM9 or COM11 virtual serial ports where I would like to see the printing of the loaded application (Do you remember
main.c?)

RE: west flash on nrf9151dk failed

Adam.L — Thu, 30 Jul 2026 09:08:22 GMT

I would drop the line below from your QEMU invocation, just so the QEMU is not fighting over the USB as well.

-device usb-host,bus=xhci.0,vendorid=0x1366,productid=0x1069

Then run sudo usbip attach --remote=<HOST> --busid=<BUSID> through the guest VM.

RE: west flash on nrf9151dk failed

Skips — Thu, 30 Jul 2026 08:46:11 GMT

To launch in Windows10 via QEMU the Ubuntu guest VM I use a powershell script or
a bash script where there are all the options that I have to pass to qemu-system-x86_64
(the bash script is running in a bash enviroment present in a MSYS2 installation).

Both of them show the same problem.

Here the full qemu-system-x86_64 options :

-name "XUBUNTU Linux 24.04.4 VM"
-M q35 -accel whpx,kernel-irqchip=off
-cpu qemu64 -smp 8 -m 4096 -rtc base=utc
-device virtio-net-pci,netdev=net0 
-boot order=c
-drive file="xubuntu-24.04.4-minimal-amd64.qcow2",if=virtio,format=qcow2,media=disk,index=2
-netdev tap,id=net0,ifname=tap0,script=no,downscript=no
-usb -device qemu-xhci,id=xhci
-device usb-host,bus=xhci.0,vendorid=0x1366,productid=0x1069
-device usb-kbd -device usb-mouse 
-device virtio-vga-gl,xres=1920,yres=1200 -display sdl,gl=on,full-screen=on

RE: west flash on nrf9151dk failed

Skips — Thu, 30 Jul 2026 08:33:33 GMT

I run in Powershell Admin shell the first command in the form:

usbipd bind -b 3-2

It return with no errors.

I run Powershell Admin shell the second command in the form:

usbipd -o win_host_ip -b 3-2

This one complains about a missing --wsl option, but I don run my Ubuntu OS from inside
wsl..

Anyway, now the command:

usbipd list

now reports that the USB device is shared but not yet attached.

Also tried to install in the Ubuntu guest the suggested qemu-guest-tool but it complains
about a missing dependency when I run

sudo systemctl start qemu-guest-agent

RE: west flash on nrf9151dk failed

Adam.L — Thu, 30 Jul 2026 07:12:05 GMT

I believe BUSID 3-2 should be your board. Could you try running the following commands for me and see if your VM is able to detect the device now?

usbipd bind --busid=3-2
usbip attach --remote= (windows-host-ip) --busid=3-2

RE: west flash on nrf9151dk failed

Skips — Thu, 30 Jul 2026 06:42:10 GMT

Hi Adam,

yes the /etc/udev/rules.d/99-jlink.rules is present.
Here is the first part of that rules.

RE: west flash on nrf9151dk failed

Skips — Thu, 30 Jul 2026 06:36:13 GMT

Hi Adam,

the prodctod you refer was an typing error.. I meant to write productid.

Below I repost the output of lsusb:

So it seems that the VM is able to grab the USB.
Also here is the output from dmesg:

It seems that the composite USB for the J-Link cannot be configurated.
I googled around to see if there is information about that error, I found
most configuration errors with value -71 but not -32.

And here the output of usbipd list:

Ok, it seems that the USB device is neither shared nor attached..

RE: west flash on nrf9151dk failed

Adam.L — Wed, 29 Jul 2026 14:02:58 GMT

Since the USB is attached, it may be a permissions issue. Do you happen to have the 99-jlink.rules installed as well?

RE: west flash on nrf9151dk failed

Skips — Wed, 29 Jul 2026 13:21:53 GMT

After the above changes, launching the lsusb command produce the following output:

It seems that the added options in Qemu for usb pass-through are ok..
But error (Cannot connet to the probe/programmer) is still present..

RE: west flash on nrf9151dk failed

Adam.L — Wed, 29 Jul 2026 12:04:51 GMT

Hi,

A few things, in your recent comment you input productod instead of productid. That might just be a typo, but just in case it wasn't QEMU might error from that or ignore the typo. Also, could you run lsusb, I am curious to see if your VM was able to grab the USB.

If not, we can try to see if device is shared in the first place. Just open up powershell on your Windows Host and run usbipd list. If the USB device has been binded properly, you should see "Shared" next to it and if it is claimed by your VM, you should see "Attached".

Best,

Adam

RE: west flash on nrf9151dk failed

Skips — Wed, 29 Jul 2026 10:04:40 GMT

Also added in my qemu invokation of Ubuntu VM the following arguments:

-device qemu-xhci -usb -device usb-host,vendorid=0x1366,productod=0x1069

but still obtaining the final error:

1051246391: Emulator error: Failed to open connection: Cannot connect to the probe/programmer. (Generic)

RE: west flash on nrf9151dk failed

Skips — Tue, 28 Jul 2026 14:55:37 GMT

Another piece of infomation: