Searched refs:some (Results 101 – 125 of 591) sorted by relevance
12345678910>>...24
| /Zephyr-latest/doc/services/portability/posix/implementation/ |
| D | index.rst | 32 elsewhere, unless required both by the POSIX API implementation and some other feature. An
41 depends on ``libzfoo`` for the implementation of some functionality "foo" in Zephyr. If
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister_statuses.rst | 35 ``TestCase``, also called Case, is a piece of code that aims to verify some assertion.
47 ``TestInstance``, also called Instance, is a Suite on some platform.
86 - Test was skipped by some other reason than previously delineated.
|
| D | bsim.rst | 9 In the Zephyr project we use the `Babblesim`_ simulator to test some of the Zephyr radio protocols,
10 including the BLE stack, 802.15.4, and some of the networking stack.
56 * Self checking embedded application/tests: In which some of the simulated devices applications are
57 built with some checks which decide if the test is passing or failing. These embedded
156 required, and some Zephyr users do not use or have west, but still use the build and tests scripts.
|
| /Zephyr-latest/doc/develop/ |
| D | env_vars.rst | 122 - adds some Zephyr-specific locations (such as zephyr's :file:`scripts`
156 - adds some Zephyr-specific locations (such as zephyr's :file:`scripts`
169 is a description of some of these important environment variables. This is not
217 You might need to update some of these variables when you
|
| /Zephyr-latest/doc/_doxygen/ |
| D | mainpage.md | 25 There are some imported or reused components of the Zephyr project that
|
| /Zephyr-latest/drivers/dma/ |
| D | Kconfig.mcux_lpc | 26 depending on this value. So, the application can save some data memory
|
| /Zephyr-latest/samples/net/sockets/sntp_client/ |
| D | README.rst | 14 some adjustments to the configuration may be needed. It also assumes
|
| /Zephyr-latest/boards/01space/esp32c3_042_oled/ |
| D | esp32c3_042_oled.dts | 36 /* Have to use uart1 as some tests are hardcoded for that DTS node :/ */
|
| /Zephyr-latest/doc/kernel/services/ |
| D | interrupts.rst | 48 own dedicated stack area (or, on some architectures, stack areas). The size
198 If time consuming processing is required the ISR should offload some or all
221 In the case of some hardware platforms, the same interrupt lines may be used
225 have to either employ some special logic or find a workaround (for example, using
260 IRQ_CONNECT() is not a C function and does some inline assembly magic
289 known at build time, in some cases this may not be acceptable. It is also
312 Regular Zephyr interrupts introduce some overhead which may be unacceptable
313 for some low-latency use-cases. Specifically:
321 * Although some architectures will do this in hardware, other architectures
324 * After the interrupt is serviced, the OS then performs some logic to
[all …]
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | tips.rst | 6 This page covers some Kconfig best practices and explains some Kconfig
41 their value from other symbols), so less restrictions apply to them. If some
47 fixed on some machines and configurable on other machines.
106 This section covers some pitfalls and good uses for ``select``.
235 some condition. Such helper symbols should preferably have no prompt or
280 machine has some arbitrarily-defined "large" amount of memory:
301 In summary, here are some recommended practices for ``select``:
419 The right fix depends on what the intention is. Here's some different scenarios
638 Here are some things to check:
671 :zephyr_file:`scripts/kconfig/lint.py` script to check for some potential
[all …]
|
| D | index.rst | 21 into detail on how Kconfig is used within the Zephyr project, and have some
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig.ns16550 | 67 In some case, e.g. ARC HS Development kit, the peripheral space of ns
96 In some configurations (e.g. edge interrupt triggers),
|
| /Zephyr-latest/doc/hardware/cache/ |
| D | index.rst | 33 :kconfig:option:`CONFIG_DCACHE` symbol and use some HAL exported function in
34 some platform-specific code to enable and manage the d-cache.
|
| /Zephyr-latest/doc/kernel/drivers/ |
| D | index.rst | 48 directly used as a random number generator source as some hardware
96 The device initialization macros populate some data structures at build time
400 In some cases you may just need to run a function at boot. For such cases, the
436 On some systems, the linear address of peripheral memory-mapped I/O (MMIO)
442 the MMIO range must be mapped into the page tables at some virtual
491 /* Write some data to the MMIO region */
503 Some drivers may have multiple MMIO regions. In addition, some drivers
504 may already be implementing a form of inheritance which requires some other
553 /* Write some data to the MMIO regions */
|
| /Zephyr-latest/subsys/logging/ |
| D | CMakeLists.txt | 54 # For some reason, running sys-t with catalog message on
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.nrf_xrtc | 22 System clock source initialization waits until clock is available. In some
|
| /Zephyr-latest/subsys/ |
| D | CMakeLists.txt | 4 # This is because, in some build configurations, the external lorawan module
|
| /Zephyr-latest/doc/templates/ |
| D | sample.tmpl | 21 Fritzing or some other visualisation tools]
|
| /Zephyr-latest/samples/bluetooth/peripheral_accept_list/ |
| D | README.rst | 14 data will only be sent to devices that are on the accept list. As a result, some
|
| /Zephyr-latest/samples/net/sockets/coap_client/ |
| D | README.rst | 14 some adjustments to the configuration may be needed.
|
| /Zephyr-latest/arch/posix/ |
| D | Kconfig | 31 concert with some of CONFIG_ASAN/UBSAN/MSAN for validation.
|
| /Zephyr-latest/arch/x86/core/ |
| D | Kconfig.ia32 | 30 this may conflict with some security scenarios where the GDT is
40 be modified at runtime at the expense of some memory.
161 some stub code to be generated at build time, one stub per dynamic
|
| /Zephyr-latest/doc/develop/west/ |
| D | troubleshooting.rst | 27 …ifest: running 'git fetch ... https://github.com/your-username/your_project ...' in /some/directory
89 This error occurs on some Linux distributions after upgrading to west 0.7.0 or
121 packages, so you may need to do some additional work to get it installed on
214 FATAL ERROR: already in an installation (<some directory>), aborting
|
| /Zephyr-latest/doc/services/crypto/ |
| D | psa_crypto.rst | 103 cannot fail, and thus, return void or some other type.
121 some implementations guarantee that certain functions always have
130 ``psa_crypto_init()``. However, some security standards require
136 others do not. In some environments, applications can share memory
|
| /Zephyr-latest/doc/develop/optimizations/ |
| D | footprint.rst | 57 support to gain some memory and improve performance. Consider the consequences
|
12345678910>>...24
