On 04.09.20 09:06, Bert Thomas wrote:
Thanks for your response! We are using our own mtd driver for at25f321 and qspi
and that driver indeed returns the number of bytes read. I changed it to 0 in
case of success and now it seems to work just fine!
I have no idea why the "old" version of RIOT
Hi,
Can you check if the issue is still present on the master branch?
There has been some rework on the MTD layer recently, the
mtd_read_page() function used by littlefs should only return non-0 on error.
However, so should mtd_spi_nor_read() on the 2020.07 branch.
What is your setup? Are y
Hi,
I've noticed drivers in RIOT will usually keep a copy of their
configuration parameters in RAM:
typedef struct {
riot_driver_params_t params;
} riot_driver_t;
void riot_driver_setup(riot_driver_t *dev,
const riot_driver_params_t *params)
{
dev->params = *params
On Wed, 15 Jul 2020 20:22:33 +0530
Rahul Jadhav wrote:
> Hi Linda,
>
> Whitefield[1] is another way to simulate RIOT-OS native on top of
> 802.15.4/PLC locally.
…
> Disclaimer: I am the lead author of Whitefield.
That's pretty cool! I didn't know about this.
Have you considered submitting the w
On Sat, 16 May 2020 22:49:54 +0200
Kees Bakker wrote:
> I'm looking for a program that can automatically reconnect to the
> USB serial after the RIOT board does a restart. So far I only found
> that minicom will do that, but not automatically.
pyterm [1] will do that. It's the default when you r
Hi,
we have a battery powered application that will spend most time in Deep
Sleep, so a wake-up will trigger a CPU reset with some backup memory
retained.
To conserve energy, the radio interface should only be activated if
there is data to send. In the common case the sensor would just wake up
Hello,
I propose to deprecate the oonf_api package [1]. The package provides a
framework to implement MANET protocols and is used by the NHDP
implementation. This one however is also marked as deprecated and is
scheduled to be removed after the 2020.04 release.
The package has not been updated
On 24.01.2015 11:04, Hiesgen, Raphael wrote:
Hello Benjamin,
I'm not sure what that documentation is based on though, running tests/malloc
will allocate and free all available memory just fine.
may I ask how you tested this?
I just flashed the test to my board (not stm32f4discovery, but _s
On 22.01.2015 15:45, Martine Lenders wrote:
Hi Raphael,
Since I am interested in the stm32f4discovery, everything should
be fine?
Was that a question? I guess it was… As far as its documentation goes
free is not possible by now on stm32f4:
https://github.com/RIOT-OS/RIOT/blob/master
