nrf_cloud_mqtt_cell_location fails in flash sector allocation.

[Nicholas Papachristos]

I am testing the un-unmodified cloud_mqtt_cell_location sample application, and my build configuration is as follows:

SDK: nRF        Connect SDK v3.4.0

Toolchain:        nRF Connect SDK Toolchain v3.4.0

Board Target:   thingy91x/nrf9151/ns

System Build:   Default

When the application runs, function flash_area_open().returns -19. I am using my own little bootloader, that runs the application from address 0x30200.

The terminal output is: <

*** Booting My Application v1.0.0-4589093774ea ***
*** Using nRF Connect SDK v3.4.0-99553055607b ***
*** Using Zephyr OS v4.4.0-bf801e4e3d19 ***
[00:00:06.779,113] <inf> nrf_cloud_mqtt_cell_location_sample: nRF Cloud MQTT Cellular Location Sample, version: 1.0.0
[00:00:07.729,797] <inf> nrf_cloud_mqtt_cell_location_sample: Connecting to LTE...
+CGEV: EXCE STATUS 0
%MDMEV: SEARCH STATUS 1
+CEREG: 2,"2149","03162E49",9
%MDMEV: PRACH CE-LEVEL 0
+CSCON: 1
+CEREG: 2,"2149","03162E49",9,0,15
[00:03:51.011,352] <wrn> lte_lc: Registration rejected, EMM cause: 15, Cell ID: 51785289, Tracking area: 8521, LTE mode: 9
+CSCON: 0
+CEREG: 2
%MDMEV: SEARCH STATUS 2
+CEREG: 2,"9D6C","0010330D",7
%MDMEV: PRACH CE-LEVEL 0
+CSCON: 1>

How can I solve the problem?

[Håkon Alseth]

Hi,

 

Based on your log, it seems that the application boots correctly. I cannot see the log line that you mention:

function flash_area_open().returns -19.

-19 is ENODEV, meaning that it cannot find the storage.

 

However, this log line indicate that there is no NB-IoT coverage in your area (connecting to a network that is not allowing you to roam):

[00:03:51.011,352] <wrn> lte_lc: Registration rejected, EMM cause: 15, Cell ID: 51785289, Tracking area: 8521, LTE mode: 9

And the remainder of the log shows that it switches to LTE cat M1, and continues to search for cell coverage in your area.

 

Kind regards,

Håkon