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]

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

[Heidi]

Hi, I have contacted the nRF Connect for Cloud team to ask about any issues on their end with this problem.

In the meantime, there is a new MFW version out (v 1.2.0) and at new nRF Connect version (v3.3.3). 

Could you upgrade to all the newest firmware, just to eliminate this as the issue? 

I have also attached the compiled asset tracker (nRF9160) and usb-uart bridge (nRF52840) applications from the 1.2 tag of NCS (as opposed to the master branch) just to eliminate the possibility of the master branch being unstable. 

I would also like to apologize for all the issues you're having with this device. The Thingy:91 is meant to work as an out-of-box experience, but unfortunately, there are occasional issues with things like this. 

mfw_nrf9160_1.2.0.zip

thingy91_asset_tracker_nbiot_v_1_2_27_04.hex

thingy91_usb_uart_bridge_v1_2_27_04.hex

[Smythey]

I have upgraded the device using the three files that you sent, but it is still not connecting with the Vodafone network. If you recall, I could originally connect to the Vodafone network and could see my data on the Connect for Cloud website, but not in graphical form. Now the device does nothing much at all.

[Heidi]

That's strange. Did you use a debugger or MCUboot when flashing? The .hex files I attached are meant to be used with a debugger. 

[Smythey]

Yes. I am using a Segger J-Link Lite debugger.

[Heidi]

Okay, and you're making sure to select the debugger in the programmer application when flashing?

And switching SW2 on the Thingy:91 to the nRF52 position when flashing to the nRF52?

And then remembering to switch back when viewing the debug log from the application? 

I apologize if some of these questions are basic, I just want to cover all the bases. 

[Smythey]

Yes to all of those questions.

[Heidi]

Okay.

Could you open up JLinkCommander and see the HW revision and target voltage of the debugger?

[Smythey]

Weirdly, I can ping the Vodafone SIM in the Thingy:91 from the other end (the Arkessa website) and it shows as "connected".

[Smythey]

This is looking more promising

[Smythey]

Yay!

The last set of files you sent me did work eventually, after a couple of power cycles. Thanks for all your help.