zephyr/boards/arm/stm3210c_eval/stm3210c_eval.yaml

identifier: stm3210c_eval
name: STM3210C-EVAL
type: mcu
arch: arm
toolchain:
  - zephyr
  - gnuarmemb
ram: 64
flash: 256
boards: add board meta-data Add board metadata to be consumed by the sanitycheck script to provide better matching with testcases and to test based on features declated in the board files. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-04-05 11:08:59 +08:00			`identifier: stm3210c_eval`
update: board names Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-06-17 02:23:38 +08:00			`name: STM3210C-EVAL`
boards: add board meta-data Add board metadata to be consumed by the sanitycheck script to provide better matching with testcases and to test based on features declated in the board files. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-04-05 11:08:59 +08:00			`type: mcu`
			`arch: arm`
			`toolchain:`
			`- zephyr`
build: Replace GCC ARM Embedded with GNU Arm Embedded The old GCC ARM Embedded website on launchpad (https://launchpad.net/gcc-arm-embedded) has been superseeded by the new GNU Arm Embedded one (https://developer.arm.com/open-source/gnu-toolchain/gnu-rm). This also means a change of name from "GCC" to "GNU". Reflect this in the enviroment variables so that the proper term is used henceforth. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> 2018-08-03 23:11:23 +08:00			`- gnuarmemb`
boards: Add "ram" and "flash" properties for a number of boards Currently, it seems that only boards with smaller amount of RAM get a value for "ram" property, and very few boards have "flash" defined. However, to test bigger sample applications, it's helpful to have these properties universally defined. Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org> 2018-03-14 05:40:40 +08:00			`ram: 64`
			`flash: 256`