Searched full:natively (Results 1 – 25 of 33) sorted by relevance
12
/Zephyr-latest/boards/native/nrf_bsim/ |
D | Kconfig | 12 Will produce a console Linux process which can be executed natively. 23 Will produce a console Linux process which can be executed natively. 34 Will produce a console Linux process which can be executed natively. 45 Will produce a console Linux process which can be executed natively.
|
/Zephyr-latest/boards/native/native_posix/ |
D | Kconfig | 12 Will produce a console Linux process which can be executed natively.
|
/Zephyr-latest/drivers/i3c/ |
D | Kconfig | 154 natively the submissions are converted back to struct i3c_msg values that 160 an issue where you are using RTIO, your driver does not implement submit natively,
|
/Zephyr-latest/samples/bluetooth/ |
D | bluetooth.rst | 14 then be used with any external Host (including Zephyr running natively or with
|
/Zephyr-latest/dts/bindings/mipi-dbi/ |
D | renesas,smartbond-mipi-dbi.yaml | 54 support read functionality, natively.
|
/Zephyr-latest/boards/native/native_sim/ |
D | Kconfig | 13 Will produce a console Linux process which can be executed natively.
|
/Zephyr-latest/doc/develop/getting_started/ |
D | installation_win.rst | 12 built-in functionality to natively run Ubuntu binaries directly on a standard
|
/Zephyr-latest/subsys/testsuite/ |
D | Kconfig | 53 Build natively with the compiler standard `--coverage` options, 61 Build natively with the compiler source based coverage options.
|
/Zephyr-latest/doc/develop/sca/ |
D | index.rst | 59 The following is a list of SCA tools natively supported by Zephyr build system.
|
/Zephyr-latest/drivers/i2c/ |
D | Kconfig | 105 natively the submissions are converted back to struct i2c_msg values that 111 an issue where you are using RTIO, your driver does not implement submit natively,
|
/Zephyr-latest/boards/native/nrf_bsim/doc/ |
D | nrf54l15bsim.rst | 20 run applications natively on the development system. This has the benefit of
|
D | nrf5340bsim.rst | 20 run applications natively on the development system. This has the benefit of
|
D | nrf52_bsim.rst | 20 run applications natively on the development system. This has the benefit of
|
/Zephyr-latest/doc/develop/languages/c/ |
D | index.rst | 9 Zephyr is primarily written in C and natively supports applications written in
|
/Zephyr-latest/dts/bindings/mspi/ |
D | mspi-device.yaml | 59 MSPI controller may natively support multiple peripheral devices
|
/Zephyr-latest/doc/develop/ |
D | beyond-GSG.rst | 64 and tools used for developing software that runs natively on your host 304 Run a Sample Application natively (Linux)
|
/Zephyr-latest/doc/connectivity/bluetooth/ |
D | bluetooth-dev.rst | 146 * The POSIX arch and native simulator to emulate the processor, and run natively on your host.
|
/Zephyr-latest/samples/modules/thrift/hello/ |
D | README.rst | 85 client in the QEMU environment, and the peer is built and run natively on
|
/Zephyr-latest/arch/arm/core/ |
D | Kconfig | 142 When an additional natively-compiled language support is added
|
/Zephyr-latest/boards/native/doc/ |
D | arch_soc.rst | 83 These limitations are due to the code executing natively in 420 When using this architecture, the code is compiled natively for the host system,
|
D | bsim_boards_design.rst | 22 and execute the embedded code natively on Linux.
|
/Zephyr-latest/doc/services/rtio/ |
D | index.rst | 218 To check if your bus supports RTIO natively, you can check the driver API implementation, if the
|
/Zephyr-latest/arch/x86/core/ia32/ |
D | crt0.S | 308 * Physical start address = 0. When executing natively, this
|
/Zephyr-latest/doc/kernel/services/ |
D | interrupts.rst | 65 A hardware platform can support more interrupt lines than natively-provided 537 enabled. This data structure is used natively by the CPU and is simply an
|
/Zephyr-latest/subsys/bluetooth/controller/ |
D | Kconfig | 322 Only values supported natively by the SoC are available.
|
12