Hoverboard-Firmware-Hack-Gen2.x
Hoverboard-Firmware-Hack-Gen2.x copied to clipboard
RoboDurden
XK3011PT A32AA019 is this familiar or similar?
Hello!
I would like to use this board through serial control. But haven't been able to identify the IC to start experimenting.
This is what the big chip name reads XT3011PT A32AA019
Would appreciate any direction. Thank you!!
Pictures of the board attached
before posting an issue you should remove all the connectors and rf module blocking the pcb and use the master board not the slave but no there seems to be no information about this chip it could been rebranded chip but the pin number is also wrong they have really cutten corners on this board theres not much on it if you are desprate ypu can try to read the chip id anyways with swd programmer and search for that if its an rebranded chip you will be able to find it if it do not have a programming headder its an asic and not reprogramable now the mm32spin05 board is supported you should just buy one of those
Sorry here is a cleaner picture.
Am assuming it's the master board because it has a RF receiver on it? Or else the other board too has the same IC on it
now the mm32spin05 board is supported you should just buy one of those
Are you suggesting to buy one of the hoverboard that's built using this IC? Unfortunately I can't look at what IC it is before purchasing, and am unable to return this back.
I got mine on www.hoverpro.in
you are desprate ypu can try to read the chip id anyways with swd programmer and search for that if its an rebranded chip you will be able to find it if it do not have a programming headder
Does the bottom right corner of the image I posted look like the SWD programming header?
The RF receiver board
I am also highly pesimistic about this mcu. Could you please link the exact module you purchased so we have photos from the outside look/housing and other people will not buy this hoverboard.
The 2.2 layout has a 32 pin version of the gd32f130. If you are extremely lucky, your mcu is pin compatible:
PA14 is SWD CLK and PA13 is SWD_IO. You could test with the multimeter in beeping diode-tester mode to see if these two pins go the the 4 pin female dupont header.
P.S. i would not buy a MM32 motherboard but try to get a good old GD32F130 with 64kB and two dual-opamp 8-sot chips on board.
P.P.S. as this 4 pin header is for rf module, it will rather connect to a serial uart and not the SWD header. Maybe @AILIFE4798 could see a chance with serial flashing, but i have never looked into that way.
Thank you so much for your reply guys!
This is the exact piece I purchased. https://hoverpro.in/product/h6-eco-military-blue-hoverboard-with-bluetooth-and-remote/
If there's a way I can identify hoverboard with GD32F130 on this website it would be great. Or if there are links to the products on Amazon, somewhere on the repo/wiki please direct me there.
the empity 4 pin connector may be swd but i cannot tell without enough information the master board have a power button and 15v regulator, the rf module is on slave to spread the pins to use cheaper micro controllers a mm32 board is $2 for a set or gd32c8 board is $1 for one piece i developed the mm32 firmware and robo developed the gd32 firmware so you can decide which one you want i will admit the gd 32 board have 2 opamp and may support foc in the future while your current board do not even have comparator in the chip
P.P.S. as this 4 pin header is for rf module, it will rather connect to a serial uart and not the SWD header.
No. I meant there's a seperate unused 4pin header(green circled), nothing soldered. And one black with female headers soldered(red circled) which has the RF for serial.
I have added a "BEWARE of these hoverboards" folder :
https://github.com/RoboDurden/Hoverboard-Firmware-Hack-Gen2.x/tree/main/BEWARE%20of%20these%20hoverboards
As we have autodetect at least for gd32 by now, it might be worth some further investigation on how to flash these custom mcu - if possible at all.
But i for sure will have not time for that.
@AILIFE4798 please post the $1 / $2 links again. But i thought the gd32 board was only the slave board ?
@saikumaru does your hoverboard have plastic wheels or good old aluminium rims ?
Today i fear you can only get complete hoverboards with old gd32f130 as used and no longer brand new :-/
yeah gd32 is only slave and i have not able to get it working yet and i cannot debug gd32f130 for some reason to find whats wrong i will post link later if it still exist
MM32 aliexpress: de,aliexpress,com/item/1005005959910034.html MM32 taobao: item,taobao,com/item.htm?id=743458922569 GD32 taobao: item,taobao,com/item.htm?id=722577319258
= MM32 aliexpress: https://de.aliexpress.com/item/1005005959910034.html (does not ship to Germany) MM32 taobao: https://item.taobao.com/item.htm?id=743458922569 GD32 taobao: https://item.taobao.com/item.htm?id=722577319258
Ok here is the other board. This has the power switch and also a Bluetooth device powered through it. So this must be the master board? I hope it gives a better idea now
@saikumaru does your hoverboard have plastic wheels or good old aluminium rims ?
Today i fear you can only get complete hoverboards with old gd32f130 as used and no longer brand new :-/
Mine is plastic wheel with rubber tyres. Like the QC sticker says, this one was manufactured in November '23. So definitely new :( but new IC as well
yes this is the master but theres also not a whole lot on it didnt even see self hold circuitry i think its using asic unfortunately not available on chinese website even or just rebranded chip
the layout2.21 mm32 board have manufacture date of 20240113
to try prevent people like us flashing it the manufacture will laser off the original marking and write new one but if the empty header is swd you can try to read the chip ID to find
The 2.2 layout has a 32 pin version of the gd32f130. If you are extremely lucky, your mcu is pin compatible:
PA14 is SWD CLK and PA13 is SWD_IO. You could test with the multimeter in beeping diode-tester mode to see if these two pins go the the 4 pin female dupont header.
This does match! I am able to beep the pins 23, 24 as you pointed out to the two pins of the 4pin dupont header. Should I just got ahead and solder a SWD connector and follow some suggested steps?
you should read chip ID with pyocd and the board is 5v so be careful
Are these steps documented anywhere please, especially the 5V care? I had played with ESP32/82666/Atmegas in the past, but not something that has an SWD
stlink v2 clone can all handle 5v if you want to use esp32 you need a series resistor 150R should be enough as the current does not exeed the 20ma rated for protection diode
I think the "Flash via PYocd" wiki page is still missing.
Yes, I see the link doesn't exist on wiki. Would you suggest something else please? "Flash via Keil"?
on my stlink it cannot detect target so i assume it wont work
your board actually is like the mm32 board using chip internal comparator for phase current i can see the circuit in your better picture
maybe you can replace it with a mm32 because mm32spin06 is abailable in 32pin
unfortunately they not only erased the number, but also the dimple in the chip so i cannot tell which way is up and if the pinout is correct
check the ground and VDD connection, the gd32f130 32pin do not have ground???
I think the 32 pin MCU does not have the 32 pins to the side but underneath. Gnd are 9 pads underneath in the middle of the backside.
I think replacing the MCU is not worth the trouble anyway. But if doing it the a little heat gun from the backside is the easiest way anyway I guess. So it does not really makes.a difference if the pins are underneath.
But here the pins are sideways, so maybe your Mm32 32 pin version fits.
Or maybe India has stepped up and can now also produce such simple MCU :-)
yes true the mcu cost more then $1 probably so just get a new board to replace
I see the pin 32 is connected to ground of 78L05, and also is one of the pins of dupont header. But what should the 4th pin be please?
I see the 4th pin on header is connected to a sensor on the back, after a resistor. But can't trace it back to MCU anywhere. Should this be a 5V connection?