Hi,
the `random` should IMHO also stay strictly an API for *pseudo* random
number generators, I agree however with Michel's issue, that hwnrg should
be used for seed generation if available.
Cheers,
Martine
2018-03-05 17:08 GMT+01:00 Michel Rottleuthner <
michel.rottleuth...@haw-hamburg.de>:
>
Hi,
Not sure it will help but I recently tried to use a Semtech LoRa radio with an
Arduino Zero and using a second SPI (for the radio) was working with the
following configuration:
{
.dev = &SERCOM1->SPI,
.miso_pin = GPIO_PIN(PA, 19),
.mosi_pin = GPIO_PIN(PA, 16),
.clk_pin = GPIO_PIN(PA, 1
Hey,
Im trying to use the AT86RF233 with the Arduino M0 Pro (using the Arduino
Zero configuration).
Using the default SPI configuration (and pins) didnt work, why I tried to
change the SPI to the Arduino_Pins 11,12,13 in order to have CS (PIN 10)
using the same SERCOM as the other SPI pins.
Ho
Hi Josua,
IMO: cpu/periph is right if its part of the SOC (as you already said,
there should be no dependency to the at86rf2xx driver -if possible- ).
Regarding your other question: I think the answer is no, at the moment
its not guaranteed that calls to random32 are directed to hwrng, see [1
Thanks Martine,
But as the atmegarfr2 is a soc this is the hwrng for this device.
So what would be the best place to put it if not as cpu/periph in this special
case?
I would then implement it as CPU feature and remove the depency to the
at86rf2xx driver.
Still the remaining question is it ma
Hi Josua,
when the RNG component of the at86rf2xx driver was provided in [1] we
decided to not implement the `periph/hwnrg` with it.
Main reasons are that it is
1. Not a `periph` (i.e. a CPU feature)
2. Hard to integrate when e.g. the CPU already provides a `hwnrg`.
Hope this helps,
Martine
[1]
Hello all,
While implementing the at86rfr2 transceiver for the jiminy board I thought of
also implement the hwrng.
What I did is implementing in cpu/atmega256rfr2/periph/hwnrg.c
hwrng_init
hwrng_read
Added feature and module to makefiles.
Now I have some questions:
1. How do I best include
Joakim this sounds like you have some idea how to? Could you please elaborate?
Best regards,
Josua
Von: devel [mailto:devel-boun...@riot-os.org] Im Auftrag von Joakim Nohlgård
Gesendet: Donnerstag, 1. März 2018 16:42
An: RIOT OS kernel developers
Betreff: Re: [riot-devel] Improve Documentation
