Thingy:91

[Hoang]

Dear, 

I received THINGY:91 from NordicSemi. I use 10pins cable to connect to nRF9160 DK to program for THINGY:91. 

and, I am using ncs_v1.0.0

I am trying to run asset_tracker application, 

and I am confusing about: 

1. which board should I select? I tried to use    ncs_v1.0.0/zephyr/boards/arm/nrf9160_pca10090

but after programming, the LED on THINGY:91 changed to RED color, and I couldnt connect it from nrfcloud 

I couldn't find pca20035 on ncs_v1.0.0. Do I need to use another version of ncs ?

2. How can I debug the output from THINGY:91

The terminal still shows the output from nRF9160 DK, nothing from THINGY:91

Thanks, 

Mvh

Hoang Nguyen

[Hoang]

Dear Bjørn Kvaale

I found nrf9160_pca20035 then I tried to program asset_tracker to THINGY:91, pressed the button (long press) then connected to nrfcloud and put the THINGY:91 outside. 

"Waiting for GPS Data...."

How to activate GPS? Do I need to use the external GPS antenna? 

Thanks 

Mvh

Hoang Nguyen

[Hoang]

Hi MJD093 Can you help?

[MJD093]

Ok so you have or haven't gotten the Thingy:91 to acquire a lock? Little confused here

[Hoang]

Bjørn Kvaale, 

I got the problem when I run asset_tracker on nRF9160 DK: ( It worked yesterday) 

SPM: NS image at 0x18200
SPM: NS MSP at 0x2002b4f8
SPM: NS reset vector at 0x20d09
SPM: prepare to jump to Non-Secure image.
***** Booting Zephyr OS build v1.14.99-ncs2-rc4-495-ga8933a2ead01 *****
[00:00:00.245,544] [1B][0m<dbg> nrf9160_gps.init: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577[1B][0m
Asset tracker started
[00:00:00.256,652] [1B][0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100264319[1B][0m
[00:00:00.265,930] [1B][0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100264319/shadow[1B][0m
[00:00:00.277,618] [1B][0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: $aws/things/nrf-352656100264319/shadow/get/accepted[1B][0m
[00:00:00.290,222] [1B][0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100264319/shadow/get/rejected[1B][0m
[00:00:00.302,795] [1B][0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100264319/shadow/update/delta[1B][0m
[00:00:00.315,734] [1B][0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100264319/shadow/update[1B][0m
[00:00:00.327,606] [1B][0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100264319/shadow/get[1B][0m
Connecting to LTE network. This may take several minutes.
[00:00:02.424,591] [1B][0m<dbg> lte_lc.at_handler: recv: +CEREG: 2,"765D","0110C303",7
[1B][0m
[00:00:03.684,783] [1B][0m<dbg> lte_lc.at_handler: recv: +CEREG: 5,"765D","0110C303",7
[1B][0m
Connected to LTE network
[00:00:03.968,078] [1B][0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0x82492d34[1B][0m
cloud_connect failed: -111
LTE link disconnect
Shutdown modem

[Bjørn Kvaale]

Nope, no external GPS antenna is needed. I am taking a look at this case & will get back to you soon. Good to hear at least that you did not get the nrf cloud 111 error, which is related to deleted certificates.

[Bjørn Kvaale]

cloud error 111 relates to missing certificates. If you have already connected your 91 DK to the nRF Cloud, you can use the procedure provided here to recover the missing certificates.

[Bjørn Kvaale]

I believe the antenna circuit is correctly matched. Not sure I can provide any info on the Thingy:91 GPS circuit, as it is not publicly available yet.