Searched refs:executable (Results 1 – 25 of 133) sorted by relevance
123456
| /Zephyr-4.3.0/share/sysbuild/cmake/modules/ |
| D | native_simulator_sb_extensions.cmake | 9 # this function adds an extra build target which will copy the executable produced by
15 # this final executable in the same place as for non-sysbuild builds.
35 # and configures the final image to assemble the child images into its final executable.
|
| /Zephyr-4.3.0/scripts/west_commands/ |
| D | run_tests.py | 33 command = [sys.executable, '-m'] + cmd
|
| D | packages.py | 162 cmd = [sys.executable, "-m", "pip", "install"]
|
| /Zephyr-4.3.0/drivers/serial/ |
| D | Kconfig.native_pty | 14 to either connect to the terminal from which the executable was run, or into
37 which invoked the native executable. This is good enough for
51 If the native executable is called with the --attach_uart
|
| /Zephyr-4.3.0/arch/common/ |
| D | fill_with_zeros.ld | 9 * counter) in executable segments with TrapInstr pattern, e.g. for ARM the
|
| /Zephyr-4.3.0/boards/amd/versal2_rpu/ |
| D | CMakeLists.txt | 11 # Ensure DTC executable is available
|
| /Zephyr-4.3.0/boards/amd/versalnet_apu/ |
| D | CMakeLists.txt | 11 # Ensure DTC executable is available
|
| /Zephyr-4.3.0/boards/native/nrf_bsim/doc/ |
| D | nrf5340bsim.rst | 86 Assembling both MCUs images into a single executable
91 to that MCU code image, and an executable (``zephyr/zephyr.exe``) that includes the native simulator
94 If you want to assemble an executable including a previously built image for the other MCU,
99 You can also use :ref:`System build (sysbuild) <sysbuild>` to build your dual MCU executable.
108 and cannot use an embedded image to assemble a native executable.
|
| D | nrf52_bsim.rst | 115 Note that the executable is a BabbleSim executable. The ``-nosim`` command line
126 resulting executable to the simulator bin folder with a sensible name:
200 … about attaching to the UART output, refer to the output of the ``-help`` option of the executable.
|
| /Zephyr-4.3.0/scripts/kconfig/ |
| D | lint.py | 328 sys.exit(executable() + "error: " + msg)
332 print(executable() + "warning: " + msg, file=sys.stderr)
335 def executable(): function
|
| /Zephyr-4.3.0/doc/develop/getting_started/ |
| D | installation_mac.rst | 14 Dock. This means that if you download executable binaries using a web browser,
25 choice. This will apply to any executable being launched from such terminal
|
| /Zephyr-4.3.0/scripts/dts/ |
| D | dtdoctor_sca_wrapper.py | 61 sys.executable,
|
| /Zephyr-4.3.0/include/zephyr/arch/x86/ia32/ |
| D | segmentation.h | 161 uint8_t executable:1; member
276 .executable = 1, \
288 .executable = 0, \
|
| /Zephyr-4.3.0/samples/subsys/fs/ext2_fstab/ |
| D | README.rst | 17 and afterwards run the generated executable file within the build folder.
|
| /Zephyr-4.3.0/samples/subsys/fs/fatfs_fstab/ |
| D | README.rst | 18 and afterwards run the generated executable file within the build folder.
|
| /Zephyr-4.3.0/boards/native/native_sim/doc/ |
| D | cross_compile.rst | 79 Now you have an executable, ``zephyr/zephyr.exe``, you can copy and run in your target machine.
84 It is possible to execute this cross compiled executable in your development host. For this you need
86 Ubuntu 24.04 you can install with the ``qemu-user`` package. With this, you can run the executable
|
| /Zephyr-4.3.0/scripts/tests/twister_blackbox/ |
| D | test_addon.py | 220 check_installed_command = [sys.executable, '-m', 'pip', 'list']
221 install_command = [sys.executable, '-m', 'pip', 'install', '--no-input', pth_path]
222 uninstall_command = [sys.executable, '-m', 'pip', 'uninstall', '--yes',
|
| /Zephyr-4.3.0/boards/native/native_sim/ |
| D | Kconfig | 35 Enables the reboot implementation for the native sim executable.
|
| /Zephyr-4.3.0/boards/native/nrf_bsim/ |
| D | Kconfig.defconfig | 11 # access to its IPC buffer. Without it, the executable cannot be built.
|
| /Zephyr-4.3.0/doc/services/serialization/ |
| D | nanopb.rst | 13 make sure the ``protoc`` executable is installed and available.
|
| /Zephyr-4.3.0/boards/silabs/dev_kits/xg27_dk2602a/doc/ |
| D | index.rst | 61 which ``commander`` executable is located is present in the :envvar:`PATH` environment
68 - Otherwise, one should specify full path to the ``commander`` executable:
|
| /Zephyr-4.3.0/doc/contribute/style/ |
| D | index.rst | 31 code, make the file *$ZEPHYR_BASE/.git/hooks/pre-commit* executable and edit
42 *$ZEPHYR_BASE/.git/hooks/pre-push* executable and edit it to contain:
|
| /Zephyr-4.3.0/subsys/bindesc/ |
| D | Kconfig | 8 Binary Descriptors - constant data accessible outside of the executable image
|
| /Zephyr-4.3.0/cmake/compiler/armclang/ |
| D | target.cmake | 10 # the final executable.
|
| /Zephyr-4.3.0/subsys/usb/device/class/dfu/ |
| D | Kconfig | 47 the executable image is always decrypted despite the image
|
123456
