zephyr/boards/posix/nrf52_bsim/nrf52_bsim.yaml

identifier: nrf52_bsim
name: NRF52 BabbleSim board
type: native
arch: posix
simulation: native
env:
  - BSIM_OUT_PATH
toolchain:
  - zephyr
testing:
  ignore_tags:
    - modem
    - uart
supported:
  - gpio
new simulated board: nrf52_bsim Added a new simulated board, which models the NRF52832 SOC. Its main use is for workstation testing and simulation of the BLE stack and any application which relies mostly on it. It uses BabbleSim (http://Babblesim.github.io) for the radio simulation. And the NRF52 HW models hosted in that same GitHub organization: https://github.com/BabbleSim/ext_NRF52_hw_models For speed it uses the POSIX arch to (not) emulate the CPU. It uses Vanilla Zephyr, with a couple of configuration differences: * It uses (like other POSIX arch boards) the system libC * It does not use the nrfx hosted by Zehpyr in ext/, but the one provided by the HW models. Otherwise it relies in the same drivers as the real NRF52 boards. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> 2018-09-14 22:20:11 +08:00			`identifier: nrf52_bsim`
			`name: NRF52 BabbleSim board`
			`type: native`
			`arch: posix`
boards: native: mark as simulator Mark native_posix platform as a simulator. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2022-11-22 03:02:21 +08:00			`simulation: native`
nrf52_bsim: declare BSIM_OUT_PATH as required env var Do not use with sanitycheck if BSIM_OUT_PATH is not defined. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2018-10-19 00:24:25 +08:00			`env:`
			`- BSIM_OUT_PATH`
new simulated board: nrf52_bsim Added a new simulated board, which models the NRF52832 SOC. Its main use is for workstation testing and simulation of the BLE stack and any application which relies mostly on it. It uses BabbleSim (http://Babblesim.github.io) for the radio simulation. And the NRF52 HW models hosted in that same GitHub organization: https://github.com/BabbleSim/ext_NRF52_hw_models For speed it uses the POSIX arch to (not) emulate the CPU. It uses Vanilla Zephyr, with a couple of configuration differences: * It uses (like other POSIX arch boards) the system libC * It does not use the nrfx hosted by Zehpyr in ext/, but the one provided by the HW models. Otherwise it relies in the same drivers as the real NRF52 boards. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> 2018-09-14 22:20:11 +08:00			`toolchain:`
			`- zephyr`
			`testing:`
			`ignore_tags:`
nrf52_bsim: twister yaml: Reduce filtering Two parts: 1) The nrf52_bsim has had an overall driver filter since the begining. But nowadays it supports most of the nrf drivers, so it can be used to run these drives' tests. It is actually the only platform which allows running these drivers in CI without HW (for ex. upstream). Instead of filtering all drivers, filter only the drivers which cannot yet be used in this board. 2) This platform is not a good target to test the modem drivers, as will not be able to run those until somebody would want to include models of their respective HW, for which there is currently no intention. Build only tests are better suited in native_posix. Moreover, most of those will fail to build due to their use of either a GPIO or UART which are not yet supported in this board. Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no> 2023-05-01 16:27:52 +08:00			`- modem`
			`- uart`
nrf52_bsim: test filter: Remove GPIO filter The HW models now also support the GPIO. Let's stop filtering it out, and instead explicitly claim we support it. Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no> 2023-06-29 18:55:17 +08:00			`supported:`
			`- gpio`