mirror of
https://github.com/EFeru/hoverboard-firmware-hack-FOC.git
synced 2025-08-04 01:54:27 +02:00
Updated Compiling and flashing the firmware (markdown)
@@ -1,7 +1,5 @@
|
|||||||
Right to the STM32/GD32 chip, 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/GD32 chip, 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>
|
||||||
|
|
||||||
In case you connected the pins and you get connection errors, make sure your ST-Link dongle pins are real, by sliding the plastic cover and checking on the ST-Link board itself. An example can be seen [here](https://youtu.be/XWh8yJ_p0HA?t=60).
|
|
||||||
|
|
||||||
If you have never flashed your board 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 board 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.
|
||||||
@@ -87,10 +85,9 @@ If you have set default_envs in [platformio.ini](/platformio.ini) you can ommit
|
|||||||
### Troubleshooting
|
### Troubleshooting
|
||||||
If you cannot flash the firmware:
|
If you cannot flash the firmware:
|
||||||
- If the LED on the ST-Link is blinking, the driver installation probably didn't go well
|
- If the LED on the ST-Link is blinking, the driver installation probably didn't go well
|
||||||
|
- Make sure you properly soldered the headers/wires, clean contact is mandatory
|
||||||
|
- Make sure your ST-Link dongle pins are real, by sliding the plastic cover and checking on the ST-Link board itself. An example can be seen [here](https://youtu.be/XWh8yJ_p0HA?t=60)
|
||||||
- Make sure you properly [unlocked](https://github.com/EFeru/hoverboard-firmware-hack-FOC/wiki/How-to-Unlock-MCU-Flash) the chip
|
- Make sure you properly [unlocked](https://github.com/EFeru/hoverboard-firmware-hack-FOC/wiki/How-to-Unlock-MCU-Flash) the chip
|
||||||
- Make sure you don't have an already open connection to the chip in another software (st-link utility, ...)
|
- Make sure you 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 pin-out can differ on some of the mainboards
|
- Also keep in mind the debugging header pin-out can differ on some of the mainboards
|
||||||
- In case you connected the pins and you get connection errors, make sure your ST-Link dongle pins are real, by sliding the plastic cover and checking on the ST-Link board itself. An example can be seen [here](https://youtu.be/XWh8yJ_p0HA?t=60)
|
|
||||||
|
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user