mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-06 20:06:47 +00:00
91d7ec5a35
mdb runner is quite special as it can be used to run Zephyr on both simulator (nSIM) and real hardware. However it is really misleading as same command (west flash) will run Zephyr in simulation for one board and try to run it on HW for another board. Things are getting worse for boards supporting both runs in simulation and on real hardware. Let's split mdb runner for mdb-hw (for runs on HW) and mdb-nsim (for runs in simulation) runners. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
58 lines
1.1 KiB
YAML
58 lines
1.1 KiB
YAML
#
|
|
# Schema to validate a YAML file describing a Zephyr test platform
|
|
#
|
|
# We load this with pykwalify
|
|
# (http://pykwalify.readthedocs.io/en/unstable/validation-rules.html),
|
|
# a YAML structure validator, to validate the YAML files that describe
|
|
# Zephyr test platforms
|
|
#
|
|
# The original spec comes from Zephyr's sanitycheck script
|
|
#
|
|
|
|
type: map
|
|
mapping:
|
|
"identifier":
|
|
type: str
|
|
"name":
|
|
type: str
|
|
"type":
|
|
type: str
|
|
enum: ["mcu", "qemu", "sim", "unit", "native"]
|
|
"simulation":
|
|
type: str
|
|
enum: ["qemu", "simics", "xt-sim", "renode", "nsim", "mdb-nsim"]
|
|
"arch":
|
|
type: str
|
|
"toolchain":
|
|
type: seq
|
|
seq:
|
|
- type: str
|
|
"env":
|
|
type: seq
|
|
seq:
|
|
- type: str
|
|
"ram":
|
|
type: int
|
|
"flash":
|
|
type: int
|
|
"sanitycheck":
|
|
type: bool
|
|
"supported":
|
|
type: seq
|
|
seq:
|
|
- type: str
|
|
"testing":
|
|
type: map
|
|
mapping:
|
|
"default":
|
|
type: bool
|
|
"only_tags":
|
|
type: seq
|
|
seq:
|
|
-
|
|
type: str
|
|
"ignore_tags":
|
|
type: seq
|
|
seq:
|
|
- type: str
|