nRF9160 Dev kit Verification Failed out of the box

[deaker]

I just ordered and opened up the nRF9160 dev kit from Digikey.  I was going through the quick start and I named the device and when I went through the verification step, it failed.  I've attached a screen snapshot and the log it generated.  Why is this?

Fullscreen 2026-01-25T16_16_07.605Z-log.txt Download

2026-01-25T16:16:07.895Z INFO Initialising the bundled nrfutil device
2026-01-25T16:16:07.902Z DEBUG Started watching devices
2026-01-25T16:16:12.101Z INFO Successfully installed nrfutil core version: 8.1.1
2026-01-25T16:16:19.789Z INFO Successfully installed nrfutil device version: 2.15.7
2026-01-25T16:16:20.130Z INFO Using the bundled core version for nrfutil device: 8.1.1
2026-01-25T16:16:20.456Z INFO Using nrfutil device version: 2.15.7
2026-01-25T16:16:20.457Z INFO Using nrf-device-lib version: 0.22.5
2026-01-25T16:16:20.457Z INFO Using nrf-probe version: 0.51.0
2026-01-25T16:16:20.457Z INFO Using SEGGER J-Link version: JLink_V8.96
2026-01-25T16:16:20.458Z INFO Your version of SEGGER J-Link (8.96) is newer than the one this app was tested with (8.76). 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.
2026-01-25T16:16:20.519Z DEBUG Selected device: nRF9160 DK
2026-01-25T16:16:20.574Z DEBUG Changed step: Info
2026-01-25T16:17:27.975Z DEBUG Changed step: Rename
2026-01-25T16:18:12.593Z DEBUG Changed step: Program
2026-01-25T16:18:37.420Z INFO Opened port with options: {"path":"COM4","baudRate":115200}
2026-01-25T16:18:41.540Z INFO Closed port: COM4
2026-01-25T16:18:41.891Z ERROR Unable to convert nusb device to Usb on enumerate Error { code: Generic, message: "no usb identifier for DeviceInfo { bus_id: \"PCIROOT(0)#PCI(1400)#USBROOT(0)\", device_address: 5, port_chain: [24], vendor_id: 0x0BDA, product_id: 0x0411, device_version: 0x0104, usb_version: 0x0300, class: 0x09, subclass: 0x00, protocol: 0x03, speed: Some(Super), manufacturer_string: None, product_string: Some(\"4-Port USB 3.0 Hub\"), serial_number: None, instance_id: \"USB\\\\VID_0BDA&PID_0411\\\\5&8C7C8BA&0&24\", parent_instance_id: \"USB\\\\ROOT_HUB30\\\\4&2006862c&0&0\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(24)\", \"ACPI(_SB_)#ACPI(PC00)#ACPI(XHCI)#ACPI(RHUB)#ACPI(SS08)\"], port_number: 24, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x00, interface_string: None }] }", source: None }
2026-01-25T16:18:41.891Z ERROR Unable to convert nusb device to Usb on enumerate Error { code: Generic, message: "no usb identifier for DeviceInfo { bus_id: \"PCIROOT(0)#PCI(1400)#USBROOT(0)\", device_address: 2, port_chain: [6], vendor_id: 0x0BDA, product_id: 0x5411, device_version: 0x0104, usb_version: 0x0210, class: 0x09, subclass: 0x00, protocol: 0x02, speed: Some(High), manufacturer_string: None, product_string: Some(\"4-Port USB 2.0 Hub\"), serial_number: None, instance_id: \"USB\\\\VID_0BDA&PID_5411\\\\5&8C7C8BA&0&6\", parent_instance_id: \"USB\\\\ROOT_HUB30\\\\4&2006862c&0&0\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(6)\", \"ACPI(_SB_)#ACPI(PC00)#ACPI(XHCI)#ACPI(RHUB)#ACPI(HS06)\"], port_number: 6, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x01, interface_string: None }] }", source: None }
2026-01-25T16:19:16.850Z ERROR Unable to convert nusb device to Usb on enumerate Error { code: Generic, message: "no usb identifier for DeviceInfo { bus_id: \"PCIROOT(0)#PCI(1400)#USBROOT(0)\", device_address: 5, port_chain: [24], vendor_id: 0x0BDA, product_id: 0x0411, device_version: 0x0104, usb_version: 0x0300, class: 0x09, subclass: 0x00, protocol: 0x03, speed: Some(Super), manufacturer_string: None, product_string: Some(\"4-Port USB 3.0 Hub\"), serial_number: None, instance_id: \"USB\\\\VID_0BDA&PID_0411\\\\5&8C7C8BA&0&24\", parent_instance_id: \"USB\\\\ROOT_HUB30\\\\4&2006862c&0&0\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(24)\", \"ACPI(_SB_)#ACPI(PC00)#ACPI(XHCI)#ACPI(RHUB)#ACPI(SS08)\"], port_number: 24, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x00, interface_string: None }] }", source: None }
2026-01-25T16:19:16.851Z ERROR Unable to convert nusb device to Usb on enumerate Error { code: Generic, message: "no usb identifier for DeviceInfo { bus_id: \"PCIROOT(0)#PCI(1400)#USBROOT(0)\", device_address: 2, port_chain: [6], vendor_id: 0x0BDA, product_id: 0x5411, device_version: 0x0104, usb_version: 0x0210, class: 0x09, subclass: 0x00, protocol: 0x02, speed: Some(High), manufacturer_string: None, product_string: Some(\"4-Port USB 2.0 Hub\"), serial_number: None, instance_id: \"USB\\\\VID_0BDA&PID_5411\\\\5&8C7C8BA&0&6\", parent_instance_id: \"USB\\\\ROOT_HUB30\\\\4&2006862c&0&0\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(6)\", \"ACPI(_SB_)#ACPI(PC00)#ACPI(XHCI)#ACPI(RHUB)#ACPI(HS06)\"], port_number: 6, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x01, interface_string: None }] }", source: None }
2026-01-25T16:19:20.282Z ERROR Unable to convert nusb device to Usb on enumerate Error { code: Generic, message: "no usb identifier for DeviceInfo { bus_id: \"PCIROOT(0)#PCI(1400)#USBROOT(0)\", device_address: 5, port_chain: [24], vendor_id: 0x0BDA, product_id: 0x0411, device_version: 0x0104, usb_version: 0x0300, class: 0x09, subclass: 0x00, protocol: 0x03, speed: Some(Super), manufacturer_string: None, product_string: Some(\"4-Port USB 3.0 Hub\"), serial_number: None, instance_id: \"USB\\\\VID_0BDA&PID_0411\\\\5&8C7C8BA&0&24\", parent_instance_id: \"USB\\\\ROOT_HUB30\\\\4&2006862c&0&0\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(24)\", \"ACPI(_SB_)#ACPI(PC00)#ACPI(XHCI)#ACPI(RHUB)#ACPI(SS08)\"], port_number: 24, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x00, interface_string: None }] }", source: None }
2026-01-25T16:19:20.282Z ERROR Unable to convert nusb device to Usb on enumerate Error { code: Generic, message: "no usb identifier for DeviceInfo { bus_id: \"PCIROOT(0)#PCI(1400)#USBROOT(0)\", device_address: 2, port_chain: [6], vendor_id: 0x0BDA, product_id: 0x5411, device_version: 0x0104, usb_version: 0x0210, class: 0x09, subclass: 0x00, protocol: 0x02, speed: Some(High), manufacturer_string: None, product_string: Some(\"4-Port USB 2.0 Hub\"), serial_number: None, instance_id: \"USB\\\\VID_0BDA&PID_5411\\\\5&8C7C8BA&0&6\", parent_instance_id: \"USB\\\\ROOT_HUB30\\\\4&2006862c&0&0\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(6)\", \"ACPI(_SB_)#ACPI(PC00)#ACPI(XHCI)#ACPI(RHUB)#ACPI(HS06)\"], port_number: 6, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x01, interface_string: None }] }", source: None }
2026-01-25T16:20:28.439Z DEBUG Changed step: Verify
2026-01-25T16:20:31.449Z INFO Opened port with options: {"path":"COM4","baudRate":115200}
2026-01-25T16:20:33.457Z ERROR Received ERROR as return value from AT command
2026-01-25T16:20:33.464Z INFO Closed port: COM4
2026-01-25T16:23:45.945Z INFO Opened port with options: {"path":"COM4","baudRate":115200}
2026-01-25T16:23:47.946Z ERROR Received ERROR as return value from AT command
2026-01-25T16:23:47.955Z INFO Closed port: COM4

[Simon D-M]

Hi,

Can you check if the "nRF Current measurement" jumper (P22) is still on? It is located just over the micro-USB port.

If it is not on, put the jumper back on, and it should work fine. It sometimes falls during shipping.

Best regards,

Simon D-M

[deaker]

The jumper is still on.  Here is what is interesting.  When I select AT Commands it fails verification, when I select Asset Tracking it makes it through verification.  See screen snapshot.

[Simon D-M]

Hi,

I was able to replicate your issue on multiple computer. It seems like the "AT Commands" firmware binary for the nRF9160DK is not working. We'll fix it as soon as we can.

Thank you for your report !

Best regards,

Simon D-M

[Simon D-M]

Hi,

I was apparently mistaken, the bug didn't come from the .hex file, It comes from a bug in the On-Board Firmware from J-Link. It has been fixed in recent versions.

It is possible to solve the issue by updating the OB FW of your nRF9160 DK. Here is the documentation from SEGGER on how to update it.

I would recommend you going with the latest J-Link version v9.14a. You can download it here.

Best regards,

Simon D-M