nRF91 Thingy

[John_Turner]

Hi, 

I have an nRF91 Thingy that arrived last week but it's not operating as expected. I've downloaded the latest version of NRF Connect and I've been following the get started guide.

First I tried to update the cellular modem firmware using MCUboot, I press SW3 while turning on the power and I see a message that "Memory layout is not available in MCUboot mode" but when I try tp update the firmware I receive a message to place the device in MCUboot mode and to try again. The date code on the module looks like 2020.22. Does it come with the bootloader programmed.  

I then tried to register the device on nRF Cloud as an LTE module but either the IEMI or the pin isn't being recognized, the Device ID I'm using is nrf-352656101111642 which matches the IEMI on the module. I'm using the 6 digit pin on the module not the one on the SIM card. 

Questions:

Can the bootloader be programmed using the USB port on the module or is an external programmer required?

The SIM seems to be recognized but are there problems using the nRF9160 modems in Canada. Anecdotally, I located near Vancouver, B.C. in Canada and have an LTE CATM1 module from another vendor operating connecting to the Bell network less then a meter away.

JT

[John_Turner]

Hi Carl Richard,

I'm using Windows 10. Yesterday I uninstalled and then re-installed nRF Connect and MCUboot seem to operate as expected so I continued on with the steps in the video and updated the cellular firmware to version 1.2.2 (from 1.1.1). Now, unfortunately, the cellular modem no longer seems to respond in any detectable way.

Things I've tried:

- programmed the Connectivity Bridge FW as you suggested, current and previous versions. MCUboot seems to operate as expected. 

- re-programmed the modem FW, versions 1.1.1, to try to duplicate what I originally had, 1.2.2 to match what's in the latest firwmare, and 1.2.3 which is the latest modem firmware. All complete but I see no activity from the Thingy either LEDs or with the LTE monitor.

- programmed the USB to UART and AT_Client FW, multiple versions to see if the modem would respond to AT commands either through a terminal program or with the LTE Monitor.

I'm running out of ideas and I suspect I've got a hardware issue but any suggestions would be appreciated.

One thing I'd like to be able to do is issue a basic AT command to see the modem respond. Could I also ask you to clarify the uses of the different firmware versions, e.g. USB to UART Bridge, Connectivity Bridge, and the AT_Client?

JT

[Carl Richard]

Hi.

Good to hear that it reinstalling nRF Connect solved the MCUBoot issue and apologies for this poor out-of-the-box experience. I will do my best to get you up and running properly.

Did the modem upgrade pass without errors? When upgrading the modem firmware the onboard application is deleted and must be programmed again. However, I'm seeing the same issues myself with the AT_Client as you, so I must look into that. I got it working with the Asset_Tracker, so in the meantime, could you try the following:
1. Update the nRF52840 with the connectivity_bridge again. 
2. Program the thingy91_fw_2020-10-30_5522ca2b/img_fota_dfu_hex/thingy91_ltem_2020-10-30_5522ca2b.hex to the nRF9160. 
3. Observe whether the LED is lighting up and that logs are printed in the LTE Link Monitor. Please report back what you see.

You may have to reboot the device between the operations. 

As mentioned I saw the same issues with the AT_Client when testing here, so hopefully it's only a firmware bug. When using the asset_tracker my Thingy:91 responded to at-commands and logged properly.

Information about the different applications are available in the CONTENTS.txt file. A short description follows:
For the thingy91_nrf9160:
- thingy91_ltem/thing91_nbiot | this is the asset_tracker application, for LTE-M and NB networks respectively. 
- thingy91_at_client | this is the simple at_client application, for communicating directly with the modem through at-commands. There seems to be issues with this one right now.

For the thingy91_nrf52840:
- thingy91_nrf52_connectivity_bridge | this sample enables the nRF9160 to communicate over USB as well as BLE. More information in the documentation.
- thingy91_nrf52_usb_uart_bridge | An earlier version of the connectivity bridge. This is deprecated and should not be used.

Hope the asset_tracker will work for you. I will look into any issues with the at_client.

Best regards,
Carl Richard

[John_Turner]

Hi Carl Richard,

I've upgraded the modem software several times. The first time, and occasionally afterwards, it seemed to stall after the first stage and required re-booting. Most times it proceeds through both stages of programming without issue. Again, I've reprogrammed it several times.

One thing I've tried to do is re-program the unit with the original firmware. The original FW for the modem was 1.1.1 which I found in a 2019 release of the firmware. That version of the firmware only has the USB to UART application. Nothing worked so I reprogrammed it with the latest.

After programming the LED may flicker when power is applied but after that nothing. This is true of any firmware programmed. 

I've been using the LTEM version of the asset tracker application. I resorted to the AT_Client in an effort to see if the Modem was programmed. 

I'll try your suggestions and let you know what happens. 

Is there a way to use the IDE as an alternative to MCUboot without the nRF91 development kit? I also have an older nRF52 development kit but I don't think it's compatible with the nRF9160.

JT