search

flo199213 / Hoverboard-Firmware-Hack-Gen2

Hoverboard Hack Firmware Generation 2 for the Hoverboard with the two Mainboards instead of the Sensorboards (See Readme.md).
GNU General Public License v3.0
143 stars 112 forks source link

Hoverboard.axf not found #3

Open bugiworks opened 5 years ago

bugiworks commented 5 years ago

I appreciate your work, after tried one motherboard hoverboard, i want to try this split one also.

when i try to build with keil, i get the error .\Objects\Hoverboard.axf: error: L6031U: Could not open scatter description file .\Objects\Hoverboard.sct: No such file or directory Not enough information to list image symbols. Not enough information to list load addresses in the image map. Finished: 2 information, 0 warning, 0 error and 1 fatal error messages. ".\Objects\Hoverboard.axf" - 1 Error(s), 0 Warning(s). Target not created.

any solution? or any direct hex files do you have? By the way, the board im using has GD32F103 not F130, i have downloaded the pack for 103 but im not sure if it works same.

pieterjanbuntinx commented 5 years ago

Have you found any solution for this error? I'm experiencing the same

kevin0932 commented 5 years ago

Hi @bugiworks @pieterjanbuntinx , I met the same error. Did you manage to solve it? Thanks for sharing.

pieterjanbuntinx commented 5 years ago

Hi @kevin0932, No, I did not. But I found a fork of this repo that compiles. I have not managed to get it uploaded to my hoverboard controller, I don't have a STLink but I'm using a STM32 Discovery board, so that's probably the problem.

bugiworks commented 5 years ago

Unfortunately i couldnt find any solution, I will try that fork then i will update the comment.

pieterjanbuntinx commented 5 years ago

It now works for me. To solve this error I had to enable this: image

renmalek7 commented 4 years ago

Hi. Were you able to flash this firmware?

pieterjanbuntinx commented 4 years ago

Yes, I was able to flash it. It works great. What are you stuck on?

renmalek7 commented 4 years ago

I have a different board, it's also a GD32F130. Before flashing the firmware, How can I tell if the Pins are the same? 2

pieterjanbuntinx commented 4 years ago

You could perhaps measure continuity using a multimeter from the pins of the MCU to the peripherals. If that corresponds to the pinout in the code it should work. That will be quite some work though, so if you think that the layout of the PCB looks about the same as the one of this repo, you could perhaps just try it out (at your own risk). Replacement boards are not that expensive from AliExpress

renmalek7 commented 4 years ago

ok, I will do that and post the results. Do you know if there is a way to pull the original firmware from the board? Would it be posible to write it back in the board if I fail and its not burned l?

pieterjanbuntinx commented 4 years ago

No I don't think so. I thought it was locked or something. It has something to do with the options bytes

renmalek7 commented 4 years ago

ok, thank you very much for you time : )

Harsh2210 commented 4 years ago

I have a different board, it's also a GD32F130. Before flashing the firmware, How can I tell if the Pins are the same? 2

Were you able to flash the firmware? I am using the same motherboard. I wanted to know whether the pinouts are same for this one.

yodaco commented 2 years ago

I have a different board, it's also a GD32F130. Before flashing the firmware, How can I tell if the Pins are the same? 2

Were you able to flash the firmware? I am using the same motherboard. I wanted to know whether the pinouts are same for this one.

Did it work?!?