Searched refs:binary (Results 1 – 25 of 367) sorted by relevance
12345678910>>...15
| /Zephyr-latest/subsys/bindesc/ |
| D | Kconfig | 15 Enable the app to define its own binary descriptors
28 Determines the maximum size of a binary descriptor's data. The theoretical
37 Enable the app to read the binary descriptors of another image
48 Enable reading and parsing binary descriptors from RAM.
53 Enable reading and parsing binary descriptors from memory mapped flash.
58 Enable reading and parsing binary descriptors from non memory mapped flash
|
| D | Kconfig.version | 5 bool "Version binary descriptors"
7 Add the version binary descriptors
34 The kernel version as binary coded decimal, computed as
67 The app version as binary coded decimal, computed as
|
| D | Kconfig.host_info | 5 bool "Host info binary descriptors"
7 Add the host info binary descriptors
|
| /Zephyr-latest/tests/ztest/fail/ |
| D | README.rst | 12 binary which is expected to fail by calling one of the following:
19 The binary by itself, when executed, will fail to run and return a code of ``1``. The main test
20 binary will use ``popen()`` to run the failing test binary and will assert both the return code and
|
| /Zephyr-latest/tests/bluetooth/qualification/ |
| D | .gitattributes | 5 *.pts binary
6 *.bqw binary
|
| /Zephyr-latest/samples/subsys/bindesc/hello_bindesc/ |
| D | README.rst | 5 Set and access binary descriptors for a basic Zephyr application.
10 A simple sample of :ref:`binary descriptor <binary_descriptors>` definition and usage.
23 To dump all binary descriptors in the image, run:
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 8 help of executable code distributed in binary form. Binary blobs (or blobs for
9 short) are files containing proprietary machine code or data in a binary format,
12 Zephyr supports downloading and using third-party binary blobs via its built-in
18 the support for binary blobs in forks or third-party distributions of Zephyr. In
21 therefore free to create Zephyr-based downstream software which uses binary
27 Most binary blobs are distributed under proprietary licenses which vary
39 The Zephyr Project does not host binary blobs in its Git repositories or
51 include a reference to a binary blob to the upstream Zephyr distribution, a
74 The ``west blobs`` command only fetches and stores the binary blobs themselves.
81 Inclusion of binary blobs will taint the Zephyr build. The definition of
[all …]
|
| /Zephyr-latest/samples/subsys/bindesc/read_bindesc/ |
| D | README.rst | 5 Define some binary descriptors and read them.
10 A simple sample of :ref:`binary descriptor <binary_descriptors>` definition and reading.
|
| /Zephyr-latest/boards/shields/renesas_us159_da14531evz/doc/ |
| D | index.rst | 25 The DA14531 Module contained on the shield must be programmed with a binary
30 suitable binary and then program it into the DA14531 via the SWD header
32 press the "Search Online" button. The required binary file can be selected
35 .. figure:: da14531-hci-hw-flow-binary.webp
41 Press the "Program" button to program the binary file into the DA14531 Module.
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | ota.rst | 13 infrastructure to host the firmware binary and implement a method of signaling
18 same method can be used as part of OTA. The binary is first downloaded
30 When a new version is available, the device downloads and flashes the binary. In
32 TLS/DTLS, and the signed firmware binary is confirmed by MCUboot before the
43 REST api to detect firmware updates. When a new update is detected, the binary
55 the binary is downloaded and installed. MCUboot can be used to verify the
66 firmware binary to the remote device where it is verified by MCUboot before the
|
| /Zephyr-latest/soc/intel/intel_ish/utils/ |
| D | build_ish_firmware.cmake | 8 COMMAND ${CMAKE_OBJCOPY} -O binary --remove-section=aon
11 COMMAND ${CMAKE_OBJCOPY} -O binary --only-section=aon
|
| /Zephyr-latest/doc/services/binary_descriptors/ |
| D | index.rst | 6 Binary Descriptors are constant data objects storing information about the binary executable.
7 Unlike "regular" constants, binary descriptors are linked to a known offset in the binary, making
9 A few examples of constants that would make useful binary descriptors are: kernel version, app vers…
36 to a known offset in the binary image. This offset may vary between architectures,
42 the beginning of the image, in order to skip over the binary descriptors, which are right
50 value. All binary descriptor numbers (magic, tags, uints) are laid out in memory
55 The binary descriptor header starts with the magic number ``0xb9863e5a7ea46046``. It's followed
98 # Enable binary descriptors
101 # Enable definition of binary descriptors
104 # Enable default build time binary descriptors
[all …]
|
| /Zephyr-latest/doc/build/cmake/ |
| D | index.rst | 141 into four stages: the pre-build, first-pass binary, final binary, and
170 Compilation proper begins with the first intermediate binary. Source files (C
200 Unfixed size binary
201 The unfixed size intermediate binary is produced when :ref:`usermode_api`
203 It produces a binary where sizes are not fixed and thus it may be used
204 by post-process steps that will impact the size of the final binary.
212 Fixed size binary
213 The fixed size intermediate binary is produced when :ref:`usermode_api`
216 It produces a binary where sizes are fixed and thus the size must not change
217 between the intermediate binary and the final binary.
[all …]
|
| /Zephyr-latest/soc/nuvoton/npcx/ |
| D | Kconfig | 9 bool "The output binary with NPCX binary header"
12 to RAM by the firmware binary header setting. Enable this to invoke
18 bool "Build npcx binary in BIN format"
21 Build a "raw" binary zephyr/zephyr.npcx.bin in the build directory.
25 bool "Build npcx binary in HEX format"
28 Build an HEX binary zephyr/zephyr.npcx.hex in the build directory.
48 binary from flash to RAM.
|
| /Zephyr-latest/doc/services/llext/ |
| D | config.rst | 34 Build and expect relocatable files as binary object type for the LLEXT
40 Build and expect relocatable (partially linked) files as the binary
46 Build and expect shared libraries as binary object type for the LLEXT
96 To this end, the main binary contains a LLEXT-dedicated symbol table, filled
105 Perform an extra processing step on the Zephyr binary and on all
108 stored in the binary.
113 binary is no longer necessary, which provides a significant decrease in
123 Using a different value for this option in the main binary and in
|
| /Zephyr-latest/boards/arm/mps2/ |
| D | CMakeLists.txt | 7 # Building a firmware image for CPU1: this requires a binary
10 # any binary for CPU0, as this is built by the dual core sample.
|
| /Zephyr-latest/cmake/bintools/armclang/ |
| D | elfconvert_command.cmake | 25 elseif(${OUTTARGET} STREQUAL "binary")
33 if(DEFINED ONLY_SECTION AND "${OUTTARGET}" STREQUAL "binary")
49 if(DEFINED ONLY_SECTION AND "${OUTTARGET}" STREQUAL "binary")
|
| /Zephyr-latest/boards/ti/sk_am62/doc/ |
| D | index.rst | 62 These cores will then load the zephyr binary on the M4 core using remoteproc.
72 The testing requires the binary to be copied to the SD card to allow the A53 cores to load it while…
81 This builds the program and the binary is present in the :file:`build/zephyr` directory as
84 We now copy this binary onto the SD card in the :file:`/lib/firmware` directory and name it as
94 The SD card can now be used for booting. The binary will now be loaded onto the M4F core on boot.
99 The binary will run and print Hello world to the MCU_UART0 port.
104 The board is equipped with an XDS110 JTAG debugger. To debug a binary, utilize the ``debug`` build …
|
| /Zephyr-latest/cmake/bintools/llvm/ |
| D | target.cmake | 3 # Configures binary tools as llvm binary tool set
|
| /Zephyr-latest/boards/shields/mikroe_ble_tiny_click/doc/ |
| D | index.rst | 34 The DA14531 Module contained on the shield must be programmed with a binary
39 suitable binary and then program it into the DA14531 via the SWD header
41 press the "Search Online" button. The required binary file can be selected
44 .. figure:: da14531-hci-binary.webp
50 Press the "Program" button to program the binary file into the DA14531 Module.
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 008_bin-blobs.md | 3 about: Submit a proposal to integrate binary blob(s)
12 Describe where the binary blob(s) originate from
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | llext-sections.ld | 12 * to be included in the final binary.
24 * Zephyr ELF for post-processing, but it is not included in the final binary.
|
| /Zephyr-latest/tests/subsys/zbus/unittests/src/ |
| D | messages.h | 40 uint8_t binary; /* Range 0 to 1 */ member
|
| /Zephyr-latest/boards/phytec/phyboard_lyra/doc/ |
| D | phyboard_lyra_am62xx_m4.rst | 88 cores of the SoM. These cores will then load the zephyr binary on the M4 core
98 Therefore, the testing requires the binary to be copied to the SD card to allow the A53 cores to
108 This builds the program and the binary is present in the :file:`build/zephyr` directory as
111 We now copy this binary onto the SD card in the :file:`/lib/firmware` directory and name it as
121 The SD card can now be used for booting. The binary will now be loaded onto the M4F core on boot.
134 The board should boot into Linux and the binary will run and print Hello world to the MCU_UART0
141 The board is equipped with an XDS110 JTAG debugger. To debug a binary, utilize the ``debug`` build
|
| /Zephyr-latest/boards/silabs/radio_boards/xg29_rb4412a/doc/ |
| D | index.rst | 48 ``west flash`` will by default use SEGGER JLink. Make sure that the JLinkExe binary is available on
50 In this case, make sure that the commander binary is available on PATH.
68 To use the BLE function, run the command below to retrieve necessary binary
|
12345678910>>...15
