• State Not Answered
  • Replies 12 replies
  • Subscribers 74 subscribers
  • Views 2266 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 265489
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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

  • 0 in reply to 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 

  • 0 in reply to John_Turner

    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

Related
Terms of service