| /Zephyr-Core-3.5.0/scripts/west_commands/tests/ |
| D | test_dediprog.py | 38 def require_patch(program): argument
39 assert program in [DPCMD_EXE]
|
| D | test_gd32isp.py | 37 def require_patch(program): argument
38 assert program in [TEST_GD32ISP_CLI, TEST_GD32ISP_CLI_T]
|
| D | test_stm32flash.py | 60 def require_patch(program): argument
61 assert program == TEST_CMD
|
| D | test_dfu_util.py | 55 def require_patch(program): argument
56 assert program in [DFU_UTIL, TEST_EXE]
|
| D | test_pyocd.py | 155 def require_patch(program): argument
156 assert program in ['pyocd', TEST_PYOCD, RC_GDB]
|
| /Zephyr-Core-3.5.0/samples/boards/mimxrt595_evk_cm33/system_off/ |
| D | README.rst | 72 how program the OTP BOOT_CFG1 fuses to use GPIO pin PIO4_5 as the flash
79 the operation. Then program the OTP fuses after confirming the correct
89 program the OTP fuses. To download, go to https://www.nxp.com/mcuboot,
92 Steps to program OTP fuses on MIMXRT595-EVK
113 blhost -u 0x1fc9,0x0023 -- efuse-program-once 0x61 0x164000
132 >blhost -u 0x1fc9,0x0023 -- efuse-program-once 0x61 0x164000
133 Inject command 'efuse-program-once'
134 Successful generic response to command 'efuse-program-once'
|
| /Zephyr-Core-3.5.0/boards/riscv/adp_xc7k_ae350/doc/ |
| D | index.rst | 225 At first, you should run ICEman when flashing and debugging program.
242 If ``CONFIG_XIP=n``, you can load the program (``zephyr.elf``) into RAM directly
248 # Load the program into RAM and execute it
255 If ``CONFIG_XIP=y``, you need to burn the program (``zephyr.bin``) into flash memory
261 # Burn the program into flash and execute it
291 # Load and debug program
297 If ``CONFIG_XIP=y``, please follow the flashing section to burn the program into
299 Then, you can use GDB to debug program by above commands but do NOT execute ``load``
300 command since the program has been placed in the flash memory.
|
| /Zephyr-Core-3.5.0/samples/boards/bbc_microbit/line_follower_robot/ |
| D | README.rst | 18 for the robot to follow. Build and flash the program to the BBC
36 The sample program controls the robot to follow a line track and does
|
| /Zephyr-Core-3.5.0/drivers/spi/ |
| D | spi_rpi_pico_pio.c | 113 const pio_program_t *program; in spi_pico_pio_configure() local
181 program = RPI_PICO_PIO_GET_PROGRAM(spi_cpol_0_cpha_0); in spi_pico_pio_configure()
185 program = RPI_PICO_PIO_GET_PROGRAM(spi_cpol_1_cpha_1); in spi_pico_pio_configure()
193 if (!pio_can_add_program(data->pio, program)) { in spi_pico_pio_configure()
197 offset = pio_add_program(data->pio, program); in spi_pico_pio_configure()
|
| /Zephyr-Core-3.5.0/boards/arc/iotdk/doc/ |
| D | index.rst | 139 'c' to continue into the program.
175 Most of the time you will not be flashing your program but will instead debug
176 it using openocd and gdb. The program can be download via the USB cable into
179 When you are ready to deploy the program so that it boots up automatically on
180 reset or power-up, you can follow the steps to place the program on SPI-FLASH
183 For instructions on how to write your program to FLASH, refer to the
|
| /Zephyr-Core-3.5.0/subsys/fs/ |
| D | Kconfig.littlefs | 37 int "Minimum size of a block program"
40 All program operations will be a multiple of this value.
47 needs a read cache, a program cache, and one additional cache
50 multiple of the read and program sizes of the underlying flash
|
| /Zephyr-Core-3.5.0/drivers/flash/ |
| D | Kconfig.simulator | 26 bool "Allow program units to be programmed more than once"
28 …If selected, writing to a non-erased program unit will succeed, otherwise, it will return an error.
|
| /Zephyr-Core-3.5.0/boards/arm/stm32h747i_disco/support/ |
| D | openocd_stm32h747i_disco_m7.cfg | 8 # Use connect_assert_srst here to be able to program
|
| /Zephyr-Core-3.5.0/boards/arm/gd32f403z_eval/doc/ |
| D | index.rst | 86 Before program your board make sure to configure boot setting and serial port.
114 allow flash programming and debug over USB. There are also program and debug
125 #. Run your favorite terminal program to listen for output. Under Linux the
186 #. Run your favorite terminal program to listen for output. Under Linux the
|
| /Zephyr-Core-3.5.0/boards/arm/gd32a503v_eval/doc/ |
| D | index.rst | 102 Before program your board make sure to configure boot setting and serial port.
119 allow flash programming and debug over USB. There are also program and debug
130 #. Run your favorite terminal program to listen for output. Under Linux the
190 #. Run your favorite terminal program to listen for output. Under Linux the
|
| /Zephyr-Core-3.5.0/boards/arm/gd32e103v_eval/doc/ |
| D | index.rst | 83 Before program your board make sure to configure boot setting and serial port.
111 allow flash programming and debug over USB. There are also program and debug
122 #. Run your favorite terminal program to listen for output. Under Linux the
183 #. Run your favorite terminal program to listen for output. Under Linux the
|
| /Zephyr-Core-3.5.0/boards/arm/nucleo_h745zi_q/support/ |
| D | openocd.cfg | 9 # Use connect_assert_srst here to be able to program
|
| /Zephyr-Core-3.5.0/boards/arm/nucleo_h7a3zi_q/support/ |
| D | openocd.cfg | 10 # Use connect_assert_srst here to be able to program
|
| /Zephyr-Core-3.5.0/boards/arm/stm32h735g_disco/support/ |
| D | openocd.cfg | 10 # Use connect_assert_srst here to be able to program
|
| /Zephyr-Core-3.5.0/samples/drivers/jesd216/ |
| D | README.rst | 49 Byte program: type 32 + 1 * B us, max 192 + 6 * B us
50 Page program: typ 896 us, max 5376 us
|
| /Zephyr-Core-3.5.0/boards/arm/nucleo_h723zg/support/ |
| D | openocd.cfg | 16 # Use connect_assert_srst here to be able to program
|
| /Zephyr-Core-3.5.0/cmake/linker/lld/ |
| D | target_base.cmake | 38 # So do not create RELRO program header.
|
| /Zephyr-Core-3.5.0/boards/riscv/it8xxx2_evb/doc/ |
| D | index.rst | 152 Use the winflash tool to program a zephyr application
173 it will work if you turn on ITE board. You can use a terminal program
177 terminal program to connect it(Speed: 115200).
189 #. Run your favorite terminal program to listen for output.
|
| /Zephyr-Core-3.5.0/boards/arc/em_starterkit/doc/ |
| D | index.rst | 37 If you have a larger program, you can select the EM7D or EM11D, which gives
124 program image from SPI-Flash into executable memory. Zephyr initialization will
262 'c' to continue into the program.
297 Most of the time you will not be flashing your program but will instead
298 debug it using openocd and gdb. The program can be download via the USB
301 When you are ready to deploy the program so that it boots up automatically
302 on reset or power-up, you can follow the steps to place the program on
305 For instructions on how to write your program to SPI-FLASH,
|
| /Zephyr-Core-3.5.0/cmake/bintools/gnu/ |
| D | target.cmake | 29 set(CMAKE_GDB ${CMAKE_GDB_NO_PY} CACHE FILEPATH "Path to a program." FORCE)
|
