NTN with the nrf9151?

AchimKraus

Just to mention:
The “Recovery & Programming Mini Fixture” (unfortunately out of stock) helps sometimes to go back and use jlink.

torntrousers

I’ve tried on a Raspberry Pi and also get no where , always some variation on the “ARM specific error occurred.” is the only way to do it J-Link? Looking at the Feather and an nRF9151 SMA DK i can’t even see where the correct pins or pads are 🙁 is there some picture online that shows how to wire them up?

jaredwolff

You may need to recover it first:

https://docs.circuitdojo.com/nrf9151-feather/device-recovery.html?highlight=recovery#the-solution

Let me try it on the Windows setup I have here to confirm it’s not anything else.

It should definitely work on a RPi running Linux.

torntrousers

Check it out! and with the stock Feather antenna too:

[00:02:40.850,860] <dbg> ntn_module: gnss_location_work_handler: SV:  27 C/N0: 36.2 el: 65 az: 125 signal: 1 in fix: 1 unhealthy: 0
[00:02:40.851,104] <inf> ntn_module: Exiting GNSS mode
[00:02:40.859,313] <dbg> lte_lc: cfun_mode_set: Functional mode set to 30
[00:02:40.859,344] <inf> ntn_module: Entering NTN mode
[00:02:40.985,321] <dbg> lte_lc: edrx_request: enable=1, requested_edrx_value_ltem=0000, edrx_value_ltem=, requested_ptw_value_ltem=, ptw_value_ltem=, 
[00:02:40.985,504] <dbg> lte_lc: edrx_request: enable=1, requested_edrx_value_nbiot=0000, edrx_value_nbiot=, requested_ptw_value_nbiot=, ptw_value_nbiot=
[00:02:40.985,717] <dbg> lte_lc: edrx_request: enable=1, requested_edrx_value_ntn_nbiot=1001, edrx_value_ntn_nbiot=, requested_ptw_value_ntn_nbiot=, ptw_value_ntn_nbiot=
[00:02:40.994,689] <dbg> lte_lc: dns_fallback_set: Fallback DNS address successfully set to 1.1.1.1
[00:02:41.009,460] <dbg> lte_lc: cfun_mode_set: Functional mode set to 0
[00:02:41.014,892] <dbg> lte_lc: xsystemmode_mode_set: System mode set to 8, preference 0
[00:02:41.023,345] <dbg> lte_lc: psm_req: enable=0, tau=00001100, rat=00000011
[00:02:46.024,078] <dbg> ntn_module: set_ntn_active_mode: NTN now initialized, using lte_lc_connect_async to connect to network
[00:02:46.024,108] <dbg> lte_lc: lte_lc_connect_async: Connecting asynchronously
[00:02:46.024,108] <dbg> lte_lc: event_handler_list_handler_append: Handler already registered. Nothing to do
[00:02:46.060,607] <dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=15
[00:02:46.060,729] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A375
[00:02:46.060,760] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00033871
[00:02:46.060,791] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A919
[00:02:46.060,791] <dbg> lte_lc: event_handler_list_dispatch: Done
[00:02:46.060,974] <inf> ntn: Location updates requested immediately, accuracy: 200 m
[00:02:46.061,035] <dbg> ntn_module: ntn_event_handler: NTN location requested: true, accuracy: 200 m
[00:02:46.061,462] <dbg> lte_lc: pdn_on_modem_cfun: Subscribing to +CNEC=16 and +CGEREP=1
[00:02:46.063,385] <dbg> lte_lc: cfun_mode_set: Functional mode set to 1
[00:02:46.063,537] <dbg> ntn_module: state_running_run: NTN location is still valid, skipping location request
[00:03:59.001,098] <dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 2,"0FAA","000F51EA",14
[00:03:59.001,159] <dbg> lte_lc: parse_cereg: Network registration status: 2
[00:03:59.001,312] <dbg> lte_lc: parse_cereg: LTE mode: 14
[00:03:59.001,342] <dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=0
[00:03:59.001,373] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A375
[00:03:59.001,373] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00033871
[00:03:59.001,403] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A919
[00:03:59.001,434] <dbg> lte_lc: event_handler_list_dispatch: Done
[00:03:59.001,464] <dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=4
[00:03:59.001,495] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A375
[00:03:59.001,525] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00033871
[00:03:59.001,556] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A919
[00:03:59.001,556] <dbg> lte_lc: event_handler_list_dispatch: Done
[00:03:59.001,586] <dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=5
[00:03:59.001,617] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A375
[00:03:59.001,617] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00033871
[00:03:59.001,647] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A919
[00:03:59.001,647] <dbg> lte_lc: event_handler_list_dispatch: Done
[00:04:03.872,467] <dbg> lte_lc: at_handler_cscon: +CSCON notification
[00:04:03.872,558] <dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=3
[00:04:03.872,589] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A375
[00:04:03.872,589] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00033871
[00:04:03.872,619] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A919
[00:04:03.872,619] <dbg> ntn_module: lte_lc_evt_handler: LTE_LC_RRC_MODE_CONNECTED
[00:04:03.872,650] <dbg> lte_lc: event_handler_list_dispatch: Done
[00:04:18.497,833] <dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=14
[00:04:18.498,046] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A375
[00:04:18.499,298] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00033871
[00:04:18.499,328] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A919
[00:04:18.499,328] <dbg> ntn_module: lte_lc_evt_handler: PDN connection activated
[00:04:18.499,603] <dbg> lte_lc: event_handler_list_dispatch: Done
[00:04:18.499,816] <dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 5,"0FAA","000F51EA",14,,,"11100000","00111000"
[00:04:18.499,877] <dbg> lte_lc: parse_cereg: Network registration status: 5
[00:04:18.500,061] <dbg> lte_lc: parse_cereg: LTE mode: 14
[00:04:18.500,152] <dbg> lte_lc: parse_cereg: Active time: 11100000
[00:04:18.500,244] <dbg> lte_lc: parse_cereg: TAU: 00111000
[00:04:18.500,274] <dbg> lte_lc: psm_parse: TAU: 86400 sec, active time: -1 sec
[00:04:18.500,305] <dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=0
[00:04:18.500,305] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A375
[00:04:18.500,762] <dbg> ntn_module: state_ntn_run: Setting up socket
[00:04:18.502,716] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00033871
[00:04:18.502,746] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A919
[00:04:18.502,746] <dbg> ntn_module: lte_lc_evt_handler: LTE_LC_NW_REG_REGISTERED_ROAMING
[00:04:18.502,777] <dbg> lte_lc: event_handler_list_dispatch: Done
[00:04:18.502,807] <dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=1
[00:04:18.502,838] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A375
[00:04:18.502,868] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00033871
[00:04:18.502,899] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A919
[00:04:18.502,929] <dbg> lte_lc: event_handler_list_dispatch: Done
[00:04:18.503,051] <dbg> lte_lc: at_handler_cedrxp: +CEDRXP notification
[00:04:18.503,173] <dbg> lte_lc: parse_edrx: eDRX value for NTN NB-IoT: 163.83, PTW: 10.23
[00:04:18.503,204] <dbg> lte_lc: event_handler_list_dispatch: Dispatching event: type=2
[00:04:18.503,234] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A375
[00:04:18.503,265] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x00033871
[00:04:18.503,265] <dbg> lte_lc: event_handler_list_dispatch:  - handler=0x0001A919
[00:04:18.503,295] <dbg> lte_lc: event_handler_list_dispatch: Done
[00:04:18.503,967] <dbg> ntn_module: state_ntn_run: Socket connected successfully
[00:04:18.503,997] <dbg> ntn_module: state_ntn_run: Sending initial GNSS data
[00:04:18.508,392] <dbg> ntn_module: sock_send_gnss_data: Sent GNSS data payload of 82 bytes: Device: *7141, temp: 25, lat=51.59, lon=-0.10, alt=81.82, time=2026-04-03 13:45:56
[00:04:18.508,422] <dbg> ntn_module: state_ntn_run: Initial GNSS data sent successfully

quite happy : )

torntrousers

I don’t know how you get modem updater to work, i had to do this diff (written by AI) before it would successfuly update the modem firmware:
https://community.circuitdojo.com/assets/files/2026-04-03/1775224391-202600-fix.diff

jaredwolff

Thanks for the diff! I’ll look into making sure it’s compatible for both nRF9160 and nRF9151.

jaredwolff

Turned out to be an issue with upgrading the probe-rs crate. Again sorry for the issues @torntrousers. Should be resolved now on Github

jaredwolff

AchimKraus The “Recovery & Programming Mini Fixture” (unfortunately out of stock) helps sometimes to go back and use jlink.

Update: we built a few more and they’re available on the store should anyone need one: https://www.circuitdojo.com/products/recovery-fixture

« Previous Page