Supports DapLink/STLink/JLink programmers

Common programmers used for programming ARM core microcontrollers include ST-Link, J-Link, and DAP-Link.
 
Hardware Design:
1. Uses a Type-C interface, adds indicator lights, power output switching, a reset button, anti-backflow Schottky diodes, and a resettable fuse.
2. Two SWD interfaces: Interface 1 uses a 2.54mm pin header, with the common pinout as 3V3--SWD---SCK---GND. Interface 2 uses an MX1.25-4p connector (purchased with a 16-15 coupon). This design utilizes
three solutions, all supporting virtual serial ports. It allows for direct programming and serial port debugging.
4. The pin configuration is compatible with ST-Link, J-Link, and DAP-Link.
 
Component availability, price, and soldering difficulty:
1. Common components are used, mostly obtainable from platform vendors with a 16-15 coupon, reducing personal DIY costs. (Thanks to LCSC!)
2. The components are arranged somewhat densely, requiring a steady hand for soldering. Solder paste and heating plate are relatively simple.
Apply solder
paste, mount the components, and place them on the heating plate. Key point
complete
 
!!!
Firmware burning and testing
: First, the ST-Link firmware is burned: Two versions are used depending on whether F103CBT6 or F103C8T6 is used.
Version 1: STMF103CBT6, 128k flash version, burning STLinkV2.J28.M18_CB.bin firmware
. I used my old programmer to burn the new one;
opened J-flash Lite
, selected firmware, clicked burn, and the burning was successful.
 
Connect the new programmer to USB; the Link+ LED will stay on. Device Manager will display an STM32 STLink serial bus device.
Testing was performed using OpenOCD configured in the CLion IDE development environment. The ST-Link information was successfully displayed, the firmware version was v2, and the burning was successfully recognized.
The test used ST's official programming tool, ST-LINK Utility, and successfully connected, recognized the MCU core, and successfully programmed it. (Note: The SWD interface must be connected to the MCU to be programmed for a successful connection.)
The new version of ST's official programming tool, STM32CubeProgrammer, also successfully connected and recognized it. (Note: The SWD interface must be connected to the MCU to be programmed for a successful connection.)
Firmware upgrade:
Using the upgrade tool included with the new version of ST's official programming tool, STM32CubeProgrammer,
the firmware was upgraded based on this version. Click "Open in update made" several times until the new firmware version appears, then click "Upgrade" to complete the upgrade. The upgraded firmware version is V2J45M30.
Now you can happily use ST-LINK.
It can be directly recognized and used in various IDEs without changing the driver. However, the J-Link solution requires driver switching in the OpenOCD and J-FLASH IDEs. The following describes the firmware programming and testing of the J-Link solution.
When the program driver is J-Link, the device displays as J-Link driver. At this time, official supporting programs such as J-FLASH can be used,
but the CLion environment's OpenOCD will not recognize J-Link. In this case, the driver needs to be changed
 
to libusdk. The first time using it, you need to use Zadig to change the program; afterwards, you can directly update and switch the driver in Device Manager.
After updating to the libusdk driver, CLion OpenOCD can recognize and program normally. If you need to use J-Flash, you need to switch the driver back to J-Link. (To avoid this pitfall!!)
 
Serial port tests for both ST-Link and J-Link solutions are normal. The serial port baud rate is set to a maximum of 200000 for stable output.
----Recommended simple connection schemes for SWD:
Self-programming. For the through-hole type, design a 4-pin header interface on the edge of the board, as close to the edge as possible, with the distance from the center of the hole to the edge of the board less than 2.3. This PCB layout is generally easy to achieve.
To facilitate direct programming, pay attention to the pin order. If the interface is located on the right or top of the board, the pin order is GND--SCK--SWA---3V3; the order is reversed on the left and bottom. Otherwise, direct programming via the pin header will be impossible,
or the pins may be blocked by the serial port header. In this case, a programming cable will be required.