crasbe

No need to apologize. The RIOT build system can be quite a beast and integrating a package that wasn't designed for RIOT is not an easy task. Unfortunately I don't...

I gave this a test with an nRF52DK devboard and the tests run successfully: Then I tested the example and it did work for small executables (10 bytes), but resulted...

Perhaps you can add some of the remarks to the README in the examples folder. Especially the explanation how to create a .bin/.fae file should (also) be part of the...

@GGuche-2XS-Univ-Lille what's the current status? I now have a DWM1001 module and could give this another test.

Okay, I'll take a look at it again soon. About the CI failure on MSP430: this is caused by this line: https://github.com/2xs/xipfs/blob/cd45f5d60bab584c47f603470fb4768688704d3c/include/xipfs.h#L61 On the MSP430, the values for `#define`s are...

Of course you can start with a new PR, no worries :) Working with git and GitHub can be quite a steep learning curve and unfortunately sometimes a clean start...

(Possibly) Unresolved Review Points: https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2038214528 ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2067050803~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2067063534~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2067073241~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2067218117~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2068462870~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2068515596~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2068517891~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2068518783~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2081957711~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2120561042~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2081968057~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2084237583~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2084243366~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2096119604~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2123992817~~ ~~https://github.com/RIOT-OS/RIOT/pull/21390#discussion_r2124093187~~ Ping @mguetschow

I ran `make -C examples/networking/coap/unicoap-message generate-Makefile.ci` locally and this is the `Makefile.ci` it generated: ``` BOARD_INSUFFICIENT_MEMORY := \ arduino-duemilanove \ arduino-nano \ arduino-uno \ atmega328p \ atmega328p-xplained-mini \ atmega8 \...

@carl-tud when you add the `examples/networking/coap/unicoap-message/Makefile.ci` file, you can squash the commit directly.

I'm not sure this is so easy to distinguish in a shell script. Do the `extern "C"` declarations do any harm in a header with only macros?