-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gen2.1.9 (ex2.11) - Help identify board layout (GD32F130C8T6) #27
Comments
Okay you have to update your downloaded code and uncomment your layout in config.h :
In remoteDummy.c uncomment line 19:
Then turning the motor by hand might already light up some leds. UART header might also already work. You will need a permanent on switch instead of an the push button to keep the bord powered until you have traced the two pins i mentioned earlier. Of course there is the risk that you will break your board. |
There are no photo-diodes / light barriers on the backside AND id do not see a header to plugin two connectos with exteran photo-diodes ?? |
Hi @RoboDurden! Thanks a lot for your quick response. I got good news -- bad news: I flashed the layout following your instructions. Also, I did trace that all the battery status LEDs and they are all here: I also changed it in the layout:
The bad news is that I can no longer connect to the target to flash the changes I tried everything. Restarting, reinstalling St-link USB drive... updated it's firmware... Nothing works! Any idea what could it be and how to unbrick it if it's not fried? |
If you are running Windows, make a batch file in the st-flash-exe folder: st-flash --connect-under-reset write hoverboard.bin 0x8000000.bat containing the single line https://pionierland.de/hoverhack/gen2/ReadyToFlash/st-flash%201.7.0%20Windows%20x86%2064bit.zip locate your latest hoverboard.bin file in HoverBoardGigaDevice/BinariesToFlash If this does not work, you need the NREST pin Unplugging the st-link-v2 of course also helps sometimes.. Try tracing the three hall inputs ! |
I see. My cheap clone is a little different so I used this article since it looks exactly the same. Surprisingly it uses exactly the same MCU as the board (GD32F130C8T6): What I do not get if I should now connect the NRST of the ST-Link to the NRST of the board? |
Thanks for all your help again! I've had no success with connecting the RST wire but it may be due to different issue. After a lot of trial and error I think the cheap clone may be faulty and bending pushing it up and down in the USB port worked the best. I wrote this
(It goes into ./HoverBoardGigaDevice/BinariesToFlash/) That's what it looks like before connecting the ST-Link dongle and right after it's connected it flashes it successfully without the NRST wire Video_2023-09-30_150548.mp4I can now see 2 leds flash when I rotate the motor by hand: IMG_5409.mp4I couldn't get the middle hall/led work and I tried every single pin:
There is no issue with the led itself because I can change the Red, green, orange and the led works so it's either the wrong hall pin or something else overwriting it? How do I test the motor if it works? I've tried with What should I try next? |
It is a bit risky to also connect the 3.3V from st-link to hoverboard. Better only power the board with a 2A CC power supply. Which led is not working ? And make sure the other two have the correct color naming:
disable the following lines by adding // before each: #define DEBUG_LED_PIN LED_RED Then the DEBUG_LedSet macros in defines.h is defined to nothing and some code somewhere in the project will not overwrite the LED_RED behavior:
If The motor should spin nicely with |
Nice bat file ! Thank you ! |
And please close the motor when sending speed commands. It can not spin freely with the backside bearing missing. |
@miro-ux your bat file is not behaving like in your nice video :-(
Windows 10 here. |
Okay, i get flash error -1 :-/
I currently try to flash a gen1 board with EFeru binary.. |
@RoboDurden Sorry to hear that. I think it's due to the error. If it doesn't flash successfully it will keep looping. No sure why you're getting |
Sorry for the confusion. I think i simply had to reboot my Laptop. Windows :-/ |
Hi I have this board also from a razor hovertrax. I worked on this last year and am revisiting now.
shutdown main.c:485 changed to:
|
Thanks for your defines. You have an old source code. I have moved to PB14 nstead of GPIOB and GPIO_PIN_14 quite long ago. So the Uart protocols might no longer be compatible! |
Hi, I'm a complete noob. 👋🏻
I can't tell if any of the layouts are the one I have.
I was able to unlock the board and flash it from Keil but now I'm afraid to power it on due to not knowing which layout to config.
The MCU is a GD32F130C8T6
I'm also not sure if I got the master/slave right.
Master:
![hoverboard_GD32F130C8T6_hovertrax_razor](https://private-user-images.githubusercontent.com/7188826/270464288-f491ca16-b9b1-4092-8125-e3418caca224.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM0NDI5MDIsIm5iZiI6MTcyMzQ0MjYwMiwicGF0aCI6Ii83MTg4ODI2LzI3MDQ2NDI4OC1mNDkxY2ExNi1iOWIxLTQwOTItODEyNS1lMzQxOGNhY2EyMjQuanBnP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgxMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MTJUMDYwMzIyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ODJhOTM2YzlkNmQ2ZWJkYWU4ZDlmZGFmMWJiNzhkYTM5NGUzZjBkOTNmZTUyMmQ4NjA1MzQyZjAzNjcyOWI4NiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.33gONntncE09DSe_fLom-F-IU1HoTKvGBJYGnZN61oU)
The Slave looks identical except it has the Switch+Switch LED I think and has no charger port.
![IMG_5374](https://private-user-images.githubusercontent.com/7188826/270465033-72c1dadf-3770-4bbf-a1f4-9a123c4293d9.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM0NDI5MDIsIm5iZiI6MTcyMzQ0MjYwMiwicGF0aCI6Ii83MTg4ODI2LzI3MDQ2NTAzMy03MmMxZGFkZi0zNzcwLTRiYmYtYTFmNC05YTEyM2M0MjkzZDkuanBnP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgxMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MTJUMDYwMzIyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NTMwMzExYjAwYzY2NDkwZGFlMzcwNWZhN2M2YWUxOTZjYjYwYjBjYmUwOTA0OGI2NzJjOTRkYmNmZDE5ZjZmYSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.I__BQ1pebP1nEXuCO-V444xJsPH-u7YHaETMBifcMtA)
MOSFET + MCU view:
![image](https://private-user-images.githubusercontent.com/7188826/270465966-0fd9e764-4104-4f22-86b6-32ba45ab8ea4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM0NDI5MDIsIm5iZiI6MTcyMzQ0MjYwMiwicGF0aCI6Ii83MTg4ODI2LzI3MDQ2NTk2Ni0wZmQ5ZTc2NC00MTA0LTRmMjItODZiNi0zMmJhNDVhYjhlYTQucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgxMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MTJUMDYwMzIyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NmIzZTg1ZTIyZjQ2ZGJmNzhhYWI5NjgwOWRjYTJkZjZmYzFiYTE3YjViMGY5OTA5NzNiYTE0Y2IwYTBjYzIyOCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.qA5ttteIkubFfDmhQoesqXIQVyhvI0bIWq3tZY_rTCs)
Please let me know if you need anything else to help me identify or what should I do if it's a new layout.
The text was updated successfully, but these errors were encountered: