OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/boards/posix/native_posix/native_posix_64.yaml

22 lines
275 B
YAML
Raw Normal View History

native_posix: introduce a native_posix_64 board configuration Because the only difference between native_posix and native_posix_64 should be 32-bit vs 64-bit compilation, the NATIVE_POSIX menu option is turned into NATIVE_POSIX_32 and the NATIVE_POSIX_64 is added, with both selecting NATIVE_POSIX. This way nothing changes for the existing native_posix target, allowing it to share almost everything with the 64-bit version. Both flavors are made available for CI tests to pick them. This assumes both 32-bit and 64-bit build environments are available. Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
2019-05-18 04:49:52 +08:00
identifier: native_posix_64
name: Native 64-bit POSIX port
type: native
boards: posix: native_posix_64: Add sim: native If one does not specify `simulation: native` in a `testcase.yaml` file, then when trying to run tests with `native_posix_64` as the platform, the `TestInstance.setup_handler` method in `scripts/pylib/twister/twisterlib/testinstance.py` will not assign a handler and one's tests will be marked as ran, but the test output will all be of the form "... No status" since the test binary is built but not ran. Fixes #54605 Signed-off-by: Pete Dietl <petedietl@gmail.com>
2023-02-08 15:48:27 +08:00
simulation: native
native_posix: introduce a native_posix_64 board configuration Because the only difference between native_posix and native_posix_64 should be 32-bit vs 64-bit compilation, the NATIVE_POSIX menu option is turned into NATIVE_POSIX_32 and the NATIVE_POSIX_64 is added, with both selecting NATIVE_POSIX. This way nothing changes for the existing native_posix target, allowing it to share almost everything with the 64-bit version. Both flavors are made available for CI tests to pick them. This assumes both 32-bit and 64-bit build environments are available. Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
2019-05-18 04:49:52 +08:00
arch: posix
boards: posix: native_posix: Add memory sizes for twister This commit adds the missing flash and RAM size properties for native_posix and native_posix_64 so that the integration tests that require large memory can run on this board. Note that the flash and RAM sizes of 64MiB specified here is an arbitrary value choosen to ensure that all currently supported tests can run, since there is no inherent limit for the POSIX boards. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
2021-08-14 13:42:07 +08:00
ram: 65536
flash: 65536
native_posix: introduce a native_posix_64 board configuration Because the only difference between native_posix and native_posix_64 should be 32-bit vs 64-bit compilation, the NATIVE_POSIX menu option is turned into NATIVE_POSIX_32 and the NATIVE_POSIX_64 is added, with both selecting NATIVE_POSIX. This way nothing changes for the existing native_posix target, allowing it to share almost everything with the 64-bit version. Both flavors are made available for CI tests to pick them. This assumes both 32-bit and 64-bit build environments are available. Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
2019-05-18 04:49:52 +08:00
toolchain:
twister: native_posix: Ignor filtering by toolchain for native_posix In the case of native_posix (and other "host" toolchain based platforms) Twister shouldn't filter tests by ZEPHYR_TOOLCHAIN_VARIANT. The PR replaces `- zephyr` with `- host` in native_posix(_64).yaml and modify the filter in twisterlib.py to not block building if "host" is under the platform supported toolchains. Fixes: #38418 Signed-off-by: Maciej Perkowski <Maciej.Perkowski@nordicsemi.no>
2021-09-09 22:16:49 +08:00
- host
native_posix: introduce a native_posix_64 board configuration Because the only difference between native_posix and native_posix_64 should be 32-bit vs 64-bit compilation, the NATIVE_POSIX menu option is turned into NATIVE_POSIX_32 and the NATIVE_POSIX_64 is added, with both selecting NATIVE_POSIX. This way nothing changes for the existing native_posix target, allowing it to share almost everything with the 64-bit version. Both flavors are made available for CI tests to pick them. This assumes both 32-bit and 64-bit build environments are available. Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
2019-05-18 04:49:52 +08:00
- llvm
supported:
board: posix: native_posix: list CAN as a supported feature List CAN as a supported feature on native_posix/native_posix_64. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-02-23 23:32:20 +08:00
- can
drivers: counter native: Add top value conf and multi channel support The counter_native_posix driver currently does not support top value configuration, i.e. `ctr_set_top_value` returns `-ENOTSUP`. This commit adds support for top value configuration, and with the counter API now fully implemented, adds `counter` to `supported` peripherals for native_posix target. It also resolves an existing bug in which the counter ISR did not reset upon reaching `TOP_VALUE`. And adds support for multiple channels Signed-off-by: Jason Wright <jason@jpw.nyc> Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
2023-10-13 10:47:18 +08:00
- counter
boards: posix: add dma support to native_posix boards Like other driver APIs, we can add an `emul` variant to `native_posix` and `native_posix_64` that should allow us to simplify applilcation and library development and to also increase test coverage in CI. Signed-off-by: Christopher Friedt <cfriedt@meta.com>
2023-05-29 00:40:23 +08:00
- dma
boards: native_posix: list eeprom as supported List 'eeprom' as a supported feature for the native_posix and native_posix_64 boards. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2020-03-30 15:36:12 +08:00
- eeprom
native_posix: introduce a native_posix_64 board configuration Because the only difference between native_posix and native_posix_64 should be 32-bit vs 64-bit compilation, the NATIVE_POSIX menu option is turned into NATIVE_POSIX_32 and the NATIVE_POSIX_64 is added, with both selecting NATIVE_POSIX. This way nothing changes for the existing native_posix target, allowing it to share almost everything with the 64-bit version. Both flavors are made available for CI tests to pick them. This assumes both 32-bit and 64-bit build environments are available. Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
2019-05-18 04:49:52 +08:00
- netif:eth
- usb_device
drivers: adc: add ADC emulator ADC emulator is designed to be used in tests on native_posix board. It supports 1-16 bit resolution range and all GAINs from enum adc_gain. Reference voltages and number of emulated channels are set through dts. Using special API from drivers/adc/adc_emul.h it is possible to set constant voltage value returned by given ADC channel or set custom function which allows to simulate complex output. Also reference voltages can be changed in runtime using the API. The CL also includes: - Add adc definitions of ADC emulator in tests/drivers/adc/adc_api/src/test_adc.c for supporting test suites. - Add test for ADC emulator API in tests/drivers/adc/adc_emul/ Signed-off-by: Tomasz Michalec <tm@semihalf.com>
2021-04-15 20:27:34 +08:00
- adc
native_posix: Add gpio to supported list Add gpio to supported list in native_posix boards so that the gpio tests with the gpio_emul will run in twister. Signed-off-by: Jeremy Bettis <jbettis@google.com>
2021-11-11 23:50:14 +08:00
- gpio
tests/drivers/rtc/rtc_api_helpers: Test for more archs The test suite was limited to the native_posix board, now it is built and run for any board supported by CI. The native_posix yaml files for both 32 and 64 bit boards have been expanded to support rtc, allowing CI to build and test the rtc_api test suite against the native_posix and native_posix_64 boards. Signed-off-by: Bjarki Arge Andreasen <baa@trackunit.com>
2023-04-06 01:29:54 +08:00
- rtc
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: zephyr