nRF9160 to Google Cloud Pub/Sub: Build errors

RE: nRF9160 to Google Cloud Pub/Sub: Build errors

Heidi — Wed, 05 Feb 2020 09:34:58 GMT

Hi Dheeraj, please make a new ticket on DevZone and explain the issue while also linking to this ticket if it's similar.

Best regards,

Heidi

RE: nRF9160 to Google Cloud Pub/Sub: Build errors

Dheeraj — Tue, 04 Feb 2020 23:51:36 GMT

I am facing the same above issue while connecting my Thingy91 PCA20035 device to Google cloud uisng MQTT bridge.

I have placed nRFDKtoGoogleCloud folder inside the ncs-folder, for example giving the path \ncs\nrf\samples\nrf9160\nRF9160DKtoGoogleCloud.

I followed this guide to send data to the GCP using the Thingy:91 : https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/how-to-connect-nrf91-to-google-cloud

I m pretty sure I did it correct and followed all steps listed there.

After writing the hex file to the thingy:91 this is the serial output.

This is my build error logs:

***** Booting Zephyr OS version 2.1.0-rc1 *****
Provisioning
GCLOUD_HOSTNAME:mqtt.googleapis.com
GCLOUD THREAD LIVES
[00:00:00.939,575] <err> gcloud: key delete err: 2 No such file or directory
[00:00:01.519,470] <err> gcloud: key delete err: 2 No such file or directory
[00:00:02.098,663] <err> gcloud: key delete err: 2 No such file or directory
[00:00:02.678,314] <err> gcloud: key delete err: 2 No such file or directory
[00:00:03.260,894] <err> gcloud: key delete err: 2 No such file or directory
[00:00:03.386,901] <dbg> gcloud.gcloud_provision: CERT:
-----BEGIN CERTIFICATE-----
MIIBdTCCARugAwIBAgIJAOvj4PVfAgqjMAoGCCqGSM49BAMCMBYxFDASBgNVBAMM
C25yZjkxLW1hcnRlMCAXDTE5MDQwNTExMTUxN1oYDzQ3NTcwMzAyMTExNTE3WjAW
MRQwEgYDVQQDDAtucmY5MS1tYXJ0ZTBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IA
BAq8otkWGnocpdAxlnpJdVn6EBb1WbQnZXLFaYzsMeXWGFIIO02hWTvaSUPI1xNs
0QB8c3IU9oBhDXkRNU2Nqi2jUDBOMB0GA1UdDgQWBBRLAhO335CAd280I/qVQmiM
07nd8TAfBgNVHSMEGDAWgBRLAhO335CAd280I/qVQmiM07nd8TAMBgNVHRMEBTAD
AQH/MAoGCCqGSM49BAMCA0gAMEUCIF2kQO7Cqn73ANmwBdgGA1y/KGOpOU4I/ywF
LEu8trOUAiEA8//UWttMRkmaylghw3mgsYGGKk17rY+4j+4mGUwvDnw=
-----END CERTIFICATE-----

Provisioning complete
Initializing modem
Establishing LTE link (this may take some time) ...
[00:00:06.564,483] <dbg> lte_lc.parse_nw_reg_status: Network registration status: 2
[00:00:09.131,195] <dbg> lte_lc.parse_nw_reg_status: Network registration status: 5
Modem configured
Connecting to Google Cloud
[00:00:09.227,691] <inf> gcloud: Got CONNECT command
[00:00:09.252,288] <dbg> gcloud.gcloud_thread: Initiating broker
[00:00:09.676,086] <dbg> gcloud.broker_init: IPv4 Address found 0xce857d4a
[00:00:09.702,667] <dbg> gcloud.gcloud_thread: Making JWT
[00:00:10.487,609] <dbg> gcloud.make_jwt: timestamp: 1580855965
Timestamp: 1580855965[00:00:10.830,932] <dbg> gcloud.gcloud_thread: Initiating client
[00:00:11.204,559] <dbg> gcloud.make_jwt: timestamp: 1580855966
Timestamp: 1580855966[00:00:11.547,485] <dbg> gcloud.client_init: JWT:
eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJzcGFucGFya2luZyIsImV4cCI6MTU4MDg5OTE2NiwiaWF0IjoxNTgwODU1OTY2fQ.g1_nGrphjRQ5kFYHij3hlTmLZp81dy9615EoEtSxyNnyf92dlW3lMpzmRYifMqp_3C4ElG1TaGXLX3r4ImQvtA

[00:00:11.589,355] <dbg> gcloud.client_init: JWT length: 198
[00:00:11.667,724] <dbg> gcloud.gcloud_thread: Starting input timer
[00:00:11.693,725] <dbg> gcloud.gcloud_thread: Connecting mqtt
[00:00:11.739,135] <err> gcloud: mqtt_connect failed: -22 Invalid argument
GCLOUD THREAD LIVES
Sending JSON data:
{
"Message": 22019
}
[00:00:19.285,156] <wrn> gcloud: Cannot publish data while not connected to Google Cloud
[00:00:21.693,817] <inf> gcloud: Got INPUT_TIMEOUT command

GCLOUD THREAD LIVES
Sending JSON data:
{
"Message": 22019
}
[00:00:19.285,256] <wrn> gcloud: Cannot publish data while not connected to Google Cloud
[00:00:21.693,917] <inf> gcloud: Got INPUT_TIMEOUT command

Please help me with the possible solution to fix the above issue.

This is missing my final deadline for production.

Thanks

RE: nRF9160 to Google Cloud Pub/Sub: Build errors

Marte Myrvold — Tue, 24 Sep 2019 14:30:32 GMT

Hi Tim,

Yes, connection refused does sound like a problem with certificates or how the device was added on Google Cloud.

Great that you managed to solve it!

RE: nRF9160 to Google Cloud Pub/Sub: Build errors

T1mS_ — Tue, 24 Sep 2019 14:16:38 GMT

Hi ,

now it works. The problem was in the Google Cloud I guess. Something with the certificates. The error was "connection refused" so I added the device again to the cloud. 🙂

RE: nRF9160 to Google Cloud Pub/Sub: Build errors

Marte Myrvold — Tue, 24 Sep 2019 10:25:20 GMT

Hi Tim,

In order to find what error number -13 is, you can use strerror().

printk("err: %d\n", strerror(-err));

This will print what error number -13 corresponds to. You can add this where the following is in the code

LOG_ERR("mqtt_input failed: %d", err);

That is, line 635 in gcloud.c

strerror() must take a positive error number, hence the minus in front of err in the code above.

Hope this helps.

Best regards,

Marte

RE: nRF9160 to Google Cloud Pub/Sub: Build errors

T1mS_ — Tue, 24 Sep 2019 08:17:38 GMT

Hi ,

I tried it again today and now I get error -13.

I tried to find some information about the error number but can't find any.

Provisioning complete
Initializing modem
Establishing LTE link (this may take some time) ...
[00:00:04.352,233] <inf> lte_lc: Using legacy LTE PCO mode...
Modem configured
Connecting to Google Cloud
[00:00:25.399,536] <inf> gcloud: Got CONNECT command
[00:00:25.399,536] <dbg> gcloud.gcloud_thread: Initiating broker
[00:00:25.771,453] <dbg> gcloud.broker_init: IPv4 Address found 0xce857d4a
[00:00:25.771,484] <dbg> gcloud.gcloud_thread: Making JWT
[00:00:26.301,574] <dbg> gcloud.make_jwt: timestamp: 1569312515
[00:00:26.596,160] <dbg> gcloud.gcloud_thread: Initiating client
[00:00:27.723,602] <dbg> gcloud.make_jwt: timestamp: 1569312517
[00:00:28.018,188] <dbg> gcloud.client_init: JWT:
eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJmbHV0ZWQtY2xvY2stMjQ5MzE1IiwiZXhwIjoxNTY5MzU1NzE3LCJpYXQiOjE1NjkzMTI1MTd9.6MoUK~

[00:00:28.018,218] <dbg> gcloud.client_init: JWT length: 208
[00:00:28.018,218] <dbg> gcloud.gcloud_thread: Starting input timer
[00:00:28.018,249] <dbg> gcloud.gcloud_thread: Connecting mqtt
Sending JSON data:
{
"Message":22019
}
[00:00:35.409,729] <wrn> gcloud: Cannot publish data while not connected to Google Cloud
[00:00:39.603,912] <err> gcloud: mqtt_connect failed: -111 Connection refused
GCLOUD THREAD LIVES
[00:00:39.603,942] <inf> gcloud: Got INPUT_TIMEOUT command
[00:00:39.603,973] <err> gcloud: mqtt_input failed: -13
GCLOUD THREAD LIVES
Sending JSON data:
{
"Message":22019
}
[00:00:45.419,952] <wrn> gcloud: Cannot publish data while not connected to Google Cloud
[00:00:48.018,249] <inf> gcloud: Got INPUT_TIMEOUT command
[00:00:48.018,280] <err> gcloud: mqtt_input failed: -13
GCLOUD THREAD LIVES

Thanks.

Tim

RE: nRF9160 to Google Cloud Pub/Sub: Build errors

T1mS_ — Mon, 23 Sep 2019 15:30:02 GMT

Hi Marte,

this did the trick! Now it is not crashing anymore. 😬

Now it fails at sending the data... :D

phyr Oa***** Booting Zephyr OS build v1.14.99-ncs3-snapshot2-1279-g1c3a001f62e6 *****
[00:00:00.291,717] <err> at_host: UART check failed: 12. Dropping buffer and retrying.
Provisioning
GCLOUD THREAD LIVES
[00:00:02.575,225] <err> gcloud: key delete err: 2 No such file or directory
[00:00:03.008,209] <err> gcloud: key delete err: 2 No such file or directory
[00:00:03.445,648] <err> gcloud: key delete err: 2 No such file or directory
[00:00:03.885,925] <err> gcloud: key delete err: 2 No such file or directory
[00:00:03.885,925] <dbg> gcloud.gcloud_provision: CERT:
-----BEGIN CERTIFICATE-----
MIIBdTCCARugAwIBAgIJAOvj4PVfAgqjMAoGCCqGSM49BAMCMBYxFDASBgNVBAMM
C25yZjkxLW1hcnRlMCAXDTE5MDQwNTExMTUxN1oYDzQ3NTcwMzAyMTExNTE3WjAW
MRQwEgYDVQQDDAtucmY5MS1tYXJ0ZTBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IA
BAq8otkWGnocpdAxlnpJdVn6EBb1WbQnZXLFaYzsMeXWGFIIO02hWTvaSUPI1xNs
0QB8c3IU9oBhDXkRNU2Nqi2jUDBOMB0GA1UdDgQWBBRLAhO335CAd280I/qVQmiM
07nd8TAfBgNVHSMEGDAWgBRLAhO335CAd280I/qVQmiM07nd8TAMBgNVHRMEBTAD
AQH/MAoGCCqGSM49BAMCA0gAMEUCIF2kQO7Cqn73ANmwBdgGA1y/KGOpOU4I/ywF
LEu8trOUAiEA8//UWttMRkmaylghw3mgsYGGKk17rY+4j+4mGUwvDnw=
-----END CERTIFICATE-----

Provisioning complete
Initializing modem
Establishing LTE link (this may take some time) ...
[00:00:04.336,090] <inf> lte_lc: Using legacy LTE PCO mode...
Modem configured
Connecting to Google Cloud
[00:00:29.186,645] <inf> gcloud: Got CONNECT command
[00:00:29.186,645] <dbg> gcloud.gcloud_thread: Initiating broker
[00:00:29.588,562] <dbg> gcloud.broker_init: IPv4 Address found 0xce857d4a
[00:00:29.588,592] <dbg> gcloud.gcloud_thread: Making JWT
[00:00:30.038,696] <dbg> gcloud.make_jwt: timestamp: 1569252388
[00:00:30.333,160] <dbg> gcloud.gcloud_thread: Initiating client
[00:00:30.900,695] <dbg> gcloud.make_jwt: timestamp: 1569252389
[00:00:31.194,732] <dbg> gcloud.client_init: JWT:
eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJmbHV0ZWQtY2xvY2stMjQ5MzE1IiwiZXhwIjoxNTY5Mjk1NTg5LCJpYXQiOjE1NjkyNTIzODl9.tc22w~

[00:00:31.194,763] <dbg> gcloud.client_init: JWT length: 208
[00:00:31.194,763] <dbg> gcloud.gcloud_thread: Starting input timer
[00:00:31.194,793] <dbg> gcloud.gcloud_thread: Connecting mqtt
GCLOUD THREAD LIVES
Sending JSON data:
{
"Message":22019
}
[00:00:39.196,838] <wrn> gcloud: Cannot publish data while not connected to Google Cloud
[00:00:41.194,824] <inf> gcloud: Got INPUT_TIMEOUT command
[00:00:41.194,885] <inf> gcloud: MQTT event: 0
[00:00:41.194,885] <dbg> gcloud.mqtt_event_handler: Got CONNACK
[00:00:41.194,915] <err> gcloud: MQTT connect failed: 5
GCLOUD THREAD LIVES
Sending JSON data:
{
"Message":22019
}
[00:00:49.207,061] <wrn> gcloud: Cannot publish data while not connected to Google Cloud
[00:00:51.194,824] <inf> gcloud: Got INPUT_TIMEOUT command
GCLOUD THREAD LIVES
Sending JSON data:
{
"Message":22019
}
[00:00:59.217,285] <wrn> gcloud: Cannot publish data while not connected to Google Cloud
[00:01:01.194,824] <inf> gcloud: Got INPUT_TIMEOUT command
GCLOUD THREAD LIVES

With the lte link monitor I proved that I have an lte connection, so this should not be the reason for the error.

I also get the "CONNACK" so I have a connection, right?

Right after the "Connect acknowledgment" I get "MQTT connect failed: 5".

I will search around to finf out what this means. :)

Do you might have another tip for me?

Best regards,

Tim

RE: nRF9160 to Google Cloud Pub/Sub: Build errors

Marte Myrvold — Mon, 23 Sep 2019 14:15:33 GMT

Hi Tim,

This tells you that it fails at

return api->write(port, access_op, pin, value);

If you scroll up, you will see which function it fails in, which I assume is the following:

static inline int z_impl_gpio_write

It seems like the problem might be related to nRF9160DK and Thingy:91 having different pinouts, considering the project was originally written for the DK. I would assume that the LEDs are the problem, so one possible fix is to remove all instances in main.c where the following function is called

dk_set_led_on()

Let me know whether this works.

Best Regard,

Marte

RE: nRF9160 to Google Cloud Pub/Sub: Build errors

T1mS_ — Mon, 23 Sep 2019 13:47:10 GMT

Yes, I'm already on v1.0.0.

To be honest, I've no idea what this tells me:

Thanks,

Tim

RE: nRF9160 to Google Cloud Pub/Sub: Build errors

Marte Myrvold — Mon, 23 Sep 2019 13:38:48 GMT

Hi,

Have you tried with version v1.0.0 of ncs?

Also, to get more information about when the hard fault happened, you can open the file /build/zephyr/zephyr.lst and search for your faulting instruction address, which is 1921c in the output above.

RE: nRF9160 to Google Cloud Pub/Sub: Build errors

T1mS_ — Mon, 23 Sep 2019 12:17:32 GMT

Hi,

I fixed the error. After moving the whole directory to the c drive root instead of using all these sub folders.

After writing the hex file to the thingy:91 this is the serial output. Did messed something up with the certificates?

9-23T13:00:52.943Z INFO Modem port is opened
2019-09-23T13:00:52.949Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-09-23T13:01:04.632Z INFO Modem port is opened
2019-09-23T13:01:04.634Z DEBUG modem << [00:00:01.161,804] <err> gcloud: key delete err: 2 No such file or directory\x0D\x0A
2019-09-23T13:01:04.635Z DEBUG modem << [00:00:01.595,428] <err> gcloud: key delete err: 2 No such file or directory\x0D
2019-09-23T13:01:04.636Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-09-23T13:01:04.638Z DEBUG modem << [00:00:02.032,806] <err> gcloud: key delete err: 2 No such file or directory\x0D\x0A
2019-09-23T13:01:04.780Z DEBUG modem << +CFUN: 4\x0D
2019-09-23T13:01:04.781Z DEBUG modem << \x0A
2019-09-23T13:01:04.782Z DEBUG modem << OK\x0D\x0A\x00
2019-09-23T13:01:04.787Z DEBUG modem >> AT+CFUN=1\x0D\x0A
2019-09-23T13:01:05.569Z DEBUG modem << [00:00:02.473,114] <err> gcloud: key delete err: 2 No such file or directory\x0D
2019-09-23T13:01:05.574Z DEBUG modem << [00:00:02.473,114] <dbg> gcloud.gcloud_provision: CERT:\x0A
2019-09-23T13:01:05.576Z DEBUG modem << -----BEGIN CERTIFICATE-----\x0A
2019-09-23T13:01:05.583Z DEBUG modem << MIIBdTCCARugAwIBAgIJAOvj4PVfAgqjMAoGCCqGSM49BAMCMBYxFDASBgNVBAMM\x0A
2019-09-23T13:01:05.587Z DEBUG modem << C25yZjkxLW1hcnRlMCAXDTE5MDQwNTExMTUxN1oYDzQ3NTcwMzAyMTExNTE3WjAW\x0A
2019-09-23T13:01:05.592Z DEBUG modem << MRQwEgYDVQQDDAtucmY5MS1tYXJ0ZTBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IA\x0A
2019-09-23T13:01:05.599Z DEBUG modem << BAq8otkWGnocpdAxlnpJdVn6EBb1WbQnZXLFaYzsMeXWGFIIO02hWTvaSUPI1xNs\x0A
2019-09-23T13:01:05.604Z DEBUG modem << 0QB8c3IU9oBhDXkRNU2Nqi2jUDBOMB0GA1UdDgQWBBRLAhO335CAd280I/qVQmiM\x0A
2019-09-23T13:01:05.610Z DEBUG modem << 07nd8TAfBgNVHSMEGDAWgBRLAhO335CAd280I/qVQmiM07nd8TAMBgNVHRMEBTAD\x0A
2019-09-23T13:01:05.615Z DEBUG modem << AQH/MAoGCCqGSM49BAMCA0gAMEUCIF2kQO7Cqn73ANmwBdgGA1y/KGOpOU4I/ywF\x0A
2019-09-23T13:01:05.620Z DEBUG modem << LEu8trOUAiEA8//UWttMRkmaylghw3mgsYGGKk17rY+4j+4mGUwvDnw=\x0A
2019-09-23T13:01:05.622Z DEBUG modem << -----END CERTIFICATE-----\x0A\x0D
2019-09-23T13:01:06.600Z DEBUG modem << OK\x0D
2019-09-23T13:01:06.603Z DEBUG modem << Initializing modem\x0A
2019-09-23T13:01:06.606Z DEBUG modem << --- 1 messages dropped ---\x0D
2019-09-23T13:01:06.610Z DEBUG modem << Establishing LTE link (this may take some time) ...\x0A
2019-09-23T13:01:06.617Z DEBUG modem << [00:00:04.341,705] <inf> lte_lc: Using legacy LTE PCO mode...\x0D\x0A
2019-09-23T13:01:06.618Z DEBUG modem << Modem configured\x0A\x0D
2019-09-23T13:01:06.620Z DEBUG modem << Connecting to Google Cloud\x0A\x0D
2019-09-23T13:01:06.625Z DEBUG modem << [00:00:04.342,193] <err> os: Exception occurred in Secure State\x0D
2019-09-23T13:01:06.633Z DEBUG modem << [00:00:04.342,224] <err> os: ***** HARD FAULT *****\x0D
2019-09-23T13:01:06.635Z DEBUG modem << [00:00:04.342,224] <err> os:   Fault escalation (see below)\x0D\x0A
2019-09-23T13:01:06.640Z DEBUG modem << [00:00:04.342,254] <err> os: ***** BUS FAULT *****\x0D
2019-09-23T13:01:06.645Z DEBUG modem << [00:00:04.342,254] <err> os:   Precise data bus error\x0D
2019-09-23T13:01:06.650Z DEBUG modem << [00:00:04.342,254] <err> os:   BFAR Address: 0x50008120\x0D
2019-09-23T13:01:06.657Z DEBUG modem << [00:00:04.342,285] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000001  r2/a3:  0x00037ad0\x0D
2019-09-23T13:01:06.666Z DEBUG modem << [00:00:04.342,285] <err> os: r3/a4:  0x00000001 r12/ip:  0x20029104 r14/lr:  0x00012be5\x0D
2019-09-23T13:01:06.669Z DEBUG modem << [00:00:04.342,315] <err> os:  xpsr:  0x61000000\x0D
2019-09-23T13:01:06.678Z DEBUG modem << [00:00:04.342,315] <err> os: s[0]:  0x00000000  s[1]:  0x00000000  s[2]:  0x00000000  s[3]:  0x00000000\x0A
2019-09-23T13:01:06.688Z DEBUG modem << [00:00:04.342,346] <err> os: s[4]:  0x00000000  s[5]:  0x00000000  s[6]:  0x00000000  s[7]:  0x00000000\x0A
2019-09-23T13:01:06.699Z DEBUG modem << [00:00:04.342,376] <err> os: s[8]:  0x00000000  s[9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000000\x0A
2019-09-23T13:01:06.707Z DEBUG modem << [00:00:04.342,376] <err> os: s[12]:  0x00000000  s[13]:  0xffffffff  s[14]:  0x00000000  s[15]:  0x00000000\x0A
2019-09-23T13:01:06.711Z DEBUG modem << [00:00:04.342,407] <err> os: fpscr:  0x00000000\x0A
2019-09-23T13:01:06.718Z DEBUG modem << [00:00:04.342,407] <err> os: Faulting instruction address (r15/pc): 0x0001921c\x0D
2019-09-23T13:01:06.724Z DEBUG modem << [00:00:04.342,407] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception\x0D
2019-09-23T13:01:06.733Z DEBUG modem << [00:00:04.342,437] <err> os: Current thread: 0x20023214 (unknown)\x0D\x0A
2019-09-23T13:01:06.735Z DEBUG modem << [00:00:04.470,947] <err> os: Halting system\x0D\x0A