This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

If change iBASIS sim card to another PCA10090 DK board

Hi

There are two PCA10090 DK boards. Each one had its own iBASIS card.

Previously, I registered these two in nRF Connect for Cloud. DK board A with SIM card A.

DK board B with SIM card B. Both of them can connect to cloud and work simulated GPS and orientation.

Then, I tried to swap SIM cards. That is DK board A with card B and DK board B with card A.

I found they can not connect to cloud. Why?

Did nRF Cloud identify the device for modem information and SIM card information both?

Thanks.

Jeffery

 

Parents
  • Hello,

    This might be a case of a bug that has been witnessed a lot lately. It's being worked on to fix it.

  • I'm also experiencing this on my device after I removed it from nrfcloud and are trying to re-activate it.

    I get this message, and then the device reboots and it all repeats.

    Do I have to do anything to be able to re-connect my device to nrfcloud?

    SPM: NS image at 0xc000
    SPM: NS MSP at 0x2002c4c0
    SPM: NS reset vector at 0x14715
    SPM: prepare to jump to Non-Secure image.
    ***** Booting Zephyr OS build v1.14.99-ncs3-snapshot2-1266-g8711cfd5d348 *****
    [00:00:00.243,713] <dbg> nrf9160_gps.init: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577
    Asset tracker started
    [00:00:00.254,608] <dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100266058
    [00:00:00.263,702] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100266058/shadow
    [00:00:00.275,207] <dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: $aws/things/nrf-352656100266058/shadow/get/accepted
    [00:00:00.287,567] <dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100266058/shadow/get/rejected
    [00:00:00.299,896] <dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100266058/shadow/update/delta
    [00:00:00.312,591] <dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100266058/shadow/update
    [00:00:00.324,249] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100266058/shadow/get
    Connecting to LTE network. This may take several minutes.
    [00:00:02.695,404] <dbg> lte_lc.at_handler: recv: +CEREG: 2,"76C1","013F1700",7
    
    [00:00:03.815,704] <dbg> lte_lc.at_handler: recv: +CEREG: 5,"76C1","013F1700",7
    
    Connected to LTE network
    [00:00:04.222,930] <dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0xa4445f03
    cloud_connect failed: -111
    LTE link disconnect
    Shutdown modem
    

  • It could be that you have accidentally deleted or overwritten the certificates. If that's the case this post shows how you can recover them.

Reply Children
No Data
Related