Searched refs:some (Results 151 – 175 of 591) sorted by relevance
12345678910>>...24
| /Zephyr-latest/doc/services/tfm/ |
| D | requirements.rst | 4 The following are some of the boards that can be used with TF-M:
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | designware_arc_mwdt.rst | 14 objcopy might be used for some steps like device tree preprocessing and ``.bin`` file
|
| /Zephyr-latest/subsys/usb/device/class/dfu/ |
| D | Kconfig | 63 Make sure there is some kind of recovery mechanism.
|
| /Zephyr-latest/doc/services/retention/ |
| D | index.rst | 11 power failure (or during some low-power modes on some devices) nor should it be
31 you are using, there is a zephyr driver which can be used which will use some
|
| /Zephyr-latest/drivers/i3c/ |
| D | Kconfig | 109 initializing those devices. This is because some devices
155 are given to i3c_transfer. This requires some number of msgs be available to convert
|
| /Zephyr-latest/samples/userspace/prod_consumer/ |
| D | README.rst | 9 Consider a "sample driver" which gets incoming data from some unknown source
11 to perform some processing on this data and then write the processed data
|
| /Zephyr-latest/samples/ |
| D | sample_definition_and_criteria.rst | 28 expected value to have some level of testing for the sample itself.
35 buildability and, in some cases, if a sample is performing as expected, i.e. you
|
| /Zephyr-latest/samples/subsys/llext/edk/ |
| D | README.rst | 26 providing some level of isolation - although the kernel one still has access
57 Copy the EDK to some place and extract it:
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | fatal.rst | 16 Zephyr provides some macros to perform runtime assertions which may be
61 If at runtime ``foo`` had some unexpected value, the error produced may
82 It makes use of the ``__ASSERT()`` macro, but has some extra flexibility. It
203 caught. :kconfig:option:`CONFIG_HW_STACK_PROTECTION` is supported on some
|
| /Zephyr-latest/cmake/compiler/arcmwdt/ |
| D | target.cmake | 39 # The MWDT compiler can replace some code with call to builtin functions.
|
| /Zephyr-latest/boards/native/native_sim/ |
| D | Kconfig | 39 interact with some other driver/device which runs at real time.
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 70 debugging why some object was unexpectedly not being tracked. This
127 * A type field indicating what kind of object this is, which is some
213 must have :c:func:`k_object_init` called on it at some point by a supervisor
216 are embedded within some larger struct and initialized statically.
239 to define some new kernel object types. There are different steps needed
|
| /Zephyr-latest/doc/develop/west/ |
| D | built-in.rst | 6 This page describes west's built-in commands, some of which were introduced in
141 However, if you had added some local commits onto a previously detached
143 behind some commits which are no longer referred to by any branch. These
144 may be garbage-collected and lost at some point in the future. To avoid
272 This is because some Git servers have historically not allowed fetching
|
| /Zephyr-latest/doc/build/dts/ |
| D | phandles.rst | 48 is related to ``node-a`` in some way.
50 One common example is when ``node-a`` represents some hardware that
93 "owned" by some other node.
193 specifier spaces before moving on to some information about devicetree
213 phandles followed by some number of cells:
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | index.rst | 51 Next, you'll install some host dependencies using your package manager.
194 as some required Python dependencies may be difficult to install.
537 Here are some next steps for exploring Zephyr:
552 Here are some tips for fixing some issues related to the installation process.
601 developers; some are major Zephyr contributors. `Accessibility`_ has been
|
| /Zephyr-latest/subsys/fs/zms/ |
| D | Kconfig | 56 For some memory technologies, write cycles for memory cells are limited and any
|
| /Zephyr-latest/scripts/coccinelle/ |
| D | mini_lock.cocci | 5 /// supposed to exit with the lock held, or where there is some preceding
|
| /Zephyr-latest/soc/espressif/common/ |
| D | Kconfig | 13 ESP32 SoC has multiple revisions, some of which are not supported by the current
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | bap_scan_delegator.rst | 5 in the examples below, some lines of debug have been
|
| /Zephyr-latest/doc/develop/languages/c/ |
| D | common_libc.rst | 6 Zephyr provides some C library functions that are designed to be used in
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | i2c.rst | 21 given SoC will generally support the controller role, and some will also
|
| /Zephyr-latest/boards/vngiotlab/nrf52_vbluno52/doc/ |
| D | index.rst | 91 Here are some sample applications that you can use to test different
|
| /Zephyr-latest/doc/services/dsp/ |
| D | index.rst | 39 If your application requires some additional customization, it's possible to
|
| /Zephyr-latest/samples/basic/custom_dts_binding/ |
| D | README.rst | 43 For demonstration purposes, some boards use the GPIO pin of the built-in LED.
|
| /Zephyr-latest/samples/boards/intel/adsp/code_relocation/ |
| D | linker_xtensa_intel_adsp_cavs.ld | 25 * script would also place some BSS section on SRAM0, which would break
|
12345678910>>...24
