zephyr/boards/st/stm32f4_disco/stm32f4_disco.yaml

identifier: stm32f4_disco
name: ST STM32F4 Discovery
type: mcu
arch: arm
toolchain:
  - zephyr
  - gnuarmemb
  - xtools
ram: 128
flash: 1024
supported:
  - can
  - pwm
  - counter
  - usb
vendor: st
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 05:08:59 +02:00			`identifier: stm32f4_disco`
boards: stm32: Fix boards names in yaml and/or doc files For auto doc generation purpose, get name value of boards' yaml files in sync with name provided as board name in .rst file Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org> 2020-05-04 17:05:27 +02:00			`name: ST STM32F4 Discovery`
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 05:08:59 +02: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 17:11:23 +02:00			`- gnuarmemb`
boards: arm: Add xtools as a supported toolchain Update all ARM boards to have xtools as a supported toolchain. Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2019-01-09 17:25:16 +01:00			`- xtools`
boards: stm32f4_disco: Fix yaml ram size Total RAM is 192, including 64K CCM. Signed-off-by: Kwon Tae-young <tykwon@m2i.co.kr> 2019-04-19 05:09:06 +02:00			`ram: 128`
boards: stm32: Enable CCM and update yaml Following fix SRAM size to take into account CCM, enable CCM and update yaml files in boards including fixed soc dtsi definitions. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org> 2019-03-25 11:40:24 +01:00			`flash: 1024`
boards: add supported features Update board definitions with supported feature. This is temporary until we have full coverage for device drivers in DTS, then we can use DTS instead. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-12-08 16:24:28 +01:00			`supported:`
boards: stm32f4_disco: enable canbus Define CAN_1 and CAN_2 canbus controllers and enable CAN_2 in the ST STM32F4 Disco development board. Signed-off-by: Ivo Clarysse <ivo@bcdevices.com> 2020-01-25 16:30:15 +01:00			`- can`
boards: add supported features Update board definitions with supported feature. This is temporary until we have full coverage for device drivers in DTS, then we can use DTS instead. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-12-08 16:24:28 +01:00			`- pwm`
boards: Update yaml for boards supporting rtc/counter (2/3) Few boards supporting RTC were missing rtc as supported rtc feature in yaml files. Fix this. Add counter to all boards supporting rtc as RTC IP now support both rtc and counter API. Change split in 3 parts in order to lower CI load and get shippable happy. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org> 2019-02-07 09:00:01 +01:00			`- counter`
boards: add usb to stm32f4_disco This patch adds USB capabilities to the stm32f4 discovery board. As the board has a MicroUSB port that I would like to use as stdout I just added USB. The needed entry within pinmux.c is already there but USB was missing in the dts file and documentation. I tested it with the upcomming commit. Signed-off-by: Alexander Polleti <metapsycholo@gmail.com> 2018-08-28 17:21:50 +02:00			`- usb`
boards: add vendor to board yaml This is coming from devicetree and corrosponds to what we have in the dts/bindings/vendor-prefixes.txt file. This will allow for static filtering, especially with twister, i.e. no need to build anything to know the vendor of a board All of the vendor data was extracted automatically from the devicetree, so some platforms might not have the right vendor or no vendor at all right now, we need to fix some of the DTS information or do this manually to get this 100% correct. But we are close. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2023-06-22 20:47:45 +02:00			`vendor: st`