nRF Connect for Cloud not displaying asset tracker graphical data

[Smythey]

I have my Thingy:91 working now but I can only see "terminal" data in nRF Connect for Cloud. I was expecting to see graphs of the data and a map when I have a GPS fix. The "Cellular Link Monitor" says I should update my firmware but I am on the latest version. What's going on?

[Smythey]

When I flash either of those files, te file memory layout looks like this

and the Thingy:91 stops working.

Every working version of the software I have used has a memory layout like this:

When I flash either of those hex files you sent, the modem stops responding to commands. Have you actually tested that firmware yourself on a Thingy:91?

[Heidi-Irene Harvey Sollie]

The memory layout looks correct. I have not tested the NB-IoT version as my SIM card does not support it, but it has been confirmed by other developers as well as our customers.

Have you updated the firmware on the nRF52840 on the Thingy:91, as described in the getting started steps here. 

If not, you can do this using the nRF Programmer application, just remember to switch SW2 on the board to the nRF52 side. 

thingy91_nrf52_usb_uart_bridge_2019-11-29_d3130d77.hex

[Smythey]

OK. I have updated the modem firmware, the demo application and the nRF52840 firmware. Now there is no connection with the modem. In nRF Connect, under Select Device, the only device I now see is the J-Link debugger. Previously I saw two USB connections, one of which allowed me to communicate with the modem.

The device is now not working at all.

[Heidi-Irene Harvey Sollie]

I see. Could you please try the files I attached below instead, which were built today?  Again if you don't know whether your network supports ePCO, try that one first. 

Additionally, when you updated the certificates, did you make sure to download the device certificates for "nrf-<IMEI>", where <IMEI> is the 15-digit code on the PCB of the Thingy? I just ask because I know a few customers have had trouble with that. The "nrf-" part is important, and the input is case-sensitive so it has to be lower case. 

thingy91_usb_uart_bridge_1703.hex

thingy91_asset_tracker_nbiot_legacy_pco_1703.hexthingy91_asset_tracker_nbiot_1703.hex

[Smythey]

I have tried those files (including the legacy version - although I never needed that before).

2020-03-17T09_13_34.724Z-log.txtNow the Thingy:91 is in a continual reboot cycle. Worryingly, I see the message "Non-secure callable region 0 placed in flash region 2 with size 32". I have attached the log file so you can diagnose.

Yes, I did enter the device certificate correctly.

[Heidi-Irene Harvey Sollie]

Hi, thanks for the log! That was very useful. I see you're getting this error code 

asset_tracker: cloud_connect failed: -95

which is EOPNOTSUPP  95 /* Operation not supported on transport endpoint */

This is either some issue with your certificates or an error code from the modem, which doesn't translate and just uses EOPNOTSUPP as a catch-all. 

I think getting a modem trace will be very useful, see this tutorial for how to do it. 

You could also try updating the certificates again, perhaps that is the issue. 

Best regards,

Heidi

[Smythey]

Hi

I didn't have time to look at this again until today. When I query the certificates, I get the screenshot below. Does this look wrong to you? If not, what should it look like.

[Heidi-Irene Harvey Sollie]

Hi, this looks fine and it tells us that the nRF Cloud certificates have not been erased, so the problem isn't your certificates. Again, a modem trace will help us find the root cause. 

[Smythey]

I have tried to follow the tutorial to get a modem trace but it seems to be written for the nRF9160 development kit and Step 2 in particular doesn't seem to make sense for the Thingy:91. The result was that I got no trace. Also, the tutorial doesn't explain how you would collect a modem trace when running the Thingy:91 demo application. It only covers running the demo AT client as far as I understand it.

[Heidi-Irene Harvey Sollie]

Hi!

You're right, step 2 is different for the Thingy:91, you should flash the Connectivity Bridge to the nRF52840. 

The tutorial uses the AT Client sample as an example but you can get a trace from the Asset Tracker sample as well.

Flash the AT Client sample first and send AT%XMODEMTRACE=1,2 and AT+CFUN=0 to save.

Then add the CONFIG_BSD_LIBRARY_TRACE_ENABLED=y configuration to the application you want to take a trace with and flash it to the device.

Best regards,

Heidi

[Smythey]

Hi

Is it possible to send me a pre-compiled version of the Connectivity Bridge for the Thingy:91?

Looking at the instructions, it seems I would have to install a huge toolchain just to compile it.It sounds simple - "send us a modem trace", but achieving this has already taken hours of my time. I am only trying to run the demo asset tracker application.

Steve

[Heidi-Irene Harvey Sollie]

I completely understand, here you go. Make sure to set SW2 to the nRF52 position when flashing. 

I also attached a newly built copy of the asset_tracker sample from the master branch of NCS with support for NB-IoT (not legacy) and the trace config enabled in case you wanted to try getting a modem trace again.

I understand the process might be hard, but it's difficult for me to understand what the issue might be without it. 

thingy91_connectivity_bridge.hex

thingy91_asset_tracker_nbiot_2704.hex

Best regards,

Heidi