Home
last modified time | relevance | path

Searched refs:targets (Results 126 – 150 of 203) sorted by relevance

123456789

/Zephyr-latest/doc/develop/debug/
Dindex.rst332 By default, all I2C communication is logged between all I2C controllers and I2C targets.
337 allowlist of I2C targets to log.
/Zephyr-latest/doc/releases/
Drelease-notes-1.11.rst51 * New POSIX architecture for native GNU/Linux and macOS build targets:
250 * :github:`3546` - Enabling networking for targets w/o network hw causes hang on boot
429 * :github:`5853` - Using newlibc in a project breaks 'rom_report' and 'ram_report' targets.
430 * :github:`5866` - ram_report not working for qemu targets
Drelease-notes-3.6.rst210 * The :ref:`simulated nrf5340 targets<nrf5340bsim>` now include the IPC and MUTEX peripherals,
215 * The nrf*_bsim simulated targets now include models of the UART peripheral. It is now possible
219 * For the native simulator based targets it is now possible to set via Kconfig command line
277 globally when building with Picolibc or for the native (``ARCH_POSIX``) targets.
357 * The nRFx counter driver now works with simulated nrf*_bsim targets.
1310 now run in CI based on the :ref:`nrf5340_bsim<nrf5340bsim>` targets.
1311 Several other runtime AMP tests based on these targets have been added to CI, including tests
/Zephyr-latest/cmake/modules/
Dextensions.cmake698 # dependency between the two targets
711 # targets
730 # from the build system. The Zephyr build system has targets for
2516 # C++ property targets used for toolchain abstraction.
2520 # compiler-cpp targets.
2544 # before setting the property on compiler or compiler-cpp targets.
3555 # zephyr_get_targets(<directory> <types> <targets>)
3557 # Get build targets for a given directory and sub-directories.
3564 # returns a list of targets in <targets> matching the required <types>.
3565 function(zephyr_get_targets directory types targets)
[all …]
Dkernel.cmake121 # all targets exports their compile commands to fetch object files.
/Zephyr-latest/boards/u-blox/ubx_evkninab4/doc/
Dindex.rst114 debugging targets are not currently available.
/Zephyr-latest/samples/bluetooth/hci_uart_3wire/
DREADME.rst141 You can use following targets:
/Zephyr-latest/boards/nxp/lpcxpresso55s16/doc/
Dindex.rst85 Currently available targets for this board are:
/Zephyr-latest/doc/hardware/porting/
Dshields.rst63 shields (and/or targets) shall not be captured here.
/Zephyr-latest/boards/u-blox/ubx_evkninab3/doc/
Dindex.rst215 debugging targets are not currently available.
/Zephyr-latest/doc/services/tfm/
Dbuild.rst140 The build system offers targets to view and analyse RAM and ROM usage in generated images.
/Zephyr-latest/samples/bluetooth/hci_uart/
DREADME.rst141 You can use following targets:
/Zephyr-latest/doc/develop/tools/
Dclion.rst112 Note that other CMake targets like ``puncover`` or ``hardenconfig`` can also be called at this
/Zephyr-latest/boards/enjoydigital/litex_vexriscv/doc/
Dindex.rst142 … ./litex-boards/litex_boards/targets/digilent_arty.py --build --timer-uptime --csr-json csr.json
/Zephyr-latest/boards/nxp/lpcxpresso55s36/doc/
Dindex.rst80 Currently available targets for this board are:
/Zephyr-latest/boards/native/native_sim/doc/
Dindex.rst159 native_sim comes with two targets: A 32 bit and 64 bit version.
163 This mimics the ABI of most embedded systems Zephyr targets,
450 The EEPROM simulator can also be used in the native targets. In these, you have the added feature
457 The flash simulator can also be used in the native targets. In this you have the option to keep
/Zephyr-latest/arch/xtensa/
DKconfig252 # Need to verify functionalities with targets supporting these.
/Zephyr-latest/boards/native/nrf_bsim/doc/
Dnrf52_bsim.rst42 and will use the same drivers as the nrf52 dk targets for these.
/Zephyr-latest/subsys/bluetooth/mesh/
Ddfu_cli.c22 (sys_slist_t *)&((cli)->blob.inputs)->targets, target, blob.n)
358 (sys_slist_t *)&((cli)->blob.inputs)->targets, in send_update_start()
/Zephyr-latest/drivers/i3c/
Di3c_mcux.c1411 for (int idx = 0; idx < payload->targets.num_targets; idx++) { in mcux_i3c_do_ccc()
1413 &payload->targets.payloads[idx]; in mcux_i3c_do_ccc()
/Zephyr-latest/boards/arm/mps2/doc/
Dmps2_an521.rst91 This memory map enables the two alternative board targets to be used together
95 When using one of the alternative board targets (``mps2/an521/cpu0/ns`` or
/Zephyr-latest/boards/nxp/imx8mm_evk/doc/
Dindex.rst109 CPU's UART4. This is used for the M4 and A53 core targets.
/Zephyr-latest/
DKconfig.zephyr86 This option is selected by targets having a FLASH_LOAD_OFFSET
142 alignment requirements on most ARM targets, although some targets
227 This option is selected by targets that require SRAM_OFFSET.
/Zephyr-latest/doc/develop/flash_debug/
Dnordic_segger.rst158 and the development computer for logging and input. Zephyr supports RTT on nRF5x targets,
/Zephyr-latest/boards/u-blox/ubx_bmd340eval/doc/
Dindex.rst399 for more details); however, the standard debugging targets

123456789