Software and Protocols - All Comments

RE: Connecting to AWS cloud services using the nRF9160

user107948 — Wed, 03 Nov 2021 17:06:53 GMT

Hello Hakan,
Any updates?
Can you please try to run with the latest (1.3.1) firmware drop?
Thanks!
John

RE: nRF9160 DK: Offloading Bluetooth Low Energy related tasks to nRF52840 SoC

user84036 — Mon, 05 Jul 2021 09:47:14 GMT

I have questions regarding the communication between nRF52 and nRF91.

1. Is this UART connection similar to enable interface between two chips, by adding the below line on overlay file?

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:17099f24-56d9-4914-8463-48a5b76e9b75:type=c_cpp&text=%23include%20%3Cnrf9160dk_uart1_on_if0_3.dtsi%3E]

2. In my application, I am using NUS service, and using uart0. Now I want to create another uart, uart1, in order to pass the data I received from BLE on nRF52 to nRF91, and send it over LTE network. But on the nRF52 side, I think it is not working. Probably there is something wrong with the device tree or configuration, since I got the device.

Do you have any idea? Thank you very much.

RE: nRF9160 DK: Offloading Bluetooth Low Energy related tasks to nRF52840 SoC

user84036 — Mon, 05 Jul 2021 07:55:29 GMT

Thank you for interesting approach.

RE: nRF9160 DK: Offloading Bluetooth Low Energy related tasks to nRF52840 SoC

user101635 — Mon, 31 May 2021 10:33:47 GMT

Not sure if I should post here, or to the community in general, but .....

What you have created is basically what I am looking for, a simple way to pass data between the 9160 & 52840. I have pulled the above code, where the 9160 compiles and installs fine, but the 52840 gives an error with respect to CONFIG_BOARD_NRF9160DK_INTERFACE0_MCU=y and CONFIG_BOARD_NRF9160DK_INTERFACE1_MCU=y

/code/sdk-nrf/samples/nrf9160/nrf9160dk_serial/nrf52840/prj.conf:7: warning: attempt to assign the value 'y' to the undefined symbol BOARD_NRF9160DK_INTERFACE0_MCU

Did you run into this error - as I didnt see anything in the community when I searched for the error.

I am running on the 9160dk.

RE: nRF9160 DK: Offloading Bluetooth Low Energy related tasks to nRF52840 SoC

user71845 — Fri, 15 Jan 2021 15:05:30 GMT

This is a really interesting article. How difficult would it be to have a similar approach to other HA protocols?

RE: Enabling and testing TLS in mqtt_simple

user13635 — Wed, 25 Nov 2020 12:44:18 GMT

I have followed these instructions and got to the point where it says "At this point the sample should compile but won't use TLS". It does compile but does not make a connection. I am building for 9160-DK (ns) on the command line on MacOS. I suspect that the problem may be that I am trying to use the supplied iBasis SIM straight out of the box.

RE: Monitoring nRF9160 data usage with connectivity statistics

user87816 — Wed, 09 Sep 2020 11:55:17 GMT

Is there a way to determine air time? Aka how long the modem was in an active state of communications?
AT%XCONNSTAT? only tells you how much data was transmitted.

RE: How to connect nRF9160 DK to Google Cloud

user85877 — Tue, 28 Jul 2020 20:33:54 GMT

Thanks for the tutorial Marte!

For anyone interested, I've ported the gcloud library to the latest ncs version and the Thingy91.

This application gets readings from the onboard environmental sensor and publishes to an MQTT topic as described in the post above.

https://github.com/mcallistertad/nrf_google_iot_core/

RE: Enabling and testing TLS in mqtt_simple

user78282 — Wed, 18 Mar 2020 18:22:28 GMT

I added all of the code snippets above to the files indicated. I reloaded the project from the open nfrconnect sdk project. When I look in main.c all of the conditionals for CONFIG_MQTT_LIB_TLS remain grayed out. prj.conf has CONFIG_MQTT_LIB_TLS=y. What am I missing?

RE: Enabling and testing TLS in mqtt_simple

user87732 — Tue, 03 Mar 2020 23:41:51 GMT

Hi Daniel,

I have followed these instructions carefully but I am getting the build error:

'sec_tag_list' undeclared (first use in this function); did you mean 'sec_tag_t'?

from the changes to client_init (error line in bold below):

#if defined(CONFIG_MQTT_LIB_TLS)
struct mqtt_sec_config *tls_config = &client->transport.tls.config;

client->transport.type = MQTT_TRANSPORT_SECURE;

tls_config->peer_verify = CONFIG_PEER_VERIFY;
tls_config->cipher_count = 0;
tls_config->cipher_list = NULL;
tls_config->sec_tag_count = ARRAY_SIZE(sec_tag_list);
tls_config->sec_tag_list = sec_tag_list;
tls_config->hostname = CONFIG_MQTT_BROKER_HOSTNAME;
#else
/* MQTT transport configuration */
client->transport.type = MQTT_TRANSPORT_NON_SECURE;
#endif /* defined(CONFIG_MQTT_LIB_TLS) */

maybe I have been looking at this too long and its obvious but any help would be appreciated...

RE: Enabling and testing TLS in mqtt_simple

user86377 — Sat, 15 Feb 2020 08:47:06 GMT

hi nordic

it have some erro about cred.py, with NRFJPROG DLL: -3 INVALID_PARAMETER

"
C:\temp\ncs\nrf\samples\nrf9160\mqtt_simple\cred>python cred.py --CA_cert ../build/zephyr/CA.crt --client_cert ../build/zephyr/client.crt --client_private_key ../build/zephyr/client.key --sec_tag 51966 --program_app merged.hex
xxxxxxxxxxxxxxx
error: An error was reported by NRFJPROG DLL: -3 INVALID_PARAMETER.
C:\temp\ncs\nrf\samples\nrf9160\mqtt_simple\cred>nrfjprog.exe -v
nrfjprog version: 9.8.1
JLinkARM.dll version: 6.54c
"

RE: Enabling and testing TLS in mqtt_simple

user77106 — Tue, 04 Feb 2020 14:27:42 GMT

Excellent article! I especially like the trick of the cred.py mini-application to read IMEI and write certificates and application images.

Heads-up to anyone depending on full TLS validation: it seems that hostname validation doesn't work properly as of right now. It's a subtle bug that doesn't complain or fail, but doesn't actually enable. (i.e. the hostname will never be checked against the cert name)

The PEER_VERIFY=2 does work on most servers, though, so you can still be sure that the server you're connecting to is using a cert from the designated CA, which mitigates most of the risk.

RE: Automating nRF91 TLS credential management via serial port AT commands

user75305 — Tue, 14 Jan 2020 16:45:53 GMT

This is great! I would have had to build something similar myself eventually, so it's great that you shared this. Regarding the method of finding the correct serial port. From PySerial you can use the serial.tools.list_ports method to find all the ports. It identifies them by Vendor ID, VID, PID, Serial Number, and a few other useful nuggets of info. You can then (usually) find the correct one to use based on this info.

RE: The four kinds of data you need to consider when developing an IoT product

user75091 — Wed, 18 Dec 2019 01:58:00 GMT

I worked on Azure and the concept of device twins looks similar to what I used their for connecting many computers. Surely, the same concept will be very much beneficial for low power embedded devices.