Searched refs:onto (Results 51 – 75 of 85) sorted by relevance
1234
92 Flashing and Debugging Zephyr onto the raytac_mdbt50q_db_40/nrf52840 board
143 Load the M4 binary onto the desired memory and start its execution using:
113 Flashing the Zephyr kernel onto Arduino Due requires the `bossa tool`_.
208 the ST-LINK onto the ArgonKey.
221 Flashing Zephyr onto 96Boards Nitrogen
153 #. Flash it onto the board as described in Option 1.
137 Flashing and Debugging Zephyr onto the raytac_mdbt53v_db_40_nrf5340 board
61 * `Dev-Install: Installing Developer and Test packages onto a Chrome OS device <https://www.chromiu…
92 pointer onto the stack as a standard "frame pointer" defined in the
133 Flashing and Debugging Zephyr onto the raytac_mdbt53_db_40_nrf5340 board
354 Flashing Zephyr onto Thingy:52 requires an external J-Link programmer. The
182 This provisions the Zephyr kernel and the CPU configuration onto the board,211 You can either debug a running image that was flashed onto the device in User
224 Load the M4 binary onto the desired memory and start its execution using:
175 instance by adding the ``zephyr,pm-device-runtime-auto`` flag onto the corresponding
69 #. Flash built image onto board and reset the board.
183 Load the M4 binary onto the desired memory and start its execution using:
138 {-r,--rebase}'[rebase checked out branch onto the new manifest-rev]'
27 sample application that can be flashed onto the nRF51822
115 - Used for mounting onto the pin headers on the main board.
191 In the event that a thread pushes more data onto its execution stack than its
205 Load the M7 binary onto the desired memory and start its execution using:
146 same firmware image that is programmed onto the chip):
214 Load the M7 binary onto the desired memory and start its execution using:
288 executable image onto the SPI-FLASH in such a way that it is understood
163 - Flash the binary onto the device to run the sample: