Hoverboard-Firmware-Hack-Gen2 icon indicating copy to clipboard operation
Hoverboard-Firmware-Hack-Gen2 copied to clipboard

Published 20 hours ago • verified publisher icon flo199213

Hoverboard.axf not found

Open bugiworks opened this issue 7 years ago • 14 comments
trafficstars

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.

bugiworks avatar Nov 03 '18 17:11 bugiworks

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

pieterjanbuntinx avatar Nov 27 '18 15:11 pieterjanbuntinx

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

kevin0932 avatar Dec 21 '18 12:12 kevin0932

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.

pieterjanbuntinx avatar Dec 21 '18 12:12 pieterjanbuntinx

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

bugiworks avatar Dec 25 '18 05:12 bugiworks

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

pieterjanbuntinx avatar Feb 26 '19 17:02 pieterjanbuntinx

Hi. Were you able to flash this firmware?

renmalek7 avatar Apr 08 '20 11:04 renmalek7

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

pieterjanbuntinx avatar Apr 08 '20 11:04 pieterjanbuntinx

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

renmalek7 avatar Apr 08 '20 12:04 renmalek7

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

pieterjanbuntinx avatar Apr 08 '20 12:04 pieterjanbuntinx

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?

renmalek7 avatar Apr 08 '20 13:04 renmalek7

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

pieterjanbuntinx avatar Apr 08 '20 13:04 pieterjanbuntinx

ok, thank you very much for you time : )

renmalek7 avatar Apr 08 '20 13:04 renmalek7

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.

Harsh2210 avatar Jun 16 '20 16:06 Harsh2210

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?!?

yodaco avatar Jul 23 '22 20:07 yodaco