Searched refs:able (Results 226 – 250 of 306) sorted by relevance
12345678910>>...13
/Zephyr-latest/boards/st/stm32h747i_disco/doc/ |
D | index.rst | 208 Drivers are able to take into account both Option Bytes configurations
|
/Zephyr-latest/boards/st/stm32l562e_dk/doc/ |
D | index.rst | 179 options and get back the platform back to a "normal" state and be able to run
|
/Zephyr-latest/doc/develop/west/ |
D | extensions.rst | 241 able to use it, too.
|
D | zephyr-cmds.rst | 64 able to find the Zephyr repository with the following:
|
D | workspaces.rst | 343 You may be able to make something like this "work" for yourself and your own
|
/Zephyr-latest/subsys/mgmt/mcumgr/grp/img_mgmt/src/ |
D | img_mgmt.c | 48 to be able to figure out application running slot.
|
/Zephyr-latest/drivers/console/ |
D | Kconfig | 98 # Workaround for not being able to have commas in macro arguments
|
/Zephyr-latest/tests/benchmarks/thread_metric/ |
D | thread_metric_readme.txt | 224 This function creates a memory pool able to satisfy at least one
|
/Zephyr-latest/boards/nxp/frdm_mcxn947/doc/ |
D | index.rst | 206 To be able to program the firmware, you need to put the board in ``DFU mode``
|
/Zephyr-latest/doc/security/ |
D | sensor-threat.rst | 13 relays this sensor data to this service. The cloud service is also able 103 certificate to be able to intercept this. [th-time]_
|
/Zephyr-latest/doc/services/rtio/ |
D | index.rst | 180 Finally, the consumer will be able to access the allocated buffer via
|
/Zephyr-latest/doc/kernel/memory_management/ |
D | heap.rst | 107 only be able to perform DMA to certain regions, etc...
|
/Zephyr-latest/doc/hardware/porting/ |
D | arch.rst | 205 Therefore, the context switching must thus be able to handle all these cases. 440 :c:func:`arch_cpu_atomic_idle`, on the other hand, must be able to atomically 670 be able to be placed before it, with support for carve-outs if necessary. 672 * The memory protection hardware must be able to program a region that exactly
|
/Zephyr-latest/doc/connectivity/usb/device/ |
D | usb_device.rst | 472 Also, one controller may be able to have IN/OUT endpoints on the same endpoint 474 may only be able to handle one endpoint per endpoint number. Information about
|
/Zephyr-latest/subsys/bluetooth/controller/ |
D | Kconfig.df | 164 is able to store. For nRF5x-based controllers, the hardware imposes
|
/Zephyr-latest/boards/st/b_u585i_iot02a/doc/ |
D | index.rst | 192 options and get back the platform back to a "normal" state and be able to run
|
/Zephyr-latest/boards/nordic/nrf52840dongle/doc/ |
D | index.rst | 268 You should now be able to scan for Bluetooth devices using a smartphone or
|
/Zephyr-latest/samples/net/sockets/dumb_http_server_mt/src/ |
D | response_100k.html.bin | 31 … Zephyr OS is modular and supports multiple architectures, developers are able to easily tailor an…
|
/Zephyr-latest/subsys/bluetooth/host/ |
D | Kconfig | 621 The Resolve List on a Controller is not able to accommodate multiple 663 With this option enabled, the application will be able to call the 726 With this option enabled, the application will be able to perform LESC
|
/Zephyr-latest/doc/connectivity/bluetooth/ |
D | bluetooth-tools.rst | 180 is very useful to be able to see the full log of exchanges between the two,
|
D | bluetooth-le-host.rst | 94 non-connectable, i.e. other device will not be able to connect to it.
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | sar_cfg.rst | 25 The transport layer is able to transport up to 32 segments with its SAR mechanism, with a maximum
|
/Zephyr-latest/doc/build/dts/ |
D | phandles.rst | 248 Without the ``#baz-cells`` property, the devicetree tooling would not be able
|
/Zephyr-latest/doc/kernel/usermode/ |
D | kernelobjects.rst | 176 untrusted or exploited code will then be able to access the object. Use
|
/Zephyr-latest/doc/develop/api/ |
D | api_lifecycle.rst | 8 maintaining and extending Zephyr's APIs need to be able to introduce
|
12345678910>>...13