Hoverboard-Firmware-Hack-Gen2.x
Hoverboard-Firmware-Hack-Gen2.x copied to clipboard
RoboDurden
Wiki: Topic to discuss the Wiki
@RoboDurden @AILIFE4798
Just wanted to create an area were we can discuss progress wiki.
I am trying to organize things by MCU type and then board layouts.
I personally don't really like the github wiki markup, and would much rather it be basic html or something. I will give it some time though.
i will deal with the esp32 and esp8266 later the serial have to be added later because again no hardware on me the 2.6.1 is not around
@RoboDurden What MCU is on? 2.1 2.6 GD32F130C6T6? 2.9 Can you confirm GD32F103C6T6 or GD32F103C8T6, I believe it is labeled wrong?
Just added information about setting up Keil and the Blink sketch for 2.8 to its wiki. It needs some formatting help, but it outlines the blink issue I am experiencing.
My Gen2.x is a fork from Gen2.1 = https://github.com/krisstakos/Hoverboard-Firmware-Hack-Gen2.1
= GD32F130C6T6 = 32kB , 48 pin.
2.6.0 = GD32F130 ????
2.6.1 =GD32F130C6T6
2.9 = GD32F103C6T6
But i also only looked at the images in the Schematics... folders.
Yes i also would like an interactive search where you select gateDriverChips/analogGateDrivers and then 32pin/48pin and then GD/MM/STM/LKS and then C6/C8 while the list of images decreases..
Would be easy for me to do in javascript. But i am not sure if html is possible on github.
And this is not high up on my todo list. People will have to spend several days on their hoverboard projects. It is okay for them to spend two minutes on our impressive list of supported boards :-)
Serial flashing toturial is not coming anytime soon because no board with me again I think I'll have to wait for my other c8t6 boards And the serial method is only for gd32 and mm32 lks32 does not have bootloader so if SWD is disabled that chip is trashed you cannot reprogram it under any circumstances
@AILIFE4798 Don't you have online second hand sites in your country ? Here in the Western so called democracies which in truth are nothing but Postcolonial Fascist Dictatorships of Decadency ( PFDD, www.RoboDurden.de ) you can easily buy used hoverboards for $30 incl. shipping.
Maybe try Ruten 露天, Shopee 蝦皮 , Yahoo! Auctions or Facebook marketplace. If you don't have paypal, a seller might accept Paypal :-)
hoverboard is too long to be shiped if the seller didnt take it apart and split it in half first but trust me ive tried didnt find any good ones thats close by so i can pick it up my self actually needed 2 more for my project so i def wanted some more
I am trying to organize things by MCU type and then board layouts.
I personally don't really like the github wiki markup, and would much rather it be basic html or something. I will give it some time though.
idk how to use markup either so i will not have any formatting
@reed-dan the esp8266 daplink wiki is complete please read it and try it your self
I personally don't really like the github wiki markup, and would much rather it be basic html or something. I will give it some time though.
if you want to make better wiki with html i can host it on my server and other people will not be able to edit it
@RoboDurden autodetect guide finished please edit it because only you know what it exactly does
@RoboDurden please move all board layout from readme to wiki with this example
As i said, I do want to keep the large list of known boards on the readme to give hope to new users that their board is one of them.
I think, the wiki only needs special information not the full pin definitions..
But adding all the photos from the schematics folders might be a good idea.
I now live outdoors again. -5°C this night.
Because readme is only one page at current rate the known board will grow to none senseable level very quickly It is better to move everything in readme to wiki And in first line of readme put a link to wiki And yes when you have a page for each board then you can include all photo in the end of page
@AILIFE4798 , all this here will not save the world. And every 3.6 seconds a human dies from hunger. The Western so called democracy are responsible for over 1,100,000,000 deaths in Africa since 1955.
If you waste your time on unnecessary things, you are an evil man !
I made some improvements to the side menu to make the MCUs collapsible. I think this collapse feature may be nice on some of the other pages as well.
yes, home page of wiki does look nice. I guess i will remove the many images from readme and put a big link to the new wiki instead.
2.1 has never been tested, that why I only offer a test binary. It should work as the gen2.x is a fork of 2.1. but no one ever tested it. Same for 2.6.0. there might be more differences than the buzzer.
When I was making the list, I knew I would wont to make a category for mcu that should work pending autodetect.
@RoboDurden I thought you had said somewhere that you wanted to keep track of one other piece of information along with the mcu for each layout, what was that? It was one of the other chips I believe.
there is only 4 chips on the board the mcu, the imu(not used so not this),the gate driver ic, the opamp and maybe some buck regulator ic and bluetooth ic dont think theres any worth documenting
is there anything need to be added to wiki other then serial which ill need to test first
Well I did propose the wiki so that you could summarize the progress you have made concerning the mm32. And then start a fresh 2.8 issue that only builds on knowledge from the wiki. If you like to build a complete wiki then you might want to copy everything from the readme to wiki pages.
idk why a new issue is needed but i created it anyways most part of readme is in wiki now except the board list is still not complete but i think @reed-dan is working on it
i had a quick search on how to add javascript to github pages, and it seems this can only be done on github.io: https://robodurden.github.io/ But i do not want to spread information on yet another url.
The interactive search could be done with multiple drop down lists :-/ 1 First dropdown: analog gate drirvers or gate driver chips. 2. dropdown 32pin/48pin 3. GD/MM/STM/LKS 4. C6/C8
And each dropdown would need little images to show the user where to look on the pcb.
But then the user would only see board images after he has choosen all the four drop down lists.
I would prefer that new users see the full (impressive) list like in read.me and then can click on the four filters to reduce the number of images.
But this requires javascript.
And again, i think the Issues should be the place where we communicate and work. And the wiki only the place where found knowledge is stored so new users do not need to read lengthy issues.
i can tell you that i suceeded with flashing by serial wiki will be in few hours