Sim Card not Detected on Thingy:91

[rishj09]

Hi, 

I am in the process in getting the AWS version of the Asset Tracker v2 on my Thingy:91. I was having some issues with getting the cerificate but was able to get that resolved as seen in this ticket (https://devzone.nordicsemi.com/f/nordic-q-a/84015/provisioning-device-certificate-for-aws-on-thingy91). 

Now, I am having issues with my Thingy91 recognizing my Sim card. Prior to this, I was able to use the device with the vanilla Asset Tracker v2 with nRF cloud and there were no issues. I have tried using another sim card (which I tested was working on my DK) and I get the same error. When I am running the Asset Tracker v2 code, it keeps on rebooting as seen in the error log below as it seems to think that a sim card is not detected. 

�*** Booting Zephyr OS build v2.7.0-ncs1  ***ng!
[00:00:00.223,876] <wrn> at_notif: Already initialized. Nothing to do
[00:00:00.240,356] <inf> event_manager: APP_EVT_START
[00:00:00.247,009] <inf> event_manager: DATA_EVT_CONFIG_INIT
[00:00:00.253,570] <inf> event_manager: APP_EVT_ACTIVITY_DETECTION_DISABLE
[00:00:00.261,383] <inf> event_manager: MODEM_EVT_INITIALIZED
[00:00:00.332,702] <inf> event_manager: MODEM_EVT_LTE_CONNECTING
[00:00:00.577,941] <err> modem_module: No SIM card detected!
[00:00:00.584,442] <inf> event_manager: MODEM_EVT_ERROR - Error code -134
[00:00:00.592,193] <inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE
[00:00:00.599,151] <inf> event_manager: UTIL_EVT_SHUTDOWN_REQUEST
[00:00:00.606,201] <inf> event_manager: UI_EVT_SHUTDOWN_READY
[00:00:00.612,396] <wrn> modules_common: Module "ui" shutdown registered
[00:00:00.619,842] <inf> event_manager: GPS_EVT_SHUTDOWN_READY
[00:00:00.626,190] <wrn> modules_common: Module "gps" shutdown registered
[00:00:00.634,094] <inf> event_manager: APP_EVT_SHUTDOWN_READY
[00:00:00.640,380] <wrn> modules_common: Module "app" shutdown registered
[00:00:00.648,559] <inf> event_manager: DATA_EVT_SHUTDOWN_READY
[00:00:00.654,968] <wrn> modules_common: Module "data" shutdown registered
[00:00:00.663,085] <inf> event_manager: MODEM_EVT_LTE_DISCONNECTED
[00:00:00.670,379] <inf> event_manager: CLOUD_EVT_SHUTDOWN_READY
[00:00:00.676,910] <wrn> modules_common: Module "cloud" shutdown registered
[00:00:00.684,753] <inf> event_manager: SENSOR_EVT_SHUTDOWN_READY
[00:00:00.691,314] <wrn> modules_common: Module "sensor" shutdown registered
[00:00:00.756,347] <inf> event_manager: MODEM_EVT_SHUTDOWN_READY
[00:00:00.762,969] <wrn> modules_common: Module "modem" shutdown registered
[00:00:00.770,507] <wrn> util_module: All modules have ACKed the reboot request.
[00:00:00.778,533] <wrn> util_module: Reboot in 5 seconds.

I have also tried to get some additional information through LTE Link Monitor. The error code I get for AT%XSIM? seems to indicate it is an USIM failure. However, this exact sim card is working on my DK. Could this be an issue introduced by something I did when installing the certificates? I have also tried reflashing the modem firmware but the issue still persists. 

2022-02-05T21:57:22.036Z DEBUG modem >> AT+CFUN=1
2022-02-05T21:57:22.056Z DEBUG modem << OK
2022-02-05T21:57:22.297Z DEBUG modem << +CEREG: 90
2022-02-05T21:57:23.533Z DEBUG modem >> AT+CFUN?
2022-02-05T21:57:23.542Z DEBUG modem << +CFUN: 1
2022-02-05T21:57:23.551Z DEBUG modem << OK
2022-02-05T21:57:23.566Z DEBUG modem >> AT+CGSN=1
2022-02-05T21:57:23.581Z DEBUG modem << +CGSN: "352656106116299"
2022-02-05T21:57:23.583Z DEBUG modem << OK
2022-02-05T21:57:23.589Z DEBUG modem >> AT+CGMI
2022-02-05T21:57:23.603Z DEBUG modem << Nordic Semiconductor ASA
2022-02-05T21:57:23.605Z DEBUG modem << OK
2022-02-05T21:57:23.607Z DEBUG modem >> AT+CGMM
2022-02-05T21:57:23.619Z DEBUG modem << nRF9160-SICA
2022-02-05T21:57:23.621Z DEBUG modem << OK
2022-02-05T21:57:23.623Z DEBUG modem >> AT+CGMR
2022-02-05T21:57:23.635Z DEBUG modem << mfw_nrf9160_1.3.1
2022-02-05T21:57:23.637Z DEBUG modem << OK
2022-02-05T21:57:23.637Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.1] SerNr: 352656106116299
2022-02-05T21:57:23.639Z DEBUG modem >> AT+CEMODE?
2022-02-05T21:57:23.653Z DEBUG modem << +CEMODE: 2
2022-02-05T21:57:23.658Z DEBUG modem << OK
2022-02-05T21:57:23.669Z DEBUG modem >> AT%XCBAND=?
2022-02-05T21:57:23.683Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
2022-02-05T21:57:23.688Z DEBUG modem << OK
2022-02-05T21:57:23.696Z DEBUG modem >> AT+CMEE?
2022-02-05T21:57:23.707Z DEBUG modem << +CMEE: 1
2022-02-05T21:57:23.709Z DEBUG modem << OK
2022-02-05T21:57:23.722Z DEBUG modem >> AT+CNEC?
2022-02-05T21:57:23.734Z DEBUG modem << +CNEC: 24
2022-02-05T21:57:23.736Z DEBUG modem << OK
2022-02-05T21:57:23.741Z DEBUG modem >> AT+CGEREP?
2022-02-05T21:57:23.752Z DEBUG modem << +CGEREP: 1,0
2022-02-05T21:57:23.754Z DEBUG modem << OK
2022-02-05T21:57:23.759Z DEBUG modem >> AT+CIND=1,1,1
2022-02-05T21:57:23.768Z DEBUG modem << OK
2022-02-05T21:57:23.770Z DEBUG modem >> AT+CEREG=5
2022-02-05T21:57:23.776Z DEBUG modem << OK
2022-02-05T21:57:23.778Z DEBUG modem >> AT+CEREG?
2022-02-05T21:57:23.786Z DEBUG modem << +CEREG: 5,90
2022-02-05T21:57:23.788Z DEBUG modem << OK
2022-02-05T21:57:23.804Z DEBUG modem >> AT%CESQ=1
2022-02-05T21:57:23.810Z DEBUG modem << OK
2022-02-05T21:57:23.818Z DEBUG modem >> AT+CESQ
2022-02-05T21:57:23.826Z DEBUG modem << +CESQ: 99,99,255,255,255,255
2022-02-05T21:57:23.828Z DEBUG modem << OK
2022-02-05T21:57:23.839Z DEBUG modem >> AT%XSIM=1
2022-02-05T21:57:23.844Z DEBUG modem << OK
2022-02-05T21:57:23.852Z DEBUG modem >> AT%XSIM?
2022-02-05T21:57:23.859Z DEBUG modem << %XSIM: 0,9
2022-02-05T21:57:23.860Z DEBUG modem << OK

Thanks!  

[Charlie]

Hi Rishj, 

Yes, you can contact your distributor or our local sales team to get it replaced if the HW has an issue.

You can use the following AT commands with the sample: nRF9160: Serial LTE modem — nRF Connect SDK 1.8.0 documentation (nordicsemi.com) to test the internet connection without considering the certification.

2022-02-09T09:55:22.872Z DEBUG modem << Ready
2022-02-09T09:55:27.627Z DEBUG modem >> AT+CFUN=1
2022-02-09T09:55:27.678Z DEBUG modem << OK
2022-02-09T09:55:43.355Z DEBUG modem >> AT+CGPADDR
2022-02-09T09:55:43.429Z DEBUG modem << +CGPADDR: 0,"10.2.241.235","2A02:2121:0604:7788:0000:0000:0F89:FFEC"
2022-02-09T09:55:43.439Z DEBUG modem << OK
2022-02-09T09:55:52.186Z DEBUG modem >> AT+CGCONTRDP=0
2022-02-09T09:55:52.285Z DEBUG modem << +CGCONTRDP: 0,,"telenor.smart","","","193.213.112.4","130.67.15.198",,,,,1500
2022-02-09T09:55:52.297Z DEBUG modem << +CGCONTRDP: 0,,"telenor.smart","","","2001:4600:0004:0FFF:0000:0000:0000:0052","2001:4600:0004:1FFF:0000:0000:0000:0052",,,,,1500
2022-02-09T09:55:52.299Z DEBUG modem << OK
2022-02-09T09:55:58.890Z DEBUG modem >> AT#XPING="www.google.com",45,5000,5,1000
2022-02-09T09:55:59.633Z DEBUG modem << OK
2022-02-09T09:55:59.775Z DEBUG modem << #XPING: 0.107 seconds
2022-02-09T09:56:00.976Z DEBUG modem << #XPING: 0.153 seconds
2022-02-09T09:56:02.177Z DEBUG modem << #XPING: 0.150 seconds
2022-02-09T09:56:03.376Z DEBUG modem << #XPING: 0.150 seconds
2022-02-09T09:56:04.496Z DEBUG modem << #XPING: 0.085 seconds
2022-02-09T09:56:05.533Z DEBUG modem << #XPING: average 0.129 seconds

Best regards,

Charlie

[rishj09]

Thanks for those commands. Unfortunately, the AT commands AT+CGPADDR and AT+CGCONTRDP=0 do not create a response and the ping requests raises an error. 

Going back to the hardware, can you shed some light on voltage/current measurements I could make on the test points to make sure the sim hardware is functioning properly?

Also, is it possible to get some input on the team responsible for the tool used to flash the certificates I had linked in my original post to see if it is possible some error in that process is causing this issue? 

Physically, I do not see anything wrong with this sim card holder and connections. 

[Charlie]

Hi Rishj,

rishj09 said:

Going back to the hardware, can you shed some light on voltage/current measurements I could make on the test points to make sure the sim hardware is functioning properly?

You can download the schematic from the Thingy91 page, but I do not suggest you go in this direction since it will be time-consuming, and you even do not have another Thingy91 as a reference. We really hope you focus on your development. Testing on another Thingy91 will simply help to confirm where the issue comes from.

rishj09 said:

Also, is it possible to get some input on the team responsible for the tool used to flash the certificates I had linked in my original post to see if it is possible some error in that process is causing this issue? 

In theory, it shouldn't be possible because the operations of the certificate happen on the nRF9160 Modem core and the flash inside, it is not related to the SIM card.

Best regards,

Charlie

[Charlie]

Hi Rishj,

rishj09 said:

Going back to the hardware, can you shed some light on voltage/current measurements I could make on the test points to make sure the sim hardware is functioning properly?

You can download the schematic from the Thingy91 page, but I do not suggest you go in this direction since it will be time-consuming, and you even do not have another Thingy91 as a reference. We really hope you focus on your development. Testing on another Thingy91 will simply help to confirm where the issue comes from.

rishj09 said:

Also, is it possible to get some input on the team responsible for the tool used to flash the certificates I had linked in my original post to see if it is possible some error in that process is causing this issue? 

In theory, it shouldn't be possible because the operations of the certificate happen on the nRF9160 Modem core and the flash inside, it is not related to the SIM card.

Best regards,

Charlie

[rishj09]

I understand, thank you! I am on a limited student budget but will try to get a hold of another Thingy91 to better debug this issue.