Thanks Juan,
That's a lot of information to digest. It will take me a bit of time
to go through.
-- Kees
On 27-05-19 14:17, Juan Ignacio Carrano wrote:
Hi Kees,
Some observations:
1- WFI will not send you to the deepest sleep states- clocks are
gated, but many things remain powered.
2- If
Hey Oleg,
Are you using the watchdog?
On 27-05-19 07:30, Oleg Artamonov wrote:
Hi
We do. On STM32L0, STM32L1, nRF52, etc.
Checking for interrupt flags is absolutely useless here - 1) WFI
checks for any relevant interrupt flags, 2) interrupt still can happen
between check and WFI.
--
Hi,
this is a reminder or maybe new information for some: The Hack'n'ACK this
month will start in Berlin (and Paris?) tomorrow already at 3pm. If we see
a success in the number of attendance, this might become a regular thing.
Kind regards,
Martine
Am Mo., 27. Mai 2019 um 17:01 Uhr schrieb
This is a notification for:
Title: Hack'n'ACK
https://meet.jit.si/riot-hacknack
When: Tue May 28, 2019 5pm – 10pm Central European Time - Berlin
Where: FU Berlin; HAW Hamburg
Calendar: RIOT Events
Who:
* Martine Lenders - creator
Event details:
On 5/27/19 2:36 PM, Emmanuel Baccelli wrote:
Seems to me that a quick riotboot porting guide could be useful somewhere
in the wiki.
More in the `riotboot` documentation in the repository I would say.
On Mon, May 27, 2019 at 2:30 PM Gaëtan Harter
wrote:
Hi Brenton,
if you only use the
On 24/5/19 11:40, Kaspar Schleiser wrote:
> IMO the syslog API itself should not be used for new or RIOT-targeting
applications...
Except it already is:
#define log_write(level, ...) printf(__VA_ARGS__)
and
static inline void log_write(unsigned level, const char *format, ...) {
While
Seems to me that a quick riotboot porting guide could be useful somewhere
in the wiki.
On Mon, May 27, 2019 at 2:30 PM Gaëtan Harter
wrote:
> Hi Brenton,
>
> if you only use the default `riotboot/flash` or `flash` in
> `tests/riotboot` targets, you do not need flasher changes.
> But you should
Hi Brenton,
if you only use the default `riotboot/flash` or `flash` in
`tests/riotboot` targets, you do not need flasher changes.
But you should not use `riotboot/flash-slot0` and `riotboot/flash-slot1`
targets for the moment.
To have the support declared and merged in RIOT, it also needs to
Hi Kees,
Some observations:
1- WFI will not send you to the deepest sleep states- clocks are gated,
but many things remain powered.
2- If you are using the timer module and depending on you clock
configuration you may experience more or less frequent wake ups. Whether
this is acceptable is
Hi We do. On STM32L0, STM32L1, nRF52, etc. Checking for interrupt flags is absolutely useless here - 1) WFI checks for any relevant interrupt flags, 2) interrupt still can happen between check and WFI. -- Sincerely yours,Oleg Artamonov+7 (916) 631-34-90www.unwds.com 26.05.2019, 18:40, "Kees
Hi Kaspar,
IMO the syslog API itself should not be used for new or RIOT-targeting
applications. Having it available makes porting existing code easier,
thus I still think it is valid to have it available.
Having the syslog-over-udp functionality available is pretty awesome,
especially if it
11 matches
Mail list logo
