Searched refs:flashed (Results 26 – 50 of 361) sorted by relevance
12345678910>>...15
| /Zephyr-latest/boards/panasonic/panb511evb/doc/ |
| D | index.rst | 36 be built, flashed, and debugged in the usual way. See
|
| /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/st/nucleo_f031k6/doc/ |
| D | index.rst | 76 flashed in the usual way (see :ref:`build_an_application` and
82 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
|
| /Zephyr-latest/boards/st/nucleo_f042k6/doc/ |
| D | index.rst | 76 flashed in the usual way (see :ref:`build_an_application` and
82 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
|
| /Zephyr-latest/boards/st/stm32f0_disco/doc/ |
| D | index.rst | 69 flashed in the usual way (see :ref:`build_an_application` and
75 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
|
| /Zephyr-latest/boards/st/stm32l4r9i_disco/doc/ |
| D | index.rst | 56 built and flashed in the usual way (see :ref:`build_an_application`
62 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
|
| /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/boards/bytesatwork/bytesensi_l/doc/ |
| D | index.rst | 100 The byteSENSI-L board can be flashed with the SEGGER JLink programmer.
|
| /Zephyr-latest/boards/electronut/nrf52840_blip/doc/ |
| D | index.rst | 84 built and flashed in the usual way (see :ref:`build_an_application`
96 Applications are flashed and run as usual (see :ref:`build_an_application` and
|
| /Zephyr-latest/boards/electronut/nrf52840_papyr/doc/ |
| D | nrf52840_papyr.rst | 93 built and flashed in the usual way (see :ref:`build_an_application`
108 Applications are flashed and run as usual (see :ref:`build_an_application` and
|
| /Zephyr-latest/boards/renesas/ek_ra4w1/doc/ |
| D | index.rst | 83 built, flashed, and debugged in the usual way. See
90 Program can be flashed to EK-RA4W1 via the on-board SEGGER J-Link debugger.
|
| /Zephyr-latest/boards/renesas/ek_ra6m2/doc/ |
| D | index.rst | 73 built, flashed, and debugged in the usual way. See
80 Program can be flashed to EK-RA6M2 via the on-board SEGGER J-Link debugger.
|
| /Zephyr-latest/boards/st/stm32l1_disco/doc/ |
| D | index.rst | 90 flashed in the usual way (see :ref:`build_an_application` and
96 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
|
| /Zephyr-latest/boards/others/stm32_min_dev/doc/ |
| D | index.rst | 48 The board can be flashed by using STLinkV2 with the following connections.
124 built and flashed in the usual way (see :ref:`build_an_application` and
|
| /Zephyr-latest/boards/renesas/fpb_ra4e1/doc/ |
| D | index.rst | 67 built, flashed, and debugged in the usual way. See
74 Program can be flashed to FPB-RA4E1 via the on-board SEGGER J-Link debugger.
|
| /Zephyr-latest/boards/renesas/fpb_ra6e1/doc/ |
| D | index.rst | 68 built, flashed, and debugged in the usual way. See
75 Program can be flashed to FPB-RA6E1 via the on-board SEGGER J-Link debugger.
|
| /Zephyr-latest/boards/renesas/fpb_ra6e2/doc/ |
| D | index.rst | 72 built, flashed, and debugged in the usual way. See
79 Program can be flashed to fpb-RA6E2 via the on-board SEGGER J-Link debugger.
|
| /Zephyr-latest/boards/st/nucleo_l073rz/doc/ |
| D | index.rst | 96 flashed in the usual way (see :ref:`build_an_application` and
102 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
|
| /Zephyr-latest/boards/st/nucleo_l152re/doc/ |
| D | index.rst | 94 flashed in the usual way (see :ref:`build_an_application` and
100 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
|
| /Zephyr-latest/boards/makerbase/mks_canable_v20/doc/ |
| D | index.rst | 74 flashed in the usual way (see :ref:`build_an_application` and
80 The board could be flashed using west.
|
| /Zephyr-latest/boards/st/nucleo_l011k4/doc/ |
| D | index.rst | 85 flashed in the usual way (see :ref:`build_an_application` and
91 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
|
| /Zephyr-latest/boards/st/nucleo_l031k6/doc/ |
| D | index.rst | 84 flashed in the usual way (see :ref:`build_an_application` and
90 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
|
| /Zephyr-latest/boards/st/nucleo_l053r8/doc/ |
| D | index.rst | 94 flashed in the usual way (see :ref:`build_an_application` and
100 The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
|
| /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/boards/qorvo/decawave_dwm1001_dev/doc/ |
| D | index.rst | 19 flashed, and debugged in the usual way. See :ref:`build_an_application` and
|
12345678910>>...15
