Home
last modified time | relevance | path

Searched refs:onto (Results 26 – 50 of 85) sorted by relevance

1234

/Zephyr-latest/boards/olimex/olimexino_stm32/doc/
Dindex.rst351 Flashing Zephyr onto OLIMEXINO-STM32
354 Flashing the Zephyr kernel onto OLIMEXINO-STM32 requires the
/Zephyr-latest/boards/others/promicro_nrf52840/doc/
Dindex.rst72 #. Flash it onto the board. You may need to mount the device.
/Zephyr-latest/boards/st/steval_fcu001v1/doc/
Dindex.rst84 Flashing Zephyr onto the steval_fcu001v1 board requires an external ST-LINK/V2-1 programmer.
/Zephyr-latest/boards/nordic/nrf52840dongle/doc/
Dindex.rst164 #. Flash it onto the board. Note :file:`/dev/ttyACM0` is for Linux; it will be
214 #. Flash it onto the board. Note :file:`/dev/ttyACM0` is for Linux; it will be
293 onto the back side of the board.
/Zephyr-latest/boards/seeed/seeeduino_xiao/doc/
Dindex.rst8 onto 14 pins.
/Zephyr-latest/drivers/clock_control/
DKconfig.stm32102 Allows to output various different clock sources onto the MCO pin
/Zephyr-latest/samples/drivers/video/capture/
DREADME.rst11 device then uses the :ref:`display_api` to display them onto an LCD screen (if any).
/Zephyr-latest/samples/boards/nordic/dynamic_pinctrl/
DREADME.rst16 able to boot onto multiple board revisions.
/Zephyr-latest/cmake/compiler/gcc/
Dtarget.cmake131 # Appending onto any existing values lets users specify
/Zephyr-latest/boards/adafruit/trinket_m0/doc/
Dindex.rst8 onto 5 pins.
/Zephyr-latest/boards/ruuvi/ruuvitag/doc/
Dindex.rst108 The easiest way to flash Zephyr onto a RuuviTag requires an external Ruuvi DEVKIT. More information…
/Zephyr-latest/boards/adafruit/itsybitsy/doc/
Dindex.rst8 and range of I/O broken out onto 21 GPIO pins.
/Zephyr-latest/boards/atmel/sam/sam_e70_xplained/doc/
Dindex.rst53 Flashing the Zephyr project onto SAM E70 MCU requires the `OpenOCD tool`_.
/Zephyr-latest/boards/atmel/sam/sam4e_xpro/doc/
Dindex.rst54 Flashing the Zephyr project onto SAM4E MCU requires the `OpenOCD tool`_.
/Zephyr-latest/boards/atmel/sam/sam_v71_xult/doc/
Dindex.rst59 Flashing the Zephyr project onto SAM V71 MCU requires the `OpenOCD tool`_.
/Zephyr-latest/boards/ezurio/bl654_usb/doc/
Dbl654_usb.rst117 #. Flash it onto the board. Note :file:`/dev/ttyACM0` is for Linux; it will be
/Zephyr-latest/boards/adafruit/itsybitsy_m4_express/doc/
Dindex.rst8 broken out onto 23 GPIO pins.
/Zephyr-latest/boards/adafruit/feather_nrf52840/doc/
Dindex.rst99 Flashing Zephyr onto both the Feather nRF52840 Express and Sense is possible
/Zephyr-latest/samples/drivers/clock_control_litex/
DREADME.rst50 …r it is needed to cast a pointer to structure :c:struct:`litex_clk_setup` onto :c:type:`clock_cont…
/Zephyr-latest/doc/
Dglossary.rst33 Once an application image is loaded onto a board, the image takes control
186 as well as that of its :term:`west projects <west project>` onto your
/Zephyr-latest/boards/seeed/xiao_ble/doc/
Dindex.rst64 header onto the back side of the board.
/Zephyr-latest/doc/services/ipc/ipc_service/
Dipc_service.rst53 To send data between domains or CPUs, an endpoint must be registered onto
/Zephyr-latest/boards/adafruit/nrf52_adafruit_feather/doc/
Dindex.rst81 Flashing Zephyr onto the ``nrf52_adafruit_feather`` board requires an external
/Zephyr-latest/boards/altr/max10/doc/
Dindex.rst151 This provisions the Zephyr kernel and the CPU configuration onto the board,
186 You can either debug a running image that was flashed onto the device in User
/Zephyr-latest/boards/raytac/mdbt50q_db_33/doc/
Dindex.rst92 Flashing and Debugging Zephyr onto the raytac_mdbt50q_db_33/nrf52833 board

1234