This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Thingy:91 SIM Expired

I just received my Nordic Thingy91 and when I tried activating the SIM, the following message came up:

"Unfortunately this SIM has expired. We are sorry for the inconvenience. Please contact iBasis for a free replacement."

I have contacted iBasis both through email and through the iBasis Tech support to get a replacement SIM (I have yet to receive a response).

In the meantime, I'm I able to use my own SIM card from my phone? I inserted the card and when I try to "Add LTE Device" in nRF cloud, it says that "There was an error adding your device: No device found for this id. The device has not yet been provisioned." Also, LTE Link Monitor can connect to the UART, but there is no activity and no response from any AT command.

What to do?

Parents
  • I now have another issue with the Thingy. After putting the unit into MCUboot mode by pressing SW4 while switching SW1 to the ON position, I loaded one of the hex files from the img_app_bl folder (doesn't matter which one, I've tried a number of them) and wrote it successfully to the device. However, when I cycle power, none of the apps (Programmer, LTE Link Monitor, Trace Collector) see the device any longer. The device was visible before I wrote the hex file for the first time. The LED comes on first as blinking green and then after a few minutes goes to blinking blue. I am able to program hex files in MCUboot mode, but when it's not in that mode none of the apps see the Thingy.

  • Hi Fred,

    I'm I able to use my own SIM card from my phone?

    You need a SIM card that specially supports LTE-M/NB-IoT network.  SIM used by mobile phones normally does not have support on Cellular IoT networks.

    LTE Link Monitor can connect to the UART, but there is no activity and no response from any AT command.

    You need to program either of the following sample firmware in order to run AT commands.

    nRF9160: Serial LTE modem — nRF Connect SDK 1.8.0 documentation (nordicsemi.com)

    nRF9160: AT Client — nRF Connect SDK 1.8.0 documentation (nordicsemi.com)

    fackbell said:
    I loaded one of the hex files from the img_app_bl folde

    According to CONTENTS.txt, img_fota_dfu_hex/ is the correct choice if you do DFU through USB with the bootloader. When you need to reprogram the whole firmware including the bootloader with a programer like J-LInk, the firmware in img_app_bl/ is the correct choice.

    Best regards

    Charlie

  • I tried both serial_lte_modem_2021-12-15_cfedfdfa.hex and thingy91_at_client_2021-12-15_cfedfdfa.hex files from the img_fota_dfu_hex folder as suggested with the same result which is after writing the file and cycling power, the device is not available in any of the apps. The LED's cycle between a short green and a long red. So, for now this device is a brick. Let me know what else I can do to get this up and going.

Reply
  • I tried both serial_lte_modem_2021-12-15_cfedfdfa.hex and thingy91_at_client_2021-12-15_cfedfdfa.hex files from the img_fota_dfu_hex folder as suggested with the same result which is after writing the file and cycling power, the device is not available in any of the apps. The LED's cycle between a short green and a long red. So, for now this device is a brick. Let me know what else I can do to get this up and going.

Children
  • Ok, I am not sure what happens and what you mean by "the device is not available in any of the apps." Let us do some debugging together to save your bricked device.

    1. To save the bricked thingy91, follow the Updating firmware through USB guidance to reprogram the nRF52840 System on Chip (SoC) application firmware(latest is thingy91_nrf52_connectivity_bridge_2021-12-15_cfedfdfa.hex),  the modem firmware on the nRF9160 System in Package (SiP)(mfw_nrf9160_1.3.1.zip),  the modem firmware on the nRF9160 System in Package (SiP)(serial_lte_modem_2021-12-15_cfedfdfa). Please share me your log file generated by the Programmer app. You should get something like this:

    2022-02-11T09:44:11.865Z INFO Application data folder: C:\Users\chs1\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
    2022-02-11T09:44:11.985Z DEBUG App pc-nrfconnect-programmer v2.3.1 official
    2022-02-11T09:44:11.985Z DEBUG App path: C:\Users\chs1\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
    2022-02-11T09:44:11.985Z DEBUG nRFConnect 3.10.0, required by the app is (^3.10.0)
    2022-02-11T09:44:11.985Z DEBUG nRFConnect path: C:\Users\chs1\AppData\Local\Programs\nrfconnect\resources\app.asar
    2022-02-11T09:44:11.985Z DEBUG HomeDir: C:\Users\chs1
    2022-02-11T09:44:11.985Z DEBUG TmpDir: C:\Users\chs1\AppData\Local\Temp
    2022-02-11T09:44:13.418Z DEBUG iface: Ethernet
    2022-02-11T09:44:13.418Z DEBUG IP4: 192.9.201.83
    2022-02-11T09:44:13.418Z DEBUG IP6: 2001:8c0:5140:801:7499:9373:cbf2:f639
    2022-02-11T09:44:13.418Z DEBUG MAC: a4:bb:6d:b6:03:9e
    2022-02-11T09:44:13.419Z DEBUG Client Id: 538c19b4886990d970d2831eabbd947f1c647983
    2022-02-11T09:44:13.419Z DEBUG Google Analytics for category pc-nrfconnect-programmer has initialized
    2022-02-11T09:44:32.285Z DEBUG Sending usage data...
    2022-02-11T09:44:32.285Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:44:32.285Z DEBUG Action: Open device
    2022-02-11T09:44:32.285Z DEBUG Label: mcuboot
    2022-02-11T09:44:32.287Z DEBUG Usage data has been sent
    2022-02-11T09:44:32.295Z DEBUG Sending usage data...
    2022-02-11T09:44:32.295Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:44:32.295Z DEBUG Action: Open jlink device family
    2022-02-11T09:44:32.295Z DEBUG Label: nRF91
    2022-02-11T09:44:32.296Z DEBUG Usage data has been sent
    2022-02-11T09:44:32.296Z DEBUG Sending usage data...
    2022-02-11T09:44:32.296Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:44:32.296Z DEBUG Action: Open jlink device version
    2022-02-11T09:44:32.296Z DEBUG Label: Thingy91
    2022-02-11T09:44:32.297Z DEBUG Usage data has been sent
    2022-02-11T09:44:32.297Z DEBUG Sending usage data...
    2022-02-11T09:44:32.297Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:44:32.298Z DEBUG Action: Open jlink device board version
    2022-02-11T09:44:32.298Z DEBUG Label: PCA20035
    2022-02-11T09:44:32.298Z DEBUG Usage data has been sent
    2022-02-11T09:44:36.702Z INFO Parsing HEX file:  C:\Users\chs1\Downloads\thingy91_fw_2021-12-15_cfedfdfa\img_fota_dfu_hex\thingy91_nrf52_connectivity_bridge_2021-12-15_cfedfdfa.hex
    2022-02-11T09:44:36.714Z INFO File was last modified at  2/11/2022, 9:44:56 AM
    2022-02-11T09:44:36.799Z INFO Update files regions according to Application core
    2022-02-11T09:44:36.799Z INFO Parse memory regions for file
    2022-02-11T09:44:40.409Z INFO Does not need to be reloaded:  C:\Users\chs1\Downloads\thingy91_fw_2021-12-15_cfedfdfa\img_fota_dfu_hex\thingy91_nrf52_connectivity_bridge_2021-12-15_cfedfdfa.hex
    2022-02-11T09:44:44.906Z INFO Writing C:\Users\chs1\Downloads\thingy91_fw_2021-12-15_cfedfdfa\img_fota_dfu_hex\thingy91_nrf52_connectivity_bridge_2021-12-15_cfedfdfa.hex to device FC21DF82ED0E9C4B
    2022-02-11T09:45:05.194Z INFO MCUboot DFU completed successfully!
    2022-02-11T09:45:15.055Z DEBUG Sending usage data...
    2022-02-11T09:45:15.055Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:15.055Z DEBUG Action: Close device
    2022-02-11T09:45:15.055Z DEBUG Label: 
    2022-02-11T09:45:15.056Z DEBUG Usage data has been sent
    2022-02-11T09:45:15.057Z INFO Target device closed
    2022-02-11T09:45:28.190Z DEBUG Sending usage data...
    2022-02-11T09:45:28.191Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:28.191Z DEBUG Action: Open device
    2022-02-11T09:45:28.191Z DEBUG Label: mcuboot
    2022-02-11T09:45:28.192Z DEBUG Usage data has been sent
    2022-02-11T09:45:28.194Z DEBUG Sending usage data...
    2022-02-11T09:45:28.194Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:28.194Z DEBUG Action: Open jlink device family
    2022-02-11T09:45:28.194Z DEBUG Label: nRF91
    2022-02-11T09:45:28.195Z DEBUG Usage data has been sent
    2022-02-11T09:45:28.195Z DEBUG Sending usage data...
    2022-02-11T09:45:28.195Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:28.195Z DEBUG Action: Open jlink device version
    2022-02-11T09:45:28.195Z DEBUG Label: Thingy91
    2022-02-11T09:45:28.196Z DEBUG Usage data has been sent
    2022-02-11T09:45:28.196Z DEBUG Sending usage data...
    2022-02-11T09:45:28.196Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:28.196Z DEBUG Action: Open jlink device board version
    2022-02-11T09:45:28.196Z DEBUG Label: PCA20035
    2022-02-11T09:45:28.197Z DEBUG Usage data has been sent
    2022-02-11T09:45:32.327Z DEBUG Sending usage data...
    2022-02-11T09:45:32.327Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:32.327Z DEBUG Action: Open device
    2022-02-11T09:45:32.327Z DEBUG Label: mcuboot
    2022-02-11T09:45:32.328Z DEBUG Usage data has been sent
    2022-02-11T09:45:32.331Z DEBUG Sending usage data...
    2022-02-11T09:45:32.331Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:32.331Z DEBUG Action: Open jlink device family
    2022-02-11T09:45:32.332Z DEBUG Label: nRF91
    2022-02-11T09:45:32.332Z DEBUG Usage data has been sent
    2022-02-11T09:45:32.333Z DEBUG Sending usage data...
    2022-02-11T09:45:32.333Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:32.333Z DEBUG Action: Open jlink device version
    2022-02-11T09:45:32.333Z DEBUG Label: Thingy91
    2022-02-11T09:45:32.334Z DEBUG Usage data has been sent
    2022-02-11T09:45:32.334Z DEBUG Sending usage data...
    2022-02-11T09:45:32.334Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:32.334Z DEBUG Action: Open jlink device board version
    2022-02-11T09:45:32.334Z DEBUG Label: PCA20035
    2022-02-11T09:45:32.335Z DEBUG Usage data has been sent
    2022-02-11T09:45:36.220Z INFO Checking ZIP file:  C:\Users\chs1\Downloads\thingy91_fw_2021-12-15_cfedfdfa\mfw_nrf9160_1.3.1.zip
    2022-02-11T09:45:36.220Z INFO File was last modified at  2/11/2022, 9:44:57 AM
    2022-02-11T09:45:38.410Z INFO Update files regions according to Application core
    2022-02-11T09:45:38.410Z INFO Parse memory regions for file
    2022-02-11T09:45:40.725Z INFO Checking ZIP file:  C:\Users\chs1\Downloads\thingy91_fw_2021-12-15_cfedfdfa\mfw_nrf9160_1.3.1.zip
    2022-02-11T09:45:40.725Z INFO File was last modified at  2/11/2022, 9:44:57 AM
    2022-02-11T09:45:49.836Z DEBUG Sending usage data...
    2022-02-11T09:45:49.836Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:49.836Z DEBUG Action: Close device
    2022-02-11T09:45:49.836Z DEBUG Label: 
    2022-02-11T09:45:49.837Z DEBUG Usage data has been sent
    2022-02-11T09:45:49.839Z INFO Target device closed
    2022-02-11T09:45:58.224Z DEBUG Sending usage data...
    2022-02-11T09:45:58.224Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:58.224Z DEBUG Action: Open device
    2022-02-11T09:45:58.224Z DEBUG Label: mcuboot
    2022-02-11T09:45:58.225Z DEBUG Usage data has been sent
    2022-02-11T09:45:58.228Z DEBUG Sending usage data...
    2022-02-11T09:45:58.228Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:58.229Z DEBUG Action: Open jlink device family
    2022-02-11T09:45:58.229Z DEBUG Label: nRF91
    2022-02-11T09:45:58.229Z DEBUG Usage data has been sent
    2022-02-11T09:45:58.230Z DEBUG Sending usage data...
    2022-02-11T09:45:58.230Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:58.230Z DEBUG Action: Open jlink device version
    2022-02-11T09:45:58.230Z DEBUG Label: Thingy91
    2022-02-11T09:45:58.231Z DEBUG Usage data has been sent
    2022-02-11T09:45:58.231Z DEBUG Sending usage data...
    2022-02-11T09:45:58.231Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:45:58.231Z DEBUG Action: Open jlink device board version
    2022-02-11T09:45:58.231Z DEBUG Label: PCA20035
    2022-02-11T09:45:58.233Z DEBUG Usage data has been sent
    2022-02-11T09:46:01.027Z INFO Checking ZIP file:  C:\Users\chs1\Downloads\thingy91_fw_2021-12-15_cfedfdfa\mfw_nrf9160_1.3.1.zip
    2022-02-11T09:46:01.028Z INFO File was last modified at  2/11/2022, 9:44:57 AM
    2022-02-11T09:46:04.993Z INFO Modem DFU starts to write...
    2022-02-11T09:46:04.994Z INFO Writing C:\Users\chs1\Downloads\thingy91_fw_2021-12-15_cfedfdfa\mfw_nrf9160_1.3.1.zip to device THINGY91_C793DD5BD4D9
    2022-02-11T09:48:25.407Z INFO Modem DFU completed successfully!
    2022-02-11T09:48:32.564Z DEBUG Sending usage data...
    2022-02-11T09:48:32.564Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:48:32.565Z DEBUG Action: Close device
    2022-02-11T09:48:32.565Z DEBUG Label: 
    2022-02-11T09:48:32.566Z DEBUG Usage data has been sent
    2022-02-11T09:48:32.567Z INFO Target device closed
    2022-02-11T09:48:38.677Z DEBUG Sending usage data...
    2022-02-11T09:48:38.678Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:48:38.678Z DEBUG Action: Open device
    2022-02-11T09:48:38.678Z DEBUG Label: mcuboot
    2022-02-11T09:48:38.678Z DEBUG Usage data has been sent
    2022-02-11T09:48:38.680Z DEBUG Sending usage data...
    2022-02-11T09:48:38.680Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:48:38.680Z DEBUG Action: Open jlink device family
    2022-02-11T09:48:38.680Z DEBUG Label: nRF91
    2022-02-11T09:48:38.681Z DEBUG Usage data has been sent
    2022-02-11T09:48:38.681Z DEBUG Sending usage data...
    2022-02-11T09:48:38.681Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:48:38.681Z DEBUG Action: Open jlink device version
    2022-02-11T09:48:38.682Z DEBUG Label: Thingy91
    2022-02-11T09:48:38.682Z DEBUG Usage data has been sent
    2022-02-11T09:48:38.683Z DEBUG Sending usage data...
    2022-02-11T09:48:38.683Z DEBUG Category: pc-nrfconnect-programmer
    2022-02-11T09:48:38.683Z DEBUG Action: Open jlink device board version
    2022-02-11T09:48:38.683Z DEBUG Label: PCA20035
    2022-02-11T09:48:38.683Z DEBUG Usage data has been sent
    2022-02-11T09:48:43.646Z INFO Parsing HEX file:  C:\Users\chs1\Downloads\thingy91_fw_2021-12-15_cfedfdfa\img_fota_dfu_hex\serial_lte_modem_2021-12-15_cfedfdfa.hex
    2022-02-11T09:48:43.646Z INFO File was last modified at  2/11/2022, 9:44:56 AM
    2022-02-11T09:48:43.738Z INFO Update files regions according to Application core
    2022-02-11T09:48:43.739Z INFO Parse memory regions for file
    2022-02-11T09:48:46.567Z INFO Does not need to be reloaded:  C:\Users\chs1\Downloads\thingy91_fw_2021-12-15_cfedfdfa\img_fota_dfu_hex\serial_lte_modem_2021-12-15_cfedfdfa.hex
    2022-02-11T09:48:47.791Z INFO Writing C:\Users\chs1\Downloads\thingy91_fw_2021-12-15_cfedfdfa\img_fota_dfu_hex\serial_lte_modem_2021-12-15_cfedfdfa.hex to device THINGY91_C793DD5BD4D9
    2022-02-11T09:49:44.465Z INFO MCUboot DFU completed successfully!
    

    2. Connect the thingy91 with LTE Link Monitor app, you should see the following output with AT+CFUN?

    AT+CFUN?
    +CFUN: 0
    OK

    Best regards,

    Charlie

  • I programmed the 'thingy91_nrf52_connectivity_bridge_2021-12-15_cfedfdfa.hex" file (the only one I didn't try) and then the "mfw_nrf9160_1.3.1.zip" file. After cycling power, I can now select the device in the programmer and the LTE Link Monitor, which wasn't showing up previously. LTE Link Monitor shows that the Modem port is opened, but none of the AT commands work. I'm assuming this is because my Thingy was shipped with an expired SIM card, so I'm not able to do anything in the monitor until I get my replacement SIM? Let me know if this assumption isn't correct. I've attached a screen shot of the monitor.

    Also, when I try programming the "serial_lte_modem_2021-12-15_cfedfdfa.hex" file, I can no longer see/select the Thingy either in the programmer or the LTE Link Monitor.

  • Hi Fred,

    fackbell said:
    I'm not able to do anything in the monitor until I get my replacement SIM?

    The AT command is not related to SIM card. It is the modem core that responds back current state.

    fackbell said:
    when I try programming the "serial_lte_modem_2021-12-15_cfedfdfa.hex" file, I can no longer see/select the Thingy either in the programmer or the LTE Link Monitor.

    This is probably the reason you did not see the response from AT command because you did not successfully program this serial LTE modem application firmware.

    Following  Updating firmware through USB guidance section 5 Update the nRF9160 SiP application, do you mean you have a problem at step c? but it is exactly the same action as the modem firmware update you did with "mfw_nrf9160_1.3.1.zip". Please double-check and provide more details about your failure if the problem still exists.

    Best regards,

    Charlie

Related