- fix false test failure on picolibc
- For picolibc, the result of mallinfo().uordblks doesn't go back
to zero after the first allocation. By adding `free(malloc(4))`
before recording the pre-test mallinfo() value, this issues is
worked arround
- increase test coverage to also cover realloc()
- ease testing with picolibc by allowing `make PICOLIBC=1 flash test`
Add ATmega328P Xplained Mini board. The board is an official
development kit from MCHP based on the Arduino UNO, reduced
hardware, with a xplainedmini debugger and CDC ACM serial
converter.
Signed-off-by: Gerson Fernando Budke <nandojve@gmail.com>
This board is based on rak4260 with rak specific pinmappings.
ADC, LED and UART as well as USB ist supposed to work.
Mostly adopted from SAM R34 Xplained Pro board with adoption to rak pinout.
The previous sine wave cast signed integers into the PCM range, causing
jumps at zero transitions. This shifts everything up by the respective
maximum signed integer, so that the signed idle zero becomes the
unsigned PCM signal's idle half-point and can continuously cover the
whole unsigned range.
The additional warning message increases the size of the .rodata
section. For the Arduino Mega2560 this is placed in RAM (and flash), as
flash is not mapped into the data address space.
test_ieee802154_set_frame_hdr_flags0_non_beacon_non_ack
buffer given to ieee802154_set_frame_hdr has to be at least 2 bytes
see <RIOT>/sys/net/link_layer/ieee802154/ieee802154.c l32
Add atxmega-a1u-xpro board to BOARD_INSUFFICIENT_MEMORY list to
exclude test since boards don't have enough data memory.
Signed-off-by: Gerson Fernando Budke <nandojve@gmail.com>
Atmel XMEGA CPU don't have a timer prescaler div16 and div32 option.
This means that at full speed (32MHz) it is not possible have a 1MHz
clock tick. Define default tick to 500kHz and add atxmega-a1u-xpro
boards to test list.
Signed-off-by: Gerson Fernando Budke <nandojve@gmail.com>
The API doc of ptp_clock_adjust_speed says regarding the correction
parameter:
1. A call with @p correction set to `0` restores the nominal clock speed.
2. A call with a positive value for @p correction speeds the clock up
by `correction / (1 << 32)` (so up to ~50% for `INT32_MAX`).
3. A call with a negative value for @p correction slows the clock down by
`-correction / (1 << 32)` (so up to 50% for `INT32_MIN`).
So we need to divide by 2^32, not 2^32 - 1 (or `UINT32_MAX`).
