Home
last modified time | relevance | path

Searched refs:final (Results 101 – 125 of 142) sorted by relevance

123456

/Zephyr-latest/doc/services/device_mgmt/smp_groups/
Dsmp_group_10.rst287 | "end" | will be set to true if the listed group is the final supported group on |
Dsmp_group_1.rst399 | | hash or not, only sent in the final packet if |
/Zephyr-latest/subsys/testsuite/ztest/
DKconfig213 that while tests will still be marked as skipped on failed zassume calls, the final test
/Zephyr-latest/doc/connectivity/networking/api/
Dtls_credentials_shell.rst203 After the list is printed, a final summary of the found credentials will be printed in the form:
Dsockets.rst190 should take place after the file descriptor is allocated. As a final step,
/Zephyr-latest/doc/releases/
Drelease-notes-4.1.rst358 from the final application.
Dmigration-guide-4.1.rst89 It can be further trimmed down to reduce RAM consumption if the final
Drelease-notes-3.5.rst431 This fails the build if the initialization sequence in the final ELF file
435 * Added a new ``initlevels`` target for printing the final device and
436 :c:macro:`SYS_INIT` initialization sequence from the final ELF file.
439 will be included in the final binary. Syscalls associated with disabled
/Zephyr-latest/boards/st/stm32h7b3i_dk/doc/
Dindex.rst11 application development before porting to the final product, thus simplifying
/Zephyr-latest/doc/develop/flash_debug/
Dhost-tools.rst124 * The final 16 KiB is reserved for the application.
159 * The final 64 KiB is reserved for the application.
/Zephyr-latest/doc/security/standards/
Detsi-303645.rst73 - entity that creates an assembled final consumer IoT product, which is likely to contain
77 - state of the device after factory reset or after final production/assembly.
/Zephyr-latest/doc/kernel/services/other/
Dfatal.rst33 issued since assertion code is not normally present in a final product.
/Zephyr-latest/doc/security/
Dsecurity-overview.rst621 outlined in the following. Based on the final choices for the
667 platform and the final application running on top of Zephyr. If
677 assumptions on the application. If these are met, the final
Dsecure-coding.rst196 on behalf of the project, or perform final releases of the project
/Zephyr-latest/doc/build/dts/
Dhowtos.rst21 If you just want to see the "final" devicetree for your board, build an
48 The :file:`zephyr.dts` file is the final devicetree in DTS format.
/Zephyr-latest/doc/kernel/memory_management/
Dheap.rst32 until memory is available. The final argument is a
/Zephyr-latest/doc/develop/application/
Dindex.rst72 with other settings to produce the final configuration. The purpose of
93 Zephyr, then link them together into a final binary you can run on your board.
463 entry point, or top level, of the build system. The final :file:`zephyr.elf`
905 * :file:`zephyr.elf`, which contains the final combined application and
/Zephyr-latest/doc/connectivity/usb/device_next/
Dusb_device.rst163 The final step to enable the USB device is :c:func:`usbd_enable`, after that,
/Zephyr-latest/boards/st/sensortile_box_pro/doc/
Dindex.rst207 The final application may use it to declare SensorTile.box PRO device as belonging to a
/Zephyr-latest/boards/st/steval_stwinbx1/doc/
Dindex.rst223 The final application may use it to declare STEVAL-STWINBX1 device as belonging to a
/Zephyr-latest/boards/qemu/x86/
Dqemu_x86_tiny.ld71 * final ELF image. The address doesn't even have to be valid on the
/Zephyr-latest/doc/build/kconfig/
Dsetting.rst138 known as a Kconfig fragment, which are then merged to get the final
/Zephyr-latest/doc/kernel/services/
Dinterrupts.rst464 and is removed from the final build.
525 software ISR table that are then compiled and linked into the final
/Zephyr-latest/doc/build/dts/api/
Dapi.rst158 The Zephyr build system chooses a dependency ordering of the final devicetree
/Zephyr-latest/doc/build/
Dzephyr_cmake_package.rst389 # To ensure final path is absolute and does not contain ../.. in variable.

123456