Searched refs:targets (Results 76 – 100 of 207) sorted by relevance
123456789
| /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/doc/hardware/arch/ |
| D | semihost.rst | 9 Semihosting is a mechanism that enables code running on ARM and RISC-V targets
|
| /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:
|
| /Zephyr-latest/tests/subsys/llext/ |
| D | CMakeLists.txt | 50 # generate extension targets for each extension in 'ext_names'
|
| /Zephyr-latest/boards/native/doc/ |
| D | arch_soc.rst | 56 To build for the 32bit targets you must have the 32-bit C library installed in your system
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.
|
| 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
|
| /Zephyr-latest/doc/ |
| D | CMakeLists.txt | 84 # The function will create two targets for the doc build system.
88 # Both targets will produce same result, but target 2 must have no dependencies.
|
| /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/scripts/west_commands/ |
| D | run_common.py | 301 targets = []
305 targets.append('([^/]+)/' + target)
307 targets = group[group_type]
309 used_cmds.append(UsedFlashCommand(cmd, targets, data['runners'], run_first))
|
| /Zephyr-latest/drivers/i3c/ |
| D | i3c_stm32.c | 982 (payload->targets.payloads == NULL || payload->targets.num_targets == 0)) { in i3c_stm32_do_ccc()
1007 data->ccc_target_payload = payload->targets.payloads; in i3c_stm32_do_ccc()
1011 for (size_t i = 0; i < payload->targets.num_targets; i++) { in i3c_stm32_do_ccc()
1012 payload->targets.payloads[i].num_xfer = 0; in i3c_stm32_do_ccc()
1740 if (data->ccc_target_idx < payload->targets.num_targets) { in i3c_stm32_event_isr_cf()
1741 target = &payload->targets.payloads[data->ccc_target_idx++]; in i3c_stm32_event_isr_cf()
1747 (data->ccc_target_idx == payload->targets.num_targets) in i3c_stm32_event_isr_cf()
|
| /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/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/sca/polyspace/ |
| D | sca.cmake | 84 # mandatory targets #
|
| /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/samples/subsys/shell/shell_module/ |
| D | README.rst | 54 The sample may run on emulation targets. The following commands build the
|
| /Zephyr-latest/arch/common/ |
| D | Kconfig | 7 bool "Semihosting support for ARM and RISC-V targets"
|
| /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/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 | 11 functions on board targets that don't already have one.
|
| /Zephyr-latest/boards/wiznet/w5500_evb_pico/doc/ |
| D | index.rst | 160 … 'transport select swd' -f target/rp2040.cfg -c "adapter speed 2000" -c 'targets rp2040.core0' -c …
207 …fg -c 'transport select swd' -f target/rp2040.cfg -c "adapter speed 2000" -c 'targets rp2040.core0'
|
| /Zephyr-latest/cmake/modules/ |
| D | FindTargetTools.cmake | 81 # Custom targets for compiler and linker flags.
|
123456789
