mbed-os

Author	SHA1	Message	Date
amq	6a3c69488f	EFM32: make peripherals conditional * MCUs within a family like EFM32GG can omit some peripherals, e.g. EFM32GG230 doesn't have UART * This commit adds a check to make them compilable, relevant mainly for custom boards	2018-02-09 14:18:43 +00:00
Steven Cooreman	4df6986100	[EFM32] Use targets.json to improve directory structure Now that we have targets.json, we get target inheritance and can use it to clean up the EFM32 folder structure. * In the top-level EFM32 folder, there are now folders per MCU family (Giant, Leopard, ...) * Those family folders contain the CMSIS headers in the 'device' subfolder, as well as global family headers (i.e. mapping of pins to peripherals) * Inside of the family folder, there is a per-target folder containing target settings. In the future, we'll want to get rid of those by using the config system provided by targets.json	2016-10-24 18:24:49 +02:00

Author

SHA1

Message

Date

amq

EFM32: make peripherals conditional * MCUs within a family like EFM32GG can omit some peripherals, e.g. EFM32GG230 doesn't have UART * This commit adds a check to make them compilable, relevant mainly for custom boards

2018-02-09 14:18:43 +00:00

Steven Cooreman

4df6986100

[EFM32] Use targets.json to improve directory structure

Now that we have targets.json, we get target inheritance and can use it to clean up the EFM32 folder structure.
* In the top-level EFM32 folder, there are now folders per MCU family (Giant, Leopard, ...)
* Those family folders contain the CMSIS headers in the 'device' subfolder, as well as global family headers (i.e. mapping of pins to peripherals)
* Inside of the family folder, there is a per-target folder containing target settings. In the future, we'll want to get rid of those by using the config system provided by targets.json

2016-10-24 18:24:49 +02:00

2 Commits (mbed-os-5.7)