2025-10-12 9:20 AM
I am slowly following along with the user guides and used the software IDE from ST to create a blinker program of the onboard LED. That worked when connected to the ST-Link V2, and it was easy to find the correct pins, but I have the ST-Link V3 set, and I can't tell which pins to use to connect to the blue pill. I have it connected to the MB1440c. So I don't know if i can connect directly to the Blue Pill connectors or if I have to connect to the Blue Pill pins directly. Either way, I would like to overcome this last part. With the VLink 2, I couldn't upload to the Blue Pill, as it gave the 'unable to get to the core ID ST-Link error (DEV_TARGET_CMD_ERR)', and I haven't got that far with the V3 set due to connection confusion.
Help would be very much appreciated, as I am going around in circles with documentation.
2025-10-12 9:25 AM
Ps I noticed that when the v3 is connected to the pc it opend up a folder as if it were a drive.
2025-10-12 9:28 AM
The manual for the ST-Link V3 will show the pinout for the connector.
STLINK-V3SET debugger/programmer for STM8 and STM32 - User manual
You need to connect GND, SWDIO, SWCLK and VCC.
Programmers may not work correctly with boards with counterfeit chips, which 99% of the blue pill boards have, especially when using STM32CubeIDE.
The board needs powered separately--the programmer does not typically provide power.
2025-10-12 9:34 AM
I bought it from Amazon so checked the chip and it has an x on it which I believe denotes a genuine product. Thank you for that I will have a go now.
2025-10-12 9:37 AM
The board needs powered separately--the programmer does not typically provide power. do i plug the usb of the blue pill into the computer too?
2025-10-12 9:48 AM
an error:
18:46:22 : UR connection mode is defined with the HWrst reset mode
18:46:22 : UR connection mode is defined with the SWrst reset mode
18:46:22 : ST-LINK SN : 004000313234510633353533
18:46:22 : ST-LINK FW : V3J16M8B5S1
18:46:22 : Board : STLINK-V3SET
18:46:22 : Voltage : 3.25V
18:46:22 : Error: Unable to get core ID
18:46:22 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication
hopefully this is a step closer