| /Zephyr-latest/boards/silabs/radio_boards/ |
| D | index.rst | 31 In Zephyr, Radio Boards are used as board targets, irrespective of whether the
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.dwmac | 18 currently available on targets using the STM32H7X series as an
|
| /Zephyr-latest/samples/tfm_integration/ |
| D | tfm_integration.rst | 35 The current TF-M implementation specifically targets TrustZone for ARMv8-M.
|
| /Zephyr-latest/doc/develop/west/ |
| D | alias.rst | 44 call ``west build`` with the corresponding CMake targets:
|
| D | zephyr-cmds.rst | 121 CMake build targets, build targets that are linked together, and
|
| /Zephyr-latest/drivers/i3c/ |
| D | i3c_cdns.c | 1359 1 + ((payload->ccc.data_len > 0) ? payload->targets.num_targets in cdns_i3c_do_ccc()
1360 : MAX(payload->targets.num_targets - 1, 0)); in cdns_i3c_do_ccc()
1371 for (int i = 0; i < payload->targets.num_targets; i++) { in cdns_i3c_do_ccc()
1372 if (payload->targets.payloads[i].rnw) { in cdns_i3c_do_ccc()
1373 rxsize += ROUND_UP(payload->targets.payloads[i].data_len, 4); in cdns_i3c_do_ccc()
1375 txsize += ROUND_UP(payload->targets.payloads[i].data_len, 4); in cdns_i3c_do_ccc()
1398 for (int i = 0; i < payload->targets.num_targets; i++) { in cdns_i3c_do_ccc()
1429 if (i < (payload->targets.num_targets - 1)) { in cdns_i3c_do_ccc()
1432 cmd->buf = payload->targets.payloads[i].data; in cdns_i3c_do_ccc()
1433 cmd->len = payload->targets.payloads[i].data_len; in cdns_i3c_do_ccc()
[all …]
|
| D | i3c_stm32.c | 981 (payload->targets.payloads == NULL || payload->targets.num_targets == 0)) { in i3c_stm32_do_ccc()
1006 data->ccc_target_payload = payload->targets.payloads; in i3c_stm32_do_ccc()
1010 for (size_t i = 0; i < payload->targets.num_targets; i++) { in i3c_stm32_do_ccc()
1011 payload->targets.payloads[i].num_xfer = 0; in i3c_stm32_do_ccc()
1736 if (data->ccc_target_idx < payload->targets.num_targets) { in i3c_stm32_event_isr_cf()
1737 target = &payload->targets.payloads[data->ccc_target_idx++]; in i3c_stm32_event_isr_cf()
1743 (data->ccc_target_idx == payload->targets.num_targets) in i3c_stm32_event_isr_cf()
|
| /Zephyr-latest/boards/st/stm32l1_disco/doc/ |
| D | index.rst | 16 - STM32LDISCOVERY targets STM32L152RBT6, with 128K flash, 16K RAM, 4K EEPROM
17 - STM32L152CDISCOVERY targets STM32L152RCT6, with 256K flash, 32K RAM, 8K EEPROM
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf5340bsim.rst | 24 Just like for the nrf5340dk targets,
49 and will use the same drivers as the nrf5340dk targets for these.
|
| D | nrf54l15bsim.rst | 58 and will use the same drivers as the nrf54l15dk targets for these.
|
| /Zephyr-latest/boards/native/doc/ |
| D | bsim_boards_design.rst | 132 nrf_bsim targets, you are using the `native simulator`_, which is being built together with and
302 targets.
335 Note also that, for AMP targets like the :ref:`nrf5340bsim <nrf5340bsim>`, each embedded MCU has
367 - WordSize: The bsim targets, as well as normal embedded targets are 32 bit
368 targets. In the case of the bsim targets this is done by explicitly targeting
|
| D | arch_soc.rst | 179 * :ref:`User mode/userspace <usermode_api>`: When building for these targets,
227 is to meet the targets described in the previous `Rationale for this port`_
232 :alt: Comparison of different debugging targets
311 It only describes the new native simulator based architecture used by targets built with the
356 The native_sim target is a single microcontroller (MCU) target with simple HW models. Other targets
357 like the :ref:`simulated nRF5340 (nrf5340bsim)<nrf5340bsim>` are multi MCU targets. Where one
452 Note that the SOC/board split in this architecture is different than for other Zephyr targets.
|
| /Zephyr-latest/tests/bsim/bluetooth/ll/edtt/ |
| D | README.txt | 25 driver for simulated targets, meant to connect to the `bsim` EDTT transport
|
| /Zephyr-latest/boards/snps/nsim/arc_classic/doc/ |
| D | index.rst | 87 there might be exceptions from that, especially for newly added targets. You can check supported
163 * Allows to debug both single-core and multi-core ``nsim`` targets.
232 It's the nSIM with ARC GDB restriction, real HW multi-core ARC targets can be debugged with ARC
254 * for the ARCv2 targets you should use :file:`arc-zephyr-elf-gdb`
255 * for the ARCv3 targets you should use :file:`arc64-zephyr-elf-gdb`
|
| /Zephyr-latest/cmake/compiler/clang/ |
| D | compiler_flags.cmake | 13 # No property flag, this is used by the POSIX arch based targets when building with the host libC,
|
| /Zephyr-latest/samples/subsys/shell/shell_module/ |
| D | README.rst | 54 The sample may run on emulation targets. The following commands build the
|
| /Zephyr-latest/boards/norik/octopus_som/doc/ |
| D | index.rst | 35 The ``octopus_som/nrf9160`` and ``octopus_som/nrf9160/ns`` board targets support the
|
| /Zephyr-latest/tests/drivers/i2c/i2c_emul/src/ |
| D | test_forwarding_pio.cpp | 19 constexpr const struct device *targets[FORWARD_COUNT] = { variable
|
| /Zephyr-latest/doc/develop/optimizations/ |
| D | tools.rst | 7 and :ref:`data_structure_tools` using different build system targets.
14 The build system offers 3 targets to view and analyse RAM, ROM and stack usage
|
| /Zephyr-latest/cmake/modules/ |
| D | snippets.cmake | 27 # The following targets will be defined when this CMake module completes:
|
| D | FindTargetTools.cmake | 81 # Custom targets for compiler and linker flags.
|
| /Zephyr-latest/boards/digilent/arty_a7/doc/ |
| D | index.rst | 33 targets either the Spartan-7 or Artix-7 based Arty boards, whereas the Cortex-M3
34 design only targets the Artix-7 based boards. Zephyr only supports the Artix-7
|
| /Zephyr-latest/subsys/secure_storage/ |
| D | Kconfig | 10 functions on board targets that don't already have one.
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arc-support-status.rst | 91 .. [#f5] Single-thread kernel is support only for single core targets
|
| /Zephyr-latest/samples/subsys/fs/littlefs/ |
| D | README.rst | 72 partition. Two tested board targets are described below.
|
