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,

To confirm my procedure (I verified programming of the connectivity firmware to write this email using the Win 7 computer)

- I start with the nRF91 Thingy powered off. I open nRF Connect (v3.6.1) and start the programmer application (1.4.8). Since the nRF91 Thingy is OFF no devices are indicated in the programmer window.

- I then press SW4 (this is the small white button) and turn on the power. At that time the device is recognized by Windows and an available device is shown in the programmer window (in this case a single COM port)

- I select the HEX file from the DFU directory and then select "Write".Uploading image to device is shown and the progress bar advances. When it completes the message "completed successfully in 50.178 seconds" was displayed. I have foud it necessary to reprogram the connectivity software in order to update the modem.

- on completion I also hear a notification from Windows that a new device has attached and the Programmer shows "THINGY91_e2b4b..." with two com ports as the only available device. 

- in order to upgrade the Modem firmware I would proceed from this point usually by turning off the Thingy, closing the programmer app, disconnecting and reconnecting the USB cable. No device are displayed at this point in the programmer.

- I then press SW3 (the large black button) and turn on power. Windows announces a new device and THINGY91_e24b... is again displayed with two Com ports. Note: using Window 10 only a Zephyr window opens showing the CDC drivers files and only one device appears in the programmer.

- I then select Update Modem and select a *.zip file. I used the mfwnrf9160122.zip file from the 10_30_20 firmware archive. There are four messages displayed, "Step 1/2: ... Uploading image to device", after a short pause "Programming file ..." is displayed followed by "Step 2/2 ... Uploading image to device", and finally "Completed Successfully in 117 seconds". 

 - On completion Windows does not announce a new device but "THINGY91_e2b4b..." is available but I don't beleive it is in MCUBoot mode.

As far as I can tell the programming of both the modem and the connectivity software completes successfully but I see no activity on the LEDs and or communications of any kind. 

Other observations:

- Windows 10 was problematic when programming the modem firmware which is why I shifted to using the Win 7 computer. When the modem software successfully installed using the Windows 10 machine it was taking twice the time as the Win 7 computer.

- nRF Connect was re-installed this week on both machines (3.6.1) and the programmer module is version 1.4.8. 

- I used the CDC divers in the latest nRF52 SDK (17.02) in order to establish communications between nRF Connect and the Thingy91.  

- the older modem firmware installed "easier" on the Window 10 machine, e.g. version 1.1.0. It may have required the older version of USB-UART firmware as well. 

The date codes on the modem (1925E) and the board (2020.22) suggest that the module was build in April of 2020. So my assumption is that the original (operational) firmware would have been from either the 11_29_19 or the 29_04_20 releases which is why I've tried the older firmware. 

If I program the LTEM firmware, besides no LED activity, the THINGY also no longer identifies through USB to Windows, likewise pressing SW3 and cycling power does not result in an MCUboot for the modem. So in order to update the modem I first need to re-program the connectivity firmware which then re-activates the MCUBoot for the modem. 

JT

[John_Turner]

Hi Carl Richard,

I spoke to one of your FAEs on Monday and he helped me identify the problem. I had been programming the modem firmware into the nRF9160 and the Connectivity application into the nRF52840 but I didn't realize that I also needed to program the nRF9160 application firmware as well. I now having flashing lights on the Thingy.

Two follow up questions, you had mentioned that there was a bug in the AT_Client firmware, was this addressed in the firmware released last week and can an operational version of the AT_Client firmware be compiled from the SDK?

JT 

[Carl Richard]

Hi again, JT!

Glad you figured out the issue! Apologies for not responding here myself.

1. This was addressed in the firmware released last week.

2. Yes, an operational version can be compiled from the SDK. We have a blog post on how projects can be configured correctly for Thingy:91 DFU.

Best regards,
Carl Richard