nrfutil device list command fails

RE: nrfutil device list command fails

dejans — Mon, 24 Feb 2025 10:17:19 GMT

Hi,

Thank you for your feedback and suggestion for further improvement. I have forwarded your suggestion internally and relevant team will look into it.

Best regards,
Dejan

RE: nrfutil device list command fails

Ronald Hoogenboom — Fri, 21 Feb 2025 09:56:12 GMT

yes, the initial issue is resolved. Just my suggestion for further improvement remains and it is up to you if you want to take that suggestion. I think I have provided enough information so that it is clear what that suggestion is exactly.

RE: nrfutil device list command fails

dejans — Fri, 21 Feb 2025 09:50:15 GMT

Hi,

Thank you for additional information and your feedback.

[quote user="Ronald Hoogenboom"]For now, just ignoring all serial devices that don't have a com name somewhere in the FriendlyName property instead of crashing if such a device is encountered is an acceptable improvement.[/quote]

Do you have any further questions? Can we consider your initial issue resolved?

Best regards,
Dejan

RE: nrfutil device list command fails

Ronald Hoogenboom — Thu, 20 Feb 2025 10:30:54 GMT

My setup included the samsung phone on the USB bus. The line was copied from the 2251.nrfutil-device.log I attached earlier. The "No com name found" line is for the samsung phone, which has com3.

The sample demo code shows how to get to the correct com name for devices like the samsung phone that don't put the com name in the FriendlyName property using the windows API. Using this method, the nrf-device.exe can be made more 'reliable', although it might be questionable if any serial devices that have drivers that don't put the com name in the FriendlyName will ever be "supported" by nrfutil.

Indeed if you ask CoPilot how to get the com port name for usb attached serial devices in windows, he suggests to parse the FriendlyName property too at first, so I guess it is quite common practice to do that. Obviously, common practice doesn't always represent best practice.

For now, just ignoring all serial devices that don't have a com name somewhere in the FriendlyName property instead of crashing if such a device is encountered is an acceptable improvement.

RE: nrfutil device list command fails

dejans — Thu, 20 Feb 2025 10:11:37 GMT

Hi,

[quote user="Ronald Hoogenboom"]Not much, there is still:

[2025-02-18T12:40:49.073Z] [27268] DEBUG - [serialport] No com name found for \\?\USB#VID_04E8&PID_6860&Modem#7&225ecf2a&0&0001#{86e0d1e0-8089-11d0-9ce4-08003e301f73}[/quote]

Can you provide more information about *No com name found*? What was your test setup in this case?

[quote user="Ronald Hoogenboom"]I cooked up some demonstration code that uses the 'Device Parameters'.PortName to find the com name.
usbserial.cpp[/quote]

Can you elaborate on what this sample (demo code) demonstrates?

Best regards,
Dejan

RE: nrfutil device list command fails

Ronald Hoogenboom — Wed, 19 Feb 2025 14:19:23 GMT

I cooked up some demonstration code that uses the 'Device Parameters'.PortName to find the com name.
devzone.nordicsemi.com/.../usbserial.cpp

compile with g++ -o usbserial -DUNICODE -DNOMINMAX usbserial.cpp -lsetupapi

Example run:

$ ./usbserial.exe
Device Path: \\?\usb#vid_04e8&pid_6860&modem#7&225ecf2a&0&0001#{86e0d1e0-8089-11d0-9ce4-08003e301f73}, Port Name: COM3
Device Path: \\?\ftdibus#vid_0403+pid_6001+ft1m8em3a#0000#{86e0d1e0-8089-11d0-9ce4-08003e301f73}, Port Name: COM6
Device Path: \\?\ftdibus#vid_0403+pid_6001+ftynzocqa#0000#{86e0d1e0-8089-11d0-9ce4-08003e301f73}, Port Name: COM11

nrfutil device list output in the same situation:

$ nrfutil device list
852000411
product J-Link
traits jlink, seggerUsb, usb

FT1M8EM3
product US232R
ports COM6
traits serialPorts, usb

FTYNZOCQ
product UC232R
ports COM11
traits serialPorts, usb

Found 3 supported device(s)

RE: nrfutil device list command fails

Ronald Hoogenboom — Wed, 19 Feb 2025 10:08:57 GMT

Just for curiousity, what was changed?
Not much, there is still:

[2025-02-18T12:40:49.073Z] [27268] DEBUG - [serialport] No com name found for \\?\USB#VID_04E8&PID_6860&Modem#7&225ecf2a&0&0001#{86e0d1e0-8089-11d0-9ce4-08003e301f73}

While the com name is definitely there in the [Device Parameters].PortName.

Well, as long as all USB serial drivers keep putting the com name in the friendlyName property, you will be safe.

RE: nrfutil device list command fails

dejans — Tue, 18 Feb 2025 15:54:05 GMT

Hi,

[quote user="Ronald Hoogenboom"]The 2.7.16 version of nrfutil-device solves the problem! Thanks.[/quote]

This is great to hear. Thank you for this update.

Best regards,
Dejan

RE: nrfutil device list command fails

Ronald Hoogenboom — Tue, 18 Feb 2025 12:43:06 GMT

The 2.7.16 version of nrfutil-device solves the problem! Thanks.

Here is the --loglevel trace: devzone.nordicsemi.com/.../2251.nrfutil_2D00_device.log

RE: nrfutil device list command fails

dejans — Tue, 18 Feb 2025 11:10:08 GMT

Hi,

Can you try to update your "nrfutil device" to the newest version and retake logs if problem persists?

Best regards,
Dejan

RE: nrfutil device list command fails

Ronald Hoogenboom — Tue, 18 Feb 2025 08:58:09 GMT

Additionally as a reference, here is the lsusb -v of the samsung phone that makes nrfutil device list fail:

lsusb -v -s 1:44

Bus 001 Device 044: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy series, misc. (MTP mode)
Couldn't open device, some information will be missing
Device Descriptor:
bLength                18
bDescriptorType         1
bcdUSB               2.00
bDeviceClass            0
bDeviceSubClass         0
bDeviceProtocol         0
bMaxPacketSize0        64
idVendor           0x04e8 Samsung Electronics Co., Ltd
idProduct          0x6860 Galaxy series, misc. (MTP mode)
bcdDevice            4.04
iManufacturer           1 SAMSUNG
iProduct                2 SAMSUNG_Android
iSerial                 3 R9WWB0G0KBT
bNumConfigurations      1
Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0071
    bNumInterfaces          3
    bConfigurationValue     1
    iConfiguration          4
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         6 Imaging
      bInterfaceSubClass      1 Still Image Capture
      bInterfaceProtocol      1 Picture Transfer Protocol (PIMA 15470)
      iInterface              5
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81 EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200 1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01 EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200 1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82 EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x001c 1x 28 bytes
        bInterval               6
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         1
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass       2 Abstract (modem)
      bFunctionProtocol       1 AT-commands (v.25ter)
      iFunction               8
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              6
      CDC Header:
        bcdCDC               1.10
      CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          2
      CDC ACM:
        bmCapabilities       0x02
          line coding and serial state
      CDC Union:
        bMasterInterface        1
        bSlaveInterface         2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84 EP 4 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x000a 1x 10 bytes
        bInterval               9
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              7
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83 EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200 1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02 EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200 1x 512 bytes
        bInterval               0
      UNRECOGNIZED CDC: 08 24 80 0c 00 01 00 01

RE: nrfutil device list command fails

Ronald Hoogenboom — Tue, 18 Feb 2025 08:30:15 GMT

I ran the command with --log-level trace and attached the logs: devzone.nordicsemi.com/.../nrfutil_2D00_device.log devzone.nordicsemi.com/.../7183.nrfutil.log

RE: nrfutil device list command fails

dejans — Mon, 17 Feb 2025 09:55:37 GMT

Hi,

For capturing required log, you could try to run this command

nrfutil device list --log-level trace

You can find the log in the $HOME/.nrfutil/logs folder.

Best regards,
Dejan

RE: nrfutil device list command fails

Ronald Hoogenboom — Fri, 14 Feb 2025 09:55:38 GMT

I already provided the logs in the previous post. What other logs do you need?
Note that the "offending article" post is based on my assumptions of what nrfutil-device.exe is doing, which might be false. See also my post from 2 months ago, starting "OK, I guess I figured out what you're doing".If my assumptions are correct, please consider my suggestion for improvement.

RE: nrfutil device list command fails

dejans — Fri, 14 Feb 2025 08:13:53 GMT

Hi,

Can you provide any logs when using "nrfutil device list"?

Best regards,
Dejan

RE: nrfutil device list command fails

Ronald Hoogenboom — Thu, 13 Feb 2025 16:17:24 GMT

I think this is the offending article:

And this is the alternative I proposed:

All USB\Class_02&SubClass_02 devices have this PortName value in the Device Parameters subkey. No need for ComName to have no value.

RE: nrfutil device list command fails

dejans — Thu, 13 Feb 2025 15:38:42 GMT

Hi,

Thank you for the status update.
We will further look into this issue. I expect to get back to you during next week.

Best regards,
Dejan

RE: nrfutil device list command fails

Ronald Hoogenboom — Thu, 13 Feb 2025 15:09:58 GMT

Just now, I updated the device command of nrfutil to 2.7.14, but the behavior is still the same when the android phone is plugged in the USB. With the RUST_BACTRACE=full, I get:

$ RUST_BACKTRACE=full nrfutil device list
thread 'main' panicked at src\list.rs:62:30:
comName did not have a string value
stack backtrace:
0: 0x7ff672b9a641 - <unknown>
1: 0x7ff672bb1c4a - <unknown>
2: 0x7ff672b961e7 - <unknown>
3: 0x7ff672b9a485 - <unknown>
4: 0x7ff672b9bfb7 - <unknown>
5: 0x7ff672b9bd97 - <unknown>
6: 0x7ff672b9c643 - <unknown>
7: 0x7ff672b9c4c9 - <unknown>
8: 0x7ff672b9ad8f - <unknown>
9: 0x7ff672b9c0ce - <unknown>
10: 0x7ff672bceb21 - <unknown>
11: 0x7ff672bceafc - <unknown>
12: 0x7ff6727c7f55 - <unknown>
13: 0x7ff672bb1c4a - <unknown>
14: 0x7ff6727c8a72 - <unknown>
15: 0x7ff672921ffb - <unknown>
16: 0x7ff672913317 - <unknown>
17: 0x7ff6728e8ca0 - <unknown>
18: 0x7ff67295cdc5 - <unknown>
19: 0x7ff6727e3bda - <unknown>
20: 0x7ff6727bf7e2 - <unknown>
21: 0x7ff6727c4fe6 - <unknown>
22: 0x7ff6728d21da - <unknown>
23: 0x7ff672b8edec - <unknown>
24: 0x7ff6727bf96c - <unknown>
25: 0x7ff672bba44c - <unknown>
26: 0x7fff59a1259d - BaseThreadInitThunk
27: 0x7fff5a88af38 - RtlUserThreadStart
Error: Subprocess C:\Users\ronaldh\.nrfutil\bin\nrfutil-device.exe failed with unexpected exit code Some(101)

Stack backtrace:
0: git_odb_object_data
1: git_odb_object_data
2: git_midx_writer_new
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: git_odb_object_data
8: <unknown>
9: git_midx_writer_new
10: BaseThreadInitThunk
11: RtlUserThreadStart

RE: nrfutil device list command fails

dejans — Mon, 10 Feb 2025 17:01:11 GMT

Hi,

The fix has been released. Can you try to update your nrfutil-device?

Best regards,
Dejan

RE: nrfutil device list command fails

dejans — Mon, 03 Feb 2025 09:11:03 GMT

Hi,

We are getting closer to releasing the fix. I expect to get back to you by the end of the next week.

Best regards,
Dejan

RE: nrfutil device list command fails

dejans — Thu, 19 Dec 2024 19:58:54 GMT

Hi,

Thank you for this comment. I have made relevant team aware of this.

Best regards,
Dejan

RE: nrfutil device list command fails

Ronald Hoogenboom — Wed, 18 Dec 2024 16:54:48 GMT

Note that now I know the behavior is caused by the samsung phone not having the PortName included in the FriendlyName, I can confirm that with the samsung phone disconnected, the `nrfutil device list` command works normally.

RE: nrfutil device list command fails

dejans — Thu, 12 Dec 2024 15:35:36 GMT

Hi,

Thank you very much for your suggestion. We will look into your suggested solution and work further on a better fix.

Best regards,
Dejan

RE: nrfutil device list command fails

Ronald Hoogenboom — Thu, 12 Dec 2024 11:13:08 GMT

OK, I guess I figured out what you're doing.
You are traversing the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB to find 'FriendlyName's for USB devices.

I see indeed that for my 2 COM ports, there is one that has the COMx in parentheses in the FriendlyName (the BLE sniffer) and one that hasn't (the samsung phone). You are at the mercy of the USB device driver vendor it that is available or not.
However, in the subkey 'Device Parameters' ALWAYS has reliably the PortName key which has the COMx name.

I would advise to use that instead of parsing the FriendlyName to try and find the PortName, which may or may not be available.

Your're welcome!

RE: nrfutil device list command fails

Ronald Hoogenboom — Thu, 12 Dec 2024 10:08:38 GMT

I will add a few screenshots that could potentially help solving this.

There are so many 'FriendlyName's in the registry, I wasn't able to figure out which FriendlyName the nrfutil-device program finds to determine the COM name. The COM3 is my samsung phone (Copilot: The ssudmdm.sys file is a driver associated with Samsung mobile devices.) and the COM6 is the BLE sniffer.

The USB serial device (com6) is the nrf52840 dongle now programmed as BLE sniffer, so it doesn't support DFU anymore. The USB DFU is some other device (maybe also my samsung), not the nrf dongle nor the jlink.