Searched full:binaries (Results 1 – 25 of 101) sorted by relevance
12345
| /Zephyr-latest/modules/hal_infineon/cat1cm0p/ |
| D | CMakeLists.txt | 27 # Generate Include binaries and add source of psoc6_cm0p_sleep.c
29 # Generate Include binaries
36 message(WARNING "Can't find CM0+ binaries, please execute: \'west blobs fetch hal_infineon\' ")
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | other_x_compilers.rst | 36 toolchain's binaries have, e.g. the path to the directory containing the
37 compiler binaries plus the target triplet and trailing dash.
53 When using this option, all of your toolchain binaries must reside in the same
56 example above, the ``gcc-arm-none-eabi`` package installs binaries such as
|
| /Zephyr-latest/doc/services/tfm/ |
| D | requirements.rst | 41 The following Python modules are required when building TF-M binaries:
60 Part of the process of generating binaries for QEMU and merging signed
61 secure and non-secure binaries on certain platforms also requires the use of
|
| /Zephyr-latest/doc/build/signing/ |
| D | index.rst | 3 Signing Binaries
6 Binaries can be optionally signed as part of a build automatically using CMake code, there is
7 also the ability to use ``west sign`` to sign binaries too, this page describes the former, the
13 The Zephyr build system has special support for signing binaries for use with the `MCUboot`_
16 ``west flash`` will use the signed binaries.
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | test_platform.py | 35 'binaries': [],
62 binaries:
91 'binaries': ['dummy.exe', 'dummy.bin'],
|
| /Zephyr-latest/modules/ |
| D | Kconfig.mcuboot | 47 sign the final binaries using a 'west sign -t imgtool' command.
48 The signed binaries are placed in the build directory
63 If left empty, you must sign the Zephyr binaries manually.
77 sign and encrypt the final binaries using a 'west sign -t imgtool'
78 command. The binaries are placed in the build directory at
90 If left empty, you must encrypt the Zephyr binaries manually.
125 The signed, padded, and confirmed binaries are placed in the build
|
| /Zephyr-latest/boards/microchip/mec172xevb_assy6906/ |
| D | mec172xevb_assy6906.yaml | 24 binaries:
|
| /Zephyr-latest/soc/nxp/rw/ |
| D | firmwares.ld | 8 * Place the wifi and ble firmwares in rodata section. If both binaries
|
| /Zephyr-latest/boards/st/stm32wb5mm_dk/doc/ |
| D | stm32wb5mm_dk.rst | 126 Bluetooth and compatibility with STM32WB Copro Wireless Binaries
130 a valid STM32WB Coprocessor binaries (either 'Full stack' or 'HCI Layer').
131 These binaries are delivered in STM32WB Cube packages, under
134 For compatibility information with the various versions of these binaries,
138 Note that since STM32WB Cube package V1.13.2, "full stack" binaries are not
|
| /Zephyr-latest/doc/develop/test/ |
| D | bsim.rst | 119 After building the tests' required binaries you can run a test directly using its individual test
122 For example you can build the required binaries for the networking tests with
182 - Scripts expect that the binaries they require are already built. They should not compile binaries.
|
| /Zephyr-latest/samples/application_development/external_lib/ |
| D | README.rst | 36 ``Binaries`` and ``Dependencies`` and extracting them to the same folder, or
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 24 copies. But then, the biggest Zephyr application binaries we have on
45 Linux toolchain. EFI binaries are relocatable PE-COFF files --
|
| /Zephyr-latest/boards/st/stm32wb5mmg/doc/ |
| D | stm32wb5mmg.rst | 177 Bluetooth and compatibility with STM32WB Copro Wireless Binaries
181 a valid STM32WB Coprocessor binaries (either 'Full stack' or 'HCI Layer').
182 These binaries are delivered in STM32WB Cube packages, under
184 For compatibility information with the various versions of these binaries,
187 Note that since STM32WB Cube package V1.13.2, "full stack" binaries are not compatible
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_win.rst | 12 built-in functionality to natively run Ubuntu binaries directly on a standard
|
| D | installation_mac.rst | 14 Dock. This means that if you download executable binaries using a web browser,
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | runner.py | 1322 Get list of binaries paths (absolute or relative to the
1323 self.instance.build_dir), basing on information from platform.binaries
1324 or runners.yaml. If they are not found take default binaries like
1327 binaries: list[str] = []
1330 if platform.binaries:
1331 for binary in platform.binaries:
1332 binaries.append(os.path.join('zephyr', binary))
1334 # Get binaries for a single-domain build
1335 binaries += self._get_binaries_from_runners()
1336 # Get binaries in the case of a multiple-domain build
[all …]
|
| D | platform.py | 122 self.binaries = testing.get("binaries", [])
|
| /Zephyr-latest/scripts/schemas/twister/ |
| D | platform-schema.yaml | 106 "binaries":
|
| /Zephyr-latest/cmake/linker/ |
| D | linker_flags_template.cmake | 36 # Linker flag for disabling position independent binaries,
|
| /Zephyr-latest/drivers/wifi/nrf_wifi/ |
| D | CMakeLists.txt | 80 # RPU FW patch binaries based on the selected configuration
|
| /Zephyr-latest/boards/st/nucleo_wb55rg/doc/ |
| D | nucleo_wb55rg.rst | 177 Bluetooth and compatibility with STM32WB Copro Wireless Binaries
181 a valid STM32WB Coprocessor binaries (either 'Full stack' or 'HCI Layer').
182 These binaries are delivered in STM32WB Cube packages, under
184 For compatibility information with the various versions of these binaries,
187 Note that since STM32WB Cube package V1.13.2, "full stack" binaries are not compatible
|
| /Zephyr-latest/cmake/ |
| D | mcuboot.cmake | 7 # It builds signed binaries using imgtool as a post-processing step
26 # No signature key file, no signed binaries. No error, though:
70 # No imgtool, no signed binaries.
|
| /Zephyr-latest/doc/build/cmake/ |
| D | index.rst | 164 Intermediate binaries
179 The exact number of intermediate binaries is decided during the configuration
222 Intermediate binaries post-processing
225 The binaries from the previous stage are incomplete, with empty and/or
229 intermediate binaries to produce the missing pieces needed for the final
|
| /Zephyr-latest/doc/develop/west/ |
| D | sign.rst | 3 Signing Binaries
|
| /Zephyr-latest/boards/actinius/icarus_bee/doc/ |
| D | index.rst | 103 3. Merge the two binaries together.
105 If you are using Segger Embedded Studio v4.18 or later, the two binaries are built, merged, and
|
12345
