nrf-rs/nrfxlib

Rust wrapper for the Nordic nrfxlib library for the nRF9160.

nrfxlib's Issues

Add DTLS sockets

Adding DTLS sockets would allow us to add a Rust language implementation of CoAP.

Allow configuring init params

Currently the init function assumes a particular memory layout. When using a custom bootloader the memory layout may vary significantly. It would be nice to be able to pass in the addresses.

Cast errors with 0.4.0

Hi, I'm very new to doing embedded dev with Rust.
I'm trying to use https://github.com/42-technology-ltd/nrf9160-demo
but I keep getting cast errors like this:

let result = unsafe { sys::nrf_write(self.fd, ptr as *const _, length) };
    |                                                                        ^^^^^^ expected `u32`, found `usize`

Is there a way to fix this or can I help fix it?

Implement embedded-nal traits?

The embedded-nal crate exposes a couple of traits (e.g. TcpClientStack, UdpClientStack, TcpFullStack, UdpFullStack, etc) to facilitate writing networking abstractions that are platform independent.

Can't publish crate

We can't publish this crate as it uses a git-submodule. We can't publish it with a git-dep on nrfxlib-sys either. The only solution is to fix nrf-rs/nrfxlib-sys#6, publish that crate, then we can publish this crate.

Should wait_for_lte fail on not finding an available network?

I wonder if the wait_for_lte function should check on receiving a status of +CEREG: 4 and fail. I think +CEREG: 4 indicates that there's no available network i.e. "Unknown (for example, out of Evolved Terrestrial Radio Access Network (E-UTRAN) coverage)". Or is the idea to continuously try until it can get one?

Errors trying to connect

I was trying to use the nrf9160-demo application with the latest version of this repo, but I had some errors.

1. I had to change the nrf9160-hal to use 0x0000_C000 as the load address, because that's what the latest SPM seems to use. Or at least, that's what the SPM built with the "at_sample" application was expecting; I think they might auto-configure the flash partition layout depending on the application you are building.
2. I couldn't init nrfxlib with trace off, but it did work with trace on.
3. Creating a TLS socket failed with Err(Nrfxlib(Nordic("new_socket", -1, 41))) if I tried to make a TLS v1.3 socket with verification enabled. Error 41 is NRF_EPROTOTYPE.
4. Creating a TLS socket worked if I made a TLS v1.2 socket with verification disabled, but connecting to it gave Err(Nrfxlib(Nordic("tls_connect", -1, 45)), which is NRF_EOPNOTSUPP.

PollEntry mutably borrows the Pollable

Great work on the library!

One thing I was a little confused by, is the mutable borrow here. I can't really find a reason why it'd have to be mutably borrowed, since it works just fine when changing it into an immutable borrow.
The reason I had to change this was because I wanted to receive data from the socket after polling it, which was not possible because the socket was already being mutably borrowed by the PollEntry.

I'll drop a PR to change this.