I just received the Thingy 91 this morning. I've inserted the SIM have verified it on the nRF Connect for Cloud.
I cannot proceed to the next step, as the led continues to pulse blue - so I assume not connected to the network.
I am in the UK, South West London (SW15 6BF).
I assume there is no coverage here??
What are my options? If I need a different SIM, what am I looking for?
Thanks
Hello patmolloy13,
I am in the UK, South West London (SW15 6BF).
The Thingy:91 is shipped with LTE-M activated on the modem. According to GSMA Deployment Map, only NB-IoT is available in the UK.
What are my options? If I need a different SIM, what am I looking for?
Please try downloading the Thingy:91 Firmware pack from the download page. This file includes several pre-compiled versions of the Asset Tracker, with different network modes i.e. NB-IoT or LTE-M.
Package Contents:
│ CONTENTS.txt This file
│ mfwnrf9160101.zip Modem firmware, updated through nRF Connect for Desktop Programmer app
│
├───images_dfu Application images, updated over USB
│ thingy91_at_client_v0.2.3.bin Firmware for direct modem communication
│ thingy91_ltem_v0.2.2.bin Asset tracker firmware for nRF9160, LTE-M network mode
│ thingy91_nbiot_legacy_pco_v0.2.2.bin Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO
│ thingy91_nbiot_v0.2.2.bin Asset tracker firmware for nRF9160, NB-IoT network mode
│
└───images_hex Application images, updated over SWD (JLINK probe / development kit)
thingy91_at_client_v0.2.3.hex Firmware for direct modem communication
thingy91_ltem_v0.2.2.hex Asset tracker firmware for nRF9160, LTE-M network mode
thingy91_nbiot_legacy_pco_v0.2.2.hex Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO
thingy91_nbiot_v0.2.2.hex Asset tracker firmware for nRF9160, NB-IoT network mode
thingy91_nrf52_usb_v0.2.2.hex USB-UART serial bridge firmware for nRF52840
Please try to program your Thingy:91 with thingy91_nbiot_v0.2.2.hex.
Kind regards,
Øyvind
Thanks, Øyvind, I'll give that a go.
Pat
Ok, so I have made some progress, but am unable to upload the .hex file - I expect I am failing to understand something. I'm on a Windows 10 PC.
When I switch on the thingy:91 while holding in the main button, I get *two* com ports appearing (actually this happens when the main button is NOT pressed too). In my case COM29 and COM30. Not sure which port I should use, but neither of them works...
This is what I see when I run mcumgr ..
C:\Users\patmo>mcumgr --conntype=serial --connstring=COM29 image upload C:\Users\patmo\Downloads\thingy91_fw_v0.2.3\images_hex\thingy91_nbiot_v0.2.2.hex 0 B / 939.08 KiB [-------------------------------------------------------------------------------------------] 0.00%Error: NMP timeout C:\Users\patmo>mcumgr --conntype=serial --connstring=COM30 image upload C:\Users\patmo\Downloads\thingy91_fw_v0.2.3\images_hex\thingy91_nbiot_v0.2.2.hex 0 / 961622 [-------------------------------------------------------------------------------------------------] 0.00%Error: 3
First, is the Thingy:91 straight out of the box?
Can you please try running the command from C:\Users\patmo\Downloads\thingy91_fw_v0.2.3\images_hex\. This to ensure that the path is not the issue.
E.g. C:\Users\patmo\Downloads\thingy91_fw_v0.2.3\images_hex\>mcumgr --conntype=serial --connstring=COM29 image upload thingy91_nbiot_v0.2.2.hex
Getting two COM ports is correct, one is for the board controller and the other for nRF9160. However, only one is correct.
First, is the Thingy:91 straight out of the box?
Can you please try running the command from C:\Users\patmo\Downloads\thingy91_fw_v0.2.3\images_hex\. This to ensure that the path is not the issue.
E.g. C:\Users\patmo\Downloads\thingy91_fw_v0.2.3\images_hex\>mcumgr --conntype=serial --connstring=COM29 image upload thingy91_nbiot_v0.2.2.hex
Getting two COM ports is correct, one is for the board controller and the other for nRF9160. However, only one is correct.
I oversaw one detail from your last post. You're trying to load the wrong image. If you have a jlink programmer, then you can use the .hex files to update. mcumgr uses the .bin files from images_bin.
Hi Øyvind,
It's brand new out of the box. I just stuck the SIM in and hoped that it would magically work :)
I am sure the path is not the problem, actually. I can use mcumgr from whatever folder I am in. It sounds like it the .hex file causing the grief with mcumgr. I'll try the bin version.
I am a complete novice as far as Nordic goes. Had the thingy:52, though. Excellent for demos.
I'll look into a jlink programmer.
Thanks for your help!
Pat
Ok, I re-read your message and understand .. run the mcumgr command from the folder where the .bin file is located.
This has worked, I think .. I was not sure which com port but 30 works, and 29 does not.
C:\Users\patmo\Downloads\thingy91_fw_v0.2.3\images_dfu>mcumgr --conntype=serial --connstring=COM30 image upload thingy91_nbiot_v0.2.2.bin
294.77 KiB / 294.77 KiB [===================================================================] 100.00% 3.12 KiB/s 1m34s
Done
Hi Pat,
patmolloy13 said:It's brand new out of the box. I just stuck the SIM in and hoped that it would magically work :)
Yes, usually they do magically work out of the box, but sometimes the conditions for the magician is not optimized ;) LTE-M and NB-IoT are two different types of technologies.
patmolloy13 said:I am a complete novice as far as Nordic goes. Had the thingy:52, though. Excellent for demos.
Yes, and that's what we based the Thingy:91 on. We want it to be just as excellent for demos, however, the nRF9160 is a more advanced device compared to nRF52 devices.
patmolloy13 said:I'll look into a jlink programmer.
Did you find one? Based on the following comment, it seems as though you have solved it.
patmolloy13 said:
This has worked, I think .. I was not sure which com port but 30 works, and 29 does not.
C:\Users\patmo\Downloads\thingy91_fw_v0.2.3\images_dfu>mcumgr --conntype=serial --connstring=COM30 image upload thingy91_nbiot_v0.2.2.bin
294.77 KiB / 294.77 KiB [===================================================================] 100.00% 3.12 KiB/s 1m34s
As I mentioned, one COM port is for the board controller (COM29 - does not work) and the other COM30 is for the nRF9160.
From the initial post:
I cannot proceed to the next step, as the led continues to pulse blue - so I assume not connected to the network.
Are you getting any further? If not, you may need to try with another SIM from your local NB-IoT provider.
Let me know how it goes, and if you have any further questions, just ask :)
Cheers!
-Øyvind
Ok, I have flashed thingy91_nbiot_v0.2.2.bin to the device. But I am still getting no connection. How do I debug this best? Has the act of flashing this image definitely flashed the modem?
1) Is there any way (via the USB port) to see any diagnostic data that might be being generated?
2) Is there any way to verify whether the iBASIS sim has roamed (or is capable of roaming) to NB-IoT in the UK ? (London)
Thanks
Pat