Home
last modified time | relevance | path

Searched refs:tool (Results 1 – 25 of 347) sorted by relevance

12345678910>>...14

/Zephyr-Core-3.4.0/scripts/west_commands/runners/
Dezflashcli.py13 def __init__(self, cfg, tool, sn, erase=False): argument
17 self.tool = tool
39 return EzFlashCliBinaryRunner(cfg, tool=args.tool, sn=args.sn,
56 self.check_call([self.tool] + self.sn_arg + ["erase_flash"])
62 self.check_call([self.tool] + self.sn_arg + ["image_flash", self.bin_])
65 … self.check_call([self.tool] + self.sn_arg + ["write_flash", f'0x{load_offset:x}', self.bin_])
69 self.check_call([self.tool] + self.sn_arg + ["go"])
72 self.require(self.tool)
/Zephyr-Core-3.4.0/doc/develop/sca/
Dindex.rst9 tool to use. :envvar:`ZEPHYR_SCA_VARIANT` is also supported as
12 Use ``-DZEPHYR_SCA_VARIANT=<tool>``, for example ``-DZEPHYR_SCA_VARIANT=sparse``
13 to enable the static analysis tool ``sparse``.
20 Support for an SCA tool is implemented in a file:`sca.cmake` file.
21 The file:`sca.cmake` must be placed under file:`<SCA_ROOT>/cmake/sca/<tool>/sca.cmake`.
33 └── <tool>/ # Name of SCA tool, this is the value given to ZEPHYR_SCA_VARIANT
34 └── sca.cmake # CMake code that confgures the tool to be used with Zephyr
46 To use ``foo`` as SCA tool you must then specify ``-DZEPHYR_SCA_VARIANT=foo``.
/Zephyr-Core-3.4.0/soc/xtensa/nxp_adsp/
DCMakeLists.txt17 COMMENT "west sign --if-tool-available --tool rimage ..."
18 COMMAND west sign --if-tool-available --tool rimage --build-dir ${CMAKE_BINARY_DIR}
/Zephyr-Core-3.4.0/boards/arm/mec172xmodular_assy6930/
DCMakeLists.txt9 #Allow users to pre-specify the tool using '-DMEC172X_SPI_GEN=<path-to-tool>/toolname'
15 …message(WARNING "Microchip SPI Image Generation tool is not available. SPI Image will not be gener…
23 …message(WARNING "Microchip SPI Image Generation tool configuration file is not available. SPI Imag…
/Zephyr-Core-3.4.0/boards/arm/mec1501modular_assy6885/
DCMakeLists.txt11 # Else find the tool in PATH
15 # but there is no tool for Apple. So
17 message(NOTICE "There is no SPI image generation tool for MacOS.")
26 …message(WARNING "Microchip SPI Image Generation tool (${EVERGLADES_SPI_GEN_FILENAME}) is not avail…
/Zephyr-Core-3.4.0/boards/arm/mec15xxevb_assy6853/
DCMakeLists.txt11 # Else find the tool in PATH
15 # but there is no tool for Apple. So
17 message(NOTICE "There is no SPI image generation tool for MacOS.")
26 …message(WARNING "Microchip SPI Image Generation tool (${EVERGLADES_SPI_GEN_FILENAME}) is not avail…
/Zephyr-Core-3.4.0/boards/arm/mec172xevb_assy6906/
DCMakeLists.txt11 # Else find the tool in PATH
15 # but there is no tool for Apple. So
17 message(NOTICE "There is no SPI image generation tool for MacOS.")
26 …message(WARNING "Microchip SPI Image Generation tool (${MEC172X_SPI_GEN_FILENAME}) is not availabl…
/Zephyr-Core-3.4.0/boards/riscv/hifive1_revb/
Dboard.cmake6 board_runner_args(jlink "--tool-opt=-jtagconf -1,-1")
7 board_runner_args(jlink "--tool-opt=-autoconnect 1")
/Zephyr-Core-3.4.0/boards/riscv/sparkfun_red_v_things_plus/
Dboard.cmake6 board_runner_args(jlink "--tool-opt=-jtagconf -1,-1")
7 board_runner_args(jlink "--tool-opt=-autoconnect 1")
/Zephyr-Core-3.4.0/scripts/west_commands/completion/
Dwest-completion.zsh53 # Completion script for Zephyr's meta-tool, west
231 '--domain[execute build tool (make or ninja) for a given domain]:domain:'
234 {-o,--build-opt}'[options to pass to build tool (make or ninja)]:tool opt:'
247 '(-t --tool)'{-t,--tool}'[image signing tool name]:tool:(imgtool rimage)'
248 '(-p --tool-path)'{-p,--tool-path}'[path to the tool]:tool path:_directories'
249 '(-D --tool-data)'{-D,--tool-data}'[path to tool data]:tool data path:_directories'
279 '--domain[execute build tool (make or ninja) for a given domain]:domain:'
/Zephyr-Core-3.4.0/scripts/west_commands/tests/
Dtest_nrf.py515 def check_expected(tool, test_case, check_fn, get_snr, tmpdir, runner_config): argument
517 expected = EXPECTED_RESULTS[test_case][EXPECTED_MAP[tool]]
518 if tool == 'nrfutil':
547 def test_init(check_call, check_output, get_snr, require, tool, test_case, argument
550 require.side_effect = functools.partial(require_patch, tool)
554 cls = CLASS_MAP[tool]
568 check_expected(tool, test_case, CHECK_FN_MAP[tool], get_snr, tmpdir,
578 def test_create(check_call, check_output, get_snr, require, tool, test_case, argument
581 require.side_effect = functools.partial(require_patch, tool)
597 cls = CLASS_MAP[tool]
[all …]
/Zephyr-Core-3.4.0/doc/develop/west/
Dindex.rst3 West (Zephyr's meta-tool)
6 The Zephyr project includes a swiss-army knife command line tool named
10 features inspired by Google's Repo tool and Git submodules. West is also
30 context about the tool.
/Zephyr-Core-3.4.0/boards/riscv/it8xxx2_evb/doc/
Dindex.rst88 you'll need our flash tool and Download board.
152 Use the winflash tool to program a zephyr application
155 #. Open winflash tool and make sure the order you open the switch is right.
158 Then, configure your winflash tool like below.
165 #. Using winflash tool flash zephyr.bin into your ITE board.
198 #. Open a second terminal window and use linux flash tool to flash your board.
204 .. note:: The source code of ITE tool can be downloaded here:
219 #. If the flash tool reports a failure, re-plug the 8390 Download board or
/Zephyr-Core-3.4.0/boards/riscv/it82xx2_evb/doc/
Dindex.rst105 you'll need our flash tool and Download board.
170 Use the winflash tool to program a zephyr application
173 #. Open the winflash tool and make sure the order you open the switch is right.
176 Then, configure your winflash tool like below.
183 #. Using the winflash tool flash ``zephyr.bin`` into your ITE board.
216 #. Open a second terminal window and use the Linux flash tool to flash your board.
222 .. note:: The source code of ITE tool can be downloaded here:
238 #. If the flash tool reports a failure, re-plug the 8390 Download board or
/Zephyr-Core-3.4.0/boards/common/
Dpyocd.board.cmake6 board_runner_args(pyocd "--tool-opt=-S")
/Zephyr-Core-3.4.0/soc/riscv/riscv-privileged/niosv/
Dlinker.ld7 #include <zephyr/linker/linker-tool.h>
/Zephyr-Core-3.4.0/doc/security/
Dhardening-tool.rst18 To simplify this process, Zephyr offers a **hardening tool** designed to analyze an application's
20 tool looks at the KConfig options in the build target and provides tailored suggestions and
27 :tool: all
/Zephyr-Core-3.4.0/soc/nios2/nios2f-zephyr/cpu/
DREADME13 To flash this CPU, use the nios2-configure-sof tool:
18 .pof file which will then put the image onto the device using quartus_pgm tool.
/Zephyr-Core-3.4.0/boards/arm/mimxrt595_evk/
Ddc_ram.ld7 #include <zephyr/linker/linker-tool.h>
/Zephyr-Core-3.4.0/doc/develop/optimizations/
Dtools.rst34 :tool: all
44 :tool: all
61 :tool: all
110 :tool: all
167 Poke-a-hole (pahole) is an object-file analysis tool to find the size of
183 :tool: all
/Zephyr-Core-3.4.0/boards/riscv/gd32vf103v_eval/
Dboard.cmake6 "--device=GD32VF103VBT6" "--iface=jtag" "--tool-opt=-JTAGConf -1,-1"
/Zephyr-Core-3.4.0/boards/riscv/gd32vf103c_starter/
Dboard.cmake6 "--device=GD32VF103CBT6" "--iface=jtag" "--tool-opt=-JTAGConf -1,-1"
/Zephyr-Core-3.4.0/boards/arm/arduino_due/doc/
Dindex.rst140 Flashing the Zephyr kernel onto Arduino Due requires the `bossa tool`_.
142 There are GUI and command line versions of the bossa tool. The following
144 refer to the bossa tool's README file on how to build the GUI version.
146 To build the bossa tool, follow these steps:
148 #. Checkout the bossa tool's code from the repository.
162 #. Build the command line version of the bossa tool.
212 .. _bossa tool: https://github.com/shumatech/BOSSA
/Zephyr-Core-3.4.0/boards/arm/gd32e507z_eval/
Dboard.cmake7 "--device=GD32E507ZE" "--iface=jtag" "--tool-opt=-JTAGConf -1,-1"
/Zephyr-Core-3.4.0/boards/arm/cc1352r_sensortag/
Dboard.cmake6 board_runner_args(jlink "--device=CC1352R1F3" "--iface=jtag" "--tool-opt=-jtagconf -1,-1 -autoconne…

12345678910>>...14