EFeru/hoverboard-firmware-hack-FOC
1
0
Fork 1
mirror of https://github.com/EFeru/hoverboard-firmware-hack-FOC.git synced 2025-08-04 10:04:28 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated Compiling and flashing the firmware (markdown)

Candas1
2021-07-14 14:02:02 +02:00
parent cfd7a88558
commit 6662ff8f22
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
Compiling-and-flashing-the-firmware.md

@@ -1,7 +1,5 @@
Right to the STM32, there is a debugging header with GND, 3V3, SWDIO and SWCLK. Connect GND, SWDIO and SWCLK to your SWD programmer, like the ST-Link found on many STM devboards.<br> Right to the STM32, there is a debugging header with GND, 3V3, SWDIO and SWCLK. Connect GND, SWDIO and SWCLK to your SWD programmer, like the ST-Link found on many STM devboards.<br>
⚠Make sure you properly soldered the headers/wires. Also keep in mind the debugging header pinout can differ on some boards⚠
If you have never flashed your sideboard before, the MCU is probably locked. To unlock the flash, check-out the wiki page [How to Unlock MCU flash](https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/wiki/How-to-Unlock-MCU-flash). If you have never flashed your sideboard before, the MCU is probably locked. To unlock the flash, check-out the wiki page [How to Unlock MCU flash](https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/wiki/How-to-Unlock-MCU-flash).
Do not power the mainboard from the 3.3V of your programmer! This has already killed multiple mainboards. Do not power the mainboard from the 3.3V of your programmer! This has already killed multiple mainboards.
@@ -82,4 +80,11 @@ platformio run –target upload -e VARIANT_####
``` ```
If you have set default_envs in [platformio.ini](/platformio.ini) you can ommit -e parameter If you have set default_envs in [platformio.ini](/platformio.ini) you can ommit -e parameter
### Troubleshooting
If you cannot flash the firmware:
- Make sure you properly unlocked the chip
- Make sure you are don't have an already open connection to the chip in another software (st-link utility, ...)
- Make sure you properly soldered the headers/wires, clean contact is mandatory
- Also keep in mind the debugging header pinout can differ on some boards