nRF9160 SIBA unable to connect to NB-IoT network and resets every ~10 seconds.

[elephant]

nRF9160 SIBA on custom board is unable to connect to NB-IOT and resets after about 10 seconds of operation.

Without a call to lte_lc_init_and_connect the reset does not happen.

The power, as suggested in other topics is at 2.6V from dc power supply with limit set to 1A.

Side note: this setting is the only one allowing for the programmer to reach the SiP. At planned 3.3V the programmer is not able to connect to the chip. For now just a missing power IC -> power supply is used.

[JONATHAN LL]

Hi,

Can you provide a log ?

What application are you using? 

Does this happen with the AT_client ?

What MF do you have?

Regards,
Jonathan

[elephant]

As for logs. No, no uart is pointing outside, so this is problematic. Unless there is a possibility to stream logs through debug interface. Is there any?

As for app. I made a custom app. It gets stuck inside lte_lc_init_and_connect waiting for the cellular network. For about 5-7 seconds the board draws ~50mA of current -> RX mode. Then drops back to ~0. No luck with mqtt_simple sample either.

As for a reset. I figured out the cause was inside custom board files. With thingy board + custom overlay = no reset. Let these files be issue number two.

I have no idea what MF means. Manufacturer does not seem to fit.

[JONATHAN LL]

elephant said:

I have no idea what MF mean

 MF = Modem Firmware, nRF9160 DK - Downloads - nordicsemi.com


You can share the HW files an i can have a look, see if there is anything that might pose a problem. If you dont want to have the files public i can make this case private.
Regards,
Jonathan

[elephant]

Might be my bad, but it is 1.3.0 on a chip rev. B0. Did upgrade before thorough reading. It did not work with stock FW so I did an upgrade blindly.

The possibility of posting hw files is being discussed.

[JONATHAN LL]

mfw 1.3.0 on a B0 SiP should not brick the device, or be of a issue for testing or development, but it wont pass production certification.

So the issue is probably elsewhere, could you try the AT Client on your custom board?

As for debugging there is RTT that you could use, here is a different case on the RTT logging: How to setup Zephyr for RTT logging with nRF9160 - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)


Regards,
Jonathan