-
Notifications
You must be signed in to change notification settings - Fork 1
"help wanted" region `FLASH' overflowed by 1724 bytes #5
Comments
The error you're currently seeing is due to using gcc 11.3.1 instead of a more modern version (12.2.1) and is purely a zelda3 issue. Checkout the stacksmashing discord server (#homebrew channel) for more rapid responses. |
great !! thank you !! I have to check that, and I have found this way but I have to test that !! |
@GusseDev Sorry for being so slow to react.. As @BrianPugh mentionned using a newer gcc should work better. However I've just pushed a few improvements that include some memory reorg with increased margins (a few KB) to try a make it work on gcc 11 or 10. |
no worries! you do it for free and happily, it's just great what you did! |
Thanks, and please feel free to give feedback if things need to be improved. The "section overflow" issue has risen several times already and in some cases I think specific builds of gcc 12 (for raspberry pi IIRC) did not fix it. I'm hoping that with bigger margins (free space was under 1KB at some point) it will suit more configs. |
I have updated my gcc version to gcc 12.3:
But I get another error:
Have you an idea ? or maybe I forget something... |
What command are you running? Can you see the source files generated from the ROM assets in |
hmmm sorry I have made a mistake in my command (I have set Language params twice...)
|
No error during flashing? What's your flash chip? I'll try on first bank since I haven't tried it much that way. |
No issues on first bank on my side. |
Without offset params, it's flash, but no boot with the previous command.
And the exact reference of the chip I use is: MX25U51245GZ4I00 |
I have made some tests on another upgraded 64Mb GnW Mario, with the following command :
and I still get this error :
Did you think my command is good ? |
I figure you have no issue flashing the original/patched firmware or retro-go? |
maybe try setting the OPENOCD path? You're using the patched openocd? |
Yes I use the patch version, I try again with OPENOCD setting |
I don't have a flash bigger than 16MB, so I can't try it myself. I think people have successfully flashed 64MB chips. Your flags look alright. Make sure to set LARGE_FLASH=1 to disable verify (which seems to be buggy on large chip) and enable 32-bits addressing. |
To be a bit more clear, this command sounds good:
|
with LARGE_FLASH=1 error is away ! Here is my command:
and the end message (unable to reset is usual with Stlink if I'm not wrong) :
|
I've never seen this openocd error.. |
I make test without language param, and it doesn't run, so I have put LANGUAGE=us make -j12 INTFLASH_BANK=2 EXTFLASH_SIZE_MB=63 EXTFLASH_OFFSET=1048576 ADAPTER=stlink OPENOCD=/opt/openocd-git/bin/openocd GNW_TARGET=mario LANGUAGE=us LARGE_FLASH=1 flash and I get: Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD |
It doesn't run? What does it do? |
I turn off parallel build, and press reset on Gnw during flash, the process have run without error on terminal:
BUT, on GNW when I try to boot on the second bank (GAME + LEFT) I get a blue screen with the following message :
Unfortunately I have to go for now, I can do additionnal test later, I also make some test with 16Mb memory, I have some under my hand |
Hello !
thanks for your great work!
I can't wait to see how it turns out!
for the moment I'm stuck in the compilation process, I get the following error and I can't go any further:
I made the test on 2 GnW a mario and a zelda, and the trouble is the same, here is the command that I use:
And some other variations have the same result. I also do a make clean before compilation...
I tried several commands without success.
I specify that I am not 100% at ease under linux, but I manage.
For information, I manage to flash without problem the retro go coverflow version in dual boot.
My GnW are upgraded to 64Mb too.
If I miss some information don't hesitate to ask !
Thanks in advance for your help!
The text was updated successfully, but these errors were encountered: