Home
last modified time | relevance | path

Searched refs:flashed (Results 176 – 200 of 361) sorted by relevance

12345678910>>...15

/Zephyr-latest/boards/st/nucleo_f303re/doc/
Dindex.rst118 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
/Zephyr-latest/boards/franzininho/esp32s2_franzininho/doc/
Dindex.rst64 must be built (and flashed) at least once.
/Zephyr-latest/boards/st/stm32h735g_disco/doc/
Dindex.rst79 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
/Zephyr-latest/boards/st/stm3210c_eval/doc/
Dindex.rst88 flashed in the usual way (see :ref:`build_an_application` and
/Zephyr-latest/boards/st/stm32373c_eval/doc/
Dindex.rst84 flashed in the usual way (see :ref:`build_an_application` and
/Zephyr-latest/boards/ezurio/bl654_dvk/doc/
Dbl654_dvk.rst75 Applications for the ``bl654_dvk`` board configuration can be built, flashed,
/Zephyr-latest/boards/fanke/fk750m1_vbt6/doc/
Dindex.rst83 Applications for the ``fk750m1_vbt6`` board target can be built and flashed in the usual
/Zephyr-latest/boards/nxp/lpcxpresso11u68/doc/
Dindex.rst100 The LPCXpresso11U68 board can be flashed by using the on-board LPC-Link2 debug
/Zephyr-latest/boards/adafruit/grand_central_m4_express/doc/
Dindex.rst118 In addition to the built-in bootloader, the Grand Central can be flashed and
/Zephyr-latest/boards/adi/max32690fthr/doc/
Dindex.rst94 The MAX32690 MCU can be flashed by connecting an external debug probe to the
/Zephyr-latest/boards/ti/msp_exp432p401r_launchxl/doc/
Dindex.rst105 To debug a previously flashed image, after resetting the board, use the 'debug'
/Zephyr-latest/boards/st/nucleo_f412zg/doc/
Dindex.rst129 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
/Zephyr-latest/samples/boards/espressif/flash_encryption/
DREADME.rst10 Once this feature is enabled, firmware is flashed as plaintext and then the data is encrypted
/Zephyr-latest/samples/shields/npm6001_ek/doc/
Dindex.rst42 flashed, you should boot into the shell interface. The ``npm6001`` command is
/Zephyr-latest/boards/st/stm32h7s78_dk/doc/
Dindex.rst212 flashed in the usual way (see :ref:`build_an_application` and
218 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
/Zephyr-latest/boards/st/nucleo_wb55rg/doc/
Dnucleo_wb55rg.rst146 To operate bluetooth on Nucleo WB55RG, Cortex-M0 core should be flashed with
212 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
/Zephyr-latest/boards/st/nucleo_l552ze_q/doc/
Dnucleol552ze_q.rst233 flashed in the usual way (see :ref:`build_an_application` and
239 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
/Zephyr-latest/boards/st/nucleo_h745zi_q/doc/
Dindex.rst150 Flashing operation will depend on the target to be flashed and the SoC
153 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner
/Zephyr-latest/boards/nxp/mimxrt1170_evk/doc/
Dindex.rst326 To flash a dual core sample, the M4 image must be flashed first, so that it is
327 written to flash. Then, the M7 image must be flashed. The openamp sysbuild
340 image will be built and flashed to the M7 core, which loads and kicks off
/Zephyr-latest/doc/build/sysbuild/
Dindex.rst306 image is flashed in sequence. Extra arguments such as ``--runner jlink`` are
365 perform a full chip erase when flashed. If this option is enabled, then
555 helper Zephyr application to be built and flashed alongside it, but the helper
627 Applications marked as build-only can still be flashed manually, using
770 be configured or flashed in a specific order. For example, if you need some
799 As a result, ``my_sample`` will be flashed after ``sample_a`` and ``sample_b``
/Zephyr-latest/boards/st/nucleo_f207zg/doc/
Dindex.rst147 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
/Zephyr-latest/boards/atmel/sam/sam_e70_xplained/doc/
Dindex.rst58 the ROM, not the flashed image. This is determined by the value of GPNVM1
/Zephyr-latest/boards/atmel/sam/sam4e_xpro/doc/
Dindex.rst56 the ROM, not the flashed image. This is determined by the value of GPNVM1
/Zephyr-latest/boards/atmel/sam/sam_v71_xult/doc/
Dindex.rst61 located in the ROM, not the flashed image. This is determined by the value
/Zephyr-latest/boards/u-blox/ubx_evkannab1/doc/
Dindex.rst109 built and flashed in the usual way (see :ref:`build_an_application`

12345678910>>...15