Lines Matching +full:fw +full:- +full:download +full:- +full:speed
1 .. _debug-probes:
12 software supported by Zephyr, see :ref:`flash-debug-host-tools`.
21 an onboard debug probe, usb-to-serial adapter, and sometimes a drag-and-drop
27 `OpenSDA <#opensda-onboard-debug-probe>`_,
28 `LPC-Link2 <#lpc-link2-onboard-debug-probe>`_, or
29 `MCU-Link <#mcu-link-onboard-debug-probe>`_, probes depending on
31 ST boards have the `ST-LINK probe <#stlink-v21-onboard-debug-probe>`_. Each
35 with pyOCD or OpenOCD debug host tools, or with J-Link firmware to communicate
36 with J-Link debug host tools.
39 +------------------------------------------+-------------------------------------------------------…
41 …art* +--------------------+--------------------+---------------------+----------…
42 | | **J-Link Debug** | **OpenOCD** | **pyOCD…
43 +----------------+-------------------------+--------------------+--------------------+-------------…
44 | | **J-Link External** | ✓ | ✓ | …
45 … +-------------------------+--------------------+--------------------+-------------------…
46 | | **LPC-Link2 CMSIS-DAP** | | | …
47 … +-------------------------+--------------------+--------------------+-------------------…
48 | | **LPC-Link2 J-Link** | ✓ | | …
49 … +-------------------------+--------------------+--------------------+-------------------…
50 | | **MCU-Link CMSIS-DAP** | | | …
51 …g Probes +-------------------------+--------------------+--------------------+-------------------…
52 | | **MCU-Link J-Link** | ✓ | | …
53 … +-------------------------+--------------------+--------------------+-------------------…
55 … +-------------------------+--------------------+--------------------+-------------------…
57 … +-------------------------+--------------------+--------------------+-------------------…
58 | | **OpenSDA J-Link** | ✓ | | …
59 … +-------------------------+--------------------+--------------------+-------------------…
60 | | **ST-LINK/V2-1** | ✓ | ✓ | *some STM32 …
61 +----------------+-------------------------+--------------------+--------------------+-------------…
69 debuggers or high-speed tracing. You may need to adjust jumpers to prevent the
72 .. _nxp-onboard-debug-probes:
78 the :ref:`mcu-link-onboard-debug-probe`, :ref:`lpc-link2-onboard-debug-probe`
79 and :ref:`opensda-onboard-debug-probe`. Each of these probes is implemented
84 - LPC55S69: :ref:`mcu-link-onboard-debug-probe`
85 - LPC4322: :ref:`lpc-link2-onboard-debug-probe`
86 - MK20: :ref:`opensda-onboard-debug-probe`
89 so this board uses the :ref:`opensda-onboard-debug-probe`.
91 .. _mcu-link-onboard-debug-probe:
93 MCU-Link Onboard Debug Probe
96 The MCU-Link onboard debug probe uses an LPC55S69 SOC. This probe supports
99 - :ref:`mcu-link-cmsis-onboard-debug-probe` (default firmware)
100 - :ref:`mcu-link-jlink-onboard-debug-probe`
102 This probe is programmed using the MCU-Link host tools, which are installed
103 with the :ref:`linkserver-debug-host-tools`. NXP recommends using NXP's
106 .. _mcu-link-cmsis-onboard-debug-probe:
108 MCU-Link CMSIS-DAP Onboard Debug Probe
111 This is the default firmware installed on MCU-Link debug probes. The CMSIS-DAP
114 addition to debug probe functionality, the MCU-Link probes may also provide:
119 #. USB to UART, SPI and/or I2C interfaces (depending on MCU-Link
125 - :ref:`linkserver-debug-host-tools`
127 Once the MCU-Link host tools are installed, the following steps are
128 required to program the CMSIS-DAP firmware:
130 1. Make sure the MCU-Link utility is present on your host machine. This can
131 be done by installing :ref:`linkserver-debug-host-tools`.
133 #. Put the MCU-Link microcontroller into DFU boot mode by attaching the DFU
138 #. Run the ``program_CMSIS`` script, found in the installed MCU-Link ``scripts``
143 .. _mcu-link-jlink-onboard-debug-probe:
145 MCU-Link JLink Onboard Debug Probe
149 as well as a USB-Serial adapter. It is compatible with the following debug host
152 - :ref:`jlink-debug-host-tools`
155 updated. Once the MCU-Link host tools are installed, the following steps are
158 1. Make sure the MCU-Link utility is present on your host machine. This can
159 be done by installing :ref:`linkserver-debug-host-tools`.
161 #. Put the MCU-Link microcontroller into DFU boot mode by attaching the DFU
166 #. Run the ``program_JLINK`` script, found in the installed MCU-Link ``scripts``
171 .. _lpc-link2-onboard-debug-probe:
173 LPC-LINK2 Onboard Debug Probe
176 The LPC-LINK2 onboard debug probe uses an LPC4322 SOC. This probe supports
179 - :ref:`lpclink2-cmsis-onboard-debug-probe`
180 - :ref:`lpclink2-jlink-onboard-debug-probe`
181 - :ref:`lpclink2-daplink-onboard-debug-probe` (default firmware)
184 with the :ref:`linkserver-debug-host-tools`. NXP recommends using NXP's
187 .. _lpclink2-cmsis-onboard-debug-probe:
189 LPC-LINK2 CMSIS DAP Onboard Debug Probe
192 The CMSIS-DAP debug probes allow debugging from any compatible toolchain,
195 As well as providing debug probe functionality, the LPC-Link2 probes also
205 - :ref:`linkserver-debug-host-tools`
207 The probe may be updated to use CMSIS-DAP firmware with the following steps:
210 be done by installing :ref:`linkserver-debug-host-tools`.
212 #. Put the LPC-Link2 microcontroller into DFU boot mode by attaching the DFU
221 .. _lpclink2-jlink-onboard-debug-probe:
223 LPC-Link2 J-Link Onboard Debug Probe
226 .. note:: On some boards, the J-Link probe firmware will no longer power the
231 as well as a USB-Serial adapter. It is compatible with the following debug host
234 - :ref:`jlink-debug-host-tools`
236 The probe may be updated to use the J-Link firmware with the following steps:
241 be done by installing :ref:`linkserver-debug-host-tools`.
243 #. Put the LPC-Link2 microcontroller into DFU boot mode by attaching the DFU
252 .. _lpclink2-daplink-onboard-debug-probe:
254 LPC-Link2 DAPLink Onboard Debug Probe
257 The LPC-Link2 DAPLink firmware is the default firmware shipped on LPC-Link2
259 the :ref:`lpclink2-cmsis-onboard-debug-probe` firmware following the
263 .. _opensda-onboard-debug-probe:
271 - :ref:`opensda-daplink-onboard-debug-probe` (default firmware)
272 - :ref:`opensda-jlink-onboard-debug-probe`
274 .. _opensda-daplink-onboard-debug-probe:
281 - :ref:`pyocd-debug-host-tools`
282 - :ref:`openocd-debug-host-tools`
283 - :ref:`linkserver-debug-host-tools`
286 OpenSDA firmware. NXP provides `OpenSDA DAPLink Board-Specific Firmwares`_.
307 device (debug port), and a mass storage device (drag-and-drop flash
310 .. _opensda-jlink-onboard-debug-probe:
312 OpenSDA J-Link Onboard Debug Probe
317 - :ref:`jlink-debug-host-tools`
319 This probe is realized by programming the OpenSDA microcontroller with J-Link
320 OpenSDA firmware. Segger provides `OpenSDA J-Link Generic Firmwares`_ and
321 `OpenSDA J-Link Board-Specific Firmwares`_, where the latter is generally
322 recommended when available. Board-specific firmwares are required for i.MX RT
345 vendor-specific device (debug port).
347 .. _jlink-external-debug-probe:
349 J-Link External Debug Probe
352 `Segger J-Link`_ is a family of external debug probes, including J-Link EDU,
353 J-Link PLUS, J-Link ULTRA+, and J-Link PRO, that support a large number of
358 - :ref:`jlink-debug-host-tools`
359 - :ref:`openocd-debug-host-tools`
363 .. _stlink-v21-onboard-debug-probe:
365 ST-LINK/V2-1 Onboard Debug Probe
368 ST-LINK/V2-1 is a serial and debug adapter built into all Nucleo and Discovery
375 - :ref:`openocd-debug-host-tools`
376 - :ref:`jlink-debug-host-tools`
380 - :ref:`pyocd-debug-host-tools`
383 to work with J-Link. To do this, SEGGER offers a firmware upgrading the
384 ST-LINK/V2-1 on board on the Nucleo and Discovery boards. This firmware makes
385 the ST-LINK/V2-1 compatible with J-LinkOB, allowing users to take advantage of
386 most J-Link features like the ultra fast flash download and debugging speed or
387 the free-to-use GDBServer.
389 More information about upgrading ST-LINK/V2-1 to JLink or restore ST-Link/V2-1
390 firmware please visit: `Segger over ST-Link`_
392 Flash and debug with ST-Link
399 OpenOCD is available by default on ST-Link and configured as the default flash
402 .. zephyr-app-commands::
403 :zephyr-app: samples/hello_world
406 .. zephyr-app-commands::
407 :zephyr-app: samples/hello_world
410 .. tab:: _`Using Segger J-Link`
412 Once STLink is flashed with SEGGER FW and J-Link GDB server is installed on your
415 Use CMake with ``-DBOARD_FLASH_RUNNER=jlink`` to change the default OpenOCD
416 runner to J-Link. Alternatively, you might add the following line to your
419 .. code-block:: cmake
423 If you use West (Zephyr's meta-tool) you can modify the default runner using
424 the ``--runner`` (or ``-r``) option.
426 .. code-block:: console
428 west flash --runner jlink
432 .. code-block:: console
434 west debug --runner jlink
441 .. code-block:: console
448 SEGGER J-Link V6.30f - Real time terminal output
449 J-Link STLink V21 compiled Jun 26 2017 10:35:16 V1.0, SN=773895351
459 Updating or restoring ST-Link firmware
462 ST-Link firmware can be updated using `STM32CubeProgrammer Tool`_.
464 twister's device-testing option.
466 Once installed, you can update attached board ST-Link firmware with the
469 .. code-block:: console
471 …s java -jar ~/STMicroelectronics/STM32Cube/STM32CubeProgrammer/Drivers/FirmwareUpgrade/STLinkUpgra…
473 Where board_uid can be obtained using twister's generate-hardware-map
477 .. _nxp-s32-debug-probe:
488 host tools as in indicated in :ref:`nxp-s32-debug-host-tools` before you program
495 https://www.segger.com/products/debug-probes/j-link/models/other-j-links/lpcxpresso-on-board/
497 .. _OpenSDA DAPLink Board-Specific Firmwares:
500 .. _OpenSDA J-Link Generic Firmwares:
503 .. _OpenSDA J-Link Board-Specific Firmwares:
506 .. _Segger J-Link:
507 https://www.segger.com/products/debug-probes/j-link/
509 .. _Segger over ST-Link:
510 https://www.segger.com/products/debug-probes/j-link/models/other-j-links/st-link-on-board/
513 https://www.segger.com/jlink-rtt.html
516 https://www.st.com/en/development-tools/stm32cubeprog.html
522 https://www.nxp.com/design/software/automotive-software-and-tools/s32-debug-probe:S32-DP
525 https://www.nxp.com/docs/en/application-note/AN13206.pdf
528 https://os.mbed.com/blog/entry/DAPLink-bootloader-update/