nRF9160 LTE Modem IPC

RE: nRF9160 LTE Modem IPC

bjorn-spockeli — Thu, 07 Feb 2019 16:00:17 GMT

Hi Martijin,

Yes, the nRF Connect SDK is something completely different compared to the nRF5 SDK, incorporating an RTOS adds complexity, but it also gives a lot of advantages.

The nRF Connect SDK is still in development so things are being documented as we work towards a production release. Things are being updated on a daily basis, so things should get better with time.

I would recommend that you take a look at Nordic's Zephyr fork and its documentation if you want to look more on how Zephyr works.

As for more examples for the nRF9160, one of my colleagues have made several examples, among them a simple at client, available here on his fork.

Best regards

Bjørn

RE: nRF9160 LTE Modem IPC

Martijn — Wed, 06 Feb 2019 21:22:22 GMT

Great! Really appreciate that!

The main problem is that I have a hard time understanding how the examples are working. It is completely different from what I am used to with the nRF5 SDK and it does nog really fit in our current way of working.

The library looks like a good solution to interact with the modem, but I cannot really figure out how the examples work. Especially in combination with the Zephyr OS.

RE: nRF9160 LTE Modem IPC

bjorn-spockeli — Wed, 06 Feb 2019 16:06:45 GMT

Hi Martijn,

No, the encryption isnt for the AT commands, but the data that is passed with the AT commands to be sent to the cellular network. I that the documentation we have is the one that is in the nrfxlib repo. I'll ask a colleague that has been working with the nRF Connect SDK if there is anything we can share .

Best regards

Bjørn

RE: nRF9160 LTE Modem IPC

Martijn — Wed, 06 Feb 2019 15:40:06 GMT

Thank you for your answer.

Do I need to encrypt the AT commands???

I already saw the example, that is what I used to get where I am now. I do not need and want encryption right now. I just want to able to control the LTE modem. Is there any updated documentation about the bsdlib? because the documentation that is available right now, is not helping me enough.

RE: nRF9160 LTE Modem IPC

bjorn-spockeli — Wed, 06 Feb 2019 15:14:22 GMT

Hi Martijn,

the bsdlib library creates a socket interface that is used to communicate with the modem. This socket uses mbedTLS to encrypt the data that is passed to the socket. If you are looking for a AT client example for the nRF91, then we have an example here.

Best regards

Bjørn

RE: nRF9160 LTE Modem IPC

Martijn — Mon, 04 Feb 2019 21:37:48 GMT

Alright, got some progress. I think...

I did correctly include the library, but apparently the library needs the functions to be implemented by myself. I found the nrfxlib documentation: http://www.nordicsemiconductors.no/nRF_Connect_SDK/doc/0.3.0/nrfxlib/bsdlib/doc/api.html#os-specific-definitions But even after implementing these functions, I get some 'undefined references' for the libbsd_nrf9160_xxaa.a library:

make: *** [debug/nRF91.elf] Error 1
../../Resources/Targets/Nordic/nRF91/bare/Common/nrfxlib-0.3.0/bsdlib/lib/cortex-m33/soft-float\libbsd_nrf9160_xxaa.a(es256.c.o): In function `es256_key_generate':
es256.c:(.text.es256_key_generate+0x6e): undefined reference to `occ_ecdsa_p256_public_key'
../../Resources/Targets/Nordic/nRF91/bare/Common/nrfxlib-0.3.0/bsdlib/lib/cortex-m33/soft-float\libbsd_nrf9160_xxaa.a(es256.c.o): In function `es256_message_sign':
es256.c:(.text.es256_message_sign+0x88): undefined reference to `occ_ecdsa_p256_sign'
../../Resources/Targets/Nordic/nRF91/bare/Common/nrfxlib-0.3.0/bsdlib/lib/cortex-m33/soft-float\libbsd_nrf9160_xxaa.a(pk.c.o): In function `mbedtls_pk_verify':
pk.c:(.text.mbedtls_pk_verify+0x2e): undefined reference to `mbedtls_md_info_from_type'
pk.c:(.text.mbedtls_pk_verify+0x34): undefined reference to `mbedtls_md_get_size'
../../Resources/Targets/Nordic/nRF91/bare/Common/nrfxlib-0.3.0/bsdlib/lib/cortex-m33/soft-float\libbsd_nrf9160_xxaa.a(pk.c.o): In function `mbedtls_pk_verify_ext':
pk.c:(.text.mbedtls_pk_verify_ext+0x56): undefined reference to `mbedtls_md_info_from_type'
pk.c:(.text.mbedtls_pk_verify_ext+0x5c): undefined reference to `mbedtls_md_get_size'
../../Resources/Targets/Nordic/nRF91/bare/Common/nrfxlib-0.3.0/bsdlib/lib/cortex-m33/soft-float\libbsd_nrf9160_xxaa.a(pk.c.o): In function `mbedtls_pk_sign':
pk.c:(.text.mbedtls_pk_sign+0x3a): undefined reference to `mbedtls_md_info_from_type'
pk.c:(.text.mbedtls_pk_sign+0x40): undefined reference to `mbedtls_md_get_size'
../../Resources/Targets/Nordic/nRF91/bare/Common/nrfxlib-0.3.0/bsdlib/lib/cortex-m33/soft-float\libbsd_nrf9160_xxaa.a(asn1write.c.o): In function `mbedtls_asn1_store_named_data':
asn1write.c:(.text.mbedtls_asn1_store_named_data+0x10): undefined reference to `mbedtls_asn1_find_named_data'
collect2.exe: error: ld returned 1 exit status

Then I thought, maybe it is the other library. I added it, and it worked for some, but now it asks me for mbedtls functions. After some more reading I found out that liboberon_2.0.5.a is a crypto library, and I really doubt I need that.

It were just a few functions, so I made stubs for them. Now the application compiles without warnings and errors.

But why does the library require me to add a crypto lib that requires me to use mbedtls? I just want to control the LTE modem in the NRF9160.

Thank you!