diff --git a/Compiling-and-flashing-the-firmware.md b/Compiling-and-flashing-the-firmware.md
index 109093e..5142c6a 100644
--- a/Compiling-and-flashing-the-firmware.md
+++ b/Compiling-and-flashing-the-firmware.md
@@ -1,6 +1,8 @@
-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/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>
 
-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).
+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).
 
 Do not power the mainboard from the 3.3V of your programmer! This has already killed multiple mainboards.