Hi
I want to use nRF9151DK and i have jio NB-IOT sim card.
I flashed asset tracker application from quick start and it is not working or connecting to internet this is the celluler monitor report I'm attaching.
What i have tried
1:- APN:- jionet/ JioIPIoT
2:-PDP type:- IPV4V6 / IPV6
3:-Force to NB-IOT Mode
What is the issue for this is there any configs which is wrong ?
Hi,
My first guess would be that your RSRP (reference signal received power) might be too low to get a proper connection. Would it be possible for you to try from somewhere where you have a better connection with the cell tower?
However, I'm missing quite a lot of information before I can make a good guess about what is happening. Keep in mind that my first guess might be wrong here.
Can you please provide the full UART logs?
Can you also provide the raw modem trace (.mtrace or .bin) from the cellular monitor?
And just to be sure, did you activate your SIM card before trying to connect to the network?
Best regards,
Simon D-M
Hi Simon,
I have re-tested and observed some improvement in signal strength; however, the device is still unable to connect to the network.
Kindly review the attached files for reference.
Can you please provide the full UART logs?
serial-terminal-07042026_181430
Can you also provide the raw modem trace (.mtrace or .bin) from the cellular monitor?
trace-2026-04-07T12-26-28.581Z.mtrace
did you activate your SIM card before trying to connect to the network?
I have raised the query with the SIM provider and will update once I receive confirmation.
Thanks
Atul v
Hi,
Atul vishwakarma said:Can you please provide the full UART logs?
I only see AT commands. Can you try to connect the Serial Monitor and then reset the board using the reset button on the board?
What you want to see should look like this :
*** Booting nRF Connect SDK v3.1.99-234f4874371b *** *** Using Zephyr OS v4.1.99-1d73d0e3cb5f *** Attempting to boot slot 0. Attempting to boot from address 0x8200. I: Trying to get Firmware version I: Verifying signature against key 0. I: Hash: 0x53...a2 I: Firmware signature verified. Firmware version 1 *** Booting My Application v2.1.0-dev-e1f2ab3806ce *** *** Using nRF Connect SDK v3.1.99-234f4874371b *** *** Using Zephyr OS v4.1.99-1d73d0e3cb5f *** I: Starting bootloader I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3 I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3 I: Boot source: none I: Image index: 0, Swap type: none I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3 I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3 I: Boot source: none I: Image index: 1, Swap type: none I: Bootloader chainload address offset: 0x38000 I: Image version: v1.2.1 All pins have been configured as non-secure Booting TF-M v2.1.2 [Sec Thread] Secure image initializing! TF-M isolation level is: 0x00000001 TF-M Float ABI: Hard Lazy stacking enabled [00:00:00.254,699] <inf> spi_nor: gd25wb256e3ir@1: 32 MiBy flash *** Booting Asset Tracker Template v1.2.1-6f28a0a6d8b0 *** *** Using nRF Connect SDK v3.1.99-234f4874371b *** *** Using Zephyr OS v4.1.99-1d73d0e3cb5f *** [00:00:00.262,786] <dbg> main: main: Main has started [00:00:00.262,847] <dbg> main: running_entry: running_entry [00:00:00.262,878] <dbg> main: passthrough_mode_entry: passthrough_mode_entry [00:00:00.262,939] <dbg> main: passthrough_disconnected_entry: passthrough_disconnected_entry [00:00:00.263,732] <dbg> cloud: cloud_module_thread: Cloud module task started [00:00:00.263,793] <dbg> cloud: state_running_entry: state_running_entry [00:00:00.263,854] <inf> nrf_provisioning_coap: Init CoAP client [00:00:00.264,526] <dbg> cloud: state_disconnected_entry: state_disconnected_entry [00:00:00.264,892] <dbg> main: passthrough_disconnected_entry: passthrough_disconnected_entry [00:00:00.265,258] <dbg> fota: fota_module_thread: FOTA module task started [00:00:00.265,319] <dbg> fota: state_running_entry: state_running_entry [00:00:00.266,143] <dbg> fota: state_waiting_for_poll_request_entry: state_waiting_for_poll_request_entry [00:00:00.266,265] <dbg> location_module: location_module_thread: Location module task started [00:00:00.266,357] <dbg> location_module: state_running_entry: state_running_entry [00:00:00.266,998] <dbg> location_module: state_running_entry: Location library initialized [00:00:00.267,150] <dbg> network: state_running_entry: state_running_entry [00:00:00.267,181] <inf> network: Bringing network interface up and connecting to the network [00:00:00.534,149] <inf> nrf_modem_lib_trace: Trace thread ready [00:00:00.542,144] <inf> nrf_modem_lib_trace: Trace level override: 2 [00:00:00.653,686] <dbg> nrf_provisioning: cert_provision: Certificate already provisioned ...
And if you see in the logs something like this:
[00:00:08.477,142] <err> nrf_provisioning_coap: Device didn't send auth credentials [00:00:08.479,553] <wrn> nrf_provisioning: Unauthorized access: device is not yet claimed. [00:00:08.565,124] <wrn> cloud: Provisioning failed, device not claimed [00:00:08.565,155] <wrn> cloud: Claim the device using the device's attestation token on nrfcloud.com [00:00:08.565,216] <wrn> cloud: 2peeY5OEjRbg2FK1sYc1nM4DMGGPzAx5XIUtltV5M5d81R3kFD2UcvLc0FqCRu1NB6nOyvV4kJFwG1BG8AsfeaAe38Bx18w65yvDg5U5WxaNkNU9pywdMxhMP0KswD9v4xi4XxTfgcu64EbcdzwDzVxXBv6nCI6eKJeT32xmHjiWWGjZ0WAb
Either remove the token (long chain of character) or ask me to make this ticket private first.
If you manage to get this output, can you send it to me please?
Best regards,
Simon D-M
I only see AT commands. Can you try to connect the Serial Monitor and then reset the board using the reset button on the board?
Yes, I have shared the AT command logs for reference. I verified network detection using the AT Command sample with Cellular Monitor.
However, when running the Asset Tracker sample, the device is not able to successfully register to the network.
Here is the serial log from the Asset Tracker sample.
serial-terminal-07042026_191158
Hi Atul,
The modem is detecting a reset loop. It can be caused by a lot of different things.
In the traces, it looks like the either your SIM has not been provisioned or that you use the wrong APN for your SIM.
I don't have experience with that particular SIM provider so it would be best to ask them directly to check if your SIM have indeed been provisioned and activated. And ask them what is the right APN for your SIM card.
Best regards,
Simon D-M
reset loop
Atul vishwakarma let me recommend, that you read through the docu about the reset loop. It's somehow very special. If you want to overcome it, you will need to power the device for some time (30 minutes?) and the application must be stable to not reset on its own in that period. That may include watchdog resets or resets executing when flashing the device. As alternative to waiting, you may try to stop the modem with at+cfun=0 and then execute a factory reset with AT%XFACTORYRESET=0. After that, you may have a chance to exit the "reset loop" on your next reboot.
reset loop
Atul vishwakarma let me recommend, that you read through the docu about the reset loop. It's somehow very special. If you want to overcome it, you will need to power the device for some time (30 minutes?) and the application must be stable to not reset on its own in that period. That may include watchdog resets or resets executing when flashing the device. As alternative to waiting, you may try to stop the modem with at+cfun=0 and then execute a factory reset with AT%XFACTORYRESET=0. After that, you may have a chance to exit the "reset loop" on your next reboot.
Correct, I forgot to tell you about this.
Here is the link to the reset loop documentation.
@geometry dashThanks for sharing this valuable information. It’s very appreciated.
