Home
last modified time | relevance | path

Searched refs:need (Results 201 – 225 of 733) sorted by relevance

12345678910>>...30

/Zephyr-latest/boards/native/nrf_bsim/
DCMakeLists.txt18 # The nrfx HAL uses enums in its definitions,so they need to have the same size in both,
/Zephyr-latest/tests/ztest/fail/
DCMakeLists.txt26 # Once we find the config, we'll need to prepend a '-D' and append '=y' so we can pass it to the
/Zephyr-latest/samples/sensor/qdec/
DREADME.rst21 In order to run this sample you need to:
/Zephyr-latest/samples/boards/bbc/microbit/sound/
DREADME.rst21 The upgraded **BBC micro:bit v2** board does not need a separate buzzer as it has one
/Zephyr-latest/boards/intel/adsp/doc/
Dchromebooks_adsp.rst45 You will at some point wreck your device and need a recovery stick.
77 Now you need to turn of signature verification in the bootloader
143 won't run on ChromeOS's minimal distro. So we need to install a Linux
146 personality runs inside a VM, where our tools need access to the real
188 NOTE: the mkdir, iptables and sshd commands need to be run every time
220 Now you need a .config file. The Chromebook kernel ships with the
230 You will need to set some custom configuration variables differently
253 required, and you may find you need to regularly prune modules from
/Zephyr-latest/doc/connectivity/networking/api/
Dcapture.rst23 network data when there is no network interface involved, then you need to use
27 does not need to be network interface involved. For example low level HDLC
/Zephyr-latest/doc/build/kconfig/
Dextensions.rst48 no "bounce" symbols with ``option env="ENV_VAR"`` need to be defined.
114 file gets included, so only use it if you need it.
/Zephyr-latest/drivers/dma/
DKconfig.xilinx_axi_dma21 coherency for DMA accesses. If you are unsure whether you need this feature,
40 because transfers need to be started by the upstream driver.
/Zephyr-latest/doc/services/sensing/
Dindex.rst27 Use of the sensing subsystem is optional. Applications that only need to access simple sensors
127 This method is suitable for supporting some up-layer frameworks like ``CHRE``, ``HID`` which need
155 instance, and all subsequent operations on this sensor instance need use this handler,
179 Application(s) need to call :c:func:`sensing_open_sensor` to explicitly open the sensor instance.
/Zephyr-latest/drivers/sensor/nxp/fxas21002/
DKconfig24 should need to change this configuration option from the default.
/Zephyr-latest/boards/sparkfun/red_v_things_plus/doc/
Dindex.rst39 To flash and debug the board, you'll need to install the
/Zephyr-latest/cmake/bintools/arcmwdt/
Delfconvert_command.cmake46 # There could be more than one, so need to check all args.
/Zephyr-latest/cmake/modules/
DFindLlvmLld.cmake57 # own version scheme so we need to account for that.
/Zephyr-latest/drivers/ieee802154/
DKconfig.mcr20a73 might need it too). And of course it has to start before the net stack.
/Zephyr-latest/doc/contribute/style/
Dcode.rst27 * Use ``/** */`` for doxygen comments that need to appear in the documentation.
/Zephyr-latest/include/zephyr/linker/common-rom/
Dcommon-rom-init.ld52 * __zephyr_init_array_end symbols, so these need to be set correctly.
/Zephyr-latest/samples/net/zperf/
DREADME.rst24 - Client or server mode allowed without need to modify the source code.
/Zephyr-latest/doc/kernel/data_structures/
Dindex.rst20 where dynamic allocation is disallowed (i.e. there is no need to
/Zephyr-latest/samples/boards/nordic/nrfx_prs/boards/
Dnrf9160dk_nrf9160.overlay61 * respectively) need to be disabled so that Zephyr drivers won't initialize
/Zephyr-latest/samples/application_development/code_relocation_nocopy/
DREADME.rst13 directly from there without the need to copy / relocate the code. All other code
/Zephyr-latest/boards/snps/em_starterkit/doc/
Dindex.rst135 To run Zephyr application on correct arc core of EM Starter Kit, you need to
155 Since there are different firmware versions of EM Starter Kit, you need to
175 You may need to write a prj_arc.conf file if the sample doesn't have one.
185 On this board you will also need to consider the "ARC SoC Selection" and set
211 On your development environment, you will need to:
/Zephyr-latest/cmake/compiler/armclang/
Dtarget.cmake16 # 'cortex-m33+nodsp' we need that to be 'cortex-m33' for CMAKE_SYSTEM_PROCESSOR
/Zephyr-latest/boards/renode/cortex_r8_virtual/doc/
Dindex.rst28 Your software will run in simulation and you don't need to "flash" the board in a traditional way,
/Zephyr-latest/boards/96boards/nitrogen/
D96b_nitrogen.dts53 /* gpio flags need validation */
/Zephyr-latest/lib/libc/newlib/
DCMakeLists.txt12 # need to hook into the include path before the system files and

12345678910>>...30