Hoverboard-Firmware-Hack-Gen2.x
Hoverboard-Firmware-Hack-Gen2.x copied to clipboard
RoboDurden
Gen2.4.2 (ex2.8.1)
MCU:MM32SPIN05PFOP(32K)
Gate driver: uni u3116s
Voltage:5V!!!
No optical sensors is on this board It is pin compatible with Layout 2.8
the manufacture really said : fuck your foc im not gonna include an opamp for you
@AILIFE4798 , This board really looks very different to 2.8. So i would like to assign a new number 2.21 to it.
It will not help new people to identify their board when 2.21 is hidden as 2.8.1.
Yes, i am okay if you want to do a standalone MM32 firmware. Maybe you would like to copy my PAxy pin/port mapping macros and the remoteXY.c structure.
Then i indeed would like to change the board numbering to Gen2.GD.x and Gen2.MM.y
@reed-dan do you think this board is close enough to yours it is manufactured by same company but the infamous lks32mc088 is also manufactured by them so it does not mean anything the pins are not 100% compatible like led and button are not tracing a mm32board took allot more effort then a gd board even without autodetect so it is best to minimize the layouts or seperate the mm layouts from gd ones
@reed-dan do you think this board is close enough to yours it is manufactured by same company but the infamous lks32mc088 is also manufactured by them so it does not mean anything the pins are not 100% compatible like led and button are not tracing a mm32board took allot more effort then a gd board even without autodetect so it is best to minimize the layouts or seperate the mm layouts from gd ones
I think there are significant differences in the 2 boards. I think mine should be 2.8.0 and yours 2.8.1, but that is my opinion.
A sub number like 2.6.1 should only be used if the boards are really like version x and x.1 of the same manufacturer and only a minor change in the defines2_6.h is needed like buzzer on slave instead of master.
I would like to assign 2.21 to the 2.8.1
Hello all, I am new here and have a TaoTao 2130 series board with the MM32SPIN05pf. I have already traced most of the required pins, and just need to summarize the drawing. The board has a master and slave, which I have both, yet not traced the slave board yet. I am working on the testing of the pins based on the MM32SPIN05pf code you have already developed. I also have a new hoverboard with the lks32mc088 chips, master and slaves, which I hope to look at next. How do I create a new board definition? And, I am new to GitHub, so I do not know how to contribute my changes either. Sorry for being a newbie here.
Great to have another motivated owner of some mm32 boards.
The mm32 firmware is developed actively by @AILIFE4798 .
If you succeed to unlock your board and are ready to upload a firmware, I am confident that he will make a firmware ready for your board.
Please take a look at our wiki here to connect a mm32 board.
This will be the most difficult part.
RoboDurden, already unlocked the board, already tested the RGB and Headlight LEDs, working on the latching. Have the Hall and Gate pins sorted, all UART pins sorted. Testing bit by bit.
@GRROWL911 could you please make a YouTube tutorial where you simply walk through all the tools that were needed to successfully upload a new firmware to the mm32 board !!!!
@GRROWL911 you can disable latch and button in code to use a jumper to replace it test the hall and motor first if your hall and uart pin is not standard you have to wait im workng on support timer3 (already workng but code not updated) and uart2(tx working rx dma not workng)
btw unlock mm32 just require keil and stlink v2 no aditional tool needed some said its easier then the gd32
everything in the wiki is bs ill make a video in the future how to use my firmware
because things change everyday im not gonna make video every day
@GRROWL911 your layout is closer to @StomperQc 's lks32 do not have a comparator so not foc capable but should work with current feature please make a image like i did at my github repo with all the pins i will see and PLEASE DO NOT CHANGE PINMODEAF IF YOU DONT KNOW WHAT YOU ARE DOING!!! i already bricked my board with that
@GRROWL911 could you please make a YouTube tutorial where you simply walk through all the tools that were needed to successfully upload a new firmware to the mm32 board !!!!
Once I get the board working and move to the slave, I'll try post some instructions. Basically, just the same as the Wiki posted using ST-Link and pyocd.
@AILIFE4798 > btw unlock mm32 just require keil and stlink v2 no aditional tool needed some said its easier then the gd32 I was not able to unlock using Keil alone, would erase and fail to write. Using pyocd to do a chip erase worked, then just Keil.
@GRROWL911 your layout is closer to @StomperQc 's lks32 do not have a comparator so not foc capable but should work with current feature please make a image like i did at my github repo with all the pins i will see and PLEASE DO NOT CHANGE PINMODEAF IF YOU DONT KNOW WHAT YOU ARE DOING!!! i already bricked my board with that
@AILIFE4798 the LKS32 boards do look very, very similar, however I have not pulled them out of the HV yet, so no tracing. Once I have all the pins sorted and verified, I'll post the image.
you need to choose erase full chip not erase sector
@AILIFE4798 I am not sure how to set Keil up for that. I am using the VS Code edition and Keil for the first time, so I have no idea what I am doing. I've a lot more experience with the NRF52 world. I'd like to know how for the slave boards. I long ago bricked my other master board.
i do not have lks32 yet so you are on your own unless you want to send one not seen any for sell so far
@AILIFE4798 any hints on the latch/button code, I have the bins traced, however the latch does not hold, and the button does not seem to be reading correctly either. I am working slowly and methodically since this is all new to me. If I cannot get the latch/button parts working, I will just move to the motors. I also need to figure out how to startup the slave boards as they do not have a switch.
i do not have lks32 yet so you are on your own unless you want to send one not seen any for sell so far
@AILIFE4798 I'll look at them after I have these ones working.
well since when im good at keil ?lol
the hardest part of keil is to download it
if you have done it everything after is easy
idk both of my board latch an button is working fine make sure it is not commented out because then it will get bypassed by my code i think you just traced it wrong latch and button is not easy to trace
well since when im good at keil ?lol the hardest part of keil is to download it if you have done it everything after is easy
@AILIFE4798 I have not yet found any settings pages in the VS Code edition. I already had VS Code from my NRF52 boards, so adding the Keil extension was very easy. That was the easiest part.
if you need to download full keil ide download from filecr using pyocd is also ok
the reason board is bricked is the pinmodeAF does not exist when you change the pin you must change pinmodeAF to correct one
using slave board is very very hard my layout2.20 is still not working easier to unbrick the master boar
Slave board normally gets on when it receives +5V (or +15V) on the master slave uart cable.
Good night from Germany