asset_tracker: Connection was closed by the cloud.

RE: asset_tracker: Connection was closed by the cloud.

Didrik Rokhaug — Mon, 17 Feb 2020 09:21:50 GMT

The point of removing the SIM was to get enough time before the reset to send the %XMODEMTRACE command.

When capturing the trace, you need to have the SIM in, so that the trace is able to capture the disconnect from the cloud.

Sorry if I was not clear.

RE: asset_tracker: Connection was closed by the cloud.

maaya_tech — Fri, 14 Feb 2020 17:24:22 GMT

after disconnecting everything and connecting again.. retsarting the world, I was able to reflash.. I entered the command AT%XMONITOR=1,2 and at+CFUN=0

Removed the sim as mentioned above.. resset the board and started capture.. attached the tracefile and here's the log

*** Booting Zephyr OS version 2.1.99  ***

[00:00:00.003,814] 

[0m<inf> mcuboot: Starting bootloader

[0m

[00:00:00.011,932] 

[0m<inf> mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3

[0m

[00:00:00.025,146] 

[0m<inf> mcuboot: Boot source: none

[0m

[00:00:00.032,318] 

[0m<inf> mcuboot: Swap type: none

[0m

[00:00:00.459,564] 

[0m<inf> mcuboot: Bootloader chainload address offset: 0xc000

[0m

[00:00:00.469,635] 

[0m<inf> mcuboot: Jumping to the first image slot

[0m

*** Booting Zephyr OS version 2.1.99  ***

Flash region

	

	

Domain

	

	

Permissions

00 0x00000 0x08000 

	

Secure

	

	

rwxl

01 0x08000 0x10000 

	

Secure

	

	

rwxl

02 0x10000 0x18000 

	

Secure

	

	

rwxl

03 0x18000 0x20000 

	

Non-Secure

	

rwxl

04 0x20000 0x28000 

	

Non-Secure

	

rwxl

05 0x28000 0x30000 

	

Non-Secure

	

rwxl

06 0x30000 0x38000 

	

Non-Secure

	

rwxl

07 0x38000 0x40000 

	

Non-Secure

	

rwxl

08 0x40000 0x48000 

	

Non-Secure

	

rwxl

09 0x48000 0x50000 

	

Non-Secure

	

rwxl

10 0x50000 0x58000 

	

Non-Secure

	

rwxl

11 0x58000 0x60000 

	

Non-Secure

	

rwxl

12 0x60000 0x68000 

	

Non-Secure

	

rwxl

13 0x68000 0x70000 

	

Non-Secure

	

rwxl

14 0x70000 0x78000 

	

Non-Secure

	

rwxl

15 0x78000 0x80000 

	

Non-Secure

	

rwxl

16 0x80000 0x88000 

	

Non-Secure

	

rwxl

17 0x88000 0x90000 

	

Non-Secure

	

rwxl

18 0x90000 0x98000 

	

Non-Secure

	

rwxl

19 0x98000 0xa0000 

	

Non-Secure

	

rwxl

20 0xa0000 0xa8000 

	

Non-Secure

	

rwxl

21 0xa8000 0xb0000 

	

Non-Secure

	

rwxl

22 0xb0000 0xb8000 

	

Non-Secure

	

rwxl

23 0xb8000 0xc0000 

	

Non-Secure

	

rwxl

24 0xc0000 0xc8000 

	

Non-Secure

	

rwxl

25 0xc8000 0xd0000 

	

Non-Secure

	

rwxl

26 0xd0000 0xd8000 

	

Non-Secure

	

rwxl

27 0xd8000 0xe0000 

	

Non-Secure

	

rwxl

28 0xe0000 0xe8000 

	

Non-Secure

	

rwxl

29 0xe8000 0xf0000 

	

Non-Secure

	

rwxl

30 0xf0000 0xf8000 

	

Non-Secure

	

rwxl

31 0xf8000 0x100000 

	

Non-Secure

	

rwxl

Non-secure callable region 0 placed in flash region 2 with size 32.

SRAM region

	

	

Domain

	

	

Permissions

00 0x00000 0x02000

	

Secure

	

	

rwxl

01 0x02000 0x04000

	

Secure

	

	

rwxl

02 0x04000 0x06000

	

Secure

	

	

rwxl

03 0x06000 0x08000

	

Secure

	

	

rwxl

04 0x08000 0x0a000

	

Secure

	

	

rwxl

05 0x0a000 0x0c000

	

Secure

	

	

rwxl

06 0x0c000 0x0e000

	

Secure

	

	

rwxl

07 0x0e000 0x10000

	

Secure

	

	

rwxl

08 0x10000 0x12000

	

Non-Secure

	

rwxl

09 0x12000 0x14000

	

Non-Secure

	

rwxl

10 0x14000 0x16000

	

Non-Secure

	

rwxl

11 0x16000 0x18000

	

Non-Secure

	

rwxl

12 0x18000 0x1a000

	

Non-Secure

	

rwxl

13 0x1a000 0x1c000

	

Non-Secure

	

rwxl

14 0x1c000 0x1e000

	

Non-Secure

	

rwxl

15 0x1e000 0x20000

	

Non-Secure

	

rwxl

16 0x20000 0x22000

	

Non-Secure

	

rwxl

17 0x22000 0x24000

	

Non-Secure

	

rwxl

18 0x24000 0x26000

	

Non-Secure

	

rwxl

19 0x26000 0x28000

	

Non-Secure

	

rwxl

20 0x28000 0x2a000

	

Non-Secure

	

rwxl

21 0x2a000 0x2c000

	

Non-Secure

	

rwxl

22 0x2c000 0x2e000

	

Non-Secure

	

rwxl

23 0x2e000 0x30000

	

Non-Secure

	

rwxl

24 0x30000 0x32000

	

Non-Secure

	

rwxl

25 0x32000 0x34000

	

Non-Secure

	

rwxl

26 0x34000 0x36000

	

Non-Secure

	

rwxl

27 0x36000 0x38000

	

Non-Secure

	

rwxl

28 0x38000 0x3a000

	

Non-Secure

	

rwxl

29 0x3a000 0x3c000

	

Non-Secure

	

rwxl

30 0x3c000 0x3e000

	

Non-Secure

	

rwxl

31 0x3e000 0x40000

	

Non-Secure

	

rwxl

Peripheral

	

	

Domain

	

	

Status

00 NRF_P0               Non-Secure

	

OK

01 NRF_CLOCK            Non-Secure

	

OK

02 NRF_RTC0             Non-Secure

	

OK

03 NRF_RTC1             Non-Secure

	

OK

04 NRF_NVMC             Non-Secure

	

OK

05 NRF_UARTE1           Non-Secure

	

OK

06 NRF_UARTE2           Secure

	

	

SKIP

07 NRF_TWIM2            Non-Secure

	

OK

08 NRF_SPIM3            Non-Secure

	

OK

09 NRF_TIMER0           Non-Secure

	

OK

10 NRF_TIMER1           Non-Secure

	

OK

11 NRF_TIMER2           Non-Secure

	

OK

12 NRF_SAADC            Non-Secure

	

OK

13 NRF_PWM0             Non-Secure

	

OK

14 NRF_PWM1             Non-Secure

	

OK

15 NRF_PWM2             Non-Secure

	

OK

16 NRF_PWM3             Non-Secure

	

OK

17 NRF_WDT              Non-Secure

	

OK

18 NRF_IPC              Non-Secure

	

OK

19 NRF_VMC              Non-Secure

	

OK

20 NRF_FPU              Non-Secure

	

OK

21 NRF_EGU1             Non-Secure

	

OK

22 NRF_EGU2             Non-Secure

	

OK

23 NRF_DPPIC            Non-Secure

	

OK

24 NRF_GPIOTE1          Non-Secure

	

OK

25 NRF_REGULATORS       Non-Secure

	

OK

SPM: NS image at 0x18200

SPM: NS MSP at 0x2002e910

SPM: NS reset vector at 0x20371

SPM: prepare to jump to Non-Secure image.

*** Booting Zephyr OS version 2.1.99  ***

[00:00:00.235,870] 

[0m<dbg> nrf9160_gps.init: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577

[0m

[00:00:00.253,051] 

[0m<dbg> nrf9160_gps.init: COEX0 set: AT%XCOEX0=1,1,1570,1580

[0m

[00:00:00.261,291] 

[0m<inf> asset_tracker: Asset tracker started

[0m

[00:00:00.291,412] 

[0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100028375

[0m

[00:00:00.300,689] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100028375/shadow

[0m

[00:00:00.312,408] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100028375/shadow/get/accepted

[0m

[00:00:00.323,974] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100028375/shadow/get/rejected

[0m

[00:00:00.336,578] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100028375/shadow/update/delta

[0m

[00:00:00.349,548] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100028375/shadow/update

[0m

[00:00:00.361,450] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100028375/shadow/get

[0m

[00:00:00.373,779] 

[0m<inf> asset_tracker: Connecting to LTE network. 

[0m

[00:00:00.380,554] 

[0m<inf> asset_tracker: This may take several minutes.

[0m

[00:00:00.415,832] 

[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0

[0m

+CEREG: 90

[00:00:00.730,346] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 90

[0m

devzone.nordicsemi.com/.../trace_2D00_2020_2D00_02_2D00_14T17_2D00_19_2D00_20.581Z.bin

RE: asset_tracker: Connection was closed by the cloud.

maaya_tech — Fri, 14 Feb 2020 16:57:41 GMT

and here's the jlink log

Preparing target for download
Executing Reset script TargetInterface.resetAndStop()
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading ‘merged.hex’ to J-Link
Programming 34.1 KB of addresses 00000000 — 0000888f
Programming 223.3 KB of addresses 0000c000 — 00043d6b
Timeout while erasing sectors, RAMCode did not respond in time. (PC = 0xFFFFFFFF, CPSR = 0x00000000, LR = 0x21000003)!
Failed to erase sectors.
Download failed

RE: asset_tracker: Connection was closed by the cloud.

maaya_tech — Fri, 14 Feb 2020 16:49:44 GMT

I use SES.. after making the change.. and when i click on "Build and run".. it starts building and then pops a window asking "the project zephyre/merged.hex" is out of date and needs to be rebuild" Build the project before rebuilding".. I clicked yes and i see
"Failed to download application. Undocumented error" is what I get if I make that ONE change and build and run from SES

Now, if I go back to CONFIG_BSD_LIBRARY_TRACE_ENABLED=n, I see the same exact error.

Rest assured.. I have NOT touched ANYTHING other than making this one line change

RE: asset_tracker: Connection was closed by the cloud.

maaya_tech — Fri, 14 Feb 2020 16:43:26 GMT

did you do it on the form nrf-<IMEI>
Yes.. I did it with nrd-<IMEI> it was very clearly mentioned and was easy not to miss it

RE: asset_tracker: Connection was closed by the cloud.

Didrik Rokhaug — Thu, 13 Feb 2020 14:37:46 GMT

Hi, have you been able to connect your DK to nRF Cloud yet?

One possible reason for your problem is that the certificates you created were for the wrong device ID.

When you entered the IMEI, did you do it on the form nrf-<IMEI>, or just <IMEI>?

If it was the latter, could you try to create new certificates, but in the device ID field, enter nrf-<IMEI> (replacing <IMEI> with the IMEI of your DK)?

Best regards,

Didrik

RE: asset_tracker: Connection was closed by the cloud.

Didrik Rokhaug — Mon, 10 Feb 2020 09:19:30 GMT

I do understand your frustration, and we are working on making things easier.

Yes, the guide is up-to-date.

[quote user="maaya_tech"]and now you would want us to flash a copletely different app and fw to debug what's broken in a different sample application.[/quote]

There is no need to flash a different application, and I can not see that mentioned in the guide I linked. It does say that you must have the correct firmware flashed to the board controller, but if you have not touched that, there is no need to flash anything other than the application you want to debug with CONFIG_BSD_LIBRARY_TRACE_ENABLED=y.

So, if you have not changed the firmware on the board controller, you must do the following:

1. Add CONFIG_BSD_LIBRARY_TRACE_ENABLED=y in the prj.conf file in the asset_tracker folder.

2. Build and flash the asset_tracker application.

3. In the "LTE Link Monitor" application (in nRF Connect for Desktop), connect to you DK, and send the AT%XMONITOR=1,2 command.

4. Send AT+CFUN=0 to store the command in flash.

5. Open the "Trace Collector" application (in nRF Connect for Desktop), select your device, reset the device and press the "Start Capture" button.

6. Send me the captured modem trace along with the log from the "LTE Link Monitor".

To avoid the device resetting due to your problem in steps 3 and 4, you can remove the SIM card while you are doing those steps, before inserting it again when capturing the modem trace.

Best regards,

Didrik

RE: asset_tracker: Connection was closed by the cloud.

maaya_tech — Fri, 07 Feb 2020 17:29:59 GMT

that article is dated april 2019.. can you confirm if it is up-to-date ? it is very difficult for me to spend another day going through some document and then find out it is not exactly accurate..

all we need to see is a sample application with NO CHANGES MADE locally , running on an off the shelf dev board supplied by you, using a sim card supplied by you and using the nrf cloud .. I have had to file 5 tickets so far , have had to go through half a dozen different documents , despite following everything mentioned in nrf connect getting started section and we are not even close .. and now you would want us to flash a copletely different app and fw to debug what's broken in a different sample application.. I hope you understand the frustration.. and the fact that due to lack of accurate and consistent documentation and at least one day turn around time for any questions we have, it takes a lot of our time to use this chip for even as basic as a demo sample app .. I have generally had a good experience with nrf52 series and hence we decided to go with nrf91 series as well.. I will give this one last chance

RE: asset_tracker: Connection was closed by the cloud.

Didrik Rokhaug — Fri, 07 Feb 2020 15:32:57 GMT

Could you capture a modem trace for me, where you receive the POLLHUP?

You can capture a modem trace by following this guide: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/how-to-get-modem-trace-using-trace-collector-in-nrf-connect

RE: asset_tracker: Connection was closed by the cloud.

maaya_tech — Thu, 06 Feb 2020 16:18:24 GMT

c:\nrf\fw-nrfconnect-nrf>git rev-parse HEAD

d3130d77559e2206a2541b09dd26e9be2f8532ed

RE: asset_tracker: Connection was closed by the cloud.

Didrik Rokhaug — Thu, 06 Feb 2020 13:56:39 GMT

Hi.

Could you run "git rev-parse HEAD" inside the "nrf" folder, and send me the output?

Best regards,

Didrik

RE: asset_tracker: Connection was closed by the cloud.

maaya_tech — Thu, 06 Feb 2020 05:28:20 GMT

here's the complete log

*** Booting Zephyr OS version 2.1.99 ***
[00:00:00.003,509] <inf> mcuboot: Starting bootloader
[00:00:00.009,674] <inf> mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.019,714] <inf> mcuboot: Boot source: none
[00:00:00.025,146] <inf> mcuboot: Swap type: none
[00:00:00.348,388] <inf> mcuboot: Bootloader chainload address offset: 0xc000
[00:00:00.356,048] <inf> mcuboot: Jumping to the first image slot
*** Booting Zephyr OS version 2.1.99 ***
Flash region Domain Permissions
00 0x00000 0x08000 Secure rwxl
01 0x08000 0x10000 Secure rwxl
02 0x10000 0x18000 Secure rwxl
03 0x18000 0x20000 Non-Secure rwxl
04 0x20000 0x28000 Non-Secure rwxl
05 0x28000 0x30000 Non-Secure rwxl
06 0x30000 0x38000 Non-Secure rwxl
07 0x38000 0x40000 Non-Secure rwxl
08 0x40000 0x48000 Non-Secure rwxl
09 0x48000 0x50000 Non-Secure rwxl
10 0x50000 0x58000 Non-Secure rwxl
11 0x58000 0x60000 Non-Secure rwxl
12 0x60000 0x68000 Non-Secure rwxl
13 0x68000 0x70000 Non-Secure rwxl
14 0x70000 0x78000 Non-Secure rwxl
15 0x78000 0x80000 Non-Secure rwxl
16 0x80000 0x88000 Non-Secure rwxl
17 0x88000 0x90000 Non-Secure rwxl
18 0x90000 0x98000 Non-Secure rwxl
19 0x98000 0xa0000 Non-Secure rwxl
20 0xa0000 0xa8000 Non-Secure rwxl
21 0xa8000 0xb0000 Non-Secure rwxl
22 0xb0000 0xb8000 Non-Secure rwxl
23 0xb8000 0xc0000 Non-Secure rwxl
24 0xc0000 0xc8000 Non-Secure rwxl
25 0xc8000 0xd0000 Non-Secure rwxl
26 0xd0000 0xd8000 Non-Secure rwxl
27 0xd8000 0xe0000 Non-Secure rwxl
28 0xe0000 0xe8000 Non-Secure rwxl
29 0xe8000 0xf0000 Non-Secure rwxl
30 0xf0000 0xf8000 Non-Secure rwxl
31 0xf8000 0x100000 Non-Secure rwxl
Non-secure callable region 0 placed in flash region 2 with size 32.

SRAM region Domain Permissions
00 0x00000 0x02000 Secure rwxl
01 0x02000 0x04000 Secure rwxl
02 0x04000 0x06000 Secure rwxl
03 0x06000 0x08000 Secure rwxl
04 0x08000 0x0a000 Secure rwxl
05 0x0a000 0x0c000 Secure rwxl
06 0x0c000 0x0e000 Secure rwxl
07 0x0e000 0x10000 Secure rwxl
08 0x10000 0x12000 Non-Secure rwxl
09 0x12000 0x14000 Non-Secure rwxl
10 0x14000 0x16000 Non-Secure rwxl
11 0x16000 0x18000 Non-Secure rwxl
12 0x18000 0x1a000 Non-Secure rwxl
13 0x1a000 0x1c000 Non-Secure rwxl
14 0x1c000 0x1e000 Non-Secure rwxl
15 0x1e000 0x20000 Non-Secure rwxl
16 0x20000 0x22000 Non-Secure rwxl
17 0x22000 0x24000 Non-Secure rwxl
18 0x24000 0x26000 Non-Secure rwxl
19 0x26000 0x28000 Non-Secure rwxl
20 0x28000 0x2a000 Non-Secure rwxl
21 0x2a000 0x2c000 Non-Secure rwxl
22 0x2c000 0x2e000 Non-Secure rwxl
23 0x2e000 0x30000 Non-Secure rwxl
24 0x30000 0x32000 Non-Secure rwxl
25 0x32000 0x34000 Non-Secure rwxl
26 0x34000 0x36000 Non-Secure rwxl
27 0x36000 0x38000 Non-Secure rwxl
28 0x38000 0x3a000 Non-Secure rwxl
29 0x3a000 0x3c000 Non-Secure rwxl
30 0x3c000 0x3e000 Non-Secure rwxl
31 0x3e000 0x40000 Non-Secure rwxl

Peripheral Domain Status
00 NRF_P0 Non-Secure OK
01 NRF_CLOCK Non-Secure OK
02 NRF_RTC0 Non-Secure OK
03 NRF_RTC1 Non-Secure OK
04 NRF_NVMC Non-Secure OK
05 NRF_UARTE1 Non-Secure OK
06 NRF_UARTE2 Secure SKIP
07 NRF_TWIM2 Non-Secure OK
08 NRF_SPIM3 Non-Secure OK
09 NRF_TIMER0 Non-Secure OK
10 NRF_TIMER1 Non-Secure OK
11 NRF_TIMER2 Non-Secure OK
12 NRF_SAADC Non-Secure OK
13 NRF_PWM0 Non-Secure OK
14 NRF_PWM1 Non-Secure OK
15 NRF_PWM2 Non-Secure OK
16 NRF_PWM3 Non-Secure OK
17 NRF_WDT Non-Secure OK
18 NRF_IPC Non-Secure OK
19 NRF_VMC Non-Secure OK
20 NRF_FPU Non-Secure OK
21 NRF_EGU1 Non-Secure OK
22 NRF_EGU2 Non-Secure OK
23 NRF_DPPIC Non-Secure OK
24 NRF_GPIOTE1 Non-Secure OK
25 NRF_REGULATORS Non-Secure OK

SPM: NS image at 0x18200
SPM: NS MSP at 0x2002e8e8
SPM: NS reset vector at 0x20371
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS version 2.1.99 ***
[00:00:00.192,718] <dbg> nrf9160_gps.init: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577
[00:00:00.201,568] <dbg> nrf9160_gps.init: COEX0 set: AT%XCOEX0=1,1,1570,1580
[00:00:00.209,259] <inf> asset_tracker: Asset tracker started
[00:00:00.222,656] <dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100028375
[00:00:00.231,933] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100028375/shadow
[00:00:00.243,682] <dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100028375/shadow/get/accepted
[00:00:00.255,249] <dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100028375/shadow/get/rejected
[00:00:00.267,852] <dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100028375/shadow/update/delta
[00:00:00.280,822] <dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100028375/shadow/update
[00:00:00.292,724] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100028375/shadow/get
[00:00:00.305,053] <inf> asset_tracker: Connecting to LTE network.
[00:00:00.311,859] <inf> asset_tracker: This may take several minutes.
[00:00:00.326,934] <dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0
+CEREG: 2,"1E01","00768503",7,0,0,"11100000","11100000"
[00:00:01.719,940] <dbg> lte_lc.parse_nw_reg_status: Network registration status: 2
+CEREG: 5,"1E01","00768503",7,,,"11100000","11100000"
[00:00:06.511,444] <dbg> lte_lc.parse_nw_reg_status: Network registration status: 5
[00:00:06.519,866] <inf> asset_tracker: Connected to LTE network
[00:00:06.841,949] <dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0x7d800234
[00:00:12.695,312] <inf> aws_jobs: Subscribe: $aws/things/nrf-352656100028375/jobs/notify-next
[00:00:12.705,688] <inf> aws_jobs: Subscribe: $aws/things/nrf-352656100028375/jobs/$next/get/#
[00:00:13.088,653] <inf> aws_fota: subscribed to notify-next topic
[00:00:13.095,458] <inf> aws_jobs: Publish topic: $aws/things/nrf-352656100028375/jobs/$next/get
[00:00:13.104,888] <inf> aws_jobs: Publish payload {"clientToken": ""}
[00:00:13.403,839] <dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_SUBACK: id = 2114 result = 0
[00:00:13.760,253] <dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 36438 result = 0
[00:00:13.770,477] <dbg> nrf_cloud_fsm.drop_event_handler: Dropping FSM transition 4, current state 1
[00:00:13.780,548] <dbg> aws_fota.aws_fota_on_publish_evt: Received topic: $aws/things/nrf-352656100028375/jobs/$next/get/accepted
[00:00:13.793,029] <inf> aws_fota: Checking for an available job
[00:00:13.799,682] <dbg> aws_fota.get_job_execution: Got only one field: {"clientToken":"
[00:00:13.808,532] <inf> aws_fota: No queued jobs for this device
[00:00:42.076,232] <err> asset_tracker: LTE link disconnect
[00:00:42.105,895] <err> asset_tracker: Socket error: POLLHUP
[00:00:42.112,426] <err> asset_tracker: Connection was closed by the cloud.
[00:00:42.120,239] <err> asset_tracker: LTE link disconnect
+CEREG: 0,"1E01","00768503",7,0,0,"11100000","11100000"
[00:00:43.681,060] <err> asset_tracker: Shutdown modem