board failed after update mfw_nrf9151-ntn_1.0.0-1.alpha firmware

[SimonLou]

I Just got nRF9151  SMA board, try to test NTN feature , after following instruction to update so called "alpha" firmware, somehow the board can not reflash back to any vesion, 

log as bellow

2025-12-29T22:00:50.566Z INFO Initialising the bundled nrfutil device
2025-12-29T22:00:50.581Z DEBUG Started watching devices
2025-12-29T22:00:51.036Z INFO Using the bundled core version for nrfutil device: 8.1.1
2025-12-29T22:00:51.161Z INFO Using nrfutil device version: 2.15.7
2025-12-29T22:00:51.162Z INFO Using nrf-device-lib version: 0.22.5
2025-12-29T22:00:51.163Z INFO Using nrf-probe version: 0.51.0
2025-12-29T22:00:51.163Z INFO Using SEGGER J-Link version: JLink_V8.96
2025-12-29T22:00:51.165Z 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.
2025-12-29T22:00:53.590Z DEBUG Selected device: nRF9151 SMA DK
2025-12-29T22:00:53.707Z DEBUG Changed step: Info
2025-12-29T22:00:59.224Z DEBUG Changed step: Rename
2025-12-29T22:01:01.842Z DEBUG Changed step: Program
2025-12-29T22:01:26.516Z INFO Opened port with options: {"path":"COM44","baudRate":115200}
2025-12-29T22:01:30.545Z INFO Closed port: COM44
2025-12-29T22:01:30.739Z 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: [14], vendor_id: 0x2109, product_id: 0x0822, device_version: 0x0134, usb_version: 0x0320, class: 0x09, subclass: 0x00, protocol: 0x03, speed: Some(Super), manufacturer_string: None, product_string: Some(\"USB3.1 Hub \"), serial_number: None, instance_id: \"USB\\\\VID_2109&PID_0822\\\\5&FA98005&0&14\", parent_instance_id: \"USB\\\\ROOT_HUB30\\\\4&20c3df84&0&0\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(14)\", \"ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(URTH)#ACPI(SSP1)\"], port_number: 14, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x00, interface_string: None }] }", source: None }
2025-12-29T22:01:30.740Z 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: 9, port_chain: [14, 4, 4], vendor_id: 0x2109, product_id: 0x0822, device_version: 0x0134, usb_version: 0x0320, class: 0x09, subclass: 0x00, protocol: 0x03, speed: Some(Super), manufacturer_string: None, product_string: Some(\"USB3.1 Hub \"), serial_number: None, instance_id: \"USB\\\\VID_2109&PID_0822\\\\7&9DB86D0&0&4\", parent_instance_id: \"USB\\\\VID_2109&PID_0822\\\\6&22efc552&0&4\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(14)#USB(4)#USB(4)\", \"ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(URTH)#ACPI(SSP1)#USB(4)#USB(4)\"], port_number: 4, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x00, interface_string: None }] }", source: None }
2025-12-29T22:01:30.741Z 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: 7, port_chain: [14, 4], vendor_id: 0x2109, product_id: 0x0822, device_version: 0x0134, usb_version: 0x0320, class: 0x09, subclass: 0x00, protocol: 0x03, speed: Some(Super), manufacturer_string: None, product_string: Some(\"USB3.1 Hub \"), serial_number: None, instance_id: \"USB\\\\VID_2109&PID_0822\\\\6&22EFC552&0&4\", parent_instance_id: \"USB\\\\VID_2109&PID_0822\\\\5&fa98005&0&14\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(14)#USB(4)\", \"ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(URTH)#ACPI(SSP1)#USB(4)\"], port_number: 4, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x00, interface_string: None }] }", source: None }
2025-12-29T22:01:30.741Z 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: 13, port_chain: [2, 4, 4], vendor_id: 0x2109, product_id: 0x2822, device_version: 0x0134, usb_version: 0x0210, class: 0x09, subclass: 0x00, protocol: 0x02, speed: Some(High), manufacturer_string: None, product_string: Some(\"USB2.0 Hub \"), serial_number: None, instance_id: \"USB\\\\VID_2109&PID_2822\\\\7&86CF86D&0&4\", parent_instance_id: \"USB\\\\VID_2109&PID_2822\\\\6&3075f70&0&4\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(2)#USB(4)#USB(4)\", \"ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(URTH)#ACPI(HSP1)#USB(4)#USB(4)\"], port_number: 4, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x01, interface_string: None }] }", source: None }
2025-12-29T22:01:30.741Z 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: 6, port_chain: [2], vendor_id: 0x2109, product_id: 0x2822, device_version: 0x0134, usb_version: 0x0210, class: 0x09, subclass: 0x00, protocol: 0x02, speed: Some(High), manufacturer_string: None, product_string: Some(\"USB2.0 Hub \"), serial_number: None, instance_id: \"USB\\\\VID_2109&PID_2822\\\\5&FA98005&0&2\", parent_instance_id: \"USB\\\\ROOT_HUB30\\\\4&20c3df84&0&0\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(2)\", \"ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(URTH)#ACPI(HSP1)\"], port_number: 2, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x01, interface_string: None }] }", source: None }
2025-12-29T22:01:30.742Z 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: 8, port_chain: [2, 4], vendor_id: 0x2109, product_id: 0x2822, device_version: 0x0134, usb_version: 0x0210, class: 0x09, subclass: 0x00, protocol: 0x02, speed: Some(High), manufacturer_string: None, product_string: Some(\"USB2.0 Hub \"), serial_number: None, instance_id: \"USB\\\\VID_2109&PID_2822\\\\6&3075F70&0&4\", parent_instance_id: \"USB\\\\VID_2109&PID_2822\\\\5&fa98005&0&2\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(2)#USB(4)\", \"ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(URTH)#ACPI(HSP1)#USB(4)\"], port_number: 4, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x01, interface_string: None }] }", source: None }
2025-12-29T22:01:55.791Z INFO Opened port with options: {"path":"COM44","baudRate":115200}
2025-12-29T22:01:59.816Z INFO Closed port: COM44
2025-12-29T22:01:59.922Z 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: [14], vendor_id: 0x2109, product_id: 0x0822, device_version: 0x0134, usb_version: 0x0320, class: 0x09, subclass: 0x00, protocol: 0x03, speed: Some(Super), manufacturer_string: None, product_string: Some(\"USB3.1 Hub \"), serial_number: None, instance_id: \"USB\\\\VID_2109&PID_0822\\\\5&FA98005&0&14\", parent_instance_id: \"USB\\\\ROOT_HUB30\\\\4&20c3df84&0&0\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(14)\", \"ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(URTH)#ACPI(SSP1)\"], port_number: 14, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x00, interface_string: None }] }", source: None }
2025-12-29T22:01:59.922Z 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: 9, port_chain: [14, 4, 4], vendor_id: 0x2109, product_id: 0x0822, device_version: 0x0134, usb_version: 0x0320, class: 0x09, subclass: 0x00, protocol: 0x03, speed: Some(Super), manufacturer_string: None, product_string: Some(\"USB3.1 Hub \"), serial_number: None, instance_id: \"USB\\\\VID_2109&PID_0822\\\\7&9DB86D0&0&4\", parent_instance_id: \"USB\\\\VID_2109&PID_0822\\\\6&22efc552&0&4\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(14)#USB(4)#USB(4)\", \"ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(URTH)#ACPI(SSP1)#USB(4)#USB(4)\"], port_number: 4, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x00, interface_string: None }] }", source: None }
2025-12-29T22:01:59.923Z 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: 7, port_chain: [14, 4], vendor_id: 0x2109, product_id: 0x0822, device_version: 0x0134, usb_version: 0x0320, class: 0x09, subclass: 0x00, protocol: 0x03, speed: Some(Super), manufacturer_string: None, product_string: Some(\"USB3.1 Hub \"), serial_number: None, instance_id: \"USB\\\\VID_2109&PID_0822\\\\6&22EFC552&0&4\", parent_instance_id: \"USB\\\\VID_2109&PID_0822\\\\5&fa98005&0&14\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(14)#USB(4)\", \"ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(URTH)#ACPI(SSP1)#USB(4)\"], port_number: 4, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x00, interface_string: None }] }", source: None }
2025-12-29T22:01:59.923Z 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: 13, port_chain: [2, 4, 4], vendor_id: 0x2109, product_id: 0x2822, device_version: 0x0134, usb_version: 0x0210, class: 0x09, subclass: 0x00, protocol: 0x02, speed: Some(High), manufacturer_string: None, product_string: Some(\"USB2.0 Hub \"), serial_number: None, instance_id: \"USB\\\\VID_2109&PID_2822\\\\7&86CF86D&0&4\", parent_instance_id: \"USB\\\\VID_2109&PID_2822\\\\6&3075f70&0&4\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(2)#USB(4)#USB(4)\", \"ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(URTH)#ACPI(HSP1)#USB(4)#USB(4)\"], port_number: 4, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x01, interface_string: None }] }", source: None }
2025-12-29T22:01:59.923Z 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: 6, port_chain: [2], vendor_id: 0x2109, product_id: 0x2822, device_version: 0x0134, usb_version: 0x0210, class: 0x09, subclass: 0x00, protocol: 0x02, speed: Some(High), manufacturer_string: None, product_string: Some(\"USB2.0 Hub \"), serial_number: None, instance_id: \"USB\\\\VID_2109&PID_2822\\\\5&FA98005&0&2\", parent_instance_id: \"USB\\\\ROOT_HUB30\\\\4&20c3df84&0&0\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(2)\", \"ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(URTH)#ACPI(HSP1)\"], port_number: 2, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x01, interface_string: None }] }", source: None }
2025-12-29T22:01:59.923Z 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: 8, port_chain: [2, 4], vendor_id: 0x2109, product_id: 0x2822, device_version: 0x0134, usb_version: 0x0210, class: 0x09, subclass: 0x00, protocol: 0x02, speed: Some(High), manufacturer_string: None, product_string: Some(\"USB2.0 Hub \"), serial_number: None, instance_id: \"USB\\\\VID_2109&PID_2822\\\\6&3075F70&0&4\", parent_instance_id: \"USB\\\\VID_2109&PID_2822\\\\5&fa98005&0&2\", location_paths: [\"PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(2)#USB(4)\", \"ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(URTH)#ACPI(HSP1)#USB(4)\"], port_number: 4, driver: Some(\"USBHUB3\"), interfaces: [InterfaceInfo { interface_number: 0, class: 0x09, subclass: 0x00, protocol: 0x01, interface_string: None }] }", source: None }

[Simon D-M]

Hi Simon,

I have a few questions to get a bit more context:

log as bellow

Are these logs from the "Programmer" app ? Is the DK recognized by the "Programmer" app (appears in the device list, top left) ?

Has your nRF9151-SMA-DK ever worked before the modem update ?

Have you tried to recover your device with nrfutil? To recover a device with nRF Util, run the command "nrfutil.exe device recover --family nrf91" with the DK connected to your computer. 

Tell me if this last part helped you.

Best regards,

Simon D-M

[SimonLou]

There is my issue

1. When I done 1.0.0.1.alpha, on the left site orange color on the button still there, after I load lte_modem.hex, that part disapear, and on the board LED1 goes off, an none of way through comport works

2. I follow Monogoto site for nRf9151 SMA step by step, still fail

3. And my nRF connect default only 2.0.3 modem core, that is only can bring back the board for AT command

Any idea?

[SimonLou]

Hi Simon D-M

thanks for reply,

yes, I  think I have follow the instruction to do so.

1. the default firmware I got with the new board  is 2.0.3, which I can "quick start" to rollback.

2. I download 2.0.2 and unzip it, there is a zip file "mfw_nrf91x1_2.0.2.zip" which I use for "Erase and write"

3. then I use "mfw_nrf9151-ntn_1.0.0-1.alpha.zip" to "write"

4. after finish both, things happened as below

4.1 the LED1 is off

4.2 and AT command has no respond when I input.

5. then I use "quick start" to roll back to 2.0.3, LED1 is on, and AT command works find

and I also found that AT command ver 0.7 vs 1.04 (good for 2.0.3)the parament count are different , on ver 0.7 has 5, but 1.0.4 only 4

I think this is my problem for now. 

and under 2.0.3, GNSS does not seem getting any number either

below is screenshot for "write 1.0.1 alpha.zip" and after AT command no respond

and also if I user teraterm, the input also no respond to any thing.

Hi Simon D-M

First where I can download complete AT command for NTN network?

After clarify and reorganize the update steps, I finally to get the board at least able to send most of the GNSS and NTN command respond "OK"

1. run ""Program" with "nrf9151dk_mfw-2.0.2_sdk-3.1.0.zip"
1.1 unzip and load the mfw_nrf91x1_2.0.2.zip with "write"
1.2 find nrf9151dk_serial_lte_modem_2025-08-14_6c6e5b32.hex under "img_app_bl" folder, this one come with bootloader, "Erase and Write"
1.3 "add file" and browse "mfw_nrf9151-ntn_1.0.0-1.alpha.zip" where you can download from Nordic
www.nordicsemi.com/.../Download
1.4 After finish write, click on "close" and click on "Read"
1.5. this step very important, push "Reset" button on the board located at below type C connector
1.6. and open "serial terminal" and type "at at_cmd_mode" , you will enter AT command mode
1.7. type in "at+cgmr", you should see modem firmware version is
> at
at
OK
> at+cgmr
at+cgmr
mfw_nrf9151-ntn_1.0.0-1.alpha
OK

2. insert your activated NTN SIM card(one comes with package from "onomodo", 50KB free

Now you can follow the step post on Monogoto test GNSS and NTN with NTN sim come with the box

docs.monogoto.io/.../nordic-nrf9151-satellite-ntn-network

[Simon D-M]

Hi,

SimonLou said:

First where I can download complete AT command for NTN network?

As said on the changelog (link), the modem firmware ntn_1.0.0-1.alpha is aligned with v0.7 of the mfw_nrf9151-ntn AT Commands Reference Guide.

SimonLou said:

1. run ""Program" with "nrf9151dk_mfw-2.0.2_sdk-3.1.0.zip"
1.1 unzip and load the mfw_nrf91x1_2.0.2.zip with "write"
1.2 find nrf9151dk_serial_lte_modem_2025-08-14_6c6e5b32.hex under "img_app_bl" folder, this one come with bootloader, "Erase and Write"
1.3 "add file" and browse "mfw_nrf9151-ntn_1.0.0-1.alpha.zip" where you can download from Nordic
www.nordicsemi.com/.../Download
1.4 After finish write, click on "close" and click on "Read"
1.5. this step very important, push "Reset" button on the board located at below type C connector
1.6. and open "serial terminal" and type "at at_cmd_mode" , you will enter AT command mode
1.7. type in "at+cgmr", you should see modem firmware version is
> at
at
OK
> at+cgmr
at+cgmr
mfw_nrf9151-ntn_1.0.0-1.alpha
OK

2. insert your activated NTN SIM card(one comes with package from "onomodo", 50KB free

If you program the modem with the NTN modem firmware (1.3) you can skip programming the normal cellular firmware (1.1) as the NTN modem firmware is a complete modem firmware and not a patch.

Also, I would recommend building the "serial modem addon" (previously called "serial lte modem" or "slm") from source to have the latest version. We have a guide on how to do it.

(1.6) you shouldn't need to type "at_cmd_mode". It should already be ready for AT commands. However, there is a thing to be aware. The AT commands are VERY sensitive to invisible characters. So if a command doesn't work, be sure not to copy-paste it but instead write it from scratch. Also be careful with other serial terminals as they may add some unwanted termination characters that might mess up with the command.

Best regards,

Simon D-M

[SimonLou]

Hi Simon D-M

thanks for clarify. it looks like Nordic has not complete the packaging for NTN firmware as official upgrade.

there are couple of the questions for you

1. where I can find the hardware pin connection to RX/TX to external usb-ttl dongle? or for external arduino/Raspbarrery  connectivity

2. Is there an programming guide for console command, although I am not able to use if for now

Simon

[Achim Kraus]

A nRF91 SoC, in difference to most modems in market, is not just a modem; it's a modem and a combined application MCU (=> System on a Chip). The AT-cmds are therefore not passed via a UART to the modem (as others do), the AT-cmds are passed in using c-functions on the application MCU (and AFAIK uses internally IPC instead of UART).

The pins to connect a external usb-ttl will only connect to the application MCU, not to the modem. Therefore it will not enable you to send AT-cmd directly to the modem. It will only enable you to send data to the application MCU. But without application, it's not defined, what the application MCU will do with that.

Therefore, you will need:

- the modem ntn firmware. If you continue to unzip it, you continue to fail. Apply the zipped download with the tools explained a couple of times here in the forum.

- the "serial lte modem" (or a "serial modem addon"), which must be applied to the application MCU. I'm not sure, how successful you will be to build it on your own. But I also don't know, if Nordic (still) has prebuild NTN binaries as for the NTN versions before. 

After you applied both, the modem firmware and the "serial lte ...", you will be able to pass in AT-cmd to the application MCU, which will forward them to the modem.

For those, who only look for a "modem + uart at-cmds" that comes with some more complexity. But for those who look for a complete system (SoC), the nRF91 is unique and building own apps for the application MCU is much easier than doing all the AT-cmd uart stuff required by others.

[SimonLou]

Hi Achim

Thanks for your info, I guess I wilk wait till Nordic make official production release, then start again.

I am receiving MuRata, Quectel modules, there are AT command ready and also pythony ready to hand on.

Simon

[Simon D-M]

Hi,

If you want to learn to use the nRF91 series, I would recommend trying our courses on DevAcademy. If you are not familiar with Zephyr RTOS, I would recommend first taking "nRF Connect SDK Fundamentals" and then you can take "Cellular IoT Fundamentals" which was made for learning how to use cellular technologies with our nRF91 series.

Best regards,

Simon D-M