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

Updated How to Unlock MCU Flash (markdown)

Candas1
2022-11-15 07:45:18 +01:00
parent dc5d00cb1e
commit dc24fd910e
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
How-to-Unlock-MCU-Flash.md

@@ -21,6 +21,7 @@ This procedure will erase the stock MCU firmware irreversibly! Perform these ste
* Step 6: Select **Disable** in `Read Out Protection` drop-down menu and click `Apply` * Step 6: Select **Disable** in `Read Out Protection` drop-down menu and click `Apply`
![unlock3](https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/blob/main/docs/pictures/wiki_unlock/unlock_mcu_3.png) ![unlock3](https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/blob/main/docs/pictures/wiki_unlock/unlock_mcu_3.png)
<br>⚠️ On GD32 chips, WD_SW should be checked<br>
* Step 7: Click `Connect to target` * Step 7: Click `Connect to target`
@@ -28,6 +29,8 @@ This procedure will erase the stock MCU firmware irreversibly! Perform these ste
* Step 8: If you see the window above, then you have successfully unlocked your MCU. You can now flash the MCU. * Step 8: If you see the window above, then you have successfully unlocked your MCU. You can now flash the MCU.
<br>⚠️ Make sure you disconnect st-link utility if you are using another tool for flashgin the firmware later<br>
## :toolbox: Troubleshooting ## :toolbox: Troubleshooting
If you get funny, unexpected behavior from your board after flashing (see this [thread](https://github.com/EmanuelFeru/hoverboard-sideboard-hack-GD/issues/3)), it is most likely that the unlocking process did not succeed properly. To fix it follow these steps: If you get funny, unexpected behavior from your board after flashing (see this [thread](https://github.com/EmanuelFeru/hoverboard-sideboard-hack-GD/issues/3)), it is most likely that the unlocking process did not succeed properly. To fix it follow these steps:
* Step 1: Lock the GD32 following the Steps above in reverse order * Step 1: Lock the GD32 following the Steps above in reverse order