Searched full:flashed (Results 1 – 25 of 349) sorted by relevance
12345678910>>...14
| /Zephyr-latest/dts/arm/renesas/rcar/gen4/ |
| D | r8a779f0.dtsi | 15 * A custom G4MH/RH850 µC firmware has to be flashed to access them
46 * A custom G4MH/RH850 µC firmware has to be flashed to do that
|
| /Zephyr-latest/samples/subsys/ipc/openamp/ |
| D | sysbuild.cmake | 19 # Make sure MCUboot is flashed first
|
| /Zephyr-latest/samples/drivers/ipm/ipm_mcux/ |
| D | sysbuild.cmake | 19 # Make sure MCUboot is flashed first
|
| /Zephyr-latest/share/sysbuild/images/bootloader/ |
| D | CMakeLists.txt | 13 # Place MCUBoot first in list to ensure it is configured and flashed before other images.
|
| /Zephyr-latest/boards/96boards/carbon/doc/ |
| D | nrf51822.rst | 80 The 96Boards Carbon nRF51 can be flashed using an external SWD
92 flashed to the board.
122 After you've flashed the chip, you can keep debugging using the same
125 "run" at the GDB prompt to restart the program you've flashed.
|
| /Zephyr-latest/samples/drivers/ipm/ipm_esp32/ |
| D | sysbuild.cmake | 28 # Make sure MCUboot is flashed first
|
| /Zephyr-latest/scripts/schemas/ |
| D | soc-schema.yml | 116 If first, will run this command once when the first image is flashed, if
117 last, will run this command once when the final image is flashed.
|
| D | board-schema.yml | 131 If first, will run this command once when the first image is flashed, if
132 last, will run this command once when the final image is flashed.
|
| /Zephyr-latest/tests/boot/with_mcumgr/pytest/ |
| D | test_upgrade.py | 48 1) Device flashed with MCUboot and an application that contains SMP server
99 1) Device flashed with MCUboot and an application that contains SMP server
160 1) Device flashed with MCUboot and an application that contains SMP server
|
| D | test_downgrade_prevention.py | 20 1) Device flashed with MCUboot and an application that contains SMP server.
|
| /Zephyr-latest/samples/subsys/usb/audio/headset/ |
| D | README.rst | 22 After you have built and flashed the sample app image to your board, plug the
|
| /Zephyr-latest/samples/subsys/usb/audio/headphones_microphone/ |
| D | README.rst | 23 After you have built and flashed the sample app image to your board, plug the
|
| /Zephyr-latest/boards/google/dragonclaw/doc/ |
| D | index.rst | 11 connector. MCU can be flashed using μServo or SWD.
|
| /Zephyr-latest/boards/google/icetower/doc/ |
| D | index.rst | 10 connector. MCU can be flashed using μServo or SWD.
|
| /Zephyr-latest/soc/espressif/common/ |
| D | Kconfig.esptool | 35 Mode the flash chip is flashed in, as well as the default mode for the
174 before it is flashed.
|
| D | Kconfig | 23 Output is a single image that should be flashed at an offset defined by used SOC.
|
| /Zephyr-latest/samples/shields/npm1300_ek/doc/ |
| D | index.rst | 36 flashed, you should boot into the shell interface. The ``regulator`` command is
|
| /Zephyr-latest/samples/subsys/ipc/rpmsg_service/ |
| D | README.rst | 15 flashed independently, but sysbuild must be used in order to flash them in one
101 When you reset the development kit after having flashed both the application
|
| /Zephyr-latest/modules/hal_nordic/nrf-regtool/ |
| D | nrf-regtoolConfig.cmake | 51 # UICR must be flashed together with the Zephyr binary.
|
| /Zephyr-latest/boards/altr/max10/doc/ |
| D | index.rst | 186 You can either debug a running image that was flashed onto the device in User
189 Debugging With UFM Flashed Image
251 Debugging With JTAG Flashed Image
267 any) is on the device, but you should have at least flashed a CPU using
|
| /Zephyr-latest/boards/qorvo/decawave_dwm1001_dev/doc/ |
| D | index.rst | 19 flashed, and debugged in the usual way. See :ref:`build_an_application` and
|
| /Zephyr-latest/boards/qorvo/decawave_dwm3001cdk/doc/ |
| D | index.rst | 21 Applications for the ``decawave_dwm3001cdk`` board target can be built, flashed,
|
| /Zephyr-latest/boards/shields/mikroe_wifi_bt_click/doc/ |
| D | index.rst | 78 Once flashed, it is possible to verify the module. While connected, open your preferred
80 initial log and last message should be the version of the AT firmware flashed.
|
| /Zephyr-latest/boards/others/stm32f030_demo/doc/ |
| D | index.rst | 71 flashed in the usual way (see :ref:`build_an_application` and
77 The board can be flashed by using ST-LINKV2 in-circuit debugger and programmer.
|
| /Zephyr-latest/boards/st/stm32l1_disco/doc/ |
| D | index.rst | 137 flashed in the usual way (see :ref:`build_an_application` and
143 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
|
12345678910>>...14
