Hi,
I think the question is what mapping you want to have between a board (the
physical hardware) and a RIOT board. If the mapping should be 1:1, than one
physical board could have different CPUs and configurations.
If you however agree with a 1:n mapping, than having different RIOT boards for
Hi Gaëten,
BOARD_MODULE is used by the Silicon Labs SLWSTK6000b because it is one board
with many supported CPU daughter boards (different CPU, other radio configs).
You would buy that board, but also need to buy this daughter board separately.
A similar approach is used by the EFM32 CPU
Dear RIOT developers,
as part of migrating CPU and CPU_MODEL definition to `Makefile.features`
I am facing custom handling of multiple boards in the same directory
with sometime creative handling but not a proper build system integration.
There are multiple issues with this:
* none of the
