Gen2.3.1 (ex2.7) = GD32E230C8T6 #16

RoboDurden · 2023-09-07T07:07:52Z

thanks to @WizzardDr who added this new layout which needs a new Keil compiler target: #15

As i am not really experienced at all with this Keil platform, help from anybody would be appreciated :-)

I see that this board has three mosfet gate driver chips instead of analog gate drivers like the original 2.0.
Be aware that this firmware here was written for the 2.0 layout where the low side mosfets are turned on with a LOW signal !!
With layouts having gate driver chips however, the on-signal might be HIGH for both high-side and low-side mosfets.
If this is not correctly applied, all three half-bridges will short cut and burn !!

When testing a new layout it is mandatory to use a CC constant current power supply with only 1-2 A max !!!

WizzardDr · 2023-09-07T07:17:09Z

I noticed when I was tracing the connections that the Hi and Lo sides of the driver connect to TIMER0_CH2_ON TIMER0_CH2 respectively whereas the other designs had Lo to _ON. I double and triple checked since I expected it to be the same. Because of this it may be that the on and off timing also needs inverting. I will do some testing and look at how the PWM timers are setup to drive the outputs once I get it to compile.

RoboDurden · 2023-09-07T07:31:18Z

The GD32E230 also has only one advanced timer capabale of driving a 3 phase motor.
With the GD32F130, the output pins for such a 3 phase bldc is very very limited and therefore all the gen2-x layouts so far had the same output pins

// Channel G
#define BLDC_GH_PIN PA10
#define BLDC_GL_PIN PB15
// Channel B
#define BLDC_BH_PIN PA9
#define BLDC_BL_PIN PB14
// Channel Y
#define BLDC_YH_PIN PA8
#define BLDC_YL_PIN PB13

These connect to TIMER0_CH0, TIMER0_CH1 and TIMER0_CH2

We are currently working on a simpleFOC port for these Gen2 boards: Candas1/Split_Hoverboard_SimpleFOC#6 (comment)

But please also continue to get the GD32E230 compiled for this Gen2.x firmware.

RoboDurden · 2023-09-07T07:38:05Z

@Candas1 has begun with a nice spreadsheet of the pin connections for various board layouts: https://docs.google.com/spreadsheets/d/15msbDAIMxC2rIkq8Au8vf82ub1qEaS67Lc1cFb86Jpc/edit#gid=0

RoboDurden · 2023-09-07T08:05:40Z

I think that all #include "gd32f1x0.h" lines can be removed from the Inc/*.h files.
But for the Src/*.c file i guess we have to add a #ifdef TARGETXY #ELSE #ENDIF to choose between #include "gd32f1x0.h" and #include "gd32e2x0.h"
I might know how to do this with PlatformIO, but not with Keil.

RoboDurden · 2023-09-07T08:13:14Z

Yes this seems to work:

#ifdef GD32E230
#include "gd32e2x0.h"
#else
#include "gd32f1x0.h"
#endif

But the file "gd32e2x0.h" is not found. Ideas welcome.

RoboDurden · 2023-09-07T08:27:54Z

Okay, i have replace all #include "gd32f1x0.h" with #include "../Inc/target.h" in all *.c files and removed all #include "gd32f1x0.h" in the *.h files.

target.h simply is

#ifdef GD32E230
	#include "gd32e230.h"
#else
	#include "gd32f1x0.h"
#endif

This compiles successfully for the f130 target.
Still need to find the correct #include "gd32e230.h"

Will publish my code now.

RoboDurden · 2023-09-07T08:36:15Z

#include "gd32e23x.h" is the correct wording. Now it compiles but i get 10 compiler errors.
But these should not pose big problems:

Src/setup.c(63): error: use of undeclared identifier 'NVIC_PRIGROUP_PRE4_SUB0'
        nvic_priority_group_set(NVIC_PRIGROUP_PRE4_SUB0);
                                ^
Src/setup.c(117): error: too many arguments to function call, expected 2, have 3
        nvic_irq_enable(TIMER13_IRQn, 0, 0);
        ~~~~~~~~~~~~~~~                  ^
C:/Users/PAN CF-LX6/AppData/Local/Arm/Packs/GigaDevice/GD32E23x_DFP/1.0.2/Device/Firmware/Peripherals/inc\gd32e23x_misc.h(69): note: 'nvic_irq_enable' declared here
void nvic_irq_enable(uint8_t nvic_irq, uint8_t nvic_irq_priority);
     ^
Src/setup.c(327): error: too many arguments to function call, expected 2, have 3
        nvic_irq_enable(TIMER0_BRK_UP_TRG_COM_IRQn, 0, 0);
        ~~~~~~~~~~~~~~~                                ^
C:/Users/PAN CF-LX6/AppData/Local/Arm/Packs/GigaDevice/GD32E23x_DFP/1.0.2/Device/Firmware/Peripherals/inc\gd32e23x_misc.h(69): note: 'nvic_irq_enable' declared here
void nvic_irq_enable(uint8_t nvic_irq, uint8_t nvic_irq_priority);
     ^
Src/setup.c(347): error: too many arguments to function call, expected 2, have 3
        nvic_irq_enable(DMA_Channel0_IRQn, 1, 0);
        ~~~~~~~~~~~~~~~                       ^
C:/Users/PAN CF-LX6/AppData/Local/Arm/Packs/GigaDevice/GD32E23x_DFP/1.0.2/Device/Firmware/Peripherals/inc\gd32e23x_misc.h(69): note: 'nvic_irq_enable' declared here
void nvic_irq_enable(uint8_t nvic_irq, uint8_t nvic_irq_priority);
     ^
Src/setup.c(430): error: too many arguments to function call, expected 2, have 3
                nvic_irq_enable(DMA_Channel3_4_IRQn, 2, 0);
                ~~~~~~~~~~~~~~~                         ^
C:/Users/PAN CF-LX6/AppData/Local/Arm/Packs/GigaDevice/GD32E23x_DFP/1.0.2/Device/Firmware/Peripherals/inc\gd32e23x_misc.h(69): note: 'nvic_irq_enable' declared here
void nvic_irq_enable(uint8_t nvic_irq, uint8_t nvic_irq_priority);
     ^
Src/setup.c(489): error: too many arguments to function call, expected 2, have 3
        nvic_irq_enable(DMA_Channel1_2_IRQn, 2, 0);
        ~~~~~~~~~~~~~~~                         ^
C:/Users/PAN CF-LX6/AppData/Local/Arm/Packs/GigaDevice/GD32E23x_DFP/1.0.2/Device/Firmware/Peripherals/inc\gd32e23x_misc.h(69): note: 'nvic_irq_enable' declared here
void nvic_irq_enable(uint8_t nvic_irq, uint8_t nvic_irq_priority);
     ^
6 errors generated.
compiling setup.c...
compiling bldc.c...
compiling main.c...
compiling commsBluetooth.c...
compiling comms.c...
compiling it.c...
compiling led.c...
compiling commsSteering.c...
compiling commsMasterSlave.c...
RTE/Device/GD32E230C8/system_gd32e23x.c(202): error: use of undeclared identifier 'FMC_WS'
    FMC_WS = (FMC_WS & (~FMC_WS_WSCNT)) | WS_WSCNT_2;
    ^
RTE/Device/GD32E230C8/system_gd32e23x.c(202): error: use of undeclared identifier 'FMC_WS_WSCNT'
    FMC_WS = (FMC_WS & (~FMC_WS_WSCNT)) | WS_WSCNT_2;
                         ^
RTE/Device/GD32E230C8/system_gd32e23x.c(202): error: use of undeclared identifier 'FMC_WS'
    FMC_WS = (FMC_WS & (~FMC_WS_WSCNT)) | WS_WSCNT_2;
              ^
RTE/Device/GD32E230C8/system_gd32e23x.c(202): error: use of undeclared identifier 'WS_WSCNT_2'
    FMC_WS = (FMC_WS & (~FMC_WS_WSCNT)) | WS_WSCNT_2;
                                          ^
4 errors generated.
compiling system_gd32e23x.c...
".\Objects\Hoverboard.axf" - 10 Error(s), 0 Warning(s).

@WizzardDr please continue as i want to work on something else :-)

RoboDurden · 2023-09-07T08:42:16Z

5 compiler errors with

#ifdef GD32E230
	#include "gd32e23x.h"
	#define TARGET_nvic_irq_enable(a, b, c){nvic_irq_enable(a, b);}
#else
	#include "gd32f1x0.h"
	
	#define TARGET_nvic_irq_enable(a, b, c){nvic_irq_enable(a, b, c);}
#endif

:-)

RoboDurden · 2023-09-07T08:56:42Z

4 errors:

#ifdef GD32E230
	#include "gd32e23x.h"
	#define TARGET_nvic_irq_enable(a, b, c){nvic_irq_enable(a, b);}
	#define TARGET_nvic_priority_group_set(a)	// that function does not exist for this target = not needed ?
#else
	#include "gd32f1x0.h"
	
	#define TARGET_nvic_irq_enable(a, b, c){nvic_irq_enable(a, b, c);}
	#define TARGET_nvic_priority_group_set(a){nvic_priority_group_set(a);}
#endif

But the remaining four errors are not in our user code:

RTE/Device/GD32E230C8/system_gd32e23x.c(202): error: use of undeclared identifier 'FMC_WS'
    FMC_WS = (FMC_WS & (~FMC_WS_WSCNT)) | WS_WSCNT_2;
    ^
RTE/Device/GD32E230C8/system_gd32e23x.c(202): error: use of undeclared identifier 'FMC_WS_WSCNT'
    FMC_WS = (FMC_WS & (~FMC_WS_WSCNT)) | WS_WSCNT_2;
                         ^
RTE/Device/GD32E230C8/system_gd32e23x.c(202): error: use of undeclared identifier 'FMC_WS'
    FMC_WS = (FMC_WS & (~FMC_WS_WSCNT)) | WS_WSCNT_2;
              ^
RTE/Device/GD32E230C8/system_gd32e23x.c(202): error: use of undeclared identifier 'WS_WSCNT_2'
    FMC_WS = (FMC_WS & (~FMC_WS_WSCNT)) | WS_WSCNT_2;

So i guess some compiler setting must be adjusted :-/
I am out for now.

RoboDurden · 2023-09-07T09:02:46Z

Okay if i simple remove that strange line with //FMC_WS... this leads to a successful compilation:

#ifdef GD32E230
	#include "gd32e23x.h"
	#define TARGET_nvic_irq_enable(a, b, c){nvic_irq_enable(a, b);}
	#define TARGET_nvic_priority_group_set(a)	// that function does not exist for this target = not needed ?
	#define TARGET_adc_vbat_disable()
#else
	#include "gd32f1x0.h"
	
	#define TARGET_nvic_irq_enable(a, b, c){nvic_irq_enable(a, b, c);}
	#define TARGET_nvic_priority_group_set(a){nvic_priority_group_set(a);}
	#define TARGET_adc_vbat_disable(){adc_vbat_disable();}
#endif

@WizzardDr , you continue !

WizzardDr · 2023-09-07T09:46:56Z

Well this is unfortunate, I didn't see your updates, I have wasted my time doing what you have just done, but I did it worse and slower lol. I looked into the FMC stuff and found "The FMC provides a security protection function to prevent illegal code/data access on theFlash memory." so it probably isn't important. Thanks for getting it to compile.

RoboDurden · 2023-09-07T10:02:59Z

Only test the binary with a 1-2A CC power supply !!!
I have cleaned up your Schematics_2.7 a bit. Tell me if i deleted some nice images.

The master and slave boards seem to be different, slave having new room for the buzzer and bluetooth on board !

RoboDurden · 2023-09-07T10:12:23Z

I am currently working to add your defines_2-7.h ! 22 errors at the moment..

RoboDurden · 2023-09-07T10:27:19Z

Okay i added the defines_2-7.h and removed the compiler errors.


#ifdef GD32E230
	#define LAYOUT_2_7	// https://github.com/RoboDurden/Hoverboard-Firmware-Hack-Gen2.x/issues/16
#else
	#define LAYOUT_2_0	// https://github.com/flo199213/Hoverboard-Firmware-Hack-Gen2
	//#define LAYOUT_2_1	// https://github.com/krisstakos/Hoverboard-Firmware-Hack-Gen2.1
	//#define LAYOUT_2_2	// 2023/05/11 only MASTER and TEST_SPEED: motor is spinning but needs a push to startup :-/
	//#define LAYOUT_2_4	// NOT READY !!! https://github.com/RoboDurden/Hoverboard-Firmware-Hack-Gen2.x/issues/3
#endif

It seems to me that the gate driver chips expect a negated signal for low side mosfets. So maybe the 2.0 code will run.

But again, be careful !

RoboDurden · 2023-09-07T10:30:25Z

If you do not find the CHARGE_STATE_PIN then you need to deactivate (add //)

chargeStateLowActive = gpio_input_bit_get(CHARGE_STATE_PORT, CHARGE_STATE_PIN);
in main.c::367

RoboDurden · 2023-09-07T10:37:51Z

Okay i added #ifdef CHARGE_STATE_PIN to the only two references..
Shift+Strg+F is your friend !

WizzardDr · 2023-09-10T19:03:00Z

@RoboDurden I do not understand how the pulse time is correct with the PWM running in mode 1. In mode 1 "When counting up, OxCPRE is low when the counter is smaller than TIMER0_CHxCV, and high otherwise.".

Is "pulse_value" = TIMER0_CHxCV?

How does timer_channel_output_pulse_value_config(TIMER_BLDC, TIMER_BLDC_CHANNEL_G, CLAMP(g + pwm_res / 2, 10, pwm_res-10)); dictate the PWM on time rather than PWM off time?

RoboDurden · 2023-09-11T14:08:12Z

What was wrong with UCC1800_dcdc_chip.PDF ?
I did not program this firmware. I only added the different layouts and rewrote the serial communications.
I guess you are the better person to answer this pwm init code.
It will take me longer to understand that then it would take you. Candas1 i think would know the answer instantly, but i am happy that he is busy with the simpleFOC port, so i do not like to ask him.

Have you started testing the binary with a constant current power supply ???
If the defines_2-7.h is close to complete, you could give it a try.
All your pull requests are not really worth anything if you will not test the 2.7 layout at some time.
Before that, further pull requests do not really make the current gen2.x firmware better.

WizzardDr · 2023-09-11T15:29:53Z

I think that pdf is for a different chip. It shows a different pinout to the chip that is on the board. E.g. My schematic shows pin1 connected to vcc whereas that datasheet shows vcc at pin 7. That datasheet also shows an external switching mosfet.

WizzardDr · 2023-09-11T15:38:41Z

My problem at the moment is that https://github.com/EFeru/hoverboard-firmware-hack-FOC/wiki/How-to-Unlock-MCU-flash seems to have bricked the mcu... I connected it and it seamed to be unlocked, It read a 4kB image. Then I followed the step and now it just says the chip protection is enabled and it won't let me set the option bits to unlock it. STM32CubeProgrammer returns 15:36:31 : Error: Expected value for STM32F1 Option Byte "RDP": 0xA5, found: 0x1 15:36:31 : Error: Option Byte Programming failed, ST-LINK Utility doesn't work either.

WizzardDr · 2023-09-11T16:09:16Z

I lifted the Boot0 pin and used UART and got it to load the firmware. (I selected "Read Unprotect (MCU)" in STM32CubeProgrammer)

RoboDurden · 2023-09-11T16:41:16Z

If you indeed succeeded with a stlink dongle to flash with the uart protocol and not the SWD protocol, please make a youtube tutorial.
With my the 2.0 test setup the flashing quite often fails and i need to flash under reset.
I use the stlink.exe you can download on my readytoflash folder because it only need a press on the return key to run the .bat file with st-flash --connect-under-reset write hoverboard.bin 0x8000000
But these cheap st-link dongle have only the rst pin wroking for that other protokol and not the usual SWD (?)
Therefore you need to solder a tiny cable onto the little circuit board...
Already wanted to add two photos to this repo here but forgot and now i do not find the photos to show how to solder the cable.
But you can google for it..
With the 2.0 layout there is a nice small smd resistor connected to that NREST pin of the mcu.
So it is quite simple to press a male dupont pin to the end of that smd resistor connecting the mcu NRST pin and hit the return key to start the patch file.
Or F8 in the Keil ide. But this will block with some error popups if you do not succeed in the first run.
Might help you next time.

WizzardDr · 2023-09-11T20:06:43Z

I have tested it with 20v (1a) with the battery cell count set to 5, but the power doesn't seem to be latching ON.

RoboDurden · 2023-09-11T20:19:49Z

add

#define DEBUG_LED_PIN 	UPPER_LED_PIN
#define DEBUG_LED_PORT 	UPPER_LED_PORT

to your defines_2-7.h and understand how the DEBUG_LedSet macro should make the upper_led go on and off.
Then you can test if the code gets executed and were it stops. Or if it reaches the while(1) loop..

I never got the debug step by step mode working with this Keil ide.
Porting this firmware to platformIO would make debugging (also using the great StmStudio) much easier..

WizzardDr · 2023-09-11T20:21:30Z

Yes, I guess I'll have to trace more of the pcb and find the led pins.

RoboDurden · 2023-09-11T20:26:51Z

I guess these are the 5 led pins:

Good night from Germany :-)

WizzardDr · 2023-09-14T00:17:22Z

I've been trying to get it to work and have come to the realization that the main code doesn't seem to be running at all. I've blocked out the main code with ifndef and just have a small section to turn a pin on (plus some some bits to stop it complain about speed being an undefined symbol)
main.c

#define BLINKTEST
#ifdef BLINKTEST
#define BLINKTEST_PORT GPIOA
#define BLINKTEST_PIN GPIO_PIN_14
#include "gd32e23x.h"
#include "../Inc/defines.h"
int main (void){
	gpio_mode_set(BLINKTEST_PORT , GPIO_MODE_OUTPUT, GPIO_PUPD_NONE,BLINKTEST_PIN);	
	gpio_output_options_set(BLINKTEST_PORT, GPIO_OTYPE_PP, GPIO_OSPEED_10MHZ, BLINKTEST_PIN);
	gpio_bit_write(BLINKTEST_PORT, BLINKTEST_PIN, 0);
}
int32_t speed = 0; 												// global variable for speed.    -1000 to 1000
int32_t steer = 0; 												// global variable for steering. -1000 to 1000
FlagStatus beepsBackwards = SET;  			// global variable for beeps backwards
DataSlave oDataSlave;
#endif
#ifndef BLINKTEST

#define ARM_MATH_CM3
......

This should be working no matter what, right?

RoboDurden · 2023-09-14T10:03:08Z

This is the code that works on my gen2.0 test setup:

#define BLINKTEST

#ifdef BLINKTEST

#include "../Inc/target.h"
#include "../Inc/config.h"
#include "../Inc/defines.h"

uint32_t iLoop = 0;
int main (void)
{
	rcu_periph_clock_enable(RCU_GPIOA);
	rcu_periph_clock_enable(RCU_GPIOB);
	
	gpio_mode_set(SELF_HOLD_PORT , GPIO_MODE_OUTPUT, GPIO_PUPD_NONE, SELF_HOLD_PIN);	
	gpio_output_options_set(SELF_HOLD_PORT, GPIO_OTYPE_PP, GPIO_OSPEED_10MHZ, SELF_HOLD_PIN);
	gpio_bit_write(SELF_HOLD_PORT, SELF_HOLD_PIN, SET);
	
	gpio_mode_set(LED_GREEN_PORT , GPIO_MODE_OUTPUT, GPIO_PUPD_NONE,LED_GREEN);	
	gpio_output_options_set(LED_GREEN_PORT, GPIO_OTYPE_PP, GPIO_OSPEED_10MHZ, LED_GREEN);
	while(1)
	{
		gpio_bit_write(LED_GREEN_PORT, LED_GREEN, (iLoop++ % 200000) < 100000 );
	}
}

int32_t speed = 0;							// global variable for speed.    -1000 to 1000
int32_t steer = 0;							// global variable for steering. -1000 to 1000
FlagStatus beepsBackwards = SET;  			// global variable for beeps backwards
DataSlave oDataSlave;

#else
...
#endif

RoboDurden · 2024-05-24T13:14:52Z

https://github.com/RoboDurden/Hoverboard-Firmware-Hack-Gen2.x-GD32/tree/main/Arduino%20Examples/Autodetect

ITBETOITALL · 2024-06-07T22:21:51Z

Man guys are really smart. I am completely brand new to this whole thing. I'm still trying to figure out how to wire my ST link to the board. I have been using chat gpt to help me. However, that appears to be working with a toddler. Consistently looking for a brand new toy. I have already Soldered in the four headers. I think that they're called in the four holes in the board. My end use is I'm trying to make like a 4 wheel drive platform that i can control by an RC controller.

RoboDurden · 2024-06-08T06:38:00Z

Rc Controller = stupid fun project :-/

ITBETOITALL · 2024-06-08T06:59:56Z

Would you suggest. RC to ESP32 to Motherboard UART or RC to ESP32 to Arduino Uno 3 to Motherboard? You appear to be the tube god for these firmware hacks. Thank you for doing what you do. Sincerely, Christopher

RoboDurden · 2024-06-08T07:06:41Z

We have RC to ESP32 to Motherboard UART example code but I do not support it.

Please read the wiki and prove that you can solve problems yourself and have the happiness to contribute.

Otherwise you are only a brain degenerated consumer :-(

ITBETOITALL · 2024-06-08T07:18:24Z

I bricked all 4 boards being a noob. Just got em to j reflash jtonight. Using opencd.

RoboDurden · 2024-06-08T07:22:04Z

You still have not confirmed what boards you have.
@I-hate-2FA might help with openOcd.

RoboDurden · 2024-06-08T07:34:40Z

Accidentally closed

ITBETOITALL · 2024-06-08T07:35:47Z

I have the GD32E230C8T6

RoboDurden · 2024-06-08T07:36:18Z

Layout ?
Photos ?

ITBETOITALL · 2024-06-08T07:41:02Z

On the computer downstairs pushing 4am here. Lots of reading and research. Trying to do this thing. Im getting there. Ty for your time.

I-hate-2FA · 2024-06-08T09:08:57Z

do you have other board, e230 is not supported(by autodetect), you either need gd32f130 or mm32 series
rc/adc is not and never will be supported officially, but there is plenty of translation layer available to convert to remote uartbus(and for 4 motor you must use a translator anyways)
i sugest you to get the $2 board, it is fully reverse engineered and known to work well(sine wave)

I-hate-2FA · 2024-06-08T09:10:13Z

if you still want further support, go to my repo and join the discord server, if you submit the layout in database i may be able to help(we have allot of e230 unsupported board in database already)

RoboDurden · 2024-06-08T10:25:58Z

as he is living in the Eastern Time US time zone, there might be no shpping of the $2 board to the US ?
What layout database ? I thought did not want to make a database because of your universal pinFinder approach.

RoboDurden · 2024-06-08T10:53:15Z

?? i provide gd32e230 autodetect binaries: https://github.com/RoboDurden/Hoverboard-Firmware-Hack-Gen2.x/tree/main/BinariesToTest
But no one ever tested it ?

I-hate-2FA · 2024-06-08T10:59:27Z

yeah i also dont have e230 to test
if it is not tested, we assume it does not work and only test with a board which all the pins is already manually traced

I-hate-2FA · 2024-06-08T11:03:25Z

as he is living in the Eastern Time US time zone, there might be no shpping of the $2 board to the US ?

not sure, but someone from canada ordered one and shipping included is $7 still cheap

What layout database ? I thought did not want to make a database because of your universal pinFinder approach.

yeah i dont need any board numbering i just provide a list to search board support status and hardware specs based on marking, i dont include the mpmode string because some of them is not mm32

ITBETOITALL · 2024-06-08T12:26:05Z

Hoverboard Motherboard: LC_TWO_SYS 20200825
Microcontroller: GD32E230 C8T6

I'll test the auto detect. Remember noob. What is the purpose of the auto detect

RoboDurden · 2024-06-08T13:30:03Z

You either don't use your brain or you don't have one any longer.
Your board probably looks like

So you could start with https://github.com/RoboDurden/Hoverboard-Firmware-Hack-Gen2.x/raw/main/BinariesToTest/hoverboard%202.3.1%20master%20Dummy.bin

The guy who added this board to this repo also addd RC-hoverboard control: #26

But then he disappeared and that is why the 2.3.1 binaries are still in the BinariesToTest/ folder :-(

ITBETOITALL · 2024-06-08T14:17:33Z

Thank you as stated up until 5 days ago I didn't even know what a microcontroller was. Thank you so much for your guidance.

I-hate-2FA · 2024-06-08T15:50:55Z

then maybe you should read the wiki which will show you how to identify the board, you dont provide any picture, how are we supposed to know your hardware then, you really didnt use your brain

ITBETOITALL · 2024-06-12T17:56:16Z

Apologies I am new and am just trying to learn.

I have the GD32E230C8T6

wired like this.

But this is what I get no matter what I do.

I-hate-2FA · 2024-06-12T20:20:10Z

it is just the board thats already indexed and have pre compiled binary, i think even chatgpt can tell
maybe you should go read the wiki again on how to flash the board?

ITBETOITALL · 2024-06-12T22:29:59Z

I stopped at the boards. Didn't notice the bottom of the page

I-hate-2FA · 2024-06-12T23:02:43Z

It's ok, just check now, it should be linked on main page too probably

ITBETOITALL · 2024-06-12T23:16:41Z

The wiki? Should be or the board. If you follow the interactive board wiki it take you to a 404 page or it takes you to this thread

TheHassanShahzad · 2024-07-24T18:51:13Z

Hello ive also just found that my hoverboard is the 2.3.1 with black wheels and a GD32E230 chip. Firstly i have this ftdi to serial programmer and was wondering if i can use this instead of stlink or using an esp32 to flash the device
https://www.ebay.co.uk/itm/394924503900

If not then i will go with a wemos d1 mini esp8266 and the CMSIS‐DAP method. If keil says my hoverboard is blocked then i will go with the hard way? im using linux so i get to skip some steps

In both my go to will be keil for now

After that i guess im going to use an esp32 and the UART_BUS method to control both motors simultaneously on the 19200 baud rate with a diode.

I just want to double check that the binaries i need to be flashing are https://github.com/RoboDurden/Hoverboard-Firmware-Hack-Gen2.x/blob/main/BinariesToTest/hoverboard%202.3.1%20master%20Dummy.bin this one

Some more binaries were added to the Binaries to test 3 months after this but they have a few variations. all seemingly for the GD32E230 chip.

Im guessing i will be the first to test the binaries?

RoboDurden · 2024-07-24T20:03:34Z

Buy a $2 st link v2 dongle from China..
Good night from Germany

RoboDurden mentioned this issue Sep 7, 2023

New Split Board Based on GD32E230C8T6 #15

Merged

RoboDurden changed the title ~~lLayout 2.7 = GD32E230C8T6~~ layout 2.7 = GD32E230C8T6 Sep 7, 2023

RoboDurden closed this as completed Jun 8, 2024

RoboDurden reopened this Jun 8, 2024

Gen2.3.1 (ex2.7) = GD32E230C8T6 #16

Gen2.3.1 (ex2.7) = GD32E230C8T6 #16

Comments

RoboDurden commented Sep 7, 2023

WizzardDr commented Sep 7, 2023 • edited Loading

RoboDurden commented Sep 7, 2023

RoboDurden commented Sep 7, 2023

RoboDurden commented Sep 7, 2023

RoboDurden commented Sep 7, 2023

RoboDurden commented Sep 7, 2023

RoboDurden commented Sep 7, 2023

RoboDurden commented Sep 7, 2023

RoboDurden commented Sep 7, 2023

RoboDurden commented Sep 7, 2023

WizzardDr commented Sep 7, 2023

RoboDurden commented Sep 7, 2023

RoboDurden commented Sep 7, 2023

RoboDurden commented Sep 7, 2023

RoboDurden commented Sep 7, 2023 • edited Loading

RoboDurden commented Sep 7, 2023

WizzardDr commented Sep 10, 2023 • edited Loading

RoboDurden commented Sep 11, 2023

WizzardDr commented Sep 11, 2023

WizzardDr commented Sep 11, 2023

WizzardDr commented Sep 11, 2023

RoboDurden commented Sep 11, 2023

WizzardDr commented Sep 11, 2023

RoboDurden commented Sep 11, 2023

WizzardDr commented Sep 11, 2023

RoboDurden commented Sep 11, 2023 • edited Loading

WizzardDr commented Sep 14, 2023 • edited Loading

RoboDurden commented Sep 14, 2023 • edited Loading

RoboDurden commented May 24, 2024

ITBETOITALL commented Jun 7, 2024 • edited Loading

RoboDurden commented Jun 8, 2024

ITBETOITALL commented Jun 8, 2024 via email • edited by RoboDurden Loading

RoboDurden commented Jun 8, 2024

ITBETOITALL commented Jun 8, 2024 • edited Loading

RoboDurden commented Jun 8, 2024 • edited Loading

RoboDurden commented Jun 8, 2024

ITBETOITALL commented Jun 8, 2024

RoboDurden commented Jun 8, 2024 • edited Loading

ITBETOITALL commented Jun 8, 2024 • edited Loading

I-hate-2FA commented Jun 8, 2024

I-hate-2FA commented Jun 8, 2024

RoboDurden commented Jun 8, 2024

RoboDurden commented Jun 8, 2024

I-hate-2FA commented Jun 8, 2024 • edited Loading

I-hate-2FA commented Jun 8, 2024

ITBETOITALL commented Jun 8, 2024

RoboDurden commented Jun 8, 2024

ITBETOITALL commented Jun 8, 2024

I-hate-2FA commented Jun 8, 2024

ITBETOITALL commented Jun 12, 2024 • edited Loading

I-hate-2FA commented Jun 12, 2024

ITBETOITALL commented Jun 12, 2024

I-hate-2FA commented Jun 12, 2024

ITBETOITALL commented Jun 12, 2024

TheHassanShahzad commented Jul 24, 2024

RoboDurden commented Jul 24, 2024

WizzardDr commented Sep 7, 2023 •

edited

Loading

RoboDurden commented Sep 7, 2023 •

edited

Loading

WizzardDr commented Sep 10, 2023 •

edited

Loading

RoboDurden commented Sep 11, 2023 •

edited

Loading

WizzardDr commented Sep 14, 2023 •

edited

Loading

RoboDurden commented Sep 14, 2023 •

edited

Loading

ITBETOITALL commented Jun 7, 2024 •

edited

Loading

ITBETOITALL commented Jun 8, 2024 via email •

edited by RoboDurden

Loading

ITBETOITALL commented Jun 8, 2024 •

edited

Loading

RoboDurden commented Jun 8, 2024 •

edited

Loading

RoboDurden commented Jun 8, 2024 •

edited

Loading

ITBETOITALL commented Jun 8, 2024 •

edited

Loading

I-hate-2FA commented Jun 8, 2024 •

edited

Loading

ITBETOITALL commented Jun 12, 2024 •

edited

Loading