Home
last modified time | relevance | path

Searched full:binary (Results 1 – 25 of 550) sorted by relevance

12345678910>>...22

/Zephyr-Core-3.7.0/tests/lib/cmsis_dsp/matrix/
DKconfig24 bool "Test: Matrix Binary Q7"
27 bool "Test: Matrix Binary Q15"
30 bool "Test: Matrix Binary Q31"
33 bool "Test: Matrix Binary F16"
37 bool "Test: Matrix Binary F32"
40 bool "Test: Matrix Binary F64"
/Zephyr-Core-3.7.0/samples/subsys/bindesc/hello_bindesc/
Dprj.conf1 # Enable binary descriptors
4 # Enable definition of binary descriptors
7 # Enable default build time binary descriptors
11 # Enable default version binary descriptors
18 # Enable default host info binary descriptors
DREADME.rst2 :name: Binary descriptors "Hello World"
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-Core-3.7.0/doc/services/binary_descriptors/
Dindex.rst3 Binary Descriptors
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…
12 Binary descriptors are created by using the ``DEFINE_BINDESC_*`` macros. For example:
35 Binary descriptors are implemented with a TLV (tag, length, value) header linked
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
[all …]
/Zephyr-Core-3.7.0/soc/intel/intel_ish/utils/
Dbuild_ish_firmware.py7 """Script to pack EC binary with manifest header.
9 Package ecos main FW binary (kernel) and AON task binary into final EC binary
25 help="EC kernel binary to pack, \
29 help="EC aontask binary to pack, \
33 help="Output flash binary file")
38 """Returns a binary blob that represents a manifest entry"""
66 print(" kernel binary size:", kernel_size)
68 # Add manifest for main ISH binary
72 print(" AON binary size: ", aon_size)
74 # Add manifest for aontask binary
/Zephyr-Core-3.7.0/doc/contribute/
Dbin_blobs.rst3 Binary Blobs
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.
[all …]
/Zephyr-Core-3.7.0/subsys/bindesc/
DKconfig5 bool "Binary Descriptors"
8 Binary Descriptors - constant data accessible outside of the executable image
13 bool "Binary Descriptors Define"
15 Enable the app to define its own binary descriptors
DKconfig.version5 bool "Version binary descriptors"
7 Add the version binary descriptors
34 The kernel version as binary coded decimal, computed as
61 The app version as binary coded decimal, computed as
DKconfig.host_info5 bool "Host info binary descriptors"
7 Add the host info binary descriptors
/Zephyr-Core-3.7.0/tests/ztest/fail/src/
Dmain.cpp19 /* Start running the target binary. This binary is expected to fail. */ in ZTEST()
24 /* Wait for the binary to finish running and grab the output */ in ZTEST()
53 zassert_equal(1, rc, "Test binary expected to fail with return code 1, but got %d", rc); in ZTEST()
54 zassert_true(found_error_string, "Test binary did not produce the expected error string \"" in ZTEST()
/Zephyr-Core-3.7.0/boards/shields/mikroe_ble_tiny_click/doc/
Dindex.rst34 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
46 :alt: DA14531 HCI Binary File Selection
48 Selecting the DA14531 HCI Binary File for Download
50 Press the "Program" button to program the binary file into the DA14531 Module.
/Zephyr-Core-3.7.0/soc/nuvoton/npcx/
DKconfig9 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-Core-3.7.0/tests/ztest/fail/
DREADME.rst12 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-Core-3.7.0/doc/services/llext/
Dconfig.rst34 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-Core-3.7.0/doc/services/device_mgmt/
Dota.rst13 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-Core-3.7.0/include/zephyr/
Dbindesc.h28 * @brief Binary Descriptor Definition
145 /* Convenience helper for declaring a binary descriptor entry. */
155 * @brief Define a binary descriptor of type string.
158 * Define a string that is registered in the binary descriptor header.
176 * @brief Define a binary descriptor of type uint.
179 * Define an integer that is registered in the binary descriptor header.
197 * @brief Define a binary descriptor of type bytes.
200 * Define a uint8_t array that is registered in the binary descriptor header.
222 * @brief Get the value of a string binary descriptor
225 * Get the value of a string binary descriptor, previously defined by
[all …]
/Zephyr-Core-3.7.0/.github/ISSUE_TEMPLATE/
D008_bin-blobs.md2 name: Binary blobs
3 about: Submit a proposal to integrate binary blob(s)
12 Describe where the binary blob(s) originate from
/Zephyr-Core-3.7.0/doc/build/cmake/
Dindex.rst138 into four stages: the pre-build, first-pass binary, final binary, and
167 Compilation proper begins with the first intermediate binary. Source files (C
197 Unfixed size binary
198 The unfixed size intermediate binary is produced when :ref:`usermode_api`
200 It produces a binary where sizes are not fixed and thus it may be used
201 by post-process steps that will impact the size of the final binary.
209 Fixed size binary
210 The fixed size intermediate binary is produced when :ref:`usermode_api`
213 It produces a binary where sizes are fixed and thus the size must not change
214 between the intermediate binary and the final binary.
[all …]
/Zephyr-Core-3.7.0/subsys/llext/
DKconfig14 prompt "Binary object type for llext"
23 Build and expect object files as binary object type for the
31 binary object type for the llext subsystem. These object files
38 Build and expect shared libraries as binary object type for
80 from the binary. However, it can make LLEXT debugging
/Zephyr-Core-3.7.0/scripts/
Dwest-commands.yml32 help: sign a Zephyr binary for bootloader chain-loading
37 help: flash and run a binary on a board
63 help: work with binary blobs
68 help: work with Binary Descriptors
/Zephyr-Core-3.7.0/dts/bindings/bluetooth/
Dinfineon,cyw208xx-hci.yaml10 cyw920829 requires fetch binary files of Bluetooth controller firmware.
11 To fetch Binary Blobs: west blobs fetch hal_infineon
/Zephyr-Core-3.7.0/dts/bindings/serial/
Duart-controller-pin-inversion.yaml10 Invert the binary logic of tx pin. When enabled, physical logic levels are inverted and
15 Invert the binary logic of rx pin. When enabled, physical logic levels are inverted and
/Zephyr-Core-3.7.0/cmake/bintools/armclang/
Delfconvert_command.cmake25 elseif(${OUTTARGET} STREQUAL "binary")
33 if(DEFINED ONLY_SECTION AND "${OUTTARGET}" STREQUAL "binary")
49 if(DEFINED ONLY_SECTION AND "${OUTTARGET}" STREQUAL "binary")
/Zephyr-Core-3.7.0/boards/arm/mps2/
DCMakeLists.txt7 # 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-Core-3.7.0/samples/drivers/ipm/ipm_mhu_dual_core/
DREADME.rst51 …srec_cat zephyr.bin -Binary -offset $IMAGE_OFFSET zephyr_nonsecure.bin -Binary -offset $IMAGE_NS_O…
54 …srec_cat zephyr.bin -Binary -offset 0xA000000 zephyr_nonsecure.bin -Binary -offset 0xA060400 -o du…

12345678910>>...22