Thales

The demo is configured to be able to build for the different microcontrollers, so you need to specify which one you're using through cargo features. You might also want to...

> nRF51 devices only support payloads of up to 27 bytes. Maybe we should change the example to use smaller payloads, I remember that I used those sizes because I...

From the docs: https://github.com/nrf-rs/nrf-hal/blob/af83e6ed69c5ec03b1e0f6b4adae53258f57e83a/nrf-hal-common/src/ccm.rs#L40 And from the manual: Encryption (Page 121): > The AES CCM is limited to read maximum 27 bytes of the unencrypted payload (PL) regardless of what...

Isn't this API susceptible to the `mem::forget` problem ? See https://docs.rust-embedded.org/embedonomicon/dma.html#memforget

Right now, I see two solutions: - `'static` borrows, also explained in the embedonomicon: https://docs.rust-embedded.org/embedonomicon/dma.html#static-bound, you can see an example implementation here: https://github.com/stm32-rs/stm32f1xx-hal/blob/master/src/dma.rs (`Pin` probably wasn't used because it wasn't...

Not saying I'm against this, but as a workaround, you can just depend on a (compatible) version of `native-tls` (or `openssl` directly) with the feature enabled, features are additive.

First I would like to clarify that I don't think the possibility of a `fn evil()` scenario is unsound, so I don't think we have a problem in today's api...

> Then you'll have to store the shared registers globally somehow. If you use something like RTIC that allows you to share resources easily that's actually not as bad, but...

Currently, you can get both the transfer complete flag and half transfer complete flag through the `Stream` trait, we should probably add methods to get at least the transfer error...

Unfortunately, there isn't support for this on the HAL itself (yet). About your example, you will need to check the manual and the HAL code to be sure your new...