Searched full:binaries (Results 1 – 25 of 90) sorted by relevance
1234
| /Zephyr-Core-3.6.0/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-Core-3.6.0/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-Core-3.6.0/doc/services/tfm/ |
| D | requirements.rst | 42 The following Python modules are required when building TF-M binaries:
61 Part of the process of generating binaries for QEMU and merging signed
62 secure and non-secure binaries on certain platforms also requires the use of
|
| /Zephyr-Core-3.6.0/tests/bsim/ |
| D | README.md | 26 After building the tests' required binaries you can run a test directly with its individual
29 For example you can build the required binaries for the networking tests with
54 Each of these test scripts expects the binaries their require already built, and will execute
71 If these scripts or the test binaries create temporary files, they should preferably do so by
|
| /Zephyr-Core-3.6.0/scripts/tests/twister/ |
| D | test_platform.py | 35 'binaries': [],
63 binaries:
91 'binaries': ['dummy.exe', 'dummy.bin'],
|
| /Zephyr-Core-3.6.0/modules/ |
| D | Kconfig.mcuboot | 59 sign the final binaries using a 'west sign -t imgtool' command.
60 The signed binaries are placed in the build directory
75 If left empty, you must sign the Zephyr binaries manually.
89 sign and encrypt the final binaries using a 'west sign -t imgtool'
90 command. The binaries are placed in the build directory at
102 If left empty, you must encrypt the Zephyr binaries manually.
137 The signed, padded, and confirmed binaries are placed in the build
|
| /Zephyr-Core-3.6.0/boards/arm/mec172xevb_assy6906/ |
| D | mec172xevb_assy6906.yaml | 24 binaries:
|
| /Zephyr-Core-3.6.0/boards/arm/stm32wb5mm_dk/doc/ |
| D | stm32wb5mm_dk.rst | 131 Bluetooth and compatibility with STM32WB Copro Wireless Binaries
135 a valid STM32WB Coprocessor binaries (either 'Full stack' or 'HCI Layer').
136 These binaries are delivered in STM32WB Cube packages, under
139 For compatibility information with the various versions of these binaries,
143 Note that since STM32WB Cube package V1.13.2, `"full stack"` binaries are not
|
| /Zephyr-Core-3.6.0/scripts/pylib/twister/twisterlib/ |
| D | runner.py | 814 Get list of binaries paths (absolute or relative to the
815 self.instance.build_dir), basing on information from platform.binaries
816 or runners.yaml. If they are not found take default binaries like
819 binaries: List[str] = []
822 if platform.binaries:
823 for binary in platform.binaries:
824 binaries.append(os.path.join('zephyr', binary))
826 # Get binaries for a single-domain build
827 binaries += self._get_binaries_from_runners()
828 # Get binaries in the case of a multiple-domain build
[all …]
|
| D | platform.py | 63 self.binaries = testing.get("binaries", [])
|
| /Zephyr-Core-3.6.0/cmake/linker/ |
| D | linker_flags_template.cmake | 16 # Linker flag for disabling position independent binaries,
|
| /Zephyr-Core-3.6.0/samples/application_development/external_lib/ |
| D | README.rst | 36 ``Binaries`` and ``Dependencies`` and extracting them to the same folder, or
|
| /Zephyr-Core-3.6.0/scripts/schemas/twister/ |
| D | platform-schema.yaml | 74 "binaries":
|
| /Zephyr-Core-3.6.0/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-Core-3.6.0/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-Core-3.6.0/boards/arm/stm32wb5mmg/doc/ |
| D | stm32wb5mmg.rst | 184 Bluetooth and compatibility with STM32WB Copro Wireless Binaries
188 a valid STM32WB Coprocessor binaries (either 'Full stack' or 'HCI Layer').
189 These binaries are delivered in STM32WB Cube packages, under
191 For compatibility information with the various versions of these binaries,
194 Note that since STM32WB Cube package V1.13.2, "full stack" binaries are not compatible
|
| /Zephyr-Core-3.6.0/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-Core-3.6.0/doc/develop/west/ |
| D | sign.rst | 3 Signing Binaries
15 The Zephyr build system has special support for signing binaries for use with
19 signed binaries.
|
| /Zephyr-Core-3.6.0/boards/arm/nucleo_wb55rg/doc/ |
| D | nucleo_wb55rg.rst | 182 Bluetooth and compatibility with STM32WB Copro Wireless Binaries
186 a valid STM32WB Coprocessor binaries (either 'Full stack' or 'HCI Layer').
187 These binaries are delivered in STM32WB Cube packages, under
189 For compatibility information with the various versions of these binaries,
192 Note that since STM32WB Cube package V1.13.2, "full stack" binaries are not compatible
|
| /Zephyr-Core-3.6.0/cmake/modules/ |
| D | FindBabbleSim.cmake | 12 # Path to the BabbleSim build output root path (under which libraries and binaries) are kept
|
| /Zephyr-Core-3.6.0/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-Core-3.6.0/boards/arm/actinius_icarus_bee/doc/ |
| D | index.rst | 112 3. Merge the two binaries together.
114 If you are using Segger Embedded Studio v4.18 or later, the two binaries are built, merged, and
|
| /Zephyr-Core-3.6.0/boards/arm/actinius_icarus_som/doc/ |
| D | index.rst | 112 3. Merge the two binaries together.
114 If you are using Segger Embedded Studio v4.18 or later, the two binaries are built, merged, and
|
| /Zephyr-Core-3.6.0/soc/x86/intel_ish/utils/ |
| D | build_ish_firmware.py | 11 each binaries into right memory location.
|
1234
