zephyr/boards/gd/gd32f350r_eval/gd32f350r_eval.yaml

# Copyright (c) 2021 BrainCO Inc.
# SPDX-License-Identifier: Apache-2.0

identifier: gd32f350r_eval
name: GigaDevice GD32F350R Evaluation Kit
type: mcu
arch: arm
ram: 16
flash: 128
toolchain:
  - zephyr
  - gnuarmemb
  - xtools
supported:
  - watchdog
  - dma
vendor: gd
boards: arm: Introduce gd32f350r_eval board Add GD32F350R-EVAL board support on Zephyr. Signed-off-by: HaiLong Yang <cameledyang@pm.me> 2021-11-30 15:38:27 +08:00			`# Copyright (c) 2021 BrainCO Inc.`
			`# SPDX-License-Identifier: Apache-2.0`

			`identifier: gd32f350r_eval`
			`name: GigaDevice GD32F350R Evaluation Kit`
			`type: mcu`
			`arch: arm`
			`ram: 16`
			`flash: 128`
			`toolchain:`
			`- zephyr`
			`- gnuarmemb`
			`- xtools`
boards: Enable watchdog node for boards that implements GD32 SoCs Enable watchdog in each GD32 implemented board. Add the watchdog function as a supported function in each yaml files. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com> 2022-07-27 18:40:40 +08:00			`supported:`
			`- watchdog`
boards: gd32: add `dma` as supported feature Add `dma` as supported feature to yaml configuration. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com> 2022-12-10 18:32:44 +08:00			`- dma`
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-23 02:47:45 +08:00			`vendor: gd`