ONE FREE FIRMWARE FLASH TURNS TWO BROKEN HOVERBOARD MOTORS INTO A GO-KART

Every scrapped hoverboard has two good brushless motors and a mainboard — this free firmware flash turns them into a proper drive you can steer with anything.

by Emanuel Feru

FULL CAD BOM FIRMWARE DOCS

RoboticsOpen-hardware

difficulty
●●●●
time
a weekend
license
GPL-3.0
repo
repo ACTIVE1,719 stars

WHAT YOU’LL NEED

  • Dev board / microcontrollerruns the project firmware
  • Soldering kit + basic toolsone-time buy, serves every future build

Partner

Reach your Pi from anywhereRemote desktop to the machine running this build — no port forwarding, works right from the browser.Try Getscreen.me
1

COMPAREE VERDICT

This is a firmware replacement for the locked mainboard inside a hoverboard, giving you smooth field-oriented control of two brushless hub motors that would otherwise be unusable. The reference demo is a go-kart, but the same firmware has been used for wheelchairs, cargo platforms, and custom robots. The repository is honest about what it is: you flash the board, configure the control input (UART, PWM, PPM, iBUS, analog ADC, or I2C), and the motors do what you tell them. The single biggest trap is that not all hoverboard mainboards are identical — the wiki lists supported variants, but if you buy one sight-unseen from a marketplace, you may end up with an incompatible revision or a board that needs different pad connections. The author's claim that the modification is reversible is true in the sense that you can flash the original firmware back, but if you have already cut the hoverboard frame apart for a build, the hoverboard as a product is obviously not coming back. The project costs almost nothing if you already have a donor board and a programmer, but if you are buying both from scratch, budget for a second-hand hoverboard and an ST-Link clone. For someone with basic soldering skills and willingness to read a Wiki before plugging things in, this is one of the most cost-effective ways to get two powerful brushless drives. For someone expecting plug-and-play or a complete go-kart kit, it will waste a weekend.

NOT IN THE REPO

  • The repository provides the replacement firmware, flashing instructions, and a detailed wiki covering variants of the hoverboard mainboard.
  • There is no bill of materials — you bring your own broken or second-hand hoverboard, and the firmware assumes you already own an ST-Link programmer.
  • The demo build (go-kart frame) is documented in community tutorials, not in the repository itself.
  • The licence is GPL-3.0 and permits commercial use.
  • The author states no irreversible modification is made to the hardware, so factory firmware can be restored.
  • Last push was July 2026 and the project remains active.

Can I build this?

Printnothing required
Buya broken or second-hand hoverboard, an ST-Link V2 programmer (clone is fine), and wire for control signal connections
Toolssoldering iron, ST-Link Utility or STM32CubeProgrammer, and a power supply or the hoverboard's original battery pack
Skillsintermediate — you must solder signal wires, read datasheets to identify your mainboard variant, and debug serial or PWM control inputs if they do not work first try
Timea weekend — one afternoon to disassemble the hoverboard and flash the firmware, another to wire and test the control input you plan to use
Cost$ — dominated by the donor hoverboard if bought second-hand (£20–50), the ST-Link programmer if not already owned (£5–10), and optionally a control board like an Arduino or RC receiver
SafetyLithium polymer battery packs are present in most hoverboards — do not short the terminals, do not puncture cells during disassembly, and do not leave the pack connected while soldering near it. Brushless motors can deliver high torque — secure the hoverboard or frame before testing, because uncontrolled movement will injure you or damage the build. The flash process itself is low-voltage and safe.

Build at your own risk. Projects involve tools, electronics and sometimes mains voltage — follow the creator’s safety notes.

A desktop 3D printer that prints in full colorPartner · Kickstarter
A desktop 3D printer that prints in full color

HeyGears G1: 10M+ colors and transparent parts in one print, plus UV printing on flat objects. Figures, parts and labels — no painting.

See how it prints

Videos

Community walkthrough covering the flash process and wiring for one common mainboard variant.

Gallery

https://content.instructables.com/FT9/6C72/K9R4G9G5/FT96C72K9R4G9G5.png?auto=webp&fit=bounds&frame=1&height=620&width=620
https://img.youtube.com/vi/IgHCcj0NgWQ/maxresdefault.jpg
https://img.youtube.com/vi/UnlbMrCkjnE/maxresdefault.jpg

Start here

Navigation into the creator’s own docs — we don’t rewrite the guide, we route you to the source.

  1. 1.Read the repository Wiki to confirm your hoverboard mainboard is a supported variant (The Wiki lists known board types and their pad assignments — if yours is not listed, the firmware may not work or may require different signal wiring.)
  2. 2.Acquire an SWD programmer - an ST-Link V2 clone is the usual choice(A clone is adequate for this project and costs under £10.)
  3. 3.Disassemble the hoverboard, disconnect the battery, and locate the programming pads on the mainboard(The Wiki provides photos of pad locations for common boards.)
  4. 4.Flash the firmware using ST-Link Utility or STM32CubeProgrammer (The repository README links to the pre-built binary and step-by-step flashing instructions.)
  5. 5.Wire your chosen control input (PWM, UART, or I2C) and test motor response before final assembly(Start with the motors elevated or secured so they cannot move the frame during initial testing.)

Resources

Documentation, files and community threads for this build — we link straight to the original sources and never rehost the creator’s files.

KNOWN ISSUES

  • Not all hoverboard mainboards are the same — some have different microcontrollers or require different pad connections, and if you buy one second-hand without checking the variant first, the firmware may not flash or the motors may not respond.
  • The repository assumes you already know how to use an ST-Link programmer and can identify the correct pads on the mainboard — if this is your first STM32 flash, budget extra time to learn the toolchain.
  • The control input (PWM, UART, or I2C) must be configured in the firmware before flashing — the default may not match your intended input device, and reflashing to change it adds another round-trip.
  • The hoverboard's original battery pack is a multi-cell lithium polymer and must be handled carefully during disassembly — a shorted or punctured cell will catch fire.
  • The motors deliver high torque and will move the frame violently if power is applied while it is unsecured — test with the wheels off the ground or the frame clamped down.
  • The author's claim that the modification is reversible refers to the firmware only — if you have already cut the hoverboard frame or desoldered components to fit a go-kart chassis, the hoverboard itself is obviously not going back to original condition.

Can I use this firmware on any hoverboard?

No — the firmware is written for hoverboards with STM32-based mainboards, and even within that family, different revisions may have different pad layouts or require different configuration. The repository Wiki lists known compatible boards, and if yours is not on the list, you will need to reverse-engineer the pinout or find a different donor board.

Do I need to build a go-kart, or can I use the firmware for something else?

The go-kart is the reference demo, not a requirement — the firmware simply gives you smooth control of two brushless motors, and people have used it for wheelchairs, cargo platforms, robots, and other custom builds. You provide the control input and the mechanical frame.

Is the modification reversible?

You can flash the original firmware back onto the mainboard and restore factory function, but if you have already cut the hoverboard frame or removed components for a build, the hoverboard as a product is not coming back. The author's claim is about the electronics, not the physical assembly.

What control input does the firmware support?

PWM, UART, and I2C are all supported, but you must configure the firmware for your chosen input before flashing. The default may not match your intended control device (Arduino, RC receiver, joystick), so check the configuration file first.

Community builds

No community builds yet — be the first, we feature the best ones.

Discussion1

FROM THE COMPAREE TEAM

1,700 people have already starred this, and the last push was July 2026 — the project is still moving. If you have flashed one of these boards, which mainboard variant did you use, and did the control input work first try or did you have to reflash?

CompareeTEAM22d agoedited

Practical notes from our verification: the repository provides the firmware and a detailed Wiki, but does not include a bill of materials or go-kart build guide — those are in community tutorials linked from the README. The two YouTube walkthroughs we found (one for flashing, one for the go-kart assembly) are both community-made, not official project videos. The single biggest decision point is whether your donor hoverboard is a supported variant — the Wiki lists known boards, but if you are buying second-hand, ask the seller for a photo of the mainboard before committing. The claim that nothing is modified irreversibly is correct for the electronics (you can flash the original firmware back), but obviously does not apply if you have already cut the hoverboard frame apart for a build. The project is GPL-3.0 and permits commercial use, so if you are building one to sell, there is no licence trap.

Emanuel Feru

Emanuel Feru developed this firmware to unlock the potential of hoverboard hardware that would otherwise be locked to factory control schemes or discarded after mechanical failure. The project has become one of the most widely used references for repurposing brushless hub motors in the maker community.

GitHub

Star the project on GitHub

DISCLAIMER

  • Comparee is not the author of the projects featured here. All rights to each project belong to its creator — every page links to the original source, and we never host creators’ files.
  • Information is provided without warranty and may become outdated as projects evolve. Prices are indicative bands only — always check the creator’s parts list for current costs.
  • Building and operating any project is at your own responsibility. Protective equipment, safe workshop practice and compliance with local regulations are the builder’s responsibility.