west flash on nrf9151dk failed

[Skips]

Hi,

I have an Ubuntu 22.04 LTS virtual machine where I installed the version v3.4.0 of all the needed
tools and libraries as explained in
nrfconnectdocs.nordicsemi.com/.../install_ncs.html.

I started a scratch project on a nRF9151DK board that I successfully built.
Specifically I executed the following steps:

1. Cloning the version v3.4.0 of github.com/.../ncs-example-application project;
2. Executed from the root project directory the command
   nrfutil sdk-manager toolchain launch --ncs-version=v3.4.0 --shell;
3. In the root project directory created a directory scratch with the an empty
   prj,conf file and a CMakeLists.txt and a main.c file whose contents are
   
   - CMakeLists.txt
   

        cmake_minimum_required(VERSION 3.20.0)
        find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
        project(hello_work)
        target_sources(app PRIVATE src/main.c)Code

   
   
   - main.c
   

       #include <zephyr/kernel.h>
       #include  <zephyr/sys/printk.h>
   
       int main(void)
       {
           while (1) {
               printk("Hello World!\n);
               k_msleep(1000);
           }
           
           return 0;
       }

   
   
   
4. In the root project directory successfully executed the command
   west build -b nrf9151dk_nrf9151 -p=always scratch
5. I attaches the nrf9151dk board to an usb type-C port in the PC.
   Immediately a Windows Explorer popped up showing that an usb mass storage
   device was detected. In the VM in the root project directory I unsuccessfully
   executed west flash --build-dir scratch/build --runner jlink obtaining this
   error screen
   
   

When I set up the VM, I ran the sudo dpkg -i nrf-udev_1.0.1-all.deb to add udev rules
for the Ubuntu guest.

I also copied udev rules:
sudo cp ~/ncs/toolchains/fbf7391cab/usr/lib/udev/rules.d/60-dfu-util.rules /etc/udev/rules.d/
followed by sudo udevadm control --reload but with no success.
Also inspectioning those rules they seem suitable for STM32 microcontrollers/

Anyway, running nrfutil device list --traits seggerUsb inside the VM reported Supported devices found: 0

Are someone that already faced this kind of problems?
Thanks in advance for any help.

[Adam Le]

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 

[Skips]

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..

[Skips]

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

[Adam Le]

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. 

[Skips]

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?)

[Adam Le]

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.

[Skips]

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.

[Adam Le]

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.

[Skips]

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..

[Adam Le]

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. 

[Skips]

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.

[Adam Le]

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.