[Physical object verified] JLink OB_STM32F103RCT6_Series 2

This hardware design is completely open source and can be used for personal use and not for commercial use . Please respect the spirit of open source hardware!

The software part comes from the Internet . If there is any infringement, please contact me to delete the software attachments.

Friends who like my projects can follow the collection and like it:)

There are 4 issues in this series, and this is the 2nd issue:

The address of the first issue: https://oshwhub.com/duyes/jlink-zui-xiao-ban

Address for the second phase: https://oshwhub.com/duyes/jlink-zui-xiao-wai-wei-ban

The third phase address: https://oshwhub.com/duyes/jlink-zui-xiao-wai-wei-ban_copy

The address of the fourth issue: https://oshwhub.com/duyes/jlink_gd32

 Updated on November 19th:

Yesterday, I manually flashed the old firmware to CBT6. After upgrading Jlink, I used a tool to extract the upgraded firmware. The flashing into RCT6 was successful. Currently, there is no prompt to upgrade, and the speed can still be maintained at 4M. The disadvantage is that the warning window will still pop up in some cases. Friends who like it can test it themselves!

The firmware is in the attachment at the bottom!

Everyone knows that after the epidemic, the price of electronic chips has skyrocketed. The most exaggerated one is STM32F103CBT6. Not to mention the price has doubled several times, and it is not easy to buy! The current price is actually much higher than RCT6! So can RCT6 replace him? . .

I then tested it and found that part of the firmware was available! Now that it works, let’s start using Lichuang EDA to draw the board! ! !

Initially it was still a beta version V1.0, to prevent different hardware designs, a lot of jumpers were set up.

The board was bloated, and after further optimization, version V2.0 came out, which is the version I am currently using!

Here is a brief explanation of this board:

Because I only have STM32F103RCT6 and GD32F103RET6 and no other models, I can't guess whether other F10X or other models can be used.

The picture below is the actual welding diagram. You can weld according to the diagram. The crystal oscillator is Murata Ceramics 3213 8M capacitor. Because of its small size and built-in capacitor, I particularly like it!

JP2 is the output 3.3V short-contact point. Because the output part of this board is not fool-proof, it is easy to cause the target board to burn the MCU due to mis-insertion. So if Jlink does not carry 3.3V, this problem can be avoided to a large extent. If you don't want the output to have 3.3V, you don't need to short this.

JP1 is an LED switch. This hardware can burn two types of firmware currently circulating on the Internet. One is the old version of the firmware. The disadvantage is that when you click on Keil's JLINK configuration interface, a warning window will often pop up. When downloading SWD, there is no pop-up window. The speed is Not bad, it has 4M, but this old version of the firmware still has a very troublesome problem on RCT6. It will prompt to upgrade the JLINK firmware when entering the KEIL configuration. After the upgrade, it needs to continue to prompt for upgrade. In fact, the upgrade fails! In this version of the firmware, JP1 is shorted to the left and in the middle; the other is a new version of the firmware. The disadvantage is that the LED light does not light up at ordinary times. It will light up only when SWD is downloaded, but no warning window will pop up. The speed is low, 2.25M, and this firmware shorts the middle and right sides. Both firmwares can be used on this board.

The one above TYPEC is the JLINK programming port, and RST is only used when the chip is write-protected. The method is based on Baidu, so I won’t explain it in detail.

Because of the upgrade failure, I usually use the new version of firmware for this RCT6. If the speed is lower, just lower it. Better than failing to upgrade. Of course, I have considered using the old version of CBT6 firmware to upgrade first, then extract the upgraded firmware, and then burn it into RCT6 . This is theoretically feasible, but since I also want to make other versions of JLINK, this idea is left to the general public. My friend went to try it :)

Finally, I will upload my own finished picture. If you don’t understand, please click and leave a message.

Engineering friends who like me can follow the collection and like it:)