Closed zerog2k closed 6 years ago
mbed depends on a specific target name which it uses among soure code. If you have a custom board which is compatible with existing mbed's target, you map it in ~/.platformio/packages/framework-mbed/platformio/variants_remap.json
following instructions here, http://docs.platformio.org/en/latest/platforms/creating_board.html trying to create a project-specific custom board json, e.g boards/rcqr01.json
however, this alone simply does not appear to be enough. Seems mbed framework may require more than this, as I get this when building:
I can use the bbcmicrobit (as it has same 16k memory as my board), but I wanted to customize to my board, and be able to keep it with the project dir in the repo. Looking into
.platformio/packages/framework-mbed/platformio/
, i see there are a ton of VARIANTS which seem to have some mbed specific configuration, e.g. microbit: NRF51_MICROBIT/mbed_config.h & NRF51_MICROBIT/NRF51_MICROBIT.jsonmaybe this is some microbit limitation? is there any way to "extend" an existing board definition, or any way to expose the lower-level mbed configuration at project-level control (again, so it can be captured and distributed with repo)