Re: [riot-devel] Happy 10k!

Fantastic! Let's keep rocking! On Mon, Feb 22, 2016 at 6:33 AM, Ludwig Knüpfer < ludwig.knuep...@fu-berlin.de> wrote: > Hoorah! > > BTW: > what's the current SLoC count? > > Cheers, > Ludwig > > Am 22. Februar 2016 00:56:13 MEZ, schrieb Kaspar Schleiser < > kas...@schleiser.de>: > >Hey fellow

Re: [riot-devel] Happy 10k!

Hoorah! BTW: what's the current SLoC count? Cheers, Ludwig Am 22. Februar 2016 00:56:13 MEZ, schrieb Kaspar Schleiser : >Hey fellow RIOTers, > >we've passed 1 commits... > >Congratulations to everyone! > >Kaspar >___ >devel

Re: [riot-devel] Make error: SPI Driver test program

Hi, It seems you are not building for your target board but for native. Native has no SPI support (as indicated by the error message). If you export BOARD for your target hardware (which has to support SPI), things should go better. Cheers, Ludwig Am 21. Februar 2016 22:55:13 MEZ, schrieb

Re: [riot-devel] Implementing rng

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

[riot-devel] Make error: SPI Driver test program

Hi All, As a beginner's level task, I'm working on Spansion NOR flash memory (S25FL127S) interfacing with STM32F072 (ARM Cortex M0 based SOC). I've a custom board which has Spansion Flash memory connected to STM32F072 over SPI bus. I've a work-in-progress driver under:

Re: [riot-devel] Implementing rng

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

Re: [riot-devel] Implementing rng

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

Re: [riot-devel] Implementing rng

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]

Re: [riot-devel] 6LOWPAN RIOT

Hi Giri, could you maybe give some examples of what you tried already? Also have a look at PR 4725 [1] which aims to automate a lot of the bootstrapping needed to be done for LoWPAN initialization (though no RPL initialization yet). Cheers, Martine [1] https://github.com/RIOT-OS/RIOT/pull/4725