Hardware layout and configuration
UM2408
16/45
UM2408 Rev 1
6.3
Program and Debug the on-board STM32H7 target
There are two different ways to Program/Debug the on-board STM32H7 MCU.
•
Using the embedded ST-LINK/V3
•
Using an external debug tool
6.3.1
Using the ST-LINK/V3 to program and debug the on-board STM32H7
Features
The ST-LINK/V3 programming and debugging tool is integrated in the STM32H7 Nucleo-
144 board.
The ST-LINK/V3 makes the STM32H7 Nucleo-144 board Mbed enabled.
The embedded ST-LINK/V3 supports:
•
5 V power supplied by USB connector (CN1)
•
USB 2.0 high-speed-compatible interface
•
JTAG/serial wire debugging (SWD) specific features:
–
3 V to 3.6 V application voltage on the JTAG/SWD interface and 5 V tolerant
inputs
–
JTAG
–
SWD and serial viewer (SWV) communication
•
Direct firmware update feature (DFU) (CN2)
•
STDC14 (MIPI10) compatible connector (CN5)
•
Status COM LED (LD4) which blinks during communication with the PC
•
Fault red LED (LD6) alerting on USB overcurrent request
•
5 V/500 mA output power supply capability (U2) with current limitation and LED
•
Green LED ON: 5 V enabled (LD5)
How to use
It is very easy to use the ST-LINK/V3 to program and debug the on-board STM32H7.
1.
Verify that the jumper JP2 of Power Supply Sources is correctly set. (see chapter 2.3)
2. Connect the board to a PC with a USB cable 'type A to micro-B' through the USB
connector CN1.
Note:
For more details regarding the ST-LINK/V3 functionalities, see the ST-LINK/V3 User Manual
on
www.st.com
website
Drivers
Before connecting the product via USB to a PC running on Windows 7 or 8, a driver for the
ST-LINK/V3 must be installed (not require for Windows 10). It is available on
www.st.com
website.
In case the STM32H7 Nucleo-144 board is connected to the PC before installing the driver,
the PC device manager may report some Nucleo interfaces as “Unknown”.
To recover from this situation, after installing the dedicated driver, the association of
“Unknown” USB devices found on the STM32H7 Nucleo-144 board to this dedicated driver,
must be updated in the device manager manually.
