[riot-devel] Question about expected timer semantics

Hi everyone, I think everyone agrees that if a relative timer is set, it is expected to run *at least* the amount of time that is specified as interval to timer_set(). That means if now() is e.g., 0 ticks and the timer is set to wait 1 tick, the timer must trigger at 2 ticks, as even if

Re: [riot-devel] Question about expected timer semantics

> Am 26.11.2019 um 20:47 schrieb Kaspar Schleiser : > > Hi Should that be done, > or should the conversion be implemented in a way that the 1ms timer > behaves the same regardless of the lower timer having 1ms or 1us precision? Hi Kaspar, As a user/developer I would expect that sleep_ms(1)

[riot-devel] Notification: Hack'n'ACK @ Tue Nov 26, 2019 5pm - 10pm (CET) (RIOT Events)

This is a notification for: Title: Hack'n'ACK https://meet.jit.si/riot-hacknack When: Tue Nov 26, 2019 5pm – 10pm Central European Time - Berlin Where: FU Berlin; HAW Hamburg Calendar: RIOT Events Who: * Martine Lenders - creator Event details:

[riot-devel] IEEEE 802.15.4 FCF Format in "RIOT/sys/net/link_layer/ieee802154/ieee802154.c"

Hi all, I am having a hard time understanding how the "ieee802154_set_frame_hdr" function, found in this link, sets the Frame Control Field (FCF) for 802.15.4 frame header. Following the IEEE 802.15.4 FCF

[riot-devel] Please ignore!

Test (The Hack'n'ACK notification was not on this mailing list, so I'm testing if the list still works) ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] IEEEE 802.15.4 FCF Format in "RIOT/sys/net/link_layer/ieee802154/ieee802154.c"

I think you must have made a mistake in your calculations. buf[1] contains bits 8-15 of the fcf, bits 12-13 are the version bits. 12 - 8 = 4, 1 << 4 = 0x10, so the frame version is set to version 1, all other bits are zero at the beginning of that function. Best regards, Joakim Den tis 26 nov.