examples/readme: fix SAUL spelling mistake
examples/readme: Link to README.md instead of folder
examples/readme: increase title size
examples/readme: make networking category name a bit clearer
examples/readme: move nimble to own category within BLE
examples/readme: move dtls to own category
examples/readme: move heart rate sensor to nimble category
examples/readme: move arduino sketch to languages
examples/timer_periodic: fix file name issue
examples/readme: change level wording about nanocoap
This changes the API of xfa from
XFA(array_name, prio) type element_name = INITIALIZER;
to
XFA(type, array_name, prio) element_name = INITIALIZER;
this allows forcing natural alignment of the type, fixing failing tests
on `native64`.
Before, handlers writing blockwise transfer assumed that the response
header length will match the request header length. This is true for
UDP, but not for TCP: The CoAP over TCP header contains a Len field,
that gets extended for larger messages. Since the reply often is indeed
larger than the request, this is indeed often the case for CoAP over
TCP.
Note: Right now, no CoAP over TCP implementation is upstream. However,
getting rid of incorrect assumptions now will make life easier
later on.
We cannot just decrement the reference counter of power modes without
any coordination. First, this will trigger an `assert()`ion on non
STM32 MCUs that have power modes that are not used (the ref count would
be decremented below zero). Second, there hopefully is a reason a
certain power mode is blocked, e.g. because a periph driver needs a
certain clock to function.
Likely the `periph_uart` driver on STM32 boards keeps power modes
blocked after TX is completed even when no RX callback is present, which
is the waste of power this hack tries to address. But that should be
addressed there.
This updates riot-sys, riot-wrappers and the riot-example-modules in for
this example, as all those are needed for full LED exposure, as well as
coap-message-utils for better error responses. An update to
coap-handler-implementations enables the use of the latest
riot-examples-modules.
Some increase in binary size is expected due to one bug fix around the
VFS access where a zero-cost version would require threading
non-idiomatic nul-terminated strings through too many abstraction levels
to be practical.
This was previously limited to constfs due to [8], but now that that is
fixed, it can show its full potential of enumerating both directories
and mount points.
[8]: https://gitlab.com/etonomy/riot-wrappers/-/issues/8
This pulls in several updates for which there is no urgent need, but
also no good reason *not* to do them (especially as they may contain bug
fixes, even critical ones).
