Take into account stack buffers and printf for allocating the default
stack size.
This solves stack size issues with `wsn430-v1_3b` and `z1`.
It now have a main stack usage of 514 bytes out of 768 on `wsn430-v1_3b`.
Be more pedantic in expected output for shell commands.
For slow boards, `ws430-v1_3b/arduino-mega2560/msba2`, some commands
were sent before the output of the previous command.
Newlib-nano does not seem to support hexadecimal floats or the %a
specifier. What is even weirder, it reports a successful conversion
anyways.
Tests for these two cases have been commented out.
Update the 'code' section detection to also work on kinetis.
The boards using 'cortexm.ld' have the code section starting with
'.text'. For the 'cpu/kinetis/kinetis.ls' the first section is '.vector'.
Update the 'awk' matching pattern to correctly detect the kinetis boards.
It is a dependency to allow testing upcoming offset support with kinetis.
I am not 100% sure about the pattern for awk.
With `newlib-nano` and other smaller `libc`s the output of floats does
not work with `printf()`. Since minmea uses floating point operations
I used `fmt` instead.
The Arduino Leonardo requires - like the other ATmega based Arduinos - a
different frequency than the default 1000000, as this frequency cannot be
achieved on a 16MHz ATmega with any available prescaler.
When `ds18_read` returns -2506, DS18 test print `Temperature [ºC]: -25.-6`
whereas it should print `Temperature [ºC]: -25.06. This commit fixes this
issue.
Previously, there was a very tight allowed margin (100us), then some
special cases for platforms for which the test would otherwise fail,
increasing the margin.
This turned out to be a maintanance burden, as each slightly special
board needed a PR adding the special case.
This commit sets a quite large margin (1000us, 0.1% of total delay),
which should be large enough to not trip over platform-induced timer
inaccuracies, but still verify that the module is using timers
correctly.
(This is not a timer accuracy test.)
`tests/gnrc_udp` was specifically introduced for testing the release
specs. All of them ask the tester to check the packet buffer after the
test. So it makes sense to include the module that allows for that per
default for this test so the tester does not forget to include it ;-).
