RoboDurden / Hoverboard-Firmware-Hack-Gen2.x

with different defines_2-x.h for different board layouts :-) Compiles with Keil version 6
GNU General Public License v3.0
73 stars 24 forks source link

Gen2_6.1 = YK201C 1.0 = MM32SPIN25 #68

Open TheBestJohn opened 4 months ago

TheBestJohn commented 4 months ago

I'd like to add another to the list, This one looks like YK201C instead of the A version of Issue 44's board. I'll be working on it shortly, I just need access to a power supply. image

I can't identify the brand because the exterior has been abused significantly. It does have a bunch of addressable LEDs, a Bluetooth module hot glued to the case and instead of onboard xt60, a spade and barrel connector.

AILIFE4798 commented 4 months ago

you do not need to identify the brand those does not matter, only the mcu model number is important, the rest of work can be done by autodetect

AILIFE4798 commented 4 months ago

only known board that have addressable led is 2.4.1 and 2.4.2

TheBestJohn commented 4 months ago

I think I may be mistaken on the MCU. It's likely a MM32SPIN like in Issue 38. They put a metallic sticker on this thing with some form of adhesive that is impossible to get off. I've used acetone etc. However, MM32SPIN seems to have the same blue streak and 3 fiducials and this is an earlier rev off that board anyway

TheBestJohn commented 4 months ago

only known board that have addressable led is 2.4.1 and 2.4.2

Ah it seems I was mistaken in that it's not addressable, just an rgb

AILIFE4798 commented 4 months ago

you will need to make sure your board is mm32spin05 or mm32spin06 i will supply you with the firmware needed and you need trace the serial pin

your board have 5 led driver, so likely no addressable led is required your board have 1 dual comparator, so i cannot tell it is mm32 or gd32 by that i only see one linear regulator, so maybe 5v?

TheBestJohn commented 4 months ago

So I'm pretty sure those stickers had some sort of etchant mixed into the adhesive.

edit: On second thought, I suspect these were lasered off and the aluminum sticker was put there to avoid EMF/UV interference with normal operation

image there 2 header pinouts on board but one says 3.3v the other says 5v

This board is V2.0 of this so I'd be willing to bet the MCU wasn't what changed. I could be terribly wrong though. At the end of the day whether I brick it or don't do anything with it I have the same outcome. I suppose once I get a power supply I could check some voltages

AILIFE4798 commented 4 months ago

the marking is lasered off, i can still see 3 locating dimple in the chip, which match mm32spin, but it could be again a unknown chip the 5v header is for rf module so seems like the chip is operating at 3.3v the 3.3v one is swd the board you linked is mm32spin25, which i do not have and are not sure if it is compatiable with spin05, so you will have to try it

TheBestJohn commented 4 months ago

ah interesting. Thank you for finding that! I will work on getting it powered and if you add support for the spin25, I'll run whatever tests you'd like

AILIFE4798 commented 4 months ago

i will compile blink code for mm32spin25 for you i already know your led is at pd2 pd3

AILIFE4798 commented 4 months ago

if it worked ill add spin25 target to main firmware and send you autodetect+normal firmware

AILIFE4798 commented 4 months ago

to flash mm32spin25, the step is confirmed to be the same as spin05 https://github.com/RoboDurden/Hoverboard-Firmware-Hack-Gen2.x/wiki/MM32SPIN05PF%E2%80%90Layout-2.8

incase the firmware i supply is wrong, you may need to unbrick your board at some point because ive certainly done that a couple time and now you will have to test the unstable code directly from me

AILIFE4798 commented 4 months ago

if you ready tell me i have firmware now

AILIFE4798 commented 4 months ago

blink have been sucessfully tested on mm32spin25 now, but all the main firmware have to be completly rewritten, so you will have to wait a long time

TheBestJohn commented 4 months ago

blink have been sucessfully tested on mm32spin25 now, but all the main firmware have to be completly rewritten, so you will have to wait a long time

Ah ok. I'll have to borrow a power supply from my friend to test it. Thank you very much for looking into this so thoroughly! Not only did you identify the mcu with me, you've gone out of your way to write some test firmware, locate a spin25 board, test it yourself, and update me on the issues surrounding this new chip. I really appreciate it! It's very apparent you love what you do AILIFE.

RoboDurden commented 4 months ago

If this is indeed a new MCU target MM32SPIN25 then this board should be Gen2.6.1 I guess. 2.5 is LKS32 ..

Big thanks to @AILIFE4798 for covering the quickly growing MM32 family

RoboDurden commented 4 months ago

Have added this board as Gen2_6.1 to the "interactive board identifier": https://github.com/RoboDurden/Hoverboard-Firmware-Hack-Gen2.x/wiki

reed-dan commented 4 months ago

@TheBestJohn if you barrow a power supply be very careful, because the hoverboard I acquired with a very similar board to this one YK190A the pins on the power supply are opposite of the other boards/power supplied I already had. The positive and negative pins should be labeled on the bottom of the board.

TheBestJohn commented 4 months ago

image for posterity