Stm32World Wiki - User contributions [en]

External and Timer Interrupts

2026-10-20T06:51:15Z

Lth: Created page with "{{Video |series=STM32 Remake Video |number=4 |title=External and Timer Interrupts |youtube-id=g_MSOaPuJvM |description=2026 Remake of STM32 Tutorial #6 covering STM32 Interrup..."

{{Video
|series=STM32 Remake Video
|number=4
|title=External and Timer Interrupts
|youtube-id=g_MSOaPuJvM
|description=2026 Remake of STM32 Tutorial #6 covering STM32 Interrupts. We will cover both external interrupts (EXTI) and TImer Interrupts.
}}

Raspberry Pi Pico

2026-10-16T01:47:23Z

Lth: /* Miscellaneous Documentation */

[[Category:Raspberry Pi Pico]][[File:Third party RP2350 Board w. USB-C.jpg|thumb|300px|Third party RP2350 board w. USB-C]]
The [[Raspberry Pi Pico]] is a [[Category:Development Board|Development Board]] based upon either the [[RP2040]] or the [[RP2350]] [[MCU]].

== Video ==

We created a separate channel for [[RP2350]] related video: [https://youtube.com/@RPPicoWorld https://youtube.com/@RPPicoWorld]

{{#ev:youtube|7JMziWYkwSg}}

== MCU Variants ==

=== RP2040 ===

To be added

=== RP2350 ===

<div class="res-img">
[[File:Raspberry-Pi-RP2350-Block-Diagram.jpg|1200px]]
</div>

<div class="res-img">
[[File:RP2350 Block Diagram.jpg|1000px]]
</div>

== SDK ==

The SDK is available at [https://github.com/raspberrypi/pico-sdk Github]. To use, the easiest approach is to clone this repository:

<pre>
git clone --recursive git@github.com:raspberrypi/pico-sdk.git
</pre>

== USB Flashing ==

The [[Raspberry Pi Pico]] is equipped with a [[Micro-USB]] connector and it can be flashed with simple drag and drop.

== Picoprobe ==

The [[Raspberry Pi Pico]]

== Miscellaneous Documentation ==

* [https://github.com/STM32World/stm32fun_pico STM32World RP2350 Examples]
* [https://en.wikipedia.org/wiki/RP2040 Wikipedia article on R{2040]
* [https://en.wikipedia.org/wiki/RP2350 Wikipedia article on RP2350]
* [https://datasheets.raspberrypi.com/rp2040/rp2040-datasheet.pdf RP2040 Datasheet]
* [https://stm32world.com/images/3/3c/RP-008373-DS-2-rp2350-datasheet.pdf RP2350 Datasheet]
* [https://stm32world.com/images/c/c2/RP-008280-DS-2-hardware-design-with-rp2350.pdf Hardware Design with RP2350]
* [https://datasheets.raspberrypi.com/pico/pico-datasheet.pdf Raspberry Pi Pico Datasheet]
* [https://datasheets.raspberrypi.com/rp2040/hardware-design-with-rp2040.pdf Hardware Design with RP2040]

File:RP-008280-DS-2-hardware-design-with-rp2350.pdf

2026-10-16T01:46:23Z

Lth:

Streamline MCU RP2354

2026-10-15T00:21:30Z

Lth:

[[Category:RP2350]][[Category:Streamline]][[Category:Streamline Blade]]{{metadesc|RP2354 Streamline MCU board documentation}}
[[File:Streamline RP2350 setup - top left.jpg|350px|thumb|Streamline backplane with Connect and MCU RP2354]]
The [[Streamline MCU RP2354]] is a basic [[Streamline]] [[RP2354]] [[MCU]] board build around a [[RP2354]].

The [[Streamline]] backplane pin mapping was originally build around 100-pin [[STM32]] [[MCU]]s, so fitting that to [[RP2350]] took some juggling. See:

* [[Streamline Header Mapping]]
* [[Streamline Peripheral Pin Mapping]]
{{clear}}

== Videos ==

In order not to "pollute" the STM32World channel, we made another channel for RP2350 stuff. You can access this channel here: [https://www.youtube.com/@RPPicoWorld/videos https://www.youtube.com/@RPPicoWorld].

One of the first videos using the [[Streamline MCU RP2354]]:

{{#ev:youtube|z-0-4W92aTU}}

== Schematics ==

<div class="res-img">
[[File:sl_mcu_rp2354.svg|2000px]]
</div>

== Errata ==

The [[Streamline MCU RP2354]] has gone through a number of revisions. The current version is rev. D.

=== Rev. D ===

One mistake was made with the onboard LED. It is connected to the PC13 pin on the header but it is '''not''' connected to the MCU. This is easily fixed with a jumper on the header - like this:

<div class="res-img">
[[File:Rev D Fix 3.jpg|600px]]
</div>

<gallery>
File:Rev D Fix 1.jpg
File:Rev D Fix 2.jpg
File:Rev D Fix 3.jpg
File:Rev D Fix 4.jpg
</gallery>

== Gallery ==

<gallery>
File:sl_mcu_rp2354_top_right_render.png
File:sl_mcu_rp2354_top_render.png
File:sl_mcu_rp2354_top_left_render.png
File:sl_mcu_rp2354_bot_render.png
File:Streamline RP2350 setup - top left.jpg
File:Streamline RP2350 setup - top right.jpg
File:Streamline RP2350 setup - top right 2.jpg
</gallery>

STM32World Legacy

2026-10-12T13:50:16Z

Lth:

[[Category:STM32]][[Category:STM32World]][[Category:Work in progress]]{{metadesc|STM32World Development Boards Home}}
[[File:mcu board 3d.png|thumb|200px]]
Notice, [[STM32World]] is no longer under active development. Check [[Streamline]] instead.

[[STM32World]] is a series of development boards designed for rapid development and prototyping.

The idea is to have MCU boards available with multiple MCU's (possibly including non [[ST]] ones such as the ones from [[GigaDevice]]).

The boards will be stackable but rather than trying to cram every single imaginable peripheral device into every board, these will be deliberately kept simple. A CAN transceiver board will include a CAN transceiver and nothing else.

As much as possible, peripheral board will be designed in such a way that they will not conflict with each other, even though this might not be possible to achieve 100 %.

All files for hardware and software is available at [https://github.com/STM32World STM32World Github Repository]

== Why? ==

There are a gazillion [[STM32]] development boards available on the market. A very reasonable question would be: "Why create another one?"

In general development boards fall into two different categories:

# Simple boards such as the common [[Blue Pill]] and [[Black Pill]] boards
# Complex boards such as most of [[ST]]'s Nucleo and Discovery boards

The problem with the simple boards is that you have a very limited selection of [[MCU]]s and you end up with a ratnest of jumper wires.

The problem with the complex boards is that they are too opinionated. I have a [[STM32F405]] based discovery board and that one includes a complex audio part, which I have never needed nor used.

== [[STM32World Form Factor|Form Factor]] ==

[[STM32World]] boards are meant to be stackable.

All boards are 3" x 2". In many cases this is much bigger than needed but PCB's are cheap and having the boards at that size makes layout much easier.

<div class="res-img">
[[File:STM32World Board Dimensions.png|800px]]
</div>

The choice of imperial size of the PCB's themselves were mainly made due to the header being 100 mil spaced pins.

== Planned Boards ==

{| class=wikitable
|-
!
! Name
! Type
! Description
! Status
|-
| [[File:MCUSTM32F405 3D Top View.png|200px]]
| [[MCUSTM32F405]]
| MCU
| MCU Board using the [[STM32F405]] [[MCU]]
| Prototype
|-
| [[File:MCUSTM32F405 3D Top View.png|200px]]
| [[MCUSTM32F402]]
| MCU
| MCU Board using the [[STM32F402]] [[MCU]]
| Under development
|-
| [[File:PRGSTL 3D Top View.png|200px]]
| [[PRGSTL]]
| Programmer
| Board designed like a [[ST-Link|ST-Link/V2.1]] or a [[Black Magic Probe]] device
| Prototype
|-
| [[File:MEMW25Q128 3D Top View rendering.png|200px]]
| [[MEMW25Q128]]
| Storage
| [[W25Qxx|W25Q128]] SPI Serial Flash
| Prototype
|-
| [[File:MEM24CXX Rendering Top.png|200px]]
| [[MEM24CXX]]
| Storage
| [[24Cxx I²C EEPROM]]
| Prototype
|-
| [[File:proto_top_rendering.png|200px]]
| [[PROTO]]
| Prototyping
| Prototyping board
| Prototype
|-
| [[File:CAN Rendering - top view.png|200px]]
| [[CANTRANS]]
| Tranceiver
| Dual CAN Transceiver
| Prototype
|-
| [[File:STWSD Top Rendering.png|200px]]
| [[STWSD]]
| SD Card
| SD Card breakout
| Under development
|-
| [[File:DWS2812 Top Rendering.png|200px]]
| [[DWS2812]]
| Display
| [[WS2812B]] RGB LED Array
| Under development
|}

== Board Ideas ==

{| class=wikitable
|-
!
! Name
! Type
! Description
! Status
|-
| [[File:MCUSTM32F411 3D Top View.png|200px]]
| [[MCUSTM32F411]]
| MCU
| MCU Board using the [[STM32F411]] [[MCU]]
| Under development
|-
| [[File:MCUSTM32F446 3D rendering - top view.png|200px]]
| [[MCUSTM32F446]]
| MCU
| MCU Board using the [[STM32F446]] [[MCU]]
| Ready for prototype
|-
| [[File:MCUSTM32F103 3D Top View.png|200px]]
| [[MCUSTM32F103]]
| MCU
| MCU Board using the [[STM32F103]] [[MCU]]
| Under development
|-
| [[File:MCUSTM32F405 3D Top View.png|200px]]
| [[MCUGD32F405]]
| MCU
| MCU Board using the [[GD32F405]] [[MCU]]
| Under development
|-
|[[File:IOAW9523 3D Top View rendering.png|200px]]
| [[IOAW9523]]
| I/O
| [[I²C]] [[AW9523B GPIO Expander|AW9523]] based GPIO Expander and LED driver
| Under development
|-
|
| [[HID01]]
| Display/Keyboard
| Display and touch keyboard
| Under development
|-
|
| [[SEC01]]
| Security
| Security and Encryption
| Under development
|}

== Pin Use ==

The [[STM32]] processors are not 100 % flexible in mapping I/O pins, so certain peripherals can only be mapped to certain pins. Because of that, some of our board will conflict with each other.

{{STM32World Pinout}}

== Gallery ==

<gallery>
File:3 STM32World Modules - backside.jpg
File:3 STM32World Modules stacked 2.jpg
File:3 STM32World Modules stacked.jpg
File:3 STM32World Modules with headers.jpg
File:3 STM32World Modules.jpg
File:MCUSTM32F405 and MEMW25Q128.jpg
File:MCUSTM32F405 angle.jpg
File:MCUSTM32F405 Bot.jpg
File:MCUSTM32F405 Top.jpg
File:MCUSTM32F405 with headers.jpg
File:MEMW25Q128 Bot.jpg
File:MEMW25Q128 wiith headers.jpg
File:MEMW25Q128 Top.jpg
File:PRGSTL and MCUSTM32F405.jpg
File:PRGSTL Bot.jpg
File:PRGSTL Side.jpg
File:PRGSTL Top.jpg
File:PRGSTL with headers.jpg
</gallery>

PRGSTL

2026-10-12T13:49:00Z

Lth:

[[Category:STM32]][[Category:STM32World]][[Category:Work in progress]]{{metadesc|STM32World Programmer}}
NOTICE! The [[STM32World]] modules are no longer being developed. Check [[Streamline]] instead, - more specifically the [[Streamline Connect]].

[[PRGSTL]] is a programmer, that is Flashing and Debugging, for the [[STM32World]] [[:Category:STM32World MCU|MCU]] modules.

== Schematics ==

<div class="res-img">
[[File:prgstl rev a.svg]]
</div>

== Firmware ==

Unfortunately [[ST]]'s [[ST-Link]] firmware is not open source, so we can not distribute the [[PRGSTL]] modules pre-programmed. Instead, we deliver the [[PRGSTL]] module with a [[DFU]] bootloader, so that it can itself be flashed over USB.

== Gallery ==
<gallery>
File:PRGSTL Bot.jpg
File:PRGSTL Side.jpg
File:PRGSTL Top.jpg
File:PRGSTL with headers.jpg
</gallery>

PRGSTL

2026-10-12T13:47:36Z

Lth:

[[Category:STM32]][[Category:STM32World]][[Category:Work in progress]]{{metadesc|STM32World Programmer}}
NOTICE! The [[STM32World]] modules are no longer being developed. Check [[Streamline]] instead.

[[PRGSTL]] is a programmer, that is Flashing and Debugging, for the [[STM32World]] [[:Category:STM32World MCU|MCU]] modules.

== Schematics ==

<div class="res-img">
[[File:prgstl rev a.svg]]
</div>

== Firmware ==

Unfortunately [[ST]]'s [[ST-Link]] firmware is not open source, so we can not distribute the [[PRGSTL]] modules pre-programmed. Instead, we deliver the [[PRGSTL]] module with a [[DFU]] bootloader, so that it can itself be flashed over USB.

== Gallery ==
<gallery>
File:PRGSTL Bot.jpg
File:PRGSTL Side.jpg
File:PRGSTL Top.jpg
File:PRGSTL with headers.jpg
</gallery>

STM32 In-circuit Debugging

2026-10-12T11:33:08Z

Lth: Created page with "{{Video |series=STM32 Remake Video |number=3 |title=STM32 In-circuit Debugging |youtube-id=S9w6YEkzf-k |description=2026 Remake of STM32 Tutorial #5 covering STM32 in-circuit..."

{{Video
|series=STM32 Remake Video
|number=3
|title=STM32 In-circuit Debugging
|youtube-id=S9w6YEkzf-k
|description=2026 Remake of STM32 Tutorial #5 covering STM32 in-circuit debugging. We will cover Serial print, SWD and SWO.
}}

File:Jolt Connect and Black Pill.jpg

2026-10-12T01:01:09Z

Lth: Lth uploaded a new version of File:Jolt Connect and Black Pill.jpg

File uploaded with MsUpload

File:Jolt Connect and Black Pill.jpg

2026-10-12T00:53:24Z

Lth: Lth uploaded a new version of File:Jolt Connect and Black Pill.jpg

File uploaded with MsUpload

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T23:36:04Z

Lth: /* Connecting to target */

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype.]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

Contrary to the official [[ST-Link]], the pins on the [[Jolt Connect]] are clearly labelled.

{{clear}}

== Connecting to target ==
[[File:Jolt Connect and Black Pill.jpg|300px|thumb|Jolt Connect and a Blackpill board. Not wired up - yet.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

{| class="wikitable"
! Jolt Connect
! Signal
! Black Pill
! Notes
|-
| Pin 2 (3.3V)
| 3.3V
| Any 3.3V
| The Jolt Connect can drive up to around 500 mA. If the target is powered, for example via USB, this connection can be left out.
|-
| Pin 4
| GND
| GND
| Common ground. This is absolutely essential.
|-
| Pin 5
| SWCLK
| PA14
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 6
| SWDIO
| PA13
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 7
| SWO
| PB3
| Optional if trace functionality is required.
|-
| Pin 8
| RST
| R
| NRST Hardware reset target. This connection is almost never required and can safely be ignored.
|-
| Pin 9
| TX
| PA10
| Serial connection FROM the [[Jolt Connect]] to the target. If only used for printf debugging, this connection can be ignored.
|-
| Pin 10
| RX
| PA9
| Serial data from the target to the Jolt Connect.
|}

{{clear}}

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T23:35:34Z

Lth: /* Connecting to target */

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype.]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

Contrary to the official [[ST-Link]], the pins on the [[Jolt Connect]] are clearly labelled.

{{clear}}

== Connecting to target ==
[[File:Jolt Connect and Black Pill.jpg|300px|thumb|Jolt Connect and a Blackpill board.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

{| class="wikitable"
! Jolt Connect
! Signal
! Black Pill
! Notes
|-
| Pin 2 (3.3V)
| 3.3V
| Any 3.3V
| The Jolt Connect can drive up to around 500 mA. If the target is powered, for example via USB, this connection can be left out.
|-
| Pin 4
| GND
| GND
| Common ground. This is absolutely essential.
|-
| Pin 5
| SWCLK
| PA14
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 6
| SWDIO
| PA13
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 7
| SWO
| PB3
| Optional if trace functionality is required.
|-
| Pin 8
| RST
| R
| NRST Hardware reset target. This connection is almost never required and can safely be ignored.
|-
| Pin 9
| TX
| PA10
| Serial connection FROM the [[Jolt Connect]] to the target. If only used for printf debugging, this connection can be ignored.
|-
| Pin 10
| RX
| PA9
| Serial data from the target to the Jolt Connect.
|}

{{clear}}

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

File:Jolt Connect and Black Pill.jpg

2026-10-11T23:34:26Z

Lth: File uploaded with MsUpload

File uploaded with MsUpload

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T11:11:12Z

Lth: /* Pinout */

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype.]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

Contrary to the official [[ST-Link]], the pins on the [[Jolt Connect]] are clearly labelled.

{{clear}}

== Connecting to target ==
[[File:Blackpill with st-link.jpg|300px|thumb|Blackpill board with [[DIY STM32 Programmer (ST-Link/V2-1)|ST-Link]] - SWD, SWO and UART hooked up. The Jolt Connect has got an identical connector.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

{| class="wikitable"
! Jolt Connect
! Signal
! Black Pill
! Notes
|-
| Pin 2 (3.3V)
| 3.3V
| Any 3.3V
| The Jolt Connect can drive up to around 500 mA. If the target is powered, for example via USB, this connection can be left out.
|-
| Pin 4
| GND
| GND
| Common ground. This is absolutely essential.
|-
| Pin 5
| SWCLK
| PA14
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 6
| SWDIO
| PA13
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 7
| SWO
| PB3
| Optional if trace functionality is required.
|-
| Pin 8
| RST
| R
| NRST Hardware reset target. This connection is almost never required and can safely be ignored.
|-
| Pin 9
| TX
| PA10
| Serial connection FROM the [[Jolt Connect]] to the target. If only used for printf debugging, this connection can be ignored.
|-
| Pin 10
| RX
| PA9
| Serial data from the target to the Jolt Connect.
|}

{{clear}}

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T11:10:15Z

Lth: /* Pinout */

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype.]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

{{clear}}

== Connecting to target ==
[[File:Blackpill with st-link.jpg|300px|thumb|Blackpill board with [[DIY STM32 Programmer (ST-Link/V2-1)|ST-Link]] - SWD, SWO and UART hooked up. The Jolt Connect has got an identical connector.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

{| class="wikitable"
! Jolt Connect
! Signal
! Black Pill
! Notes
|-
| Pin 2 (3.3V)
| 3.3V
| Any 3.3V
| The Jolt Connect can drive up to around 500 mA. If the target is powered, for example via USB, this connection can be left out.
|-
| Pin 4
| GND
| GND
| Common ground. This is absolutely essential.
|-
| Pin 5
| SWCLK
| PA14
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 6
| SWDIO
| PA13
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 7
| SWO
| PB3
| Optional if trace functionality is required.
|-
| Pin 8
| RST
| R
| NRST Hardware reset target. This connection is almost never required and can safely be ignored.
|-
| Pin 9
| TX
| PA10
| Serial connection FROM the [[Jolt Connect]] to the target. If only used for printf debugging, this connection can be ignored.
|-
| Pin 10
| RX
| PA9
| Serial data from the target to the Jolt Connect.
|}

{{clear}}

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T10:30:20Z

Lth:

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype.]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized mostly in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

{{clear}}

== Connecting to target ==
[[File:Blackpill with st-link.jpg|300px|thumb|Blackpill board with [[DIY STM32 Programmer (ST-Link/V2-1)|ST-Link]] - SWD, SWO and UART hooked up. The Jolt Connect has got an identical connector.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

{| class="wikitable"
! Jolt Connect
! Signal
! Black Pill
! Notes
|-
| Pin 2 (3.3V)
| 3.3V
| Any 3.3V
| The Jolt Connect can drive up to around 500 mA. If the target is powered, for example via USB, this connection can be left out.
|-
| Pin 4
| GND
| GND
| Common ground. This is absolutely essential.
|-
| Pin 5
| SWCLK
| PA14
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 6
| SWDIO
| PA13
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 7
| SWO
| PB3
| Optional if trace functionality is required.
|-
| Pin 8
| RST
| R
| NRST Hardware reset target. This connection is almost never required and can safely be ignored.
|-
| Pin 9
| TX
| PA10
| Serial connection FROM the [[Jolt Connect]] to the target. If only used for printf debugging, this connection can be ignored.
|-
| Pin 10
| RX
| PA9
| Serial data from the target to the Jolt Connect.
|}

{{clear}}

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T02:42:13Z

Lth: /* Connecting to target */

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype - final device will be black]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized mostly in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

{{clear}}

== Connecting to target ==
[[File:Blackpill with st-link.jpg|300px|thumb|Blackpill board with [[DIY STM32 Programmer (ST-Link/V2-1)|ST-Link]] - SWD, SWO and UART hooked up. The Jolt Connect has got an identical connector.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

{| class="wikitable"
! Jolt Connect
! Signal
! Black Pill
! Notes
|-
| Pin 2 (3.3V)
| 3.3V
| Any 3.3V
| The Jolt Connect can drive up to around 500 mA. If the target is powered, for example via USB, this connection can be left out.
|-
| Pin 4
| GND
| GND
| Common ground. This is absolutely essential.
|-
| Pin 5
| SWCLK
| PA14
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 6
| SWDIO
| PA13
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 7
| SWO
| PB3
| Optional if trace functionality is required.
|-
| Pin 8
| RST
| R
| NRST Hardware reset target. This connection is almost never required and can safely be ignored.
|-
| Pin 9
| TX
| PA10
| Serial connection FROM the [[Jolt Connect]] to the target. If only used for printf debugging, this connection can be ignored.
|-
| Pin 10
| RX
| PA9
| Serial data from the target to the Jolt Connect.
|}

{{clear}}

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T02:31:24Z

Lth: /* Connecting to target */

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype - final device will be black]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized mostly in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

{{clear}}

== Connecting to target ==
[[File:Blackpill with st-link.jpg|300px|thumb|Blackpill board with [[DIY STM32 Programmer (ST-Link/V2-1)|ST-Link]] - SWD, SWO and UART hooked up. The Jolt Connect has got an identical connector.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

{| class="wikitable"
! Jolt Connect
! Signal
! Black Pill
! Notes
|-
| Pin 2 (3.3V)
| 3.3V
| Any 3.3V
| The Jolt Connect can drive up to around 500 mA. If the target is powered, for example via USB, this connection can be left out.
|-
| Pin 4
| GND
| GND
| Common ground. This is absolutely essential.
|-
| Pin 5
| SWCLK
| PA14
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 6
| SWDIO
| PA13
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 7
| SWO
| PB3
| Optional if trace functionality is required.
|-
| Pin 8
| NRST
| R
| Hardware reset target. This connection is almost never required and can safely be ignored.
|-
| Pin 9
| TX
| PA10
| Serial connection FROM the [[Jolt Connect]] to the target. If only used for printf debugging, this connection can be ignored.
|-
| Pin 10
| RX
| PA9
| Serial data from the target to the Jolt Connect.
|}

{{clear}}

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T02:09:42Z

Lth: /* Connecting to target */

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype - final device will be black]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized mostly in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

{{clear}}

== Connecting to target ==
[[File:Blackpill with st-link.jpg|300px|thumb|Blackpill board with [[DIY STM32 Programmer (ST-Link/V2-1)|ST-Link]] - SWD, SWO and UART hooked up.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

{| class="wikitable"
! Jolt Connect
! Signal
! Black Pill
! Notes
|-
| Pin 2 (3.3V)
| 3.3V
| Any 3.3V
| The Jolt Connect can drive up to around 500 mA. If the target is powered, for example via USB, this connection can be left out.
|-
| Pin 4
| GND
| GND
| Common ground. This is absolutely essential.
|-
| Pin 5
| SWCLK
| PA14
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 6
| SWDIO
| PA13
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 7
| SWO
| PB3
| Optional if trace functionality is required.
|-
| Pin 8
| NRST
| R
| Hardware reset target. This connection is almost never required and can safely be ignored.
|-
| Pin 9
| TX
| PA10
| Serial connection FROM the [[Jolt Connect]] to the target. If only used for printf debugging, this connection can be ignored.
|-
| Pin 10
| RX
| PA9
| Serial data from the target to the Jolt Connect.
|}

{{clear}}

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T02:04:37Z

Lth: /* Connecting to target */

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype - final device will be black]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized mostly in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

{{clear}}

== Connecting to target ==
[[File:Blackpill with st-link.jpg|300px|thumb|Blackpill board with [[DIY STM32 Programmer (ST-Link/V2-1)|ST-Link]] - SWD, SWO and UART hooked up.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

{| class="wikitable"
! Jolt Connect
! Signal
! Black Pill
! Notes
|-
| Pin 2 (3.3V)
| 3.3V
| Any 3.3V
| The Jolt Connect can drive up to around 500 mA. If the target is powered, for example via USB, this connection can be left out.
|-
| GND
| GND
| GND
| Common ground. This is absolutely essential.
|-
| Pin 5
| SWCLK
| PA14
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 6
| SWDIO
| PA13
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 7
| SWO
| PB3
| Optional if trace functionality is required.
|-
| Pin 8
| NRST
| R
| Hardware reset target. This connection is almost never required and can safely be ignored.
|-
| Pin 9
| TX
| PA10
| Serial connection FROM the [[Jolt Connect]] to the target. If only used for printf debugging, this connection can be ignored.
|-
| Pin 10
| RX
| PA9
| Serial data from the target to the Jolt Connect.
|}

{{clear}}

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T02:02:53Z

Lth: /* Connecting to target */

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype - final device will be black]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized mostly in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

{{clear}}

== Connecting to target ==
[[File:Blackpill with st-link.jpg|300px|thumb|Blackpill board with [[DIY STM32 Programmer (ST-Link/V2-1)|ST-Link]] - SWD, SWO and UART hooked up.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

{| class="wikitable"
! Jolt Connect
! Signal
! Black Pill
! Notes
|-
| Pin 2 (3.3V)
| 3.3V
| Any 3.3V
| The Jolt Connect can drive up to around 500 mA. If the target is powered, for example via USB, this connection can be left out.
|-
| GND
| GND
| GND
| Common ground. This is absolutely essential.
|-
| Pin 5
| SWCLK
| PA14
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 6
| SWDIO
| PA13
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 7
| SWO
| PB3
| Optional if trace functionality is required.
|-
| Pin 9
| TX
| PA10
| Serial connection FROM the [[Jolt Connect]] to the target. If only used for printf debugging, this connection can be ignored.
|-
| Pin 10
| RX
| PA9
| Serial data from the target to the Jolt Connect.
|}

{{clear}}

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T02:00:18Z

Lth: /* Connecting to target */

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype - final device will be black]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized mostly in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

{{clear}}

== Connecting to target ==
[[File:Blackpill with st-link.jpg|300px|thumb|Blackpill board with [[DIY STM32 Programmer (ST-Link/V2-1)|ST-Link]] - SWD, SWO and UART hooked up.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

{| class="wikitable"
! Jolt Connect
! Signal
! Black Pill
! Notes
|-
| Pin 2 (3.3V)
| 3.3V
| Any 3.3V
| The Jolt Connect can drive up to around 500 mA. If the target is powered, for example via USB, this connection can be left out.
|-
| GND
| GND
| GND
| Common ground. This is absolutely essential.
|-
| Pin 5
| SWCLK
| PA14
| On the [[Black Pill]] this pin is on the end connector.
|-
| Pin 6
| SWDIO
| PA13
| On the [[Black Pill]] this pin is on the end connector.
|}

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T01:58:03Z

Lth: /* Connecting to target */

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype - final device will be black]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized mostly in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

{{clear}}

== Connecting to target ==
[[File:Blackpill with st-link.jpg|300px|thumb|Blackpill board with [[DIY STM32 Programmer (ST-Link/V2-1)|ST-Link]] - SWD, SWO and UART hooked up.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

[[File:Jolt Connect to Black Pill.png|400px]]

{| class="wikitable"
! Jolt Connect
! Signal
! Black Pill
! Notes
|-
| Pin 2 (3.3V)
| 3.3V
| Any 3.3V
| The Jolt Connect can drive up to around 500 mA
|}

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

Jolt Connect - STM32 Programmer (ST-Link/V2-1)

2026-10-11T01:56:14Z

Lth: /* Pinout */

[[Category:STM32]][[Category:STM32 Projects]][[Category:KiCAD]][[Category:JLCPCB]][[Category:CurrentMakers]][[Category:Jolt]]{{metadesc|New and improved ST-Link/V2-1 and Black Magic Probe device}}
[[File:JC - top left 2.jpg|300px|thumb|Jolt Connect Prototype - final device will be black]]
Introducing the new and improved [[STM32]] programmer & debugger, the [[CurrentMakers]] [[Jolt Connect]]. The goal for this was to create the perfect [[STM32]] Programming and Debugging tool.

This is our new and greatly improved version. The original is documented here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

BUY [[Jolt Connect]] here: [https://currentmakers.com/products/jolt/jolt_connect/ Jolt Connect on CurrentMakers]

{{clear}}
== Videos ==

This first video cover the thoughts behind creating the [[Jolt Connect]] and why it was designed as it is.

{{#ev:youtube|8pg0efEfDvc}}

[[JLCPCB]] kindly offered to sponsor the prototypes. This video goes through the ordering process:

{{#ev:youtube|L64cD1wQDfA}}

The following video document the first prototype of the final device. All checks out beautifully.

{{#ev:youtube|TyyegjeK8TA}}

Christmas present (rev B)

{{#ev:youtube|YS1w_8ghCf4}}

Using all the [[Jolt Connect]] features:

{{#ev:youtube|VMHezAb0Ut0}}

== Pinout ==

[[File:Jolt Connect Pinout.jpg|thumb|300px|Jolt Connect Pinout]]

The pinout of the [[Jolt Connect]] IDC connector is shown on the device itself (photo to the right).

It is organized mostly in pairs:

{| class="wikitable"
!Desc
!Pin
!Pin
!Desc
|-
| +5V Supply
| 1
| 2
| +3.3V Supply
|-
| Power measure
| 3
| 4
| Common Ground
|-
| SWD CLK
| 5
| 6
| SWD DIO
|-
| Trace SWO
| 7
| 8
| Target NRST
|-
| Serial TX
| 9
| 10
| Serial RX
|}

{{clear}}

== Connecting to target ==
[[File:Blackpill with st-link.jpg|300px|thumb|Blackpill board with [[DIY STM32 Programmer (ST-Link/V2-1)|ST-Link]] - SWD, SWO and UART hooked up.]]

Wiring the [[Jolt Connect]] up to a target, depends largely on the target. For a [[Black Pill]] board it will look like this:

[[File:Jolt Connect to Black Pill.png|400px]]

== Reasoning for new design ==

Having used the original design for years some issues have crept up. This section dives into those issues and suggest how they could be improved.

=== USB-A ===

The original device used a through-hole USB-A connector. From a manufacturing point of view this connector was "troublesome" as it required hand soldering and quite frankly a bit outdated. The new version should be using USB-C.

=== Programming header ===

The original device used a 2x5 IDC header soldered on the board "sideways". This again required hand soldering and it was quite tricky to solder as the board thickness does not match the spacing between the pins on the header. The new version should use a SMD regularly mounted connector.

=== Power ===

The original version used a 3.3V LDO rated at 100 mA. This is more than enough, BUT it does limit the amount of power which can be supplied to target devices. The new version should allow more power.

== Schematics ==

The schematics is largely identical with the [[DIY STM32 Programmer (ST-Link/V2-1)|original version]].

<div class="res-img">
[[File:STM32 Programmer 2 - schematics rev b.svg|2400px]]
</div>

The main changes are the USB connector and the LDO.

== Factory firmware ==

The [[Jolt Connect]] have been designed to run multiple different firmwares. Being based on the [[STM32F103]] [[MCU]] there is no built-in [[DFU]] bootloader. We therefore deliver the device with a DFU Firmware already loaded. This enables flashing of any firmware.

=== Jolt Connect DFU ===

The [[STM32F103CB]] [[MCU]] contains 128 kB of flash. In order to be able to flash a regular bootloader in the first part of the flash memory, we locate our bootloader at the top 16 kB of flash, at address 0x801c000 to be exact. This will enable the DFU to update any part of the flash - except the top 16 kB.

Viewed from the webdfu the layout looks like this:

<pre>
Name: Jolt Connect DFU
MFG: CurrentMakers
Serial: pzhYrdOufu2Eh36G
DFU: [0483:df11] cfg=1, intf=0, alt=0, name="Jolt Connect DFU" serial="pzhYrdOufu2Eh36G"
Selected memory region: Internal Flash (128KiB)
0x08000000-0x0800ffff (readable, erasable, writable)
0x08010000-0x0801bfff (readable, erasable, writable)
0x0801c000-0x0801ffff (readable)
</pre>

=== Jolt Connect Jump ===

The jump is a separate binary located at the normal boot location at 0x8000000. It does nothing except jump up to the DFU bootloader at 0x801c000.

=== Flashing the factory firmware ===

<pre>
st-flash erase && st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000 && st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Or as individual commands:

<pre>
st-flash erase
st-flash write ~/src/jolt_connect/firmware/boot_dfu/Debug/boot_dfu.bin 0x801c000
st-flash write ~/src/jolt_connect/firmware/boot_jump/Debug/boot_jump.bin 0x8000000
</pre>

Notice that the actual dfu bootloader is flashed at the upper part of the flash memory, while the jump is flashed at the bottom. The jump - IF still there - will jump to the dfu bootloader.

After flashing the device will, to the Linux kernel, look like this:

<pre>
[362290.392700] usb 3-10.5.3: new full-speed USB device number 110 using xhci_hcd
[362290.494580] usb 3-10.5.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
[362290.494586] usb 3-10.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[362290.494588] usb 3-10.5.3: Product: Jolt Connect DFU
[362290.494589] usb 3-10.5.3: Manufacturer: CurrentMakers
[362290.494591] usb 3-10.5.3: SerialNumber: 6D7232965686
</pre>

The Linux kernel will identify that as a [[STM32]] device in [[DFU]] mode:

<pre>
Bus 003 Device 110: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
</pre>

== Flashing ST-Link firmware ==

'''Notice!''' this approach may or may not be "legal" although it does use [[ST]] provided software for the flashing.

=== Prerequisites ===

In order to go through these steps you will need the following:

* A [[Jolt Connect]] with [[DFU]] firmware (previous section)
* A working version of Java (no idea what version but works with openjdk version "21.0.9-ea")
* A copy of the ST-Link bootloader - Google for it - typically named '''Unprotected-2-1-Bootloader.bin'''
* A copy of [[ST]]'s STLinkUpgrade version 3.2.12 (can still be downloaded or Google)

=== Install bootloader ===

First step is to verify the [[Jolt Connect]] is plugged in and running. The red/blue leds will be blinking at about 2 Hz and it should show up as a DFU device.

Now point your browser to: [https://devanlai.github.io/webdfu/dfu-util/ https://devanlai.github.io/webdfu/dfu-util/].

Click on the "Connect" button:

<div class="res-img">
[[File:WebDFU Connect.png|400px]]
</div>

Select the Jolt Connect and click "Connect".

[[File:WebDFU after connect.png|600px]]

Now click Choose file and find the bootloader.

[[File:WebDFU Choose File.png|600px]]

Finally click "Download". Flashing should take perhaps 10-15 seconds and MAY result in an error (because the device resets and is no longer in DFU mode.

[[File:WebDFU download done.png|600px]]

That's it - you can now move on to the next step.

=== Flash ST-Link firmware ===

You can now fire up the ST-Link Update tool:

<pre>
lth@nb7:~/src/jolt_connect/stsw-link007$ java -jar STLinkUpgrade.jar
</pre>

This should result in the following window:

[[File:STLink Upgrade.png|600px]]

Click the "Open in Update mode" button and select '''STM32+MSD+VCP''' followed by "Upgrade"

[[File:ST-Link after upgrade first.png|600px]]

That is it - you now have a functional (but old) ST-Link.

=== Upgrade to latest version (optional) ===

The device flashed in the previous section can be upgraded with the latest version of the upgrade tool, which is part of '''STM32CubeIDE'''. Under "Help/ST-Link upgrade":

[[File:Final ST-Link upgrade and change type.png|600px]]

Notice the option of changing type which can be used to "disable" the Mass Storage device (which is not very useful).

== Flashing Black Magic Firmware ==

See this page for details on how to build: [[Black Magic Probe]]

== Flashing CMSIS DAPlink ==

See: [[CMSIS DAPlink]]

== Gallery ==
<gallery mode=slideshow>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>
<gallery>
File:Top rendering with cover.png
File:Bottom rendering.png
File:Jolt Connect covers.jpg
File:Jolt Connect top view.jpg
File:Jolt Connect btm view.jpg
File:Jolt Connect with and without cover.jpg
File:Jolt Connect sandwich.jpg
File:Jolt Connect 3 pcs assembled.jpg
File:Jolt Connect assembled side view.jpg
File:Jolt Connect assembled side view 2.jpg
File:JC - top assembled.jpg
File:JC - top front.jpg
File:JC - top left.jpg
File:JC - top left 2.jpg
File:JC - top right.jpg
File:JC - bot.jpg
File:JC - bot 2.jpg
File:JC - bot left.jpg
File:JC - bot left 2.jpg
File:Jolt Connect with jumper leads.jpg
File:Jolt Connect with ribbon.jpg
</gallery>

== Miscellaneous links ==

* [https://stm32world.com/images/d/d6/Boot_jump.bin Boot Jump binary]
* [https://stm32world.com/images/8/81/Boot_dfu.bin Boot DFU binary]
* [https://stm32world.com/images/a/a9/Blackmagic_stlink_firmware.bin Blackmagic Probe binary]
* [https://github.com/currentmakers/blackmagic Github Blackmagic fork for the Jolt Connect]
* [http://www.taylorkillian.com/2013/01/retrieving-st-linkv2-firmware-from.html ST-Link firmware analysis]

File:Jolt Connect to Black Pill.png

2026-10-11T01:56:02Z

Lth: File uploaded with MsUpload

File uploaded with MsUpload

RP2350 I2C Masterclass: 1MHz EEPROM Guide

2026-10-10T03:52:51Z

Lth: Created page with "{{Video |series=RP Pico Video |number=21 |title=RP2350 I2C Masterclass: 1MHz EEPROM Guide |youtube-id=kLF3Nqn2s6g |description=In this this video we will cover I2C on RP2350 u..."

{{Video
|series=RP Pico Video
|number=21
|title=RP2350 I2C Masterclass: 1MHz EEPROM Guide
|youtube-id=kLF3Nqn2s6g
|description=In this this video we will cover I2C on RP2350 using a M24M01 EEPROM Streamline blade as an example.
}}

Main Page

2026-10-09T07:35:36Z

Lth:

__NOTITLE__ __NOTOC__ {{metadesc|STM32World Wiki Main Page - all about STM32 and Similar MCUs}}
{| width=100%
|-
| width=33% |
| width=33% |
| width=33% |
|-
| colspan="2" | {{Box|title=Welcome|edit=Main Page/Welcome|height=300px}}
{{:Main Page/Welcome}}
{{Box/End}}
| {{Box|title=[[Recent Changes]]|theme=2|height=300px}}
{{#ask: [[:+]][[!Main Page]][[!Main Page/Welcome]][[!~STM32 Tutorial*]][[!~STM32 Bare Metal Video*]][[!~STM32 Basics*]][[!~STM32 Short*]][[!~STM32 Rant*]][[!~STM32 Miscellaneous*]][[!~KiCAD Video*]][[!~Streamline Video*]][[!~Colibri Video*]][[!~RP Pico Video*]][[!~Electronics Video*]][[!~STM32 Remake Video*]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|}
{| width=100%
|-
| width=49% |
| width=50% |
|-
| {{Box|title=End of Year Promotion|theme=3|height=400px}}
<center>
[[File:Promotion 2.jpg|620px|link=https://currentmakers.com/products/streamline/]]
</center>
{{Box/End}}
| {{Box|title=Latest video|theme=10|height=400px}}
{{#ask: [[Category:STM32 Tutorial Video||STM32 Bare Metal Video||STM32 Rant Video||STM32 Short Video||STM32 Basics Video||STM32 Miscellaneous Video||KiCAD Video||Streamline Video||Colibri Video||RP Pico Video||STM32 Remake Video||Electronics Video]]
|?Video title
|?Youtube id
|format=plainlist
|template=Video single front
|limit=1
|sort=Creation date
|order=desc
|searchlabel=
}}
{{Box/End}}
|}
{| width=100%
|-
| width=33% |
| width=33% |
| width=33% |
|-
| {{Box|title=[[Streamline]]|theme=11|height=300px}}
{{#ask: [[Category:Streamline]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[Jolt]]|theme=6|height=300px}}
{{#ask: [[Category:Jolt]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[Colibri]]|theme=2|height=300px}}
{{#ask: [[Category:Colibri]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:STM32 Documentation|STM32 Documentation]]|theme=3|height=300px}}
{{#ask: [[Category:STM32 Documentation]] OR [[Category:STM32 HOWTO]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:STM32 Development|STM32 Development]]|theme=5|height=300px}}
{{#ask: [[Category:STM32 Development]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[STM32 Tutorial Videos]]|theme=2|height=300px}}
* [[STM32 Tutorial Videos]]
* [[STM32 Bare Metal Videos]]
* [[STM32 Basics Videos]]
* [[STM32 Short Videos]]
* [[STM32 Rant Videos]]
* [[STM32 Miscellaneous Videos]]
* [[KiCAD Videos]]
* [[Streamline Videos]]
* [[Colibri Videos]]
* [[RP Pico Videos]]
* [[Electronics Videos]]
{{Box/End}}
</div>
|-
| {{Box|title=[[:Category:STM32 Hardware|STM32 Hardware]]|theme=4|height=300px}}
{{#ask: [[Category:STM32 Hardware]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:STM32 HAL|STM32 HAL]]|theme=10|height=300px}}
{{#ask: [[Category:STM32 HAL]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:STM32 Projects|STM32 Projects]]|theme=7|height=300px}}
{{#ask: [[Category:STM32 Projects]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:MCU|MCUs]]|theme=9|height=300px}}
{{#ask: [[Category:MCU]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:Components and Modules|Components and Modules]]|theme=6|height=300px}}
{{#ask: [[Category:Components and Modules]] OR [[Category:Components]] OR [[Category:Modules]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:Development Board|Development Boards]]|theme=1|height=300px}}
{{#ask: [[Category:Development Board]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:RISC-V|RISC-V]]|theme=2|height=300px}}
{{#ask: [[Category:RISC-V]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[Raspberry Pi Pico]]|theme=1|height=300px}}
{{#ask: [[Category:Raspberry Pi Pico]][[!Raspberry Pi Pico]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[ESP32]]|theme=2|height=300px}}
{{#ask: [[Category:ESP32]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:C|C Programming]]|theme=12|height=300px}}
{{#ask: [[Category:C]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:Electronics|Electronics]]|theme=13|height=300px}}
{{#ask: [[Category:Electronics]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:KiCAD|KiCAD]]|theme=14|height=300px}}
{{#ask: [[Category:KiCAD]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:CH32|CH32]]|theme=7|height=300px}}
{{#ask: [[Category:CH32]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:FPGA|FPGA]]|theme=3|height=300px}}
{{#ask: [[Category:FPGA]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[Awesome Audio Apparatus]]|theme=2|height=300px}}
{{#ask: [[Category:Awesome Audio Apparatus]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|}

Main Page

2026-10-09T07:35:08Z

Lth:

__NOTITLE__ __NOTOC__ {{metadesc|STM32World Wiki Main Page - all about STM32 and Similar MCUs}}
{| width=100%
|-
| width=33% |
| width=33% |
| width=33% |
|-
| colspan="2" | {{Box|title=Welcome|edit=Main Page/Welcome|height=300px}}
{{:Main Page/Welcome}}
{{Box/End}}
| {{Box|title=[[Recent Changes]]|theme=2|height=300px}}
{{#ask: [[:+]][[!Main Page]][[!Main Page/Welcome]][[!~STM32 Tutorial*]][[!~STM32 Bare Metal Video*]][[!~STM32 Basics*]][[!~STM32 Short*]][[!~STM32 Rant*]][[!~STM32 Miscellaneous*]][[!~KiCAD Video*]][[!~Streamline Video*]][[!~Colibri Video*]][[!~RP Pico Video*]][[!~Electronics Video*]][[!~STM32 Remake Video*]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|}
{| width=100%
|-
| width=49% |
| width=50% |
|-
| {{Box|title=End of Year Promotion|theme=3|height=400px}}
<center>
[[File:Promotion 2.jpg|49%|link=https://currentmakers.com/products/streamline/]]
</center>
{{Box/End}}
| {{Box|title=Latest video|theme=10|height=400px}}
{{#ask: [[Category:STM32 Tutorial Video||STM32 Bare Metal Video||STM32 Rant Video||STM32 Short Video||STM32 Basics Video||STM32 Miscellaneous Video||KiCAD Video||Streamline Video||Colibri Video||RP Pico Video||STM32 Remake Video||Electronics Video]]
|?Video title
|?Youtube id
|format=plainlist
|template=Video single front
|limit=1
|sort=Creation date
|order=desc
|searchlabel=
}}
{{Box/End}}
|}
{| width=100%
|-
| width=33% |
| width=33% |
| width=33% |
|-
| {{Box|title=[[Streamline]]|theme=11|height=300px}}
{{#ask: [[Category:Streamline]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[Jolt]]|theme=6|height=300px}}
{{#ask: [[Category:Jolt]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[Colibri]]|theme=2|height=300px}}
{{#ask: [[Category:Colibri]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:STM32 Documentation|STM32 Documentation]]|theme=3|height=300px}}
{{#ask: [[Category:STM32 Documentation]] OR [[Category:STM32 HOWTO]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:STM32 Development|STM32 Development]]|theme=5|height=300px}}
{{#ask: [[Category:STM32 Development]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[STM32 Tutorial Videos]]|theme=2|height=300px}}
* [[STM32 Tutorial Videos]]
* [[STM32 Bare Metal Videos]]
* [[STM32 Basics Videos]]
* [[STM32 Short Videos]]
* [[STM32 Rant Videos]]
* [[STM32 Miscellaneous Videos]]
* [[KiCAD Videos]]
* [[Streamline Videos]]
* [[Colibri Videos]]
* [[RP Pico Videos]]
* [[Electronics Videos]]
{{Box/End}}
</div>
|-
| {{Box|title=[[:Category:STM32 Hardware|STM32 Hardware]]|theme=4|height=300px}}
{{#ask: [[Category:STM32 Hardware]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:STM32 HAL|STM32 HAL]]|theme=10|height=300px}}
{{#ask: [[Category:STM32 HAL]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:STM32 Projects|STM32 Projects]]|theme=7|height=300px}}
{{#ask: [[Category:STM32 Projects]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:MCU|MCUs]]|theme=9|height=300px}}
{{#ask: [[Category:MCU]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:Components and Modules|Components and Modules]]|theme=6|height=300px}}
{{#ask: [[Category:Components and Modules]] OR [[Category:Components]] OR [[Category:Modules]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:Development Board|Development Boards]]|theme=1|height=300px}}
{{#ask: [[Category:Development Board]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:RISC-V|RISC-V]]|theme=2|height=300px}}
{{#ask: [[Category:RISC-V]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[Raspberry Pi Pico]]|theme=1|height=300px}}
{{#ask: [[Category:Raspberry Pi Pico]][[!Raspberry Pi Pico]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[ESP32]]|theme=2|height=300px}}
{{#ask: [[Category:ESP32]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:C|C Programming]]|theme=12|height=300px}}
{{#ask: [[Category:C]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:Electronics|Electronics]]|theme=13|height=300px}}
{{#ask: [[Category:Electronics]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:KiCAD|KiCAD]]|theme=14|height=300px}}
{{#ask: [[Category:KiCAD]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:CH32|CH32]]|theme=7|height=300px}}
{{#ask: [[Category:CH32]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:FPGA|FPGA]]|theme=3|height=300px}}
{{#ask: [[Category:FPGA]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[Awesome Audio Apparatus]]|theme=2|height=300px}}
{{#ask: [[Category:Awesome Audio Apparatus]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|}

Main Page

2026-10-09T07:34:46Z

Lth:

__NOTITLE__ __NOTOC__ {{metadesc|STM32World Wiki Main Page - all about STM32 and Similar MCUs}}
{| width=100%
|-
| width=33% |
| width=33% |
| width=33% |
|-
| colspan="2" | {{Box|title=Welcome|edit=Main Page/Welcome|height=300px}}
{{:Main Page/Welcome}}
{{Box/End}}
| {{Box|title=[[Recent Changes]]|theme=2|height=300px}}
{{#ask: [[:+]][[!Main Page]][[!Main Page/Welcome]][[!~STM32 Tutorial*]][[!~STM32 Bare Metal Video*]][[!~STM32 Basics*]][[!~STM32 Short*]][[!~STM32 Rant*]][[!~STM32 Miscellaneous*]][[!~KiCAD Video*]][[!~Streamline Video*]][[!~Colibri Video*]][[!~RP Pico Video*]][[!~Electronics Video*]][[!~STM32 Remake Video*]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|}
{| width=100%
|-
| width=49% |
| width=50% |
|-
| {{Box|title=End of Year Promotion|theme=3|height=400px}}
<center>
[[File:Promotion 2.jpg|100%|link=https://currentmakers.com/products/streamline/]]
</center>
{{Box/End}}
| {{Box|title=Latest video|theme=10|height=400px}}
{{#ask: [[Category:STM32 Tutorial Video||STM32 Bare Metal Video||STM32 Rant Video||STM32 Short Video||STM32 Basics Video||STM32 Miscellaneous Video||KiCAD Video||Streamline Video||Colibri Video||RP Pico Video||STM32 Remake Video||Electronics Video]]
|?Video title
|?Youtube id
|format=plainlist
|template=Video single front
|limit=1
|sort=Creation date
|order=desc
|searchlabel=
}}
{{Box/End}}
|}
{| width=100%
|-
| width=33% |
| width=33% |
| width=33% |
|-
| {{Box|title=[[Streamline]]|theme=11|height=300px}}
{{#ask: [[Category:Streamline]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[Jolt]]|theme=6|height=300px}}
{{#ask: [[Category:Jolt]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[Colibri]]|theme=2|height=300px}}
{{#ask: [[Category:Colibri]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:STM32 Documentation|STM32 Documentation]]|theme=3|height=300px}}
{{#ask: [[Category:STM32 Documentation]] OR [[Category:STM32 HOWTO]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:STM32 Development|STM32 Development]]|theme=5|height=300px}}
{{#ask: [[Category:STM32 Development]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[STM32 Tutorial Videos]]|theme=2|height=300px}}
* [[STM32 Tutorial Videos]]
* [[STM32 Bare Metal Videos]]
* [[STM32 Basics Videos]]
* [[STM32 Short Videos]]
* [[STM32 Rant Videos]]
* [[STM32 Miscellaneous Videos]]
* [[KiCAD Videos]]
* [[Streamline Videos]]
* [[Colibri Videos]]
* [[RP Pico Videos]]
* [[Electronics Videos]]
{{Box/End}}
</div>
|-
| {{Box|title=[[:Category:STM32 Hardware|STM32 Hardware]]|theme=4|height=300px}}
{{#ask: [[Category:STM32 Hardware]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:STM32 HAL|STM32 HAL]]|theme=10|height=300px}}
{{#ask: [[Category:STM32 HAL]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:STM32 Projects|STM32 Projects]]|theme=7|height=300px}}
{{#ask: [[Category:STM32 Projects]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:MCU|MCUs]]|theme=9|height=300px}}
{{#ask: [[Category:MCU]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:Components and Modules|Components and Modules]]|theme=6|height=300px}}
{{#ask: [[Category:Components and Modules]] OR [[Category:Components]] OR [[Category:Modules]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:Development Board|Development Boards]]|theme=1|height=300px}}
{{#ask: [[Category:Development Board]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:RISC-V|RISC-V]]|theme=2|height=300px}}
{{#ask: [[Category:RISC-V]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[Raspberry Pi Pico]]|theme=1|height=300px}}
{{#ask: [[Category:Raspberry Pi Pico]][[!Raspberry Pi Pico]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[ESP32]]|theme=2|height=300px}}
{{#ask: [[Category:ESP32]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:C|C Programming]]|theme=12|height=300px}}
{{#ask: [[Category:C]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:Electronics|Electronics]]|theme=13|height=300px}}
{{#ask: [[Category:Electronics]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:KiCAD|KiCAD]]|theme=14|height=300px}}
{{#ask: [[Category:KiCAD]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|-
| {{Box|title=[[:Category:CH32|CH32]]|theme=7|height=300px}}
{{#ask: [[Category:CH32]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[:Category:FPGA|FPGA]]|theme=3|height=300px}}
{{#ask: [[Category:FPGA]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
| {{Box|title=[[Awesome Audio Apparatus]]|theme=2|height=300px}}
{{#ask: [[Category:Awesome Audio Apparatus]]
|format=ul
|limit=10
|offset=0
|link=all
|sort=Modification date
|order=desc
|headers=show
|searchlabel=... further results
|propsep=,
|valuesep=,
}}
{{Box/End}}
|}

Streamline

2026-10-08T22:36:08Z

Lth: /* Rationale */

[[Category:STM32]][[Category:Streamline]][[Category:CurrentMakers]][[Category:Work in progress]]{{metadesc|Streamline Development Boards Home}}
[[File:Streamline Backplane with 2 blades - top right 3.jpg|300px|thumb|Streamline Backplane with 2 blades - 1 Connect and 1 MCU]]
This page documents the new [[CurrentMakers]] [[Streamline]] series of [[Green]] development boards. If you are looking for the previous series, that is document here: [[STM32World Legacy]].

[[Streamline]] boards are available here: [https://currentmakers.com/products/streamline/ Streamline on CurrentMakers]

{{clear}}
== Rationale ==
[[File:3 STM32World Modules stacked.jpg|300px|thumb|The old STM32World system]]
A number of [[STM32World Legacy]] boards have been developed, and produced, and in general the "system" worked very well. It did however have one fatal flaw which was the sole cause of it never being considered for more widespread production. This flaw was the board to board connector.

The original boards used a 2x20 standard pin header on each side giving a result of 80 pins. In terms of connectivity this was a pretty good solution. It did however present some issues:

# Cost - the long pin 2x20 connectors are fairly expensive - around $0.80 each - so $1.60 per board. This may not sound that high but when producing a lot it becomes a serious cost.
# Manufacturing - the headers can not be manufactured with traditional SMD technologies but require a manual step or hand soldering.
# Fragile - when shipping or disconnecting boards it is hard not to bend one or more pins and once bend it becomes extremely difficult to reconnect them.

To get around this flaw a new "connector" was considered and after a long search the best solution was the standard PCI-E X8 connector.

{{clear}}

== Videos ==

{{#ev:youtube|5xQqV7BhYxM}}

Receiving the first prototypes ever:

{{#ev:youtube|YS1w_8ghCf4}}

== Backplane ==

The overall idea is to base [[StreamLine]] around a passive backplane. The backplane contains a number of PCI connectors with 2 x 49 pins (98) that is simply connected in a parallel bus.

<div class="res-img">
[[File:Sl bp 5 top left.png|1000px]]
</div>

In each end of the bus all the A and B signals are broken out into regular pin headers.

=== Backplane rendering ===

<gallery>
File:Backplane top render.png
File:Backplane front render.png
File:Backplane front left render.png
File:Sl bp 5 top.png
File:Sl bp 5 top left.png
File:Sl bp 5 top right.png
</gallery>

== Modules ==

=== [[Backplane]]s ===

{| class="wikitable"
|-
! Name
! Image
! Description
! Status
|-
| [[Streamline Backplane 5]]
| [[File:sl_bp_5_top_left.png|80px]]
| Basic 5 position backplane
| [https://currentmakers.com/products/streamline/streamline_backplane_5/ Available]
|}

=== [[Blade]]s ===

==== STM32 ====

{| class="wikitable"
|-
! Name
! Image
! Description
! Status
|-
| [[Streamline Connect]] (ST-Link firmware)
| [[File:Sl prog top left render.png|80px]]
| Streamline Programmer & Debugger. This module is essentially identical to [[Jolt Connect]]
| [https://currentmakers.com/products/streamline/streamline_connect/ Available]
|-
| [[Streamline MCU STM32F407]]
| [[File:Sl mcu stm32f407 top left render.png|80px]]
| Streamline MCU board including a [[STM32F407]]
| [https://currentmakers.com/products/streamline/streamline_mcu_stm32f407/ Available]
|-
| [[Streamline MCU STM32H562]]
| [[File:Sl mcu stm32h562 top left render.png|80px]]
| Streamline MCU board including a [[STM32H562]]
| [https://currentmakers.com/products/streamline/streamline_mcu_stm32h562/ Available]
|-
| [[Streamline MCU STM32L475]]
| [[File:Sl mcu stm32l475 top left render.png|80px]]
| Streamline MCU board including a [[STM32L475]]
| [https://currentmakers.com/products/streamline/streamline_mcu_stm32l475/ Available]
|-
| [[Streamline MCU STM32C551]]
| [[File:Sl_mcu_stm32c551_top_left_render.png|80px]]
| Streamline MCU board including a [[STM32C551]]
| [https://currentmakers.com/products/streamline/streamline_mcu_stm32c551/ Available]
|-
| [[Streamline MCU STM32H723]]
| [[File:Sl_mcu_stm32h723_top_left_render.png|80px]]
| Streamline MCU board including a STM32H723
| Prototype
|}

==== Other MCU's ====

{| class="wikitable"
|-
! Name
! Image
! Description
! Status
|-
| [[Streamline Connect]] (DAPlink FIrmware)
| [[File:Sl prog top left render.png|80px]]
| Streamline Programmer & Debugger. This module is essentially identical to [[Jolt Connect]]
| [https://currentmakers.com/products/streamline/streamline_connect/ Available]
|-
| [[Streamline MCU RP2354]]
| [[File:Sl mcu rp2354 top left render.png|80px]]
| Streamline MCU board including a [[RP2354]]
| [https://currentmakers.com/products/streamline/streamline_mcu_rp2354/ Available]
|-
| [[Streamline MCU ESP32S6]]
| [[File:Sl mcu esp32s6 top left render.png|80px]]
| Streamline MCU board including a [[ESP32S6]]
| Planned
|}

==== Miscellaneous ====

{| class="wikitable"
|-
! Name
! Image
! Description
! Status
|-
| [[Streamline Neopixel 8x8]]
| [[File:Sl neopixel 8x8 top left render.png|80px]]
| Module with an 8x8 matrix of Neopixel WS2812 LEDs
| [https://currentmakers.com/products/streamline/streamline_neopixel_8x8/ Available]
|-
| [[Streamline Storage SD]]
| [[File:Sl storage sd top left render rev A.png|80px]]
| Module with Micro-SD slot
| [https://currentmakers.com/products/streamline/streamline_sd/ Available]
|-
| [[Streamline Storage Flash]]
| [[File:Sl storage flash top left render.png|80px]]
| Module with 16 MB Flash storage ([[W25q128]])
| [https://currentmakers.com/products/streamline/streamline_flash/ Available]
|-
| [[Streamline Storage EEPROM]]
| [[File:Sl storage eeprom top left render.png|80px]]
| Module with 512kB EEPROM storage ([[M24M01]])
| [https://currentmakers.com/products/streamline/streamline_eeprom/ Available]
|-
| [[Streamline IO Audio DAC]]
| [[File:Sl_io_pcm5102_top_left_render.png|80px]]
| PCM5102 I2S Audio DAC
| [https://currentmakers.com/products/streamline/streamline_io_audio_dac/ Available]
|-
| [[Streamline IO CAN]]
| [[File:Sl_io_can_top_left_render.png|80px]]
| CAN bus interface
| [https://currentmakers.com/products/streamline/streamline_io_can/ Available]
|-
| [[Streamline Ethernet]]
| [[File:Streamline_ethernet_top_left_render.png|80px]]
| Ethernet interface for STM32F407
| [https://currentmakers.com/products/streamline/streamline_ethernet/ Available]
|-
| [[Streamline SPI-Ethernet]]
| [[File:Streamline_seth_top_left_render.png|80px]]
| Ethernet interface via the SPI bus
| Prototype
|-
| [[Streamline RS485]]
| [[File:Streamline_rs485_top_left_render.png|80px]]
| Non-isolated RS485 interface
| Prototype
|-
| Streamline Real Time Clock
|
| Real time clock with on board coin cell battery (or supercap) backup
| Idea
|-
| Streamline ESC
|
| Electronic speed control for BLDC motors
| Idea
|-
| Streamline HS USB
|
| HS USB blade using [[USB3300]]
| Idea
|-
| Streamline WiFi
|
| WiFi interface
| Idea
|-
| Streamline Temperature/Humidity
|
| Sensor of temperature and humidity
| Idea
|-
| Streamline Compass
|
| Compass
| Idea
|-
| Streamline Gyro
|
| Gyro
| Idea
|-
| Streamline Accelerometer
|
| Accelerometer
| Idea
|-
| Streamline GPS
|
| GPS
| Idea
|-
| Streamline FM Radio
|
| FM and DAB radio receiver
| Idea
|}

== Standard Pinout ==

The pinout table is based on a [[MCU]] board with a 100 pin STM32F407. Boards using [[STM32]] [[MCU]]s with less pins will leave some of the pins unused.

* [[Streamline Peripheral Pin Mapping]] - peripheral-by-peripheral pin mapping.
* [[Streamline Header Mapping]] - Backplane-to-GPIO and GPIO-to-Backplane mapping.

== Prototype Photos ==

<gallery>
File:Streamline Backplane with 2 blades - top right 3.jpg
File:Streamline Backplane with 2 blades - top right 2.jpg
File:Streamline Backplane with 2 blades - top right.jpg
File:Streamline Backplane with 2 blades - top left.jpg
File:Streamline Backplane with 2 blades - front.jpg
File:Streamline Multiple Blades.jpg
File:Streamline MCU STM32L475 - top view.jpg
File:Streamline MCU STM32L475 - bottom view.jpg
File:Streamline MCU STM32H562 - top view.jpg
File:Streamline MCU STM32H562 - bottom view.jpg
File:Streamline MCU STM32F407 - top view.jpg
File:Streamline MCU STM32F407 - bottom view.jpg
File:Streamline Connect - top view.jpg
File:Streamline Connect - bottom view.jpg
</gallery>

== Miscellaneous Links ==

* [https://currentmakers.com CurrentMakers main site]
* [https://github.com/currentmakers/streamline_kicad_libraries Streamline KiCAD Libraries]

Streamline

2026-10-08T22:35:45Z

Lth: /* Rationale */

[[Category:STM32]][[Category:Streamline]][[Category:CurrentMakers]][[Category:Work in progress]]{{metadesc|Streamline Development Boards Home}}
[[File:Streamline Backplane with 2 blades - top right 3.jpg|300px|thumb|Streamline Backplane with 2 blades - 1 Connect and 1 MCU]]
This page documents the new [[CurrentMakers]] [[Streamline]] series of [[Green]] development boards. If you are looking for the previous series, that is document here: [[STM32World Legacy]].

[[Streamline]] boards are available here: [https://currentmakers.com/products/streamline/ Streamline on CurrentMakers]

{{clear}}
== Rationale ==
[[File:3 STM32World Modules stacked.jpg|300px|thumb|The old STM32World system]]
A number of [[STM32World Legacy]] boards have been developed, and produced, and in general the "system" worked very well. It did however have one fatal flaw which was the sole cause of it never being considered for more widespread production. This flaw was the board to board connector.

The original boards used a 2x20 standard pin header on each side giving a result of 80 pins. In terms of connectivity this was a pretty good solution. It did however present some issues:

# Cost - the long pin 2x20 connectors are fairly expensive - around $0.80 each - so $1.60 per board. This may not sound that high but when producing a lot it becomes a serious cost.
# Manufacturing - the headers can not be manufactured with traditional SMD technologies but require a manual step or hand soldering.
# Fragile - when shipping or disconnecting boards it is hard not to bend one or more pins and once bend it becomes extremely difficult to reconnect them.

To get around this flaw a new "connector" was considered and after a long search the best solution was the standard PCI-E X8 connector.

== Videos ==

{{#ev:youtube|5xQqV7BhYxM}}

Receiving the first prototypes ever:

{{#ev:youtube|YS1w_8ghCf4}}

== Backplane ==

The overall idea is to base [[StreamLine]] around a passive backplane. The backplane contains a number of PCI connectors with 2 x 49 pins (98) that is simply connected in a parallel bus.

<div class="res-img">
[[File:Sl bp 5 top left.png|1000px]]
</div>

In each end of the bus all the A and B signals are broken out into regular pin headers.

=== Backplane rendering ===

<gallery>
File:Backplane top render.png
File:Backplane front render.png
File:Backplane front left render.png
File:Sl bp 5 top.png
File:Sl bp 5 top left.png
File:Sl bp 5 top right.png
</gallery>

== Modules ==

=== [[Backplane]]s ===

{| class="wikitable"
|-
! Name
! Image
! Description
! Status
|-
| [[Streamline Backplane 5]]
| [[File:sl_bp_5_top_left.png|80px]]
| Basic 5 position backplane
| [https://currentmakers.com/products/streamline/streamline_backplane_5/ Available]
|}

=== [[Blade]]s ===

==== STM32 ====

{| class="wikitable"
|-
! Name
! Image
! Description
! Status
|-
| [[Streamline Connect]] (ST-Link firmware)
| [[File:Sl prog top left render.png|80px]]
| Streamline Programmer & Debugger. This module is essentially identical to [[Jolt Connect]]
| [https://currentmakers.com/products/streamline/streamline_connect/ Available]
|-
| [[Streamline MCU STM32F407]]
| [[File:Sl mcu stm32f407 top left render.png|80px]]
| Streamline MCU board including a [[STM32F407]]
| [https://currentmakers.com/products/streamline/streamline_mcu_stm32f407/ Available]
|-
| [[Streamline MCU STM32H562]]
| [[File:Sl mcu stm32h562 top left render.png|80px]]
| Streamline MCU board including a [[STM32H562]]
| [https://currentmakers.com/products/streamline/streamline_mcu_stm32h562/ Available]
|-
| [[Streamline MCU STM32L475]]
| [[File:Sl mcu stm32l475 top left render.png|80px]]
| Streamline MCU board including a [[STM32L475]]
| [https://currentmakers.com/products/streamline/streamline_mcu_stm32l475/ Available]
|-
| [[Streamline MCU STM32C551]]
| [[File:Sl_mcu_stm32c551_top_left_render.png|80px]]
| Streamline MCU board including a [[STM32C551]]
| [https://currentmakers.com/products/streamline/streamline_mcu_stm32c551/ Available]
|-
| [[Streamline MCU STM32H723]]
| [[File:Sl_mcu_stm32h723_top_left_render.png|80px]]
| Streamline MCU board including a STM32H723
| Prototype
|}

==== Other MCU's ====

{| class="wikitable"
|-
! Name
! Image
! Description
! Status
|-
| [[Streamline Connect]] (DAPlink FIrmware)
| [[File:Sl prog top left render.png|80px]]
| Streamline Programmer & Debugger. This module is essentially identical to [[Jolt Connect]]
| [https://currentmakers.com/products/streamline/streamline_connect/ Available]
|-
| [[Streamline MCU RP2354]]
| [[File:Sl mcu rp2354 top left render.png|80px]]
| Streamline MCU board including a [[RP2354]]
| [https://currentmakers.com/products/streamline/streamline_mcu_rp2354/ Available]
|-
| [[Streamline MCU ESP32S6]]
| [[File:Sl mcu esp32s6 top left render.png|80px]]
| Streamline MCU board including a [[ESP32S6]]
| Planned
|}

==== Miscellaneous ====

{| class="wikitable"
|-
! Name
! Image
! Description
! Status
|-
| [[Streamline Neopixel 8x8]]
| [[File:Sl neopixel 8x8 top left render.png|80px]]
| Module with an 8x8 matrix of Neopixel WS2812 LEDs
| [https://currentmakers.com/products/streamline/streamline_neopixel_8x8/ Available]
|-
| [[Streamline Storage SD]]
| [[File:Sl storage sd top left render rev A.png|80px]]
| Module with Micro-SD slot
| [https://currentmakers.com/products/streamline/streamline_sd/ Available]
|-
| [[Streamline Storage Flash]]
| [[File:Sl storage flash top left render.png|80px]]
| Module with 16 MB Flash storage ([[W25q128]])
| [https://currentmakers.com/products/streamline/streamline_flash/ Available]
|-
| [[Streamline Storage EEPROM]]
| [[File:Sl storage eeprom top left render.png|80px]]
| Module with 512kB EEPROM storage ([[M24M01]])
| [https://currentmakers.com/products/streamline/streamline_eeprom/ Available]
|-
| [[Streamline IO Audio DAC]]
| [[File:Sl_io_pcm5102_top_left_render.png|80px]]
| PCM5102 I2S Audio DAC
| [https://currentmakers.com/products/streamline/streamline_io_audio_dac/ Available]
|-
| [[Streamline IO CAN]]
| [[File:Sl_io_can_top_left_render.png|80px]]
| CAN bus interface
| [https://currentmakers.com/products/streamline/streamline_io_can/ Available]
|-
| [[Streamline Ethernet]]
| [[File:Streamline_ethernet_top_left_render.png|80px]]
| Ethernet interface for STM32F407
| [https://currentmakers.com/products/streamline/streamline_ethernet/ Available]
|-
| [[Streamline SPI-Ethernet]]
| [[File:Streamline_seth_top_left_render.png|80px]]
| Ethernet interface via the SPI bus
| Prototype
|-
| [[Streamline RS485]]
| [[File:Streamline_rs485_top_left_render.png|80px]]
| Non-isolated RS485 interface
| Prototype
|-
| Streamline Real Time Clock
|
| Real time clock with on board coin cell battery (or supercap) backup
| Idea
|-
| Streamline ESC
|
| Electronic speed control for BLDC motors
| Idea
|-
| Streamline HS USB
|
| HS USB blade using [[USB3300]]
| Idea
|-
| Streamline WiFi
|
| WiFi interface
| Idea
|-
| Streamline Temperature/Humidity
|
| Sensor of temperature and humidity
| Idea
|-
| Streamline Compass
|
| Compass
| Idea
|-
| Streamline Gyro
|
| Gyro
| Idea
|-
| Streamline Accelerometer
|
| Accelerometer
| Idea
|-
| Streamline GPS
|
| GPS
| Idea
|-
| Streamline FM Radio
|
| FM and DAB radio receiver
| Idea
|}

== Standard Pinout ==

The pinout table is based on a [[MCU]] board with a 100 pin STM32F407. Boards using [[STM32]] [[MCU]]s with less pins will leave some of the pins unused.

* [[Streamline Peripheral Pin Mapping]] - peripheral-by-peripheral pin mapping.
* [[Streamline Header Mapping]] - Backplane-to-GPIO and GPIO-to-Backplane mapping.

== Prototype Photos ==

<gallery>
File:Streamline Backplane with 2 blades - top right 3.jpg
File:Streamline Backplane with 2 blades - top right 2.jpg
File:Streamline Backplane with 2 blades - top right.jpg
File:Streamline Backplane with 2 blades - top left.jpg
File:Streamline Backplane with 2 blades - front.jpg
File:Streamline Multiple Blades.jpg
File:Streamline MCU STM32L475 - top view.jpg
File:Streamline MCU STM32L475 - bottom view.jpg
File:Streamline MCU STM32H562 - top view.jpg
File:Streamline MCU STM32H562 - bottom view.jpg
File:Streamline MCU STM32F407 - top view.jpg
File:Streamline MCU STM32F407 - bottom view.jpg
File:Streamline Connect - top view.jpg
File:Streamline Connect - bottom view.jpg
</gallery>

== Miscellaneous Links ==

* [https://currentmakers.com CurrentMakers main site]
* [https://github.com/currentmakers/streamline_kicad_libraries Streamline KiCAD Libraries]

Conditional Breakpoint Trap

2026-10-08T02:52:09Z

Lth: Created page with "{{Video |series=STM32 Short Video |number=15 |title=Conditional Breakpoint Trap |youtube-id=l2FUJsc4aGU |description=Showing how I managed to mess up conditional breakpoints a..."

{{Video
|series=STM32 Short Video
|number=15
|title=Conditional Breakpoint Trap
|youtube-id=l2FUJsc4aGU
|description=Showing how I managed to mess up conditional breakpoints as a big warning to others. Also showing how the RP2350 is more resilient to my idiocy.
}}

CH32V407 and CH32V467

2026-10-06T01:06:16Z

Lth: /* Miscellaneous links */

[[Category:CH32]][[Category:RISC-V]][[Category:CH32V4xx]][[Category:MCU]]{{metadesc|CH32V4xx RISC-V MCU documentation}}

== Miscellaneous links ==

* [https://stm32world.com/images/7/75/CH32V407DS0.pdf CH32V407/CH32V467 English Datasheet]
* [https://stm32world.com/images/9/97/CH32V407RM.pdf CH32V407/CH32V467 English Reference Manual]
* [https://stm32world.com/images/0/06/QingKeV3_Processor_Manual.pdf QingKeV3 Microprocessor Manual]

File:CH32V407DS0.pdf

2026-10-06T01:05:42Z

Lth:

CH32V407 and CH32V467

2026-10-06T01:03:56Z

Lth: /* Miscellaneous links */

[[Category:CH32]][[Category:RISC-V]][[Category:CH32V4xx]][[Category:MCU]]{{metadesc|CH32V4xx RISC-V MCU documentation}}

== Miscellaneous links ==

* [https://stm32world.com/images/9/97/CH32V407RM.pdf CH32V407/CH32V467 English Datasheet]
* [https://stm32world.com/images/0/06/QingKeV3_Processor_Manual.pdf QingKeV3 Microprocessor Manual]

File:QingKeV3 Processor Manual.pdf

2026-10-06T01:03:20Z

Lth:

CH32V407 and CH32V467

2026-10-06T00:59:24Z

Lth:

File:CH32V407RM.pdf

2026-10-06T00:58:01Z

Lth:

Category:CH32V4xx

2026-10-06T00:57:35Z

Lth: Created page with "CH32V4xx MCUs"

CH32V4xx MCUs

CH32V407 and CH32V467

2026-10-06T00:57:10Z

Lth: Created page with "Category:CH32Category:RISC-VCategory:CH32V4xxCategory:MCU{{metadesc|CH32V4xx RISC-V MCU documentation}}"

[[Category:CH32]][[Category:RISC-V]][[Category:CH32V4xx]][[Category:MCU]]{{metadesc|CH32V4xx RISC-V MCU documentation}}

ST-Link

2026-10-06T00:50:47Z

Lth: /* Upgrade issues */

[[Category:STM32]][[Category:STM32 Hardware]][[Category:ST-Link]]{{metadesc|ST-Link STM32 Flash and Debugging tool}}

There's a number of different ways to flash [[STM32]] devices. One of these is to use [[ST]]'s own [[ST-Link]] devices using the [[Serial Wire Debug]] (aka [[SWD]]) protocol.

[[File:STLink.jpg|400px]]

There are multiple benefits of using one of these [[ST-Link]] devices rather than a plain serial dongle:

# The device need not be restarted in flash mode ([[Boot0]])
# Programs can be debugged on the device

The official [[ST-Link]] as seen above are relatively cheap (< $20) and there are Chinese copies available (haven't tried those).

We are also running on a [[DIY ST-Link V2.1]] device.

== Video ==

We created a detailed video on the topic of using [[ST-Link]].

{{#ev:youtube|jHo_IpqRlRE}}

A later video dig into all the features, SWD, SWO and UART.

{{#ev:youtube|VMHezAb0Ut0}}

== ST-Link/V2 ==
[[File:ST-Link V2 Photo.png|thumb|300px|Original ST-Link/V2]]
While there must have been a V1 at some point, the ST-Link/V2 displayed in the photo to the left was for years the one to use. The original can still be purchased from places like Mouser, but there are also plenty of exact Chinese clones around (exact as in they look exactly the same).

These ST-Link devices are enclosed in a quite large white plastic casing but for some truly bizarre reason, [[ST]] could not be arsed to put a legend on the device, so one either have to have a very good memory or Google the pin out constantly.

Another very common clone are these:

[[File:Chinese ST-Link Clone.jpg|400px]]

[[File:ST-Link Bunch.jpg|400px]]

They are Chinese knock offs but they run the official [[ST-Link]] firmware and contrary to the official one they actually have the pin out legend printed on the box. Generally these devices work just fine but with certain limitations.

The V2 devices does not have any UART/Serial functionality. The original does have SWO (Serial Wire Output) which can be used to print debug information. The small Chinese knock-offs ''can'' be modified to include a SWO pin (see link [[#More Reading|here]]).

{{clear}}

== ST-Link/V2-1 (Nucleo) ==
[[File:St-Link Nucleo.png|thumb|400px]]
For beginners, the Nucleo boards are absolutely brilliant. First of all, being official [[ST]] boards they obviously include an original [[STM32]] [[MCU]], but they do in fact include '''two''' [[MCU]]s and the second one acts like a ST-Link/V2-1 device. Contrary to the [[#ST-Link/V2|ST-Link/V2]], this one does include a SWO pin AND a USB/UART interface.

ST-Link/V2-1 devices does not exist as a stand-alone product, but they can be broken off the Nucleo and used as a stand-alone device. The complete schematics is available in the manual of the Nucleo boards, so it is in fact possible to use this to build your own. An example of that is shown here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

[[File:STM32 Programmer fully assembled - 5pcs.jpg|600px|Home made ST-Link/V2-1 devices]]

{{clear}}

== ST-Link/V3MINIE ==
[[File:ST-Link V3MINIE Photo.png|thumb|300px]]
To be added
{{clear}}

== ST-Link/V3SET ==
[[File:ST-Link V3SET.png|thumb|300px]]
To be added
{{clear}}

== Hardware Analysis ==

[[ST]] does not make schematics or source code available for the official ST-Link devices, which is a pity (and a somewhat odd business decision). However, they '''do''' publish a partial schematics since a built-in ST-Link device is included in all their development boards, a partial schematics is available.

<div class="res-img">
[[File:ST-Link V2.1 Original Schematics.png|1800px]]
</div>

From the schematics we can see that the ST-Link device is build around a STM32F103CBT6 which is the 128 kB Flash version.

PC13 and PC14 (and possibly PC15 in the future) appears to be working as a means for the firmware to identify the "version" of the hardware. On above schematics, PC13 is pulled low with a resistor while PC14 (and PC15) are left floating.

A voltage divider splitting +3.3 V in half is connected to PA0 and labelled AIN_1. The ST-Link devices are capable of measuring the target processor supply voltage and this is probably a workaround of the development boards (which know their supply voltage already).

The "output" pins of the ST-Link V2 are as follows:

{| class="wikitable"
|-
! Pin
! Label
! Remarks
|-
| PA0
| AIN_1
| Probably meant as an analog input, measuring the supply voltage on the target device. On the development boards, the supply voltage is well known, so this pin is connected to a voltage divider splitting the supply voltage in half (1.65V or thereabouts).
|-
| PA5
| T_JTCK
| Target Clock
|-
| PA6
| T_JTDO
|
|-
| PA7
| T_JTDI
|
|-
| PA10
| T_SWO
| Target trace debugging. This pin is unconnected on the Chinese clone ST-Links, which is annoying.
|-
| PA12
| T_SWDIO_IN
| On development boards connected via a 100 Ohm resistor to PA14
|-
| PA13
| T_JTCK
|
|-
| PA14
| T_JTMS
|
|-
| PB0
| T_NRST
|
|-
| PB1
| T_JRST
| Labelled but not connected to anything
|}

== Upgrade issues ==
[[File:ST-Link Bunch.jpg|thumb|200px]]
The little colorful Chinese clones (shown on the right) have been reported to sometimes fail firmware upgrade. This is partly to be expected as they are '''not''' using real [[STM32]] [[MCU]]s. We bought a pile of these at some point and none of those ever failed though.
{{clear}}

== More Reading ==

Github user lujji have done a number of interesting writeups on ST-Link devices, reverse engineering the ST-Link firmware and adding trace (SWO) support to the cheap Chinese ST-Link devices.

* [https://lujji.github.io/blog/stlink-clone-trace/ Adding Trace support to ST-Link clones]
* [https://lujji.github.io/blog/reverse-engineering-stlink-firmware Reverse-engineering ST-Link firmware part 1]
* [https://lujji.github.io/blog/reverse-engineering-stlink-firmware-part2 Reverse-engineering ST-Link firmware part 2]
* [https://stm32world.com/images/5/55/St-link-slsh-v2.pdf ST-Link/V2 Product Sheet]
* [https://stm32world.com/images/2/27/Stlink-v3minie.pdf ST-Link/V3MINIE Product Sheet]
* [https://stm32world.com/images/1/1c/Stlink-v3set.pdf ST-Link/V3SET Product Sheet]
* [[DIY STM32 Programmer (ST-Link/V2-1)]]

ST-Link

2026-10-06T00:50:13Z

Lth: /* Upgrade issues */

[[Category:STM32]][[Category:STM32 Hardware]][[Category:ST-Link]]{{metadesc|ST-Link STM32 Flash and Debugging tool}}

There's a number of different ways to flash [[STM32]] devices. One of these is to use [[ST]]'s own [[ST-Link]] devices using the [[Serial Wire Debug]] (aka [[SWD]]) protocol.

[[File:STLink.jpg|400px]]

There are multiple benefits of using one of these [[ST-Link]] devices rather than a plain serial dongle:

# The device need not be restarted in flash mode ([[Boot0]])
# Programs can be debugged on the device

The official [[ST-Link]] as seen above are relatively cheap (< $20) and there are Chinese copies available (haven't tried those).

We are also running on a [[DIY ST-Link V2.1]] device.

== Video ==

We created a detailed video on the topic of using [[ST-Link]].

{{#ev:youtube|jHo_IpqRlRE}}

A later video dig into all the features, SWD, SWO and UART.

{{#ev:youtube|VMHezAb0Ut0}}

== ST-Link/V2 ==
[[File:ST-Link V2 Photo.png|thumb|300px|Original ST-Link/V2]]
While there must have been a V1 at some point, the ST-Link/V2 displayed in the photo to the left was for years the one to use. The original can still be purchased from places like Mouser, but there are also plenty of exact Chinese clones around (exact as in they look exactly the same).

These ST-Link devices are enclosed in a quite large white plastic casing but for some truly bizarre reason, [[ST]] could not be arsed to put a legend on the device, so one either have to have a very good memory or Google the pin out constantly.

Another very common clone are these:

[[File:Chinese ST-Link Clone.jpg|400px]]

[[File:ST-Link Bunch.jpg|400px]]

They are Chinese knock offs but they run the official [[ST-Link]] firmware and contrary to the official one they actually have the pin out legend printed on the box. Generally these devices work just fine but with certain limitations.

The V2 devices does not have any UART/Serial functionality. The original does have SWO (Serial Wire Output) which can be used to print debug information. The small Chinese knock-offs ''can'' be modified to include a SWO pin (see link [[#More Reading|here]]).

{{clear}}

== ST-Link/V2-1 (Nucleo) ==
[[File:St-Link Nucleo.png|thumb|400px]]
For beginners, the Nucleo boards are absolutely brilliant. First of all, being official [[ST]] boards they obviously include an original [[STM32]] [[MCU]], but they do in fact include '''two''' [[MCU]]s and the second one acts like a ST-Link/V2-1 device. Contrary to the [[#ST-Link/V2|ST-Link/V2]], this one does include a SWO pin AND a USB/UART interface.

ST-Link/V2-1 devices does not exist as a stand-alone product, but they can be broken off the Nucleo and used as a stand-alone device. The complete schematics is available in the manual of the Nucleo boards, so it is in fact possible to use this to build your own. An example of that is shown here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

[[File:STM32 Programmer fully assembled - 5pcs.jpg|600px|Home made ST-Link/V2-1 devices]]

{{clear}}

== ST-Link/V3MINIE ==
[[File:ST-Link V3MINIE Photo.png|thumb|300px]]
To be added
{{clear}}

== ST-Link/V3SET ==
[[File:ST-Link V3SET.png|thumb|300px]]
To be added
{{clear}}

== Hardware Analysis ==

[[ST]] does not make schematics or source code available for the official ST-Link devices, which is a pity (and a somewhat odd business decision). However, they '''do''' publish a partial schematics since a built-in ST-Link device is included in all their development boards, a partial schematics is available.

<div class="res-img">
[[File:ST-Link V2.1 Original Schematics.png|1800px]]
</div>

From the schematics we can see that the ST-Link device is build around a STM32F103CBT6 which is the 128 kB Flash version.

PC13 and PC14 (and possibly PC15 in the future) appears to be working as a means for the firmware to identify the "version" of the hardware. On above schematics, PC13 is pulled low with a resistor while PC14 (and PC15) are left floating.

A voltage divider splitting +3.3 V in half is connected to PA0 and labelled AIN_1. The ST-Link devices are capable of measuring the target processor supply voltage and this is probably a workaround of the development boards (which know their supply voltage already).

The "output" pins of the ST-Link V2 are as follows:

{| class="wikitable"
|-
! Pin
! Label
! Remarks
|-
| PA0
| AIN_1
| Probably meant as an analog input, measuring the supply voltage on the target device. On the development boards, the supply voltage is well known, so this pin is connected to a voltage divider splitting the supply voltage in half (1.65V or thereabouts).
|-
| PA5
| T_JTCK
| Target Clock
|-
| PA6
| T_JTDO
|
|-
| PA7
| T_JTDI
|
|-
| PA10
| T_SWO
| Target trace debugging. This pin is unconnected on the Chinese clone ST-Links, which is annoying.
|-
| PA12
| T_SWDIO_IN
| On development boards connected via a 100 Ohm resistor to PA14
|-
| PA13
| T_JTCK
|
|-
| PA14
| T_JTMS
|
|-
| PB0
| T_NRST
|
|-
| PB1
| T_JRST
| Labelled but not connected to anything
|}

== Upgrade issues ==
[[File:ST-Link Bunch.jpg|thumb|200px]]
The little colorful Chinese clones have been reported to sometimes fail firmware upgrade. This is partly to be expected as they are '''not''' using real [[STM32]] [[MCU]]s. We bought a pile of these at some point and none of those ever failed though.

== More Reading ==

Github user lujji have done a number of interesting writeups on ST-Link devices, reverse engineering the ST-Link firmware and adding trace (SWO) support to the cheap Chinese ST-Link devices.

* [https://lujji.github.io/blog/stlink-clone-trace/ Adding Trace support to ST-Link clones]
* [https://lujji.github.io/blog/reverse-engineering-stlink-firmware Reverse-engineering ST-Link firmware part 1]
* [https://lujji.github.io/blog/reverse-engineering-stlink-firmware-part2 Reverse-engineering ST-Link firmware part 2]
* [https://stm32world.com/images/5/55/St-link-slsh-v2.pdf ST-Link/V2 Product Sheet]
* [https://stm32world.com/images/2/27/Stlink-v3minie.pdf ST-Link/V3MINIE Product Sheet]
* [https://stm32world.com/images/1/1c/Stlink-v3set.pdf ST-Link/V3SET Product Sheet]
* [[DIY STM32 Programmer (ST-Link/V2-1)]]

ST-Link

2026-10-06T00:45:58Z

Lth: /* Upgrade issues */

[[Category:STM32]][[Category:STM32 Hardware]][[Category:ST-Link]]{{metadesc|ST-Link STM32 Flash and Debugging tool}}

There's a number of different ways to flash [[STM32]] devices. One of these is to use [[ST]]'s own [[ST-Link]] devices using the [[Serial Wire Debug]] (aka [[SWD]]) protocol.

[[File:STLink.jpg|400px]]

There are multiple benefits of using one of these [[ST-Link]] devices rather than a plain serial dongle:

# The device need not be restarted in flash mode ([[Boot0]])
# Programs can be debugged on the device

The official [[ST-Link]] as seen above are relatively cheap (< $20) and there are Chinese copies available (haven't tried those).

We are also running on a [[DIY ST-Link V2.1]] device.

== Video ==

We created a detailed video on the topic of using [[ST-Link]].

{{#ev:youtube|jHo_IpqRlRE}}

A later video dig into all the features, SWD, SWO and UART.

{{#ev:youtube|VMHezAb0Ut0}}

== ST-Link/V2 ==
[[File:ST-Link V2 Photo.png|thumb|300px|Original ST-Link/V2]]
While there must have been a V1 at some point, the ST-Link/V2 displayed in the photo to the left was for years the one to use. The original can still be purchased from places like Mouser, but there are also plenty of exact Chinese clones around (exact as in they look exactly the same).

These ST-Link devices are enclosed in a quite large white plastic casing but for some truly bizarre reason, [[ST]] could not be arsed to put a legend on the device, so one either have to have a very good memory or Google the pin out constantly.

Another very common clone are these:

[[File:Chinese ST-Link Clone.jpg|400px]]

[[File:ST-Link Bunch.jpg|400px]]

They are Chinese knock offs but they run the official [[ST-Link]] firmware and contrary to the official one they actually have the pin out legend printed on the box. Generally these devices work just fine but with certain limitations.

The V2 devices does not have any UART/Serial functionality. The original does have SWO (Serial Wire Output) which can be used to print debug information. The small Chinese knock-offs ''can'' be modified to include a SWO pin (see link [[#More Reading|here]]).

{{clear}}

== ST-Link/V2-1 (Nucleo) ==
[[File:St-Link Nucleo.png|thumb|400px]]
For beginners, the Nucleo boards are absolutely brilliant. First of all, being official [[ST]] boards they obviously include an original [[STM32]] [[MCU]], but they do in fact include '''two''' [[MCU]]s and the second one acts like a ST-Link/V2-1 device. Contrary to the [[#ST-Link/V2|ST-Link/V2]], this one does include a SWO pin AND a USB/UART interface.

ST-Link/V2-1 devices does not exist as a stand-alone product, but they can be broken off the Nucleo and used as a stand-alone device. The complete schematics is available in the manual of the Nucleo boards, so it is in fact possible to use this to build your own. An example of that is shown here: [[DIY STM32 Programmer (ST-Link/V2-1)]].

[[File:STM32 Programmer fully assembled - 5pcs.jpg|600px|Home made ST-Link/V2-1 devices]]

{{clear}}

== ST-Link/V3MINIE ==
[[File:ST-Link V3MINIE Photo.png|thumb|300px]]
To be added
{{clear}}

== ST-Link/V3SET ==
[[File:ST-Link V3SET.png|thumb|300px]]
To be added
{{clear}}

== Hardware Analysis ==

[[ST]] does not make schematics or source code available for the official ST-Link devices, which is a pity (and a somewhat odd business decision). However, they '''do''' publish a partial schematics since a built-in ST-Link device is included in all their development boards, a partial schematics is available.

<div class="res-img">
[[File:ST-Link V2.1 Original Schematics.png|1800px]]
</div>

From the schematics we can see that the ST-Link device is build around a STM32F103CBT6 which is the 128 kB Flash version.

PC13 and PC14 (and possibly PC15 in the future) appears to be working as a means for the firmware to identify the "version" of the hardware. On above schematics, PC13 is pulled low with a resistor while PC14 (and PC15) are left floating.

A voltage divider splitting +3.3 V in half is connected to PA0 and labelled AIN_1. The ST-Link devices are capable of measuring the target processor supply voltage and this is probably a workaround of the development boards (which know their supply voltage already).

The "output" pins of the ST-Link V2 are as follows:

{| class="wikitable"
|-
! Pin
! Label
! Remarks
|-
| PA0
| AIN_1
| Probably meant as an analog input, measuring the supply voltage on the target device. On the development boards, the supply voltage is well known, so this pin is connected to a voltage divider splitting the supply voltage in half (1.65V or thereabouts).
|-
| PA5
| T_JTCK
| Target Clock
|-
| PA6
| T_JTDO
|
|-
| PA7
| T_JTDI
|
|-
| PA10
| T_SWO
| Target trace debugging. This pin is unconnected on the Chinese clone ST-Links, which is annoying.
|-
| PA12
| T_SWDIO_IN
| On development boards connected via a 100 Ohm resistor to PA14
|-
| PA13
| T_JTCK
|
|-
| PA14
| T_JTMS
|
|-
| PB0
| T_NRST
|
|-
| PB1
| T_JRST
| Labelled but not connected to anything
|}

== Upgrade issues ==

The little colorful Chinese clones have been reported to sometimes fail firmware upgrade. This is partly to be expected as they are '''not''' using real [[STM32]] [[MCU]]s. We bought a pile of these at some point and none of those ever failed though.

== More Reading ==

Github user lujji have done a number of interesting writeups on ST-Link devices, reverse engineering the ST-Link firmware and adding trace (SWO) support to the cheap Chinese ST-Link devices.

* [https://lujji.github.io/blog/stlink-clone-trace/ Adding Trace support to ST-Link clones]
* [https://lujji.github.io/blog/reverse-engineering-stlink-firmware Reverse-engineering ST-Link firmware part 1]
* [https://lujji.github.io/blog/reverse-engineering-stlink-firmware-part2 Reverse-engineering ST-Link firmware part 2]
* [https://stm32world.com/images/5/55/St-link-slsh-v2.pdf ST-Link/V2 Product Sheet]
* [https://stm32world.com/images/2/27/Stlink-v3minie.pdf ST-Link/V3MINIE Product Sheet]
* [https://stm32world.com/images/1/1c/Stlink-v3set.pdf ST-Link/V3SET Product Sheet]
* [[DIY STM32 Programmer (ST-Link/V2-1)]]

STM32CubeMX from one MCU to another

2026-10-05T05:11:20Z

Lth: Created page with "{{Video |series=STM32 Tutorial Video |number=104 |title=STM32CubeMX from one MCU to another |youtube-id=oBbHGRgLxGM |description=In this video we will demonstrate how you can..."

{{Video
|series=STM32 Tutorial Video
|number=104
|title=STM32CubeMX from one MCU to another
|youtube-id=oBbHGRgLxGM
|description=In this video we will demonstrate how you can move a STM32CubeMX project from one MCU model to another. Spoiler: it is not simple and easy!!! We will port a project from a STM32F407VE to a STM32H723VE.
}}

Streamline MCU RP2354

2026-10-05T03:49:15Z

Lth:

[[Category:RP2350]][[Category:Streamline]][[Category:Streamline Blade]]{{metadesc|RP2354 Streamline MCU board documentation}}
[[File:Streamline RP2350 setup - top left.jpg|350px|thumb|Streamline backplane with Connect and MCU RP2354]]
The [[Streamline MCU RP2354]] is a basic [[Streamline]] [[RP2354]] [[MCU]] board build around a [[RP2354]].
{{clear}}

== Videos ==

In order not to "pollute" the STM32World channel, we made another channel for RP2350 stuff. You can access this channel here: [https://www.youtube.com/@RPPicoWorld/videos https://www.youtube.com/@RPPicoWorld].

One of the first videos using the [[Streamline MCU RP2354]]:

{{#ev:youtube|z-0-4W92aTU}}

== Schematics ==

<div class="res-img">
[[File:sl_mcu_rp2354.svg|2000px]]
</div>

== Errata ==

The [[Streamline MCU RP2354]] has gone through a number of revisions. The current version is rev. D.

=== Rev. D ===

One mistake was made with the onboard LED. It is connected to the PC13 pin on the header but it is '''not''' connected to the MCU. This is easily fixed with a jumper on the header - like this:

<div class="res-img">
[[File:Rev D Fix 3.jpg|600px]]
</div>

<gallery>
File:Rev D Fix 1.jpg
File:Rev D Fix 2.jpg
File:Rev D Fix 3.jpg
File:Rev D Fix 4.jpg
</gallery>

== Gallery ==

<gallery>
File:sl_mcu_rp2354_top_right_render.png
File:sl_mcu_rp2354_top_render.png
File:sl_mcu_rp2354_top_left_render.png
File:sl_mcu_rp2354_bot_render.png
File:Streamline RP2350 setup - top left.jpg
File:Streamline RP2350 setup - top right.jpg
File:Streamline RP2350 setup - top right 2.jpg
</gallery>

Streamline MCU RP2354

2026-10-05T03:47:48Z

Lth: /* Rev. D */

[[Category:RP21350]][[Category:Streamline]][[Category:Streamline Blade]]{{metadesc|RP2354 Streamline MCU board documentation}}
[[File:Streamline RP2350 setup - top left.jpg|350px|thumb|Streamline backplane with Connect and MCU RP2354]]
The [[Streamline MCU RP2354]] is a basic [[Streamline]] [[RP2354]] [[MCU]] board build around a [[RP2354]].
{{clear}}

== Videos ==

In order not to "pollute" the STM32World channel, we made another channel for RP2350 stuff. You can access this channel here: [https://www.youtube.com/@RPPicoWorld/videos https://www.youtube.com/@RPPicoWorld].

One of the first videos using the [[Streamline MCU RP2354]]:

{{#ev:youtube|z-0-4W92aTU}}

== Schematics ==

<div class="res-img">
[[File:sl_mcu_rp2354.svg|2000px]]
</div>

== Errata ==

The [[Streamline MCU RP2354]] has gone through a number of revisions. The current version is rev. D.

=== Rev. D ===

One mistake was made with the onboard LED. It is connected to the PC13 pin on the header but it is '''not''' connected to the MCU. This is easily fixed with a jumper on the header - like this:

<div class="res-img">
[[File:Rev D Fix 3.jpg|600px]]
</div>

<gallery>
File:Rev D Fix 1.jpg
File:Rev D Fix 2.jpg
File:Rev D Fix 3.jpg
File:Rev D Fix 4.jpg
</gallery>

== Gallery ==

<gallery>
File:sl_mcu_rp2354_top_right_render.png
File:sl_mcu_rp2354_top_render.png
File:sl_mcu_rp2354_top_left_render.png
File:sl_mcu_rp2354_bot_render.png
File:Streamline RP2350 setup - top left.jpg
File:Streamline RP2350 setup - top right.jpg
File:Streamline RP2350 setup - top right 2.jpg
</gallery>

Streamline MCU RP2354

2026-10-05T03:46:00Z

Lth:

[[Category:RP21350]][[Category:Streamline]][[Category:Streamline Blade]]{{metadesc|RP2354 Streamline MCU board documentation}}
[[File:Streamline RP2350 setup - top left.jpg|350px|thumb|Streamline backplane with Connect and MCU RP2354]]
The [[Streamline MCU RP2354]] is a basic [[Streamline]] [[RP2354]] [[MCU]] board build around a [[RP2354]].
{{clear}}

== Videos ==

In order not to "pollute" the STM32World channel, we made another channel for RP2350 stuff. You can access this channel here: [https://www.youtube.com/@RPPicoWorld/videos https://www.youtube.com/@RPPicoWorld].

One of the first videos using the [[Streamline MCU RP2354]]:

{{#ev:youtube|z-0-4W92aTU}}

== Schematics ==

<div class="res-img">
[[File:sl_mcu_rp2354.svg|2000px]]
</div>

== Errata ==

The [[Streamline MCU RP2354]] has gone through a number of revisions. The current version is rev. D.

=== Rev. D ===

One mistake was made with the onboard LED. It is connected to the PC13 pin on the header but it is '''not''' connected to the MCU. This is easily fixed with a jumper on the header - like this:

<div class="res-img">
[[File:Rev D Fix 4.jpg|600px]]
</div>

<gallery>
File:Rev D Fix 1.jpg
File:Rev D Fix 2.jpg
File:Rev D Fix 3.jpg
File:Rev D Fix 4.jpg
</gallery>

== Gallery ==

<gallery>
File:sl_mcu_rp2354_top_right_render.png
File:sl_mcu_rp2354_top_render.png
File:sl_mcu_rp2354_top_left_render.png
File:sl_mcu_rp2354_bot_render.png
File:Streamline RP2350 setup - top left.jpg
File:Streamline RP2350 setup - top right.jpg
File:Streamline RP2350 setup - top right 2.jpg
</gallery>

Streamline MCU RP2354

2026-10-05T03:45:06Z

Lth: /* Rev. D */

[[Category:RP21350]][[Category:Streamline]][[Category:Streamline Blade]]{{metadesc|RP2354 Streamline MCU board documentation}}
[[File:Streamline RP2350 setup - top left.jpg|350px|thumb|Streamline backplane with Connect and MCU RP2354]]
The [[Streamline MCU RP2354]] is a basic [[Streamline]] [[RP2354]] [[MCU]] board build around a [[RP2354]].
{{clear}}

== Videos ==

In order not to "pollute" the STM32World channel, we made another channel for RP2350 stuff. You can access this channel here: [https://www.youtube.com/@RPPicoWorld/videos https://www.youtube.com/@RPPicoWorld].

One of the first videos using the [[Streamline MCU RP2354]]:

{{#ev:youtube|z-0-4W92aTU}}

== Schematics ==

<div class="res-img">
[[File:sl_mcu_rp2354.svg|2000px]]
</div>

== Errata ==

The [[Streamline MCU RP2354]] has gone through a number of revisions. The current version is rev. D.

=== Rev. D ===

One mistake was made with the onboard LED. It is connected to the PC13 pin on the header but it is '''not''' connected to the MCU. This is easily fixed with a jumper on the header - like this:

<div class="resimg">
[[File:Rev D Fix 4.jpg|width=600px]]
</div>

<gallery>
File:Rev D Fix 1.jpg
File:Rev D Fix 2.jpg
File:Rev D Fix 3.jpg
File:Rev D Fix 4.jpg
</gallery>

== Gallery ==

<gallery>
File:sl_mcu_rp2354_top_right_render.png
File:sl_mcu_rp2354_top_render.png
File:sl_mcu_rp2354_top_left_render.png
File:sl_mcu_rp2354_bot_render.png
File:Streamline RP2350 setup - top left.jpg
File:Streamline RP2350 setup - top right.jpg
File:Streamline RP2350 setup - top right 2.jpg
</gallery>

Streamline MCU RP2354

2026-10-05T03:44:40Z

Lth: /* Rev. D */

[[Category:RP21350]][[Category:Streamline]][[Category:Streamline Blade]]{{metadesc|RP2354 Streamline MCU board documentation}}
[[File:Streamline RP2350 setup - top left.jpg|350px|thumb|Streamline backplane with Connect and MCU RP2354]]
The [[Streamline MCU RP2354]] is a basic [[Streamline]] [[RP2354]] [[MCU]] board build around a [[RP2354]].
{{clear}}

== Videos ==

In order not to "pollute" the STM32World channel, we made another channel for RP2350 stuff. You can access this channel here: [https://www.youtube.com/@RPPicoWorld/videos https://www.youtube.com/@RPPicoWorld].

One of the first videos using the [[Streamline MCU RP2354]]:

{{#ev:youtube|z-0-4W92aTU}}

== Schematics ==

<div class="res-img">
[[File:sl_mcu_rp2354.svg|2000px]]
</div>

== Errata ==

The [[Streamline MCU RP2354]] has gone through a number of revisions. The current version is rev. D.

=== Rev. D ===

One mistake was made with the onboard LED. It is connected to the PC13 pin on the header but it is '''not''' connected to the MCU. This is easily fixed with a jumper on the header - like this:

<div class="res-img">
[[File:Rev D Fix 4.jpg|width=600px]]
</div>

<gallery>
File:Rev D Fix 1.jpg
File:Rev D Fix 2.jpg
File:Rev D Fix 3.jpg
File:Rev D Fix 4.jpg
</gallery>

== Gallery ==

<gallery>
File:sl_mcu_rp2354_top_right_render.png
File:sl_mcu_rp2354_top_render.png
File:sl_mcu_rp2354_top_left_render.png
File:sl_mcu_rp2354_bot_render.png
File:Streamline RP2350 setup - top left.jpg
File:Streamline RP2350 setup - top right.jpg
File:Streamline RP2350 setup - top right 2.jpg
</gallery>

Streamline MCU RP2354

2026-10-05T03:43:18Z

Lth: /* Rev. D */

[[Category:RP21350]][[Category:Streamline]][[Category:Streamline Blade]]{{metadesc|RP2354 Streamline MCU board documentation}}
[[File:Streamline RP2350 setup - top left.jpg|350px|thumb|Streamline backplane with Connect and MCU RP2354]]
The [[Streamline MCU RP2354]] is a basic [[Streamline]] [[RP2354]] [[MCU]] board build around a [[RP2354]].
{{clear}}

== Videos ==

In order not to "pollute" the STM32World channel, we made another channel for RP2350 stuff. You can access this channel here: [https://www.youtube.com/@RPPicoWorld/videos https://www.youtube.com/@RPPicoWorld].

One of the first videos using the [[Streamline MCU RP2354]]:

{{#ev:youtube|z-0-4W92aTU}}

== Schematics ==

<div class="res-img">
[[File:sl_mcu_rp2354.svg|2000px]]
</div>

== Errata ==

The [[Streamline MCU RP2354]] has gone through a number of revisions. The current version is rev. D.

=== Rev. D ===

One mistake was made with the onboard LED. It is connected to the PC13 pin on the header but it is '''not''' connected to the MCU. This is easily fixed with a jumper on the header - like this:

<gallery>
File:Rev D Fix 1.jpg
File:Rev D Fix 2.jpg
File:Rev D Fix 3.jpg
File:Rev D Fix 4.jpg
</gallery>

== Gallery ==

<gallery>
File:sl_mcu_rp2354_top_right_render.png
File:sl_mcu_rp2354_top_render.png
File:sl_mcu_rp2354_top_left_render.png
File:sl_mcu_rp2354_bot_render.png
File:Streamline RP2350 setup - top left.jpg
File:Streamline RP2350 setup - top right.jpg
File:Streamline RP2350 setup - top right 2.jpg
</gallery>