Home
last modified time | relevance | path

Searched refs:sure (Results 326 – 350 of 371) sorted by relevance

1...<<1112131415

/Zephyr-latest/drivers/wifi/esp32/
DKconfig.esp3228 Make sure there is a minimal heap available for Wi-Fi driver.
/Zephyr-latest/doc/services/tfm/
Doverview.rst191 not be in the HW-default reset state. In case of doubts, be sure to consult
/Zephyr-latest/doc/connectivity/networking/
Dnet_config_guide.rst130 Make sure that this value is high enough so that all the
/Zephyr-latest/boards/ezurio/bt610/doc/
Dbt610.rst554 You can build and flash the examples to make sure Zephyr is running correctly
/Zephyr-latest/
DCMakeLists.txt552 # sure the order of dependencies are met
819 # Make sure Picolibc is built before the rest of the system; there's no explicit
960 # Make sure that LTO will never be enabled when compiling offsets.c
2100 # database, add the generation to post build command to make sure
/Zephyr-latest/samples/tfm_integration/psa_crypto/
DREADME.rst181 Make sure your board is set up with :ref:`lpclink2-jlink-onboard-debug-probe`,
/Zephyr-latest/doc/services/llext/
Ddebug.rst21 1. Make sure the project is set up to display the verbose LLEXT debug output
/Zephyr-latest/arch/arm/core/cortex_m/
DKconfig366 sure the vector table pointer in RAM is set properly by the image upon
/Zephyr-latest/doc/build/kconfig/
Dtips.rst307 Rare exceptions might include cases where you're sure that the dependencies
466 interface, to make sure that things behave the way you expect. This is
/Zephyr-latest/subsys/bluetooth/common/
DKconfig378 Make sure the buffer number is not used by other logger,
/Zephyr-latest/boards/snps/nsim/arc_classic/doc/
Dindex.rst50 (especially after creation of a new board or modification of the existing one) make sure features
/Zephyr-latest/boards/phytec/reel_board/doc/
Dindex.rst549 You can build and flash the examples to make sure Zephyr is running correctly on
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/
Dbap.rst329 Use command :code:`gatt exchange-mtu` to make sure the MTU is configured
/Zephyr-latest/doc/build/dts/
Dintro-syntax-structure.rst222 make sure it gets linked to from gen_devicetree_rest.py too.
Dbindings-syntax.rst743 in the included files are ORed together. This makes sure that a ``required:
/Zephyr-latest/soc/espressif/esp32s3/
Ddefault_appcpu.ld53 /* Make sure new sections have consistent alignment between input and output sections */
Ddefault.ld61 /* Make sure new sections have consistent alignment between input and output sections */
/Zephyr-latest/boards/espressif/esp_wrover_kit/doc/
Dindex.rst420 Before powering up your ESP-WROVER-KIT, please make sure that the board is in good
/Zephyr-latest/soc/espressif/esp32c2/
Ddefault.ld50 /* Make sure new sections have consistent alignment between input and output sections */
/Zephyr-latest/soc/espressif/esp32c3/
Ddefault.ld50 /* Make sure new sections have consistent alignment between input and output sections */
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Ddfu.rst350 each Target node, and scans through the list to make sure that the new firmware ID has replaced
/Zephyr-latest/soc/espressif/esp32c6/
Ddefault.ld44 /* Make sure new sections have consistent alignment between input and output sections */
/Zephyr-latest/doc/develop/
Dmodules.rst1125 If you choose this option, make sure to set the variable **before** calling
1161 request to make sure it is not merged by mistake and to allow for the module to
/Zephyr-latest/soc/espressif/esp32/
Ddefault.ld56 /* Make sure new sections have consistent alignment between input and output sections */
/Zephyr-latest/soc/espressif/esp32s2/
Ddefault.ld61 /* Make sure new sections have consistent alignment between input and output sections */

1...<<1112131415