Home
last modified time | relevance | path

Searched refs:executable (Results 1 – 25 of 93) sorted by relevance

1234

/Zephyr-Core-3.5.0/scripts/west_commands/
Drun_tests.py29 mypy = [sys.executable, '-m', 'mypy', f'--config-file={here}/mypy.ini',
31 pytest = [sys.executable, '-m', 'pytest'] + sys.argv[1:]
/Zephyr-Core-3.5.0/boards/posix/native_sim/
DKconfig.board9 as a 32-bit executable.
17 as a 64-bit executable.
/Zephyr-Core-3.5.0/boards/posix/native_posix/
DKconfig.board9 as a 32-bit executable.
21 as a 64-bit executable.
/Zephyr-Core-3.5.0/subsys/bindesc/
DKconfig8 Binary Descriptors - constant data accessible outside of the executable image
/Zephyr-Core-3.5.0/arch/common/
Dfill_with_zeros.ld9 * counter) in executable segments with TrapInstr pattern, e.g. for ARM the
/Zephyr-Core-3.5.0/doc/develop/getting_started/
Dinstallation_mac.rst14 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-Core-3.5.0/scripts/kconfig/
Dlint.py328 sys.exit(executable() + "error: " + msg)
332 print(executable() + "warning: " + msg, file=sys.stderr)
335 def executable(): function
/Zephyr-Core-3.5.0/boards/posix/nrf_bsim/doc/
Dnrf5340bsim.rst86 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,
103 and cannot use an embedded image to assemble a native executable.
Dnrf52_bsim.rst114 Note that the executable is a BabbleSim executable. The ``-nosim`` command line
125 executable to the simulator bin folder with a sensible name:
/Zephyr-Core-3.5.0/include/zephyr/arch/x86/ia32/
Dsegmentation.h160 uint8_t executable:1; member
275 .executable = 1, \
287 .executable = 0, \
/Zephyr-Core-3.5.0/samples/modules/nanopb/
DREADME.rst17 make sure the ``protoc`` executable is installed and available.
/Zephyr-Core-3.5.0/drivers/serial/
DKconfig.native_posix32 which invoked the native_posix executable. This is good enough for
63 If the native_posix executable is called with the --attach_uart
/Zephyr-Core-3.5.0/doc/services/binary_descriptors/
Dindex.rst6 Binary Descriptors are constant data objects storing information about the binary executable.
41 where the image must begin with executable code (e.g. x86), a jump instruction is injected at
118 ``west`` is able to parse and display binary descriptors from a given executable image.
/Zephyr-Core-3.5.0/doc/develop/test/
Dbsim.rst16 executable, which includes the application, Zephyr OS, and models of the HW.
18 When there is radio activity, this Linux executable will connect to the BabbleSim Phy simulation
Dcoverage.rst88 …$ gcovr -r $ZEPHYR_BASE . --html -o gcov_report/coverage.html --html-details --gcov-executable <gc…
96 to build a native executable which contains your application, the Zephyr OS,
/Zephyr-Core-3.5.0/boards/arm/efr32_thunderboard/doc/
Dbrd2602.rst74 which `commander` executable is located is present in the `PATH` environment
81 - Otherwise, one should specify full path to the `commander` executable:
/Zephyr-Core-3.5.0/cmake/compiler/arcmwdt/
Dtarget.cmake9 # the final executable.
/Zephyr-Core-3.5.0/subsys/usb/device/class/dfu/
DKconfig47 the executable image is always decrypted despite the image
/Zephyr-Core-3.5.0/cmake/compiler/armclang/
Dtarget.cmake10 # the final executable.
/Zephyr-Core-3.5.0/cmake/compiler/xcc/
Dtarget.cmake62 # the final executable.
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/
Dbluetooth-dev.rst131 executable.
132 This executable is a normal Linux program, which can be debugged and
156 executable.
/Zephyr-Core-3.5.0/cmake/
Dtarget_toolchain_flags.cmake9 # multiple symlinks pointing to same executable will generate different
/Zephyr-Core-3.5.0/scripts/west_commands/runners/
Desp32.py106 cmd_flash = [sys.executable, self.espidf, '--chip', 'auto']
/Zephyr-Core-3.5.0/boards/arm/lpcxpresso55s36/
Dlpcxpresso55s36.dts152 label = "executable";
/Zephyr-Core-3.5.0/arch/nios2/
DKconfig81 anywhere in the executable. Note that if any small globals that are put

1234