Hi,
The Makefile.features defines the features of a board, that's why it lives in
the boards directory. So yes, it is intended to declare the RNG in there even
if it is not part of the CPU/SoC.
It would be architecturally nicer to have such files in various places (eg CPU,
radio, board) and
Unfortunately, it doesn't. My problems are:
a) In the case of my board, the hardware RNG is not part of the CPU but instead
of the radio chip, which is accessed by the code in driver/at86rf2xx.
b) If I implement the hwrng interface in the at86rf2xx code, how does the
samr21-xpro board learn of
Hi Mathias,
I think (but I never implemented any device drivers so take this with a
grain of salt) the most sensible solution would be to add a function to the
`at86rf2xx` driver that returns a result from the RNG and then wrap it with
`periph_hwrng` on all boards that come with this device.
Hope
Hi Mathias,
[1] is the interface that should be implemented by your driver. The
driver is CPU specific and should be placed in RIOT/cpu/*/periph/hwrng.c
like e.g. here [2].
Does that reduce your confusion or did I get you wrong :-) ?
Best
Peter
[1]
Hi Mathias,
I think the way to go here is to implement the
`drivers/include/periph/hwrng.h` interface. For this I think it makes
sense to add a function that reads the random data from the radio to the
at86rf2xx driver and call this function from the hwrng driver.
Cheers,
Hauke
On
OK, I have managed the first step myself and wrote the code which reads out the
random values from the RNG.
What would be the next step, that would allow me to set the periph_random
feature for the samr21-xpro board?
cheers
Mathias
On Die, 2016-02-16 at 16:14 +, Tausig Mathias wrote:
> Hy!
>
Hy!
I would like to use the hardware RNG from my samr1-xpro board. It should be
available by reading out a certain register, according to the AT86RF233
documentation.
My problem is, that I don't how to do that (I am pretty new to this stuff). Is
there some documentation available for this kind
