Unable to flash a build of the sample blinky following the nRF Connect SDK Fundamentals tutorial

Hey everyone,

I am new to the development of Nordic chips so I might get some things wronog here or there.

I am using windows 11 and am trying to flash a nRF54l15 DK board

Lets start with the sittuation. I am attempting to follow the nRF Connect SDK Fundamentals tutorial with a new nRF54l15-DK board. I followed all the steps for installing the nRF Connect SDK and VS Code. I then imported, build and tried to flash the code. When I did I had the fatal error that the nrfutil was not installed or in the path. I downloaded that, placed it in the blinky folder and used my windows command prompt to install it. After having done that, I lost the nrfutil fatal error but gained a new one. I also tried connecting using the quick start of the nRF connect for desktop and got to the program step. Here the Erase device shows green but the others are red.

Here is the log of the quick start, which has the same error I get from VSCode's terminal.

2025-01-10T11:01:13.537Z INFO Initialising the bundled nrfutil device
2025-01-10T11:01:13.545Z DEBUG Started watching devices
2025-01-10T11:01:14.562Z INFO Using the bundled core version for nrfutil device: 7.13.0
2025-01-10T11:01:15.012Z INFO Using nrfutil-device version: 2.7.5
2025-01-10T11:01:15.012Z INFO Using nrf-device-lib version: 0.17.41
2025-01-10T11:01:15.012Z INFO Using nrfjprog DLL version: 10.24.2
2025-01-10T11:01:15.012Z INFO Using JLink version: JLink_V7.94i
2025-01-10T11:01:16.538Z DEBUG Selected device: nRF54L15 DK
2025-01-10T11:01:16.558Z DEBUG Changed step: Info
2025-01-10T11:01:23.661Z DEBUG Changed step: Rename
2025-01-10T11:02:17.819Z DEBUG Changed step: Program
2025-01-10T11:02:45.962Z ERROR  NRFDLException(1): [Probe] Emulator error: No emulator with connection info 'Usb(JLinkSerialNumber(1057701372))' was found
2025-01-10T11:02:45.967Z ERROR [ProbeLib] [2025-01-10 11:02:45.963873Z] Trace channel disconnected unexpectedly.

I have already installed a new version of J-Link, v794i (conform these specs: https://docs.nordicsemi.com/bundle/ncs-2.9.0/page/nrf/installation/recommended_versions.html). I didn't remove the older version though, v794e.

If anyone has any idea how I can fix this problem please let me know!

Geert

Parents
  • Hi Geert

    Could you try to run "nrfutil device list" just to verify that you can see your device?  

    You might have to install device for nrfutil, this can be done by running "nrfutil install device

    I would also recommend placing nrfutil in a sensible place (I have mine in a folder named tools) and add that folder to the windows path

    Regards

    Runar

  • Hey Runar,

    Thansk for the quick response!

    I did as you adviced, moving nrfutil to a more sencible place (due to some admin restriction I moved it to the bin folder of VSCode which is within my system path) and rand nrf device list. I even reinstalled it using --force to be sure it was the newest version. This is what my cmd gave back:

    ---------------------------------------------------------------
    PS C:\Users\geert> nrfutil install device --force
    nrfutil-device already installed
    Uninstalled nrfutil-device
    [00:00:01] ###### 100% [Install packages] Install packages
    PS C:\Users\geert> nrfutil device list
    1057701372
    product         J-Link
    board version   PCA10156
    ports           COM3, vcom: 0
                    COM4, vcom: 1
    traits          boardController, devkit, jlink, seggerUsb, serialPorts, usb

    Found 1 supported device(s)

    PS C:\Users\geert>

    ---------------------------------------------------------------

    When i ran device search I noticed that only device was installed. I read through the others and as a precaution I installed completion, nrf5sdk-tools amd toolchain-manager BEFORE running the above mentioned commands.

    I also again used the nRF Connect for Desktop v5.1.0 (after restarting the program) to see if anythin changed. It again found the right board and gave the same error. Listed below is the LOG output as proof.

    ---------------------------------------------------------------

    2025-01-15T09:14:44.222Z INFO Initialising the bundled nrfutil device
    2025-01-15T09:14:44.230Z DEBUG Started watching devices
    2025-01-15T09:14:45.267Z INFO Using the bundled core version for nrfutil device: 7.13.0
    2025-01-15T09:14:45.713Z INFO Using nrfutil-device version: 2.7.5
    2025-01-15T09:14:45.713Z INFO Using nrf-device-lib version: 0.17.41
    2025-01-15T09:14:45.713Z INFO Using nrfjprog DLL version: 10.24.2
    2025-01-15T09:14:45.713Z INFO Using JLink version: JLink_V7.94i
    2025-01-15T09:14:47.224Z DEBUG Selected device: nRF54L15 DK
    2025-01-15T09:14:47.243Z DEBUG Changed step: Info
    2025-01-15T09:14:50.280Z DEBUG Changed step: Rename
    2025-01-15T09:14:51.025Z DEBUG Changed step: Program
    2025-01-15T09:14:55.203Z ERROR  NRFDLException(1): [Probe] Emulator error: No emulator with connection info 'Usb(JLinkSerialNumber(1057701372))' was found
    2025-01-15T09:14:55.207Z ERROR [ProbeLib] [2025-01-15 09:14:55.205854Z] Trace channel disconnected unexpectedly.

    ---------------------------------------------------------------

    If you have any other advice please let me know!

  • Hi 

    Thank you for the patience. Can you confirm you have install nRF Command line tools? I can see that you have Jlink so that part should be fine. 

    If you try to run throught the Quick start app from nRF Connect for Desktop, are you able to complete the process?

    Also  which version of NCS and toolchain are you using ?

    I would also like to see the output from  nrfutil device list

    Regards

    Runar

  • Hey,

    I do have nRF Command line tools installed. The version I installed is nrf-command-line-tools-10.24.2-x64 (was still in my download). I verivied it by checking the version of nrfjprog I have. The output is shown below.

    -------------------------------------------------------------------------

    PS C:\Users\geert> nrfjprog -v
    nrfjprog version: 10.24.2 external
    JLinkARM.dll version: 7.94i

    --------------------------------------------------

    When I use the Quick start of the nRF Connect for Desktop I run into the problem of my original post.. That is the log output of my quickstart attempt. To be sure I went through the quick start process again using nRF connect for desktop and below is the log.

    -------------------------------------------------------------------------

    2025-01-16T08:52:39.234Z INFO Initialising the bundled nrfutil device
    2025-01-16T08:52:39.346Z DEBUG Started watching devices
    2025-01-16T08:52:41.442Z INFO Using the bundled core version for nrfutil device: 7.13.0
    2025-01-16T08:52:41.886Z INFO Using nrfutil-device version: 2.7.5
    2025-01-16T08:52:41.886Z INFO Using nrf-device-lib version: 0.17.41
    2025-01-16T08:52:41.886Z INFO Using nrfjprog DLL version: 10.24.2
    2025-01-16T08:52:41.886Z INFO Using JLink version: JLink_V7.94i
    2025-01-16T08:52:42.238Z DEBUG Selected device: nRF54L15 DK
    2025-01-16T08:52:42.256Z DEBUG Changed step: Info
    2025-01-16T08:52:44.352Z DEBUG Changed step: Rename
    2025-01-16T08:52:45.342Z DEBUG Changed step: Program
    2025-01-16T08:52:48.142Z ERROR  NRFDLException(1): [Probe] Emulator error: No emulator with connection info 'Usb(JLinkSerialNumber(1057701372))' was found
    2025-01-16T08:52:48.146Z ERROR [ProbeLib] [2025-01-16 08:52:48.145165Z] Trace channel disconnected unexpectedly.

    --------------------------------------------------

    I believe I am using V2.9.0. When building in VSCode it says the build will use SDK v2.9.0 and the toolchain 2.9.0. Also when I look into my directory, there is only one folder with a version number and that is v2.9.0.

    Below I ran the nrfutil device list again

    -------------------------------------------------------------------------

    PS C:\Users\geert> nrfutil device list
    1057701372
    product         J-Link
    board version   PCA10156
    ports           COM3, vcom: 0
                    COM4, vcom: 1
    traits          boardController, devkit, jlink, seggerUsb, serialPorts, usb

    Found 1 supported device(s)

    PS C:\Users\geert>

    --------------------------------------------------

    That is all the info you asked for but as I was trying to understand the problem I also tried reading the firmware version of my nRF54l15DK board to see if that helps using the fw-info command. I got the same emulator error. Listed below is the output for clarification.

    -------------------------------------------------------------------------

    PS C:\Users\geert> nrfutil device fw-info --serial-number 1057701372
    Error: Failed to get firmware info for one or more devices:
     * 1057701372: [Probe] Emulator error: No emulator with connection info 'Usb(JLinkSerialNumber(1057701372))' was found, code: Generic
    PS C:\Users\geert>

    --------------------------------------------------

    Thank you for your time!

    Geert

  • I'm checking internally, but there is one thing you can try while I check. Reinstall the JLink_V7.94i and be sure to select the install legacy usb support option. If this is the first installation of Jlink on your computer you might not have the legacy support. Without the legacy support you will not be able to detect the debugger 

    Regards

    Runar

Reply
  • I'm checking internally, but there is one thing you can try while I check. Reinstall the JLink_V7.94i and be sure to select the install legacy usb support option. If this is the first installation of Jlink on your computer you might not have the legacy support. Without the legacy support you will not be able to detect the debugger 

    Regards

    Runar

Children
  • Please try the following: 

    nrfutil device --version

    and then run the following and upload the logs:

    nrfutil device list --log-level trace

    nrfutil device fw-info --serial-number 1057701372 --log-level trace

    This will create a log file in C:\Users\geert\.nrfutil\logs\nrfutil-device.log, which should provide some more information about what's happening.

    Regards

    Runar

  • Hey Runar,

    Thank you for your time. Below is the log of the cmd of all the commands you told me to use.

    -------------------------------------------------------------------------

    PS C:\Users\geert> nrfutil device --version
    nrfutil-device 2.7.11 (7005884 2025-01-15)
    commit-hash: 70058847a6226212a758c274d19aa8f95dc23cdc
    commit-date: 2025-01-15
    host: x86_64-pc-windows-msvc
    build-timestamp: 2025-01-16T09:18:42.423984900Z
    classification: nrf-external

    Detected SEGGER J-Link version: JLink_V7.94i

    The device command version you are currently using was tested with a different J-Link version (JLink_V8.10f) than the one you have installed (JLink_V7.94i). The tested version is not required, and your J-Link version will most likely work fine. If you get issues related to J-Link with your devices, use the tested version.
    PS C:\Users\geert> nrfutil device list --log-level trace
    1057701372
    product         J-Link
    board version   PCA10156
    ports           COM3, vcom: 0
                    COM4, vcom: 1
    traits          boardController, devkit, jlink, seggerUsb, serialPorts, usb

    Found 1 supported device(s)

    PS C:\Users\geert> nrfutil device fw-info --serial-number 1057701372 --log-level trace
    Error: Failed to get firmware info for one or more devices:
     * 1057701372: [Probe] Emulator error: No emulator with connection info 'Usb(JLinkSerialNumber(1057701372))' was found, code: Generic
    PS C:\Users\geertvanlammeren>

    --------------------------------------------------

    Here is the log of the nrfutil-device file within .nrfutil/log. Hopefully you can find something within it. I definitly can't.

    -------------------------------------------------------------------------

    [2025-01-16T15:19:02.432Z] [29064] INFO - nrfutil-device (version = 2.7.11, platform = x86_64-pc-windows-msvc) invoked with --version
    [2025-01-16T15:19:02.444Z] [29064] INFO - [ProbeLib] [2025-01-16 15:19:02.444586Z] Opened J-Link DLL at C:\Program Files\SEGGER\JLink_V794i\JLink_x64.dll with version 7.94i
    [2025-01-16T15:19:02.698Z] [29064] WARN - [JlinkARM] nrfutil device commands were tested using SEGGER J-Link version JLink_V8.10f, but the J-Link version you are using is JLink_V7.94i. Your installed version will most likely work fine, but if you get issues related to J-Link with your devices, use the tested version
    [2025-01-16T15:19:06.969Z] [10864] INFO - nrfutil-device (version = 2.7.11, platform = x86_64-pc-windows-msvc) invoked with list --log-level trace
    [2025-01-16T15:19:06.969Z] [10864] DEBUG - cargo = false, force_libnrfdl_lookup = false, force_nrfutil_libdir = false
    [2025-01-16T15:19:06.969Z] [10864] DEBUG - Creating the nrfdl context via nrfdl_create_context_with_config: Plugin location is assumed to be C:\Users\geert\.nrfutil\lib\nrfutil-device
    [2025-01-16T15:19:06.978Z] [10864] TRACE - [ProbeLib] [2025-01-16 15:19:06.978097Z] J-Link installation directory configured in registry: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\SEGGER\J-Link="C:\\Program Files\\SEGGER\\JLink_V794i"
    [2025-01-16T15:19:06.980Z] [10864] INFO - [ProbeLib] [2025-01-16 15:19:06.980767Z] Opened J-Link DLL at C:\Program Files\SEGGER\JLink_V794i\JLink_x64.dll with version 7.94i
    [2025-01-16T15:19:07.077Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] open
    [2025-01-16T15:19:07.077Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] start
    [2025-01-16T15:19:07.123Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] Logger sink registered in Segger backend logger
    [2025-01-16T15:19:07.123Z] [10864] DEBUG - [jlink] [NRFJPROG][JLink][-] Logger sink registered in JLink logger
    [2025-01-16T15:19:07.123Z] [10864] DEBUG - [jlink] [NRFJPROG][nRFXX][-] open
    [2025-01-16T15:19:07.123Z] [10864] DEBUG - [jlink] [NRFJPROG][nRFXX][-] just_check_family
    [2025-01-16T15:19:07.123Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] open_dll
    [2025-01-16T15:19:07.123Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] No J-Link DLL path was provided. Attempting to auto detect.
    [2025-01-16T15:19:07.126Z] [10864] TRACE - [jlink] [NRFJPROG][Client][-] Command open executed for 44 milliseconds with result 0
    [2025-01-16T15:19:07.126Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] jlink_dll_version
    [2025-01-16T15:19:07.126Z] [10864] TRACE - [jlink] [NRFJPROG][Client][-] Command jlink_dll_version executed for 0 milliseconds with result 0
    [2025-01-16T15:19:07.145Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] Set batch mode
    [2025-01-16T15:19:07.145Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] dll_version
    [2025-01-16T15:19:07.145Z] [10864] TRACE - [jlink] [NRFJPROG][Worker][-] Command open executed for 4 milliseconds with result 0
    [2025-01-16T15:19:07.145Z] [10864] DEBUG - [jlink] [NRFJPROG][nRFXX][-] dll_version
    [2025-01-16T15:19:07.145Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:07.145Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] dll_version
    [2025-01-16T15:19:07.145Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:07.145Z] [10864] TRACE - [jlink] [NRFJPROG][Worker][-] Command jlink_dll_version executed for 0 milliseconds with result 0
    [2025-01-16T15:19:07.145Z] [10864] DEBUG - [jlink] [NRFJPROG][nRFXX][-] close
    [2025-01-16T15:19:07.146Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:07.146Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] close
    [2025-01-16T15:19:07.146Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] disconnect_from_emu
    [2025-01-16T15:19:07.146Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:07.146Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] Segger Backend closed.
    [2025-01-16T15:19:07.146Z] [10864] DEBUG - [jlink] [NRFJPROG][nRFXX][-] nRF family DLL closed
    [2025-01-16T15:19:07.164Z] [10864] TRACE - [jlink] [NRFJPROG][Client][-] Command close executed for 37 milliseconds with result 0
    [2025-01-16T15:19:07.164Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] terminate
    [2025-01-16T15:19:07.178Z] [10864] TRACE - [jlink] [NRFJPROG][Client][-] Command terminate executed for 14 milliseconds with result 0
    [2025-01-16T15:19:07.179Z] [10864] TRACE - [jlink] [NRFJPROG][Worker][-] Command close executed for 34 milliseconds with result 0
    [2025-01-16T15:19:07.194Z] [10864] TRACE - [jlink] [NRFJPROG][Worker][-] Command terminate executed for 0 milliseconds with result 0
    [2025-01-16T15:19:07.194Z] [10864] TRACE - [jlink] [NRFJPROG][Worker][-] Executed 4 commands for 38 milliseconds
    [2025-01-16T15:19:07.227Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
    [2025-01-16T15:19:07.227Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
    [2025-01-16T15:19:07.228Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] Child process terminated with result 0
    [2025-01-16T15:19:07.228Z] [10864] TRACE - [jlink] [NRFJPROG][Client][-] Executed 4 commands for 95 milliseconds
    [2025-01-16T15:19:07.228Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] terminate
    [2025-01-16T15:19:07.241Z] [10864] WARN - [JlinkARM] nrfutil device commands were tested using SEGGER J-Link version JLink_V8.10f, but the J-Link version you are using is JLink_V7.94i. Your installed version will most likely work fine, but if you get issues related to J-Link with your devices, use the tested version
    [2025-01-16T15:19:07.241Z] [10864] TRACE - DeviceLister::enumerate: Checking future_status of enumerate_task_status
    [2025-01-16T15:19:07.241Z] [10864] TRACE - DeviceLister::enumerate: Waiting for enumeration to complete
    [2025-01-16T15:19:07.242Z] [10864] TRACE - DeviceLister::enumerate::enumerate_task: Start
    [2025-01-16T15:19:07.242Z] [10864] TRACE - DeviceLister::enumerate::enumerate_task: Before async_lister->enumerate
    [2025-01-16T15:19:07.242Z] [10864] DEBUG - USBLister: enumerate
    [2025-01-16T15:19:07.242Z] [10864] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_17EF&PID_30FC#1SSD21K04345ZZQ01K9J#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:07.242Z] [10864] DEBUG - usb-lister-rs: Container ID: '{2ECEDC5C-CD9E-11EF-AF27-806E6F6E6963}'
    [2025-01-16T15:19:07.242Z] [10864] DEBUG - usb-lister-rs: Hub device path: \\?\USB#VID_17EF&PID_3102#6&3640C1B5&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 3, origin: {2ECEDC5C-CD9E-11EF-AF27-806E6F6E6963}
    [2025-01-16T15:19:07.250Z] [10864] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_17EF&PID_3103#000000000000#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:07.250Z] [10864] DEBUG - usb-lister-rs: Container ID: '{2ECEDC5C-CD9E-11EF-AF27-806E6F6E6963}'
    [2025-01-16T15:19:07.250Z] [10864] DEBUG - usb-lister-rs: Hub device path: \\?\USB#VID_17EF&PID_3102#6&3640C1B5&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 2, origin: {2ECEDC5C-CD9E-11EF-AF27-806E6F6E6963}
    [2025-01-16T15:19:07.259Z] [10864] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_0489&PID_E0CD#000000000#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:07.259Z] [10864] DEBUG - usb-lister-rs: Container ID: '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
    [2025-01-16T15:19:07.259Z] [10864] DEBUG - usb-lister-rs: Hub device path: \\?\USB#ROOT_HUB30#5&33210E6E&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 4, origin: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
    [2025-01-16T15:19:07.259Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for manufacturer: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:07.259Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for product: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:07.259Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for serial number: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:07.259Z] [10864] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_1366&PID_1059#001057701372#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:07.259Z] [10864] DEBUG - usb-lister-rs: Container ID: '{B2E35B05-90B7-5F9E-BAFC-9CE5785D7D25}'
    [2025-01-16T15:19:07.259Z] [10864] DEBUG - usb-lister-rs: Hub device path: \\?\USB#ROOT_HUB30#5&1A87E6C4&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 2, origin: {B2E35B05-90B7-5F9E-BAFC-9CE5785D7D25}
    [2025-01-16T15:19:07.264Z] [10864] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_04F2&PID_B7B4#0001#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:07.264Z] [10864] DEBUG - usb-lister-rs: Container ID: '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
    [2025-01-16T15:19:07.264Z] [10864] DEBUG - usb-lister-rs: Hub device path: \\?\USB#ROOT_HUB30#5&1A87E6C4&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 3, origin: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
    [2025-01-16T15:19:07.264Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for manufacturer: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:07.264Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for product: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:07.264Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for serial number: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:07.264Z] [10864] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_10A5&PID_9800#6&3640c1b5&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:07.264Z] [10864] DEBUG - usb-lister-rs: Container ID: '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
    [2025-01-16T15:19:07.264Z] [10864] DEBUG - usb-lister-rs: Hub device path: \\?\USB#ROOT_HUB30#5&33210E6E&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 3, origin: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
    [2025-01-16T15:19:07.264Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for manufacturer: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:07.264Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for product: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:07.264Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for serial number: Received `0` as descriptor index
    [2025-01-16T15:19:07.264Z] [10864] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_046D&PID_C077#9&2dd1df7a&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:07.264Z] [10864] DEBUG - usb-lister-rs: Container ID: '{2ECEDC97-CD9E-11EF-AF27-806E6F6E6963}'
    [2025-01-16T15:19:07.264Z] [10864] DEBUG - usb-lister-rs: Hub device path: \\?\USB#VID_17EF&PID_3101#MSFT20000000001#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 4, origin: {2ECEDC97-CD9E-11EF-AF27-806E6F6E6963}
    [2025-01-16T15:19:07.268Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for serial number: Received `0` as descriptor index
    [2025-01-16T15:19:07.268Z] [10864] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_0BDA&PID_8153#3213000001#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:07.268Z] [10864] DEBUG - usb-lister-rs: Container ID: '{31E1993F-C3D3-411E-AF53-664157077175}'
    [2025-01-16T15:19:07.268Z] [10864] DEBUG - usb-lister-rs: Hub device path: \\?\USB#VID_17EF&PID_30FE#MSFT30000000001#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 1, origin: {31E1993F-C3D3-411E-AF53-664157077175}
    [2025-01-16T15:19:07.268Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for manufacturer: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:07.268Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for product: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:07.268Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for serial number: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:07.268Z] [10864] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_0BF8&PID_101E#8&135bddd1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:07.268Z] [10864] DEBUG - usb-lister-rs: Container ID: '{2ECEDC83-CD9E-11EF-AF27-806E6F6E6963}'
    [2025-01-16T15:19:07.268Z] [10864] DEBUG - usb-lister-rs: Hub device path: \\?\USB#VID_17EF&PID_30FF#MSFT20000000001#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 2, origin: {2ECEDC83-CD9E-11EF-AF27-806E6F6E6963}
    [2025-01-16T15:19:07.273Z] [10864] WARN - usb-lister-rs: Failed to get device descriptor for serial number: Received `0` as descriptor index
    [2025-01-16T15:19:07.273Z] [10864] DEBUG - USBLister: Adding new device with ID 1 and serial number: '1SSD21K04345ZZQ01K9J'
    [2025-01-16T15:19:07.273Z] [10864] DEBUG - USBLister: Adding new device with ID 2 and serial number: 'NONE'
    [2025-01-16T15:19:07.273Z] [10864] DEBUG - USBLister: Adding new device with ID 3 and serial number: 'NONE'
    [2025-01-16T15:19:07.273Z] [10864] DEBUG - USBLister: Adding new device with ID 4 and serial number: 'NONE'
    [2025-01-16T15:19:07.273Z] [10864] DEBUG - USBLister: Adding new device with ID 5 and serial number: 'NONE'
    [2025-01-16T15:19:07.273Z] [10864] DEBUG - USBLister: Adding new device with ID 6 and serial number: 'NONE'
    [2025-01-16T15:19:07.273Z] [10864] DEBUG - USBLister: Adding new device with ID 7 and serial number: 'NONE'
    [2025-01-16T15:19:07.273Z] [10864] DEBUG - USBLister: Adding new device with ID 8 and serial number: '000000000000'
    [2025-01-16T15:19:07.273Z] [10864] DEBUG - USBLister: Adding new device with ID 9 and serial number: '001057701372'
    [2025-01-16T15:19:07.273Z] [10864] TRACE - DeviceLister::enumerate::enumerate_task: After async_lister->enumerate
    [2025-01-16T15:19:07.275Z] [10864] DEBUG - Enumeration for plugin 'devkit' took 1 ms
    [2025-01-16T15:19:07.275Z] [10864] TRACE - [ProbeLib] [2025-01-16 15:19:07.275773Z] J-Link installation directory configured in registry: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\SEGGER\J-Link="C:\\Program Files\\SEGGER\\JLink_V794i"
    [2025-01-16T15:19:07.275Z] [10864] INFO - [ProbeLib] [2025-01-16 15:19:07.275945Z] Opened J-Link DLL at C:\Program Files\SEGGER\JLink_V794i\JLink_x64.dll with version 7.94i
    [2025-01-16T15:19:07.279Z] [10864] INFO - [ProbeLib] [2025-01-16 15:19:07.279067Z] Found 0 attached J-Link devices
    [2025-01-16T15:19:07.279Z] [10864] DEBUG - [ProbeLib] [2025-01-16 15:19:07.279087Z] No J-Link devices found
    [2025-01-16T15:19:07.279Z] [10864] DEBUG - Enumeration for plugin 'Probe' took 3 ms
    [2025-01-16T15:19:07.279Z] [10864] TRACE - [jlink] JLinkPlugin::enumerate
    [2025-01-16T15:19:07.372Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] open
    [2025-01-16T15:19:07.372Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] start
    [2025-01-16T15:19:07.418Z] [10864] TRACE - [jlink] [NRFJPROG][Client][-] Command open executed for 42 milliseconds with result 0
    [2025-01-16T15:19:07.418Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] enum_emu_snr
    [2025-01-16T15:19:07.421Z] [10864] TRACE - [jlink] [NRFJPROG][Client][-] Command enum_emu_snr executed for 2 milliseconds with result 0
    [2025-01-16T15:19:07.421Z] [10864] DEBUG - [jlink] Found 0 J-Link devices connected
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] Logger sink registered in Segger backend logger
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][JLink][-] Logger sink registered in JLink logger
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][nRFXX][-] open
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][nRFXX][-] just_check_family
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] open_dll
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] No J-Link DLL path was provided. Attempting to auto detect.
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] Set batch mode
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] dll_version
    [2025-01-16T15:19:07.429Z] [10864] TRACE - [jlink] [NRFJPROG][Worker][-] Command open executed for 4 milliseconds with result 0
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][nRFXX][-] enum_emu_snr
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] enum_emu_snr
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] ---just_enum_emu_snr
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] ---just_get_num_emus
    [2025-01-16T15:19:07.429Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:07.429Z] [10864] TRACE - [jlink] [NRFJPROG][Worker][-] Command enum_emu_snr executed for 2 milliseconds with result 0
    [2025-01-16T15:19:07.430Z] [10864] DEBUG - [jlink] [NRFJPROG][nRFXX][-] close
    [2025-01-16T15:19:07.430Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:07.430Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] close
    [2025-01-16T15:19:07.430Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] disconnect_from_emu
    [2025-01-16T15:19:07.430Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:07.430Z] [10864] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] Segger Backend closed.
    [2025-01-16T15:19:07.430Z] [10864] DEBUG - [jlink] [NRFJPROG][nRFXX][-] nRF family DLL closed
    [2025-01-16T15:19:07.444Z] [10864] TRACE - [jlink] [NRFJPROG][Client][-] Command close executed for 22 milliseconds with result 0
    [2025-01-16T15:19:07.444Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] terminate
    [2025-01-16T15:19:07.444Z] [10864] TRACE - [jlink] [NRFJPROG][Client][-] Command terminate executed for 0 milliseconds with result 0
    [2025-01-16T15:19:07.476Z] [10864] TRACE - [jlink] [NRFJPROG][Worker][-] Command close executed for 22 milliseconds with result 0
    [2025-01-16T15:19:07.477Z] [10864] TRACE - [jlink] [NRFJPROG][Worker][-] Command terminate executed for 0 milliseconds with result 0
    [2025-01-16T15:19:07.477Z] [10864] TRACE - [jlink] [NRFJPROG][Worker][-] Executed 4 commands for 28 milliseconds
    [2025-01-16T15:19:07.494Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
    [2025-01-16T15:19:07.494Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
    [2025-01-16T15:19:07.494Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] Child process terminated with result 0
    [2025-01-16T15:19:07.494Z] [10864] TRACE - [jlink] [NRFJPROG][Client][-] Executed 4 commands for 66 milliseconds
    [2025-01-16T15:19:07.494Z] [10864] DEBUG - [jlink] [NRFJPROG][Client][-] terminate
    [2025-01-16T15:19:07.501Z] [10864] DEBUG - Enumeration for plugin 'jlink' took 222 ms
    [2025-01-16T15:19:07.544Z] [10864] DEBUG - Enumeration for plugin 'BOARDCONTROLLER' took 43 ms
    [2025-01-16T15:19:07.546Z] [10864] DEBUG - [serialport] Looking for GUID: {b2e35b05-90b7-5f9e-bafc-9ce5785d7d25}
    [2025-01-16T15:19:07.546Z] [10864] DEBUG - [serialport] Serial numbers found: ["001051173446", "001057701372", "001057731788"]
    [2025-01-16T15:19:07.546Z] [10864] DEBUG - [serialport] Serial number: 001051173446 -> GUID: {aeda0321-676b-5c08-9c37-766349129945}
    [2025-01-16T15:19:07.546Z] [10864] DEBUG - [serialport] Serial number: 001057701372 -> GUID: {b2e35b05-90b7-5f9e-bafc-9ce5785d7d25}
    [2025-01-16T15:19:07.546Z] [10864] DEBUG - [serialport] Matching serial number? Some("001057701372")
    [2025-01-16T15:19:07.546Z] [10864] DEBUG - [serialport] serial port \\?\USB#VID_1366&PID_1059&MI_00#7&2054A236&0&0000#{86e0d1e0-8089-11d0-9ce4-08003e301f73} has USB identifier \\?\USB#VID_1366&PID_1059#001057701372#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
    [2025-01-16T15:19:07.546Z] [10864] DEBUG - [serialport] Looking for GUID: {b2e35b05-90b7-5f9e-bafc-9ce5785d7d25}
    [2025-01-16T15:19:07.547Z] [10864] DEBUG - [serialport] Serial numbers found: ["001051173446", "001057701372", "001057731788"]
    [2025-01-16T15:19:07.547Z] [10864] DEBUG - [serialport] Serial number: 001051173446 -> GUID: {aeda0321-676b-5c08-9c37-766349129945}
    [2025-01-16T15:19:07.547Z] [10864] DEBUG - [serialport] Serial number: 001057701372 -> GUID: {b2e35b05-90b7-5f9e-bafc-9ce5785d7d25}
    [2025-01-16T15:19:07.547Z] [10864] DEBUG - [serialport] Matching serial number? Some("001057701372")
    [2025-01-16T15:19:07.547Z] [10864] DEBUG - [serialport] serial port \\?\USB#VID_1366&PID_1059&MI_02#7&2054A236&0&0002#{86e0d1e0-8089-11d0-9ce4-08003e301f73} has USB identifier \\?\USB#VID_1366&PID_1059#001057701372#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
    [2025-01-16T15:19:07.547Z] [10864] DEBUG - [serialport] try to map FTDI to segger device
    [2025-01-16T15:19:07.547Z] [10864] DEBUG - [serialport] serialport enumerate update device: '001057701372'
    [2025-01-16T15:19:07.547Z] [10864] DEBUG - Enumeration for plugin 'serialport' took 2 ms
    [2025-01-16T15:19:07.547Z] [10864] DEBUG - Enumeration for plugin 'sdfu' took 0 ms
    [2025-01-16T15:19:07.547Z] [10864] DEBUG - Enumeration for plugin 'mcuBoot' took 0 ms
    [2025-01-16T15:19:07.547Z] [10864] TRACE - [broken] BrokenPlugin::enumerate
    [2025-01-16T15:19:07.548Z] [10864] DEBUG - Enumeration for plugin 'broken' took 0 ms
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: Found device with serial number: '1SSD21K04345ZZQ01K9J'
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: Found device with serial number: '<unknown>'
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: Found device with serial number: '<unknown>'
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: Found device with serial number: '<unknown>'
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: Found device with serial number: '<unknown>'
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: Found device with serial number: '<unknown>'
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: Found device with serial number: '<unknown>'
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: Found device with serial number: '000000000000'
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: Found device with serial number: '001057701372'
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: device registered to device list
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: Finished in 306 ms
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: Completed waiting for enumeration
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::enumerate: done
    [2025-01-16T15:19:07.548Z] [10864] TRACE - DeviceLister::shutDown()
    [2025-01-16T15:19:10.640Z] [13476] INFO - nrfutil-device (version = 2.7.11, platform = x86_64-pc-windows-msvc) invoked with fw-info --serial-number 1057701372 --log-level trace
    [2025-01-16T15:19:10.640Z] [13476] DEBUG - cargo = false, force_libnrfdl_lookup = false, force_nrfutil_libdir = false
    [2025-01-16T15:19:10.640Z] [13476] DEBUG - Creating the nrfdl context via nrfdl_create_context_with_config: Plugin location is assumed to be C:\Users\geert\.nrfutil\lib\nrfutil-device
    [2025-01-16T15:19:10.648Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:10.648934Z] J-Link installation directory configured in registry: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\SEGGER\J-Link="C:\\Program Files\\SEGGER\\JLink_V794i"
    [2025-01-16T15:19:10.651Z] [13476] INFO - [ProbeLib] [2025-01-16 15:19:10.651338Z] Opened J-Link DLL at C:\Program Files\SEGGER\JLink_V794i\JLink_x64.dll with version 7.94i
    [2025-01-16T15:19:10.746Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] open
    [2025-01-16T15:19:10.746Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] start
    [2025-01-16T15:19:10.793Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] Logger sink registered in Segger backend logger
    [2025-01-16T15:19:10.793Z] [13476] DEBUG - [jlink] [NRFJPROG][JLink][-] Logger sink registered in JLink logger
    [2025-01-16T15:19:10.793Z] [13476] TRACE - [jlink] [NRFJPROG][Client][-] Command open executed for 43 milliseconds with result 0
    [2025-01-16T15:19:10.793Z] [13476] DEBUG - [jlink] [NRFJPROG][nRFXX][-] open
    [2025-01-16T15:19:10.793Z] [13476] DEBUG - [jlink] [NRFJPROG][nRFXX][-] just_check_family
    [2025-01-16T15:19:10.793Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] open_dll
    [2025-01-16T15:19:10.793Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] No J-Link DLL path was provided. Attempting to auto detect.
    [2025-01-16T15:19:10.793Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] jlink_dll_version
    [2025-01-16T15:19:10.793Z] [13476] TRACE - [jlink] [NRFJPROG][Client][-] Command jlink_dll_version executed for 0 milliseconds with result 0
    [2025-01-16T15:19:10.824Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] Set batch mode
    [2025-01-16T15:19:10.824Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] dll_version
    [2025-01-16T15:19:10.824Z] [13476] TRACE - [jlink] [NRFJPROG][Worker][-] Command open executed for 4 milliseconds with result 0
    [2025-01-16T15:19:10.824Z] [13476] DEBUG - [jlink] [NRFJPROG][nRFXX][-] dll_version
    [2025-01-16T15:19:10.824Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:10.824Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] dll_version
    [2025-01-16T15:19:10.824Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:10.824Z] [13476] TRACE - [jlink] [NRFJPROG][Worker][-] Command jlink_dll_version executed for 0 milliseconds with result 0
    [2025-01-16T15:19:10.824Z] [13476] DEBUG - [jlink] [NRFJPROG][nRFXX][-] close
    [2025-01-16T15:19:10.824Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:10.824Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] close
    [2025-01-16T15:19:10.825Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] disconnect_from_emu
    [2025-01-16T15:19:10.825Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:10.825Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] Segger Backend closed.
    [2025-01-16T15:19:10.825Z] [13476] DEBUG - [jlink] [NRFJPROG][nRFXX][-] nRF family DLL closed
    [2025-01-16T15:19:10.825Z] [13476] TRACE - [jlink] [NRFJPROG][Client][-] Command close executed for 30 milliseconds with result 0
    [2025-01-16T15:19:10.825Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] terminate
    [2025-01-16T15:19:10.840Z] [13476] TRACE - [jlink] [NRFJPROG][Client][-] Command terminate executed for 15 milliseconds with result 0
    [2025-01-16T15:19:10.840Z] [13476] TRACE - [jlink] [NRFJPROG][Worker][-] Command close executed for 29 milliseconds with result 0
    [2025-01-16T15:19:10.870Z] [13476] TRACE - [jlink] [NRFJPROG][Worker][-] Command terminate executed for 0 milliseconds with result 0
    [2025-01-16T15:19:10.870Z] [13476] TRACE - [jlink] [NRFJPROG][Worker][-] Executed 4 commands for 33 milliseconds
    [2025-01-16T15:19:10.887Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
    [2025-01-16T15:19:10.887Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
    [2025-01-16T15:19:10.888Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] Child process terminated with result 0
    [2025-01-16T15:19:10.888Z] [13476] TRACE - [jlink] [NRFJPROG][Client][-] Executed 4 commands for 88 milliseconds
    [2025-01-16T15:19:10.888Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] terminate
    [2025-01-16T15:19:10.895Z] [13476] WARN - [JlinkARM] nrfutil device commands were tested using SEGGER J-Link version JLink_V8.10f, but the J-Link version you are using is JLink_V7.94i. Your installed version will most likely work fine, but if you get issues related to J-Link with your devices, use the tested version
    [2025-01-16T15:19:10.895Z] [13476] DEBUG - operation to get devices for : Ok("{\"operations\":[{\"operation\":{\"type\":\"fw-read-info\"},\"core\":\"NRFDL_DEVICE_CORE_APPLICATION\"}]}")
    [2025-01-16T15:19:10.895Z] [13476] TRACE - Operations required by a device to do: {"fw-read-info"}
    [2025-01-16T15:19:10.895Z] [13476] TRACE - DeviceLister::enumerate: Checking future_status of enumerate_task_status
    [2025-01-16T15:19:10.895Z] [13476] TRACE - DeviceLister::enumerate: Waiting for enumeration to complete
    [2025-01-16T15:19:10.895Z] [13476] TRACE - DeviceLister::enumerate::enumerate_task: Start
    [2025-01-16T15:19:10.895Z] [13476] TRACE - DeviceLister::enumerate::enumerate_task: Before async_lister->enumerate
    [2025-01-16T15:19:10.895Z] [13476] DEBUG - USBLister: enumerate
    [2025-01-16T15:19:10.895Z] [13476] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_17EF&PID_30FC#1SSD21K04345ZZQ01K9J#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:10.895Z] [13476] DEBUG - usb-lister-rs: Container ID: '{2ECEDC5C-CD9E-11EF-AF27-806E6F6E6963}'
    [2025-01-16T15:19:10.896Z] [13476] DEBUG - usb-lister-rs: Hub device path: \\?\USB#VID_17EF&PID_3102#6&3640C1B5&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 3, origin: {2ECEDC5C-CD9E-11EF-AF27-806E6F6E6963}
    [2025-01-16T15:19:10.904Z] [13476] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_17EF&PID_3103#000000000000#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:10.904Z] [13476] DEBUG - usb-lister-rs: Container ID: '{2ECEDC5C-CD9E-11EF-AF27-806E6F6E6963}'
    [2025-01-16T15:19:10.904Z] [13476] DEBUG - usb-lister-rs: Hub device path: \\?\USB#VID_17EF&PID_3102#6&3640C1B5&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 2, origin: {2ECEDC5C-CD9E-11EF-AF27-806E6F6E6963}
    [2025-01-16T15:19:10.913Z] [13476] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_0489&PID_E0CD#000000000#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:10.913Z] [13476] DEBUG - usb-lister-rs: Container ID: '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
    [2025-01-16T15:19:10.913Z] [13476] DEBUG - usb-lister-rs: Hub device path: \\?\USB#ROOT_HUB30#5&33210E6E&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 4, origin: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
    [2025-01-16T15:19:10.913Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for manufacturer: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:10.913Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for product: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:10.913Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for serial number: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:10.913Z] [13476] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_1366&PID_1059#001057701372#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:10.913Z] [13476] DEBUG - usb-lister-rs: Container ID: '{B2E35B05-90B7-5F9E-BAFC-9CE5785D7D25}'
    [2025-01-16T15:19:10.913Z] [13476] DEBUG - usb-lister-rs: Hub device path: \\?\USB#ROOT_HUB30#5&1A87E6C4&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 2, origin: {B2E35B05-90B7-5F9E-BAFC-9CE5785D7D25}
    [2025-01-16T15:19:10.918Z] [13476] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_04F2&PID_B7B4#0001#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:10.918Z] [13476] DEBUG - usb-lister-rs: Container ID: '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
    [2025-01-16T15:19:10.918Z] [13476] DEBUG - usb-lister-rs: Hub device path: \\?\USB#ROOT_HUB30#5&1A87E6C4&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 3, origin: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
    [2025-01-16T15:19:10.918Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for manufacturer: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:10.918Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for product: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:10.918Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for serial number: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:10.918Z] [13476] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_10A5&PID_9800#6&3640c1b5&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:10.918Z] [13476] DEBUG - usb-lister-rs: Container ID: '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
    [2025-01-16T15:19:10.918Z] [13476] DEBUG - usb-lister-rs: Hub device path: \\?\USB#ROOT_HUB30#5&33210E6E&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 3, origin: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
    [2025-01-16T15:19:10.918Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for manufacturer: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:10.918Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for product: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:10.918Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for serial number: Received `0` as descriptor index
    [2025-01-16T15:19:10.918Z] [13476] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_046D&PID_C077#9&2dd1df7a&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:10.918Z] [13476] DEBUG - usb-lister-rs: Container ID: '{2ECEDC97-CD9E-11EF-AF27-806E6F6E6963}'
    [2025-01-16T15:19:10.918Z] [13476] DEBUG - usb-lister-rs: Hub device path: \\?\USB#VID_17EF&PID_3101#MSFT20000000001#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 4, origin: {2ECEDC97-CD9E-11EF-AF27-806E6F6E6963}
    [2025-01-16T15:19:10.923Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for serial number: Received `0` as descriptor index
    [2025-01-16T15:19:10.923Z] [13476] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_0BDA&PID_8153#3213000001#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:10.923Z] [13476] DEBUG - usb-lister-rs: Container ID: '{31E1993F-C3D3-411E-AF53-664157077175}'
    [2025-01-16T15:19:10.923Z] [13476] DEBUG - usb-lister-rs: Hub device path: \\?\USB#VID_17EF&PID_30FE#MSFT30000000001#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 1, origin: {31E1993F-C3D3-411E-AF53-664157077175}
    [2025-01-16T15:19:10.923Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for manufacturer: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:10.923Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for product: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:10.923Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for serial number: Failed request to `DeviceIoControl`: A device attached to the system is not functioning. (0x8007001F)
    [2025-01-16T15:19:10.923Z] [13476] DEBUG - usb-lister-rs: Enumerating device 'DeviceInstanceId(\\?\USB#VID_0BF8&PID_101E#8&135bddd1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed})'
    [2025-01-16T15:19:10.923Z] [13476] DEBUG - usb-lister-rs: Container ID: '{2ECEDC83-CD9E-11EF-AF27-806E6F6E6963}'
    [2025-01-16T15:19:10.923Z] [13476] DEBUG - usb-lister-rs: Hub device path: \\?\USB#VID_17EF&PID_30FF#MSFT20000000001#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 2, origin: {2ECEDC83-CD9E-11EF-AF27-806E6F6E6963}
    [2025-01-16T15:19:10.929Z] [13476] WARN - usb-lister-rs: Failed to get device descriptor for serial number: Received `0` as descriptor index
    [2025-01-16T15:19:10.929Z] [13476] DEBUG - USBLister: Adding new device with ID 1 and serial number: 'NONE'
    [2025-01-16T15:19:10.929Z] [13476] DEBUG - USBLister: Adding new device with ID 2 and serial number: 'NONE'
    [2025-01-16T15:19:10.929Z] [13476] DEBUG - USBLister: Adding new device with ID 3 and serial number: '1SSD21K04345ZZQ01K9J'
    [2025-01-16T15:19:10.929Z] [13476] DEBUG - USBLister: Adding new device with ID 4 and serial number: 'NONE'
    [2025-01-16T15:19:10.929Z] [13476] DEBUG - USBLister: Adding new device with ID 5 and serial number: '001057701372'
    [2025-01-16T15:19:10.929Z] [13476] DEBUG - USBLister: Adding new device with ID 6 and serial number: 'NONE'
    [2025-01-16T15:19:10.929Z] [13476] DEBUG - USBLister: Adding new device with ID 7 and serial number: '000000000000'
    [2025-01-16T15:19:10.929Z] [13476] DEBUG - USBLister: Adding new device with ID 8 and serial number: 'NONE'
    [2025-01-16T15:19:10.929Z] [13476] DEBUG - USBLister: Adding new device with ID 9 and serial number: 'NONE'
    [2025-01-16T15:19:10.929Z] [13476] TRACE - DeviceLister::enumerate::enumerate_task: After async_lister->enumerate
    [2025-01-16T15:19:10.932Z] [13476] DEBUG - Enumeration for plugin 'devkit' took 1 ms
    [2025-01-16T15:19:10.932Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:10.932319Z] J-Link installation directory configured in registry: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\SEGGER\J-Link="C:\\Program Files\\SEGGER\\JLink_V794i"
    [2025-01-16T15:19:10.932Z] [13476] INFO - [ProbeLib] [2025-01-16 15:19:10.932452Z] Opened J-Link DLL at C:\Program Files\SEGGER\JLink_V794i\JLink_x64.dll with version 7.94i
    [2025-01-16T15:19:10.935Z] [13476] INFO - [ProbeLib] [2025-01-16 15:19:10.935912Z] Found 0 attached J-Link devices
    [2025-01-16T15:19:10.935Z] [13476] DEBUG - [ProbeLib] [2025-01-16 15:19:10.935930Z] No J-Link devices found
    [2025-01-16T15:19:10.935Z] [13476] DEBUG - Enumeration for plugin 'Probe' took 3 ms
    [2025-01-16T15:19:10.936Z] [13476] TRACE - [jlink] JLinkPlugin::enumerate
    [2025-01-16T15:19:11.031Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] open
    [2025-01-16T15:19:11.031Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] start
    [2025-01-16T15:19:11.078Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] Logger sink registered in Segger backend logger
    [2025-01-16T15:19:11.078Z] [13476] DEBUG - [jlink] [NRFJPROG][JLink][-] Logger sink registered in JLink logger
    [2025-01-16T15:19:11.078Z] [13476] DEBUG - [jlink] [NRFJPROG][nRFXX][-] open
    [2025-01-16T15:19:11.078Z] [13476] DEBUG - [jlink] [NRFJPROG][nRFXX][-] just_check_family
    [2025-01-16T15:19:11.078Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] open_dll
    [2025-01-16T15:19:11.078Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] No J-Link DLL path was provided. Attempting to auto detect.
    [2025-01-16T15:19:11.081Z] [13476] TRACE - [jlink] [NRFJPROG][Client][-] Command open executed for 45 milliseconds with result 0
    [2025-01-16T15:19:11.081Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] enum_emu_snr
    [2025-01-16T15:19:11.085Z] [13476] TRACE - [jlink] [NRFJPROG][Client][-] Command enum_emu_snr executed for 4 milliseconds with result 0
    [2025-01-16T15:19:11.085Z] [13476] DEBUG - [jlink] Found 0 J-Link devices connected
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] Set batch mode
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] dll_version
    [2025-01-16T15:19:11.119Z] [13476] TRACE - [jlink] [NRFJPROG][Worker][-] Command open executed for 4 milliseconds with result 0
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][nRFXX][-] enum_emu_snr
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] enum_emu_snr
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] ---just_enum_emu_snr
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] ---just_get_num_emus
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:11.119Z] [13476] TRACE - [jlink] [NRFJPROG][Worker][-] Command enum_emu_snr executed for 2 milliseconds with result 0
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][nRFXX][-] close
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] close
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] disconnect_from_emu
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][SeggerBackend][-] Segger Backend closed.
    [2025-01-16T15:19:11.119Z] [13476] DEBUG - [jlink] [NRFJPROG][nRFXX][-] nRF family DLL closed
    [2025-01-16T15:19:11.135Z] [13476] TRACE - [jlink] [NRFJPROG][Client][-] Command close executed for 49 milliseconds with result 0
    [2025-01-16T15:19:11.135Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] terminate
    [2025-01-16T15:19:11.149Z] [13476] TRACE - [jlink] [NRFJPROG][Client][-] Command terminate executed for 14 milliseconds with result 0
    [2025-01-16T15:19:11.166Z] [13476] TRACE - [jlink] [NRFJPROG][Worker][-] Command close executed for 47 milliseconds with result 0
    [2025-01-16T15:19:11.166Z] [13476] TRACE - [jlink] [NRFJPROG][Worker][-] Command terminate executed for 0 milliseconds with result 0
    [2025-01-16T15:19:11.166Z] [13476] TRACE - [jlink] [NRFJPROG][Worker][-] Executed 4 commands for 53 milliseconds
    [2025-01-16T15:19:11.199Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
    [2025-01-16T15:19:11.199Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
    [2025-01-16T15:19:11.200Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] Child process terminated with result 0
    [2025-01-16T15:19:11.200Z] [13476] TRACE - [jlink] [NRFJPROG][Client][-] Executed 4 commands for 112 milliseconds
    [2025-01-16T15:19:11.200Z] [13476] DEBUG - [jlink] [NRFJPROG][Client][-] terminate
    [2025-01-16T15:19:11.213Z] [13476] DEBUG - Enumeration for plugin 'jlink' took 277 ms
    [2025-01-16T15:19:11.256Z] [13476] DEBUG - Enumeration for plugin 'BOARDCONTROLLER' took 43 ms
    [2025-01-16T15:19:11.258Z] [13476] DEBUG - [serialport] Looking for GUID: {b2e35b05-90b7-5f9e-bafc-9ce5785d7d25}
    [2025-01-16T15:19:11.258Z] [13476] DEBUG - [serialport] Serial numbers found: ["001051173446", "001057701372", "001057731788"]
    [2025-01-16T15:19:11.258Z] [13476] DEBUG - [serialport] Serial number: 001051173446 -> GUID: {aeda0321-676b-5c08-9c37-766349129945}
    [2025-01-16T15:19:11.258Z] [13476] DEBUG - [serialport] Serial number: 001057701372 -> GUID: {b2e35b05-90b7-5f9e-bafc-9ce5785d7d25}
    [2025-01-16T15:19:11.258Z] [13476] DEBUG - [serialport] Matching serial number? Some("001057701372")
    [2025-01-16T15:19:11.258Z] [13476] DEBUG - [serialport] serial port \\?\USB#VID_1366&PID_1059&MI_00#7&2054A236&0&0000#{86e0d1e0-8089-11d0-9ce4-08003e301f73} has USB identifier \\?\USB#VID_1366&PID_1059#001057701372#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
    [2025-01-16T15:19:11.258Z] [13476] DEBUG - [serialport] Looking for GUID: {b2e35b05-90b7-5f9e-bafc-9ce5785d7d25}
    [2025-01-16T15:19:11.258Z] [13476] DEBUG - [serialport] Serial numbers found: ["001051173446", "001057701372", "001057731788"]
    [2025-01-16T15:19:11.258Z] [13476] DEBUG - [serialport] Serial number: 001051173446 -> GUID: {aeda0321-676b-5c08-9c37-766349129945}
    [2025-01-16T15:19:11.259Z] [13476] DEBUG - [serialport] Serial number: 001057701372 -> GUID: {b2e35b05-90b7-5f9e-bafc-9ce5785d7d25}
    [2025-01-16T15:19:11.259Z] [13476] DEBUG - [serialport] Matching serial number? Some("001057701372")
    [2025-01-16T15:19:11.259Z] [13476] DEBUG - [serialport] serial port \\?\USB#VID_1366&PID_1059&MI_02#7&2054A236&0&0002#{86e0d1e0-8089-11d0-9ce4-08003e301f73} has USB identifier \\?\USB#VID_1366&PID_1059#001057701372#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
    [2025-01-16T15:19:11.259Z] [13476] DEBUG - [serialport] try to map FTDI to segger device
    [2025-01-16T15:19:11.259Z] [13476] DEBUG - [serialport] serialport enumerate update device: '001057701372'
    [2025-01-16T15:19:11.259Z] [13476] DEBUG - Enumeration for plugin 'serialport' took 2 ms
    [2025-01-16T15:19:11.259Z] [13476] DEBUG - Enumeration for plugin 'sdfu' took 0 ms
    [2025-01-16T15:19:11.259Z] [13476] DEBUG - Enumeration for plugin 'mcuBoot' took 0 ms
    [2025-01-16T15:19:11.259Z] [13476] TRACE - [broken] BrokenPlugin::enumerate
    [2025-01-16T15:19:11.259Z] [13476] DEBUG - Enumeration for plugin 'broken' took 0 ms
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: Found device with serial number: '<unknown>'
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: Found device with serial number: '<unknown>'
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: Found device with serial number: '1SSD21K04345ZZQ01K9J'
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: Found device with serial number: '<unknown>'
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: Found device with serial number: '001057701372'
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: device registered to device list
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: Found device with serial number: '<unknown>'
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: Found device with serial number: '000000000000'
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: Found device with serial number: '<unknown>'
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: Found device with serial number: '<unknown>'
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: Finished in 364 ms
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: Completed waiting for enumeration
    [2025-01-16T15:19:11.259Z] [13476] TRACE - DeviceLister::enumerate: done
    [2025-01-16T15:19:11.260Z] [13476] DEBUG - [ProbeLib] [2025-01-16 15:19:11.260398Z] probe-plugin will check if the device is a NRF54H/NRF54L to determine if it should claim it
    [2025-01-16T15:19:11.260Z] [13476] DEBUG - [ProbeLib] [2025-01-16 15:19:11.260416Z] The device is recognized as a device with a supported probe. Need to run device identification to determine the device family
    [2025-01-16T15:19:11.260Z] [13476] DEBUG - [ProbeLib] [2025-01-16 15:19:11.260442Z] Looking for file in C:\Users\geert\.nrfutil\lib\nrfutil-device\plugin-probe-worker.exe
    [2025-01-16T15:19:11.260Z] [13476] DEBUG - [ProbeLib] [2025-01-16 15:19:11.260528Z] Found file at C:\Users\geert\.nrfutil\lib\nrfutil-device\plugin-probe-worker.exe
    [2025-01-16T15:19:11.260Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.260622Z] Created IPC server 49184e42-5500-43d0-997c-d350a69607fa
    [2025-01-16T15:19:11.265Z] [13476] DEBUG - [ProbeLib] [2025-01-16 15:19:11.265138Z] Spawned worker process with id 14696
    [2025-01-16T15:19:11.265Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.265198Z] Accepting IPC connection
    [2025-01-16T15:19:11.273Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.273427Z] Accepted IPC connection
    [2025-01-16T15:19:11.273Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.273456Z] The worker supervisor's role is finished
    [2025-01-16T15:19:11.275Z] [13476] DEBUG - [ProbeLib] [2025-01-16 15:19:11.275518Z] Received signal from master, returning alive worker.
    [2025-01-16T15:19:11.275Z] [13476] INFO - [ProbeLib] [2025-01-16 15:19:11.275548Z] Handshake signatures match
    [2025-01-16T15:19:11.275Z] [13476] INFO - [ProbeLib] [2025-01-16 15:19:11.275615Z] Connection with Probe worker established.
    [2025-01-16T15:19:11.275Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.275715Z] Starting trace thread
    [2025-01-16T15:19:11.275Z] [13476] INFO - [ProbeLib] [2025-01-16 15:19:11.273297Z] {jlink_usb_001057701372} nrf-probe version 0.29.0
    [2025-01-16T15:19:11.275Z] [13476] DEBUG - [ProbeLib] [2025-01-16 15:19:11.273333Z] {jlink_usb_001057701372} Sending IPC handshake response from worker...
    [2025-01-16T15:19:11.275Z] [13476] DEBUG - [ProbeLib] [2025-01-16 15:19:11.273439Z] {jlink_usb_001057701372} Started worker message processing loop
    [2025-01-16T15:19:11.275Z] [13476] DEBUG - [ProbeLib] [2025-01-16 15:19:11.275691Z] {jlink_usb_001057701372} Probe worker received initial message: Initialize(InitializeRequest { configuration: Configuration { jlink: JLinkConfig { dll_location: None }, target: TargetConfig { adac_timeout: None, swd_clock_frequency: None } }, firmware_config: None, target_family: None, override_detection: None })
    [2025-01-16T15:19:11.275Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.275730Z] {jlink_usb_001057701372} -> new
    [2025-01-16T15:19:11.275Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.275811Z] {jlink_usb_001057701372} J-Link installation directory configured in registry: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\SEGGER\J-Link="C:\\Program Files\\SEGGER\\JLink_V794i"
    [2025-01-16T15:19:11.275Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.275917Z] {jlink_usb_001057701372} -> new_from_path
    [2025-01-16T15:19:11.281Z] [13476] INFO - [ProbeLib] [2025-01-16 15:19:11.281724Z] {jlink_usb_001057701372} Opened J-Link DLL at C:\Program Files\SEGGER\JLink_V794i\JLink_x64.dll with version 7.94i
    [2025-01-16T15:19:11.281Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.281752Z] {jlink_usb_001057701372} <- new_from_path
    [2025-01-16T15:19:11.281Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.281757Z] {jlink_usb_001057701372} <- new
    [2025-01-16T15:19:11.281Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.281771Z] {jlink_usb_001057701372} Setting up JLink interface.
    [2025-01-16T15:19:11.281Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.281780Z] {jlink_usb_001057701372} -> connect
    [2025-01-16T15:19:11.281Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.281789Z] {jlink_usb_001057701372} Selecting J-Link with serial number 001057701372
    [2025-01-16T15:19:11.284Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.284245Z] {jlink_usb_001057701372} <- connect
    [2025-01-16T15:19:11.284Z] [13476] ERROR - [ProbeLib] [2025-01-16 15:19:11.284290Z] Failed to initialize worker: Emulator error: No emulator with connection info 'Usb(JLinkSerialNumber(1057701372))' was found
    [2025-01-16T15:19:11.284Z] [13476] DEBUG - [ProbeLib] [2025-01-16 15:19:11.284308Z] Terminating worker with id 14696
    [2025-01-16T15:19:11.284Z] [13476] DEBUG - [ProbeLib] [2025-01-16 15:19:11.284299Z] {jlink_usb_001057701372} Probe worker stopped.
    [2025-01-16T15:19:11.284Z] [13476] ERROR - [ProbeLib] [2025-01-16 15:19:11.284343Z] Failed to shutdown client: Io(Os { code: -2147024664, kind: Uncategorized, message: "The pipe is being closed." })
    [2025-01-16T15:19:11.284Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.284354Z] Waiting for worker to exit.
    [2025-01-16T15:19:11.285Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.285751Z] Waiting for worker to exit.
    [2025-01-16T15:19:11.286Z] [13476] ERROR - [ProbeLib] [2025-01-16 15:19:11.286227Z] Trace channel disconnected unexpectedly.
    [2025-01-16T15:19:11.286Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.286240Z] Trace thread ends now...
    [2025-01-16T15:19:11.286Z] [13476] TRACE - [ProbeLib] [2025-01-16 15:19:11.286784Z] Waiting for worker to exit.
    [2025-01-16T15:19:11.288Z] [13476] INFO - [ProbeLib] [2025-01-16 15:19:11.288834Z] Worker exited successfully
    [2025-01-16T15:19:11.288Z] [13476] ERROR -  NRFDLException(1): [Probe] Emulator error: No emulator with connection info 'Usb(JLinkSerialNumber(1057701372))' was found
    [2025-01-16T15:19:11.289Z] [13476] DEBUG - Task 0 is already completed
    [2025-01-16T15:19:11.289Z] [13476] TRACE - DeviceLister::shutDown()

    --------------------------------------------------

    Thank you agian!

  • Thanks!

    I have forwarded internally and will get back to you as soon as I hear something

    Regards

    Runar

  • Hey Runar,

    I managed to make the flashing work.

    I read my message back and saw that teh log of command PS C:\Users\geert> nrfutil device --version mentioned being made for J-Link v8.10f while I had V7.94i. I was certain I had read that V7.94i was adviced for the nRF54l15DK in the specs but I can't find it back.

    Regardless, after installing V8.10f I was able to get throught the flashing proces of VSCode. At first it didn't change when I made a change in the code but I think that is something to do with how I build. I am still interested in what your internal forward will show thought!

    Regardless, thanks for all the help!

    Geert

  • The feedback I got was that the recommended installing the driver with the legacy mode I mentioned further down. 
    It could also be that it with was a problem with the conflict between versions

    Regards

    Runar

Related