Hacking EZflash Omega Fan Translation Shinchan not working

[Bonnom]

I tried to play a english fan translation of "Shinchan Aventuras en Cineland".
The games works great on mGBA and even on my SuperCard SD flashcart but on ezflash omega it doesn't work properly.
All the english text is replaced with a bunch of "V"s and the screen becomes completely black when beginning a new game.

Does someone have a similar problem with Romhacks/fan translations games not working on the ezflash omega?

 

[Localhorst86]

I tried to play a english fan translation of "Shinchan Aventuras en Cineland".
The games works great on mGBA and even on my SuperCard SD flashcart but on ezflash omega it doesn't work properly.
All the english text is replaced with a bunch of "V"s and the screen becomes completely black when beginning a new game.

Does someone have a similar problem with Romhacks/fan translations games not working on the ezflash omega?

While I tried a few ROM hacks and translations without issues (Mother 1,2 and 3, Pokemon Chapter Red, Fire Emblem for example), I haven't played any Shinchan Game ever.
Make sure you "clean boot" the ROM on the Omega and see if the issue persists.

EDIT: I assume it's this translation?
https://github.com/LeonarthCG/Shin-chan-Translation

 

[Bonnom]

While I tried a few ROM hacks and translations without issues (Mother 1,2 and 3, Pokemon Chapter Red, Fire Emblem for example), I haven't played any Shinchan Game ever.
Make sure you "clean boot" the ROM on the Omega and see if the issue persists.

EDIT: I assume it's this translation?
https://github.com/LeonarthCG/Shin-chan-Translation

Thanks for your reply! Clean boot does not work.

I also tried other fan translation and they worked fine but I wonder why this one doesn't work on my ezflash omega since it does work on the crappy supercard sd and mGBA.
The github page is indeed the fan translation that I used. I was wondering if someone knows what causes this problem, since the translation is opensource I might be able to fix it!

 

[MilkTeeee]

Change your Save type from "Auto" to "Flash64" or "Flash128" at the menu before you launch the "clean boot"

But saving doesnt work. -.-''


Only way to play seems to be using the flashcart save state.

 

[metroid maniac]

I can confirm that the bug appears on the Definitive Edition as well.

If the ROM is save patched with GBATA and then the save type is set to SRAM 32kb, the game doesn't have these bugs and can save correctly.

EDIT: Had a thought about what the cause of this problem might be. The unpatched game is 16MB and uses EEPROM saving. This means 0x08xxxxxx addresses contain the ROM and 0x09xxxxxx addresses are used for communication with the EEPROM. The translation patch appends the new graphics and text to the ROM, meaning they are in the 0x09xxxxxx region of GBA memory. The EZ Flash probably has made this part of ROM inaccessible and is continuing to emulate EEPROM here. If EEPROM is disabled, then this ROM suddenly becomes usable again.

I'd be interested to know if this romhack works on an Everdrive GBA.

 

[MilkTeeee]

I can confirm that the bug appears on the Definitive Edition as well.

If the ROM is save patched with GBATA and then the save type is set to SRAM 32kb, the game doesn't have these bugs and can save correctly.

EDIT: Had a thought about what the cause of this problem might be. The unpatched game is 16MB and uses EEPROM saving. This means 0x08xxxxxx addresses contain the ROM and 0x09xxxxxx addresses are used for communication with the EEPROM. The translation patch appends the new graphics and text to the ROM, meaning they are in the 0x09xxxxxx region of GBA memory. The EZ Flash probably has made this part of ROM inaccessible and is continuing to emulate EEPROM here. If EEPROM is disabled, then this ROM suddenly becomes usable again.

I'd be interested to know if this romhack works on an Everdrive GBA.

How did you set the save type to specifically 32kB? It only generates 8kb save file with my patched rom using GBATA.

What's odd is using mGBA with "auto" save setting, this automatically sets the save file to SRAM and it saves without any issue, but not on my EZ Flash Omega.

Do let me know how you manage to set it and get it work on your EZ Flash

Thanks!

 

[metroid maniac]

How did you set the save type to specifically 32kB? It only generates 8kb save file with my patched rom using GBATA.

What's odd is using mGBA with "auto" save setting, this automatically sets the save file to SRAM and it saves without any issue, but not on my EZ Flash Omega.

Do let me know how you manage to set it and get it work on your EZ Flash

Thanks!

The save type must be set to SRAM on your EZ Flash. You cannot choose a patch in GBATA, just patch it with the default.

mGBA's automatic save detection and save emulation works different to the EZ flash so that makes sense.

 

[MilkTeeee]

The save type must be set to SRAM on your EZ Flash. You cannot choose a patch in GBATA, just patch it with the default.

mGBA's automatic save detection and save emulation works different to the EZ flash so that makes sense.

Thanks for the reply. I tested and it worked like you stated.

Finally I can play on my handheld!

 

[Wokann]

EEPROM save type for gba has some differences between SRAM and FLASH.
In gbatek it said

'The eeprom is connected to Bit0 of the data bus, and to the upper 1 bit (or upper 17 bits in case of large 32MB ROM) of the cartridge ROM address bus, communication with the chip takes place serially. '

For eeprom gba game below 16mb, it will block rw things exceeding 16mb, only first 16mb can be used (0x08000000-0x08FFFFFF), while 0x09000000-0x09FFFFFF can't be used. Save function in rom will set address on 0x0D000000.
For eeprom gba game exceed 16mb, it will block rw things on last 256byte, 0x08000000-0x9FFFEFF can be used, while 0x09FFFF00-0x09FFFFFF can't be used.Save function in rom will set address on 0x0DFFFF00.
It depends on both software save rw function in gba rom and hardware how eeprom chips connecting to cartridge.

Post automatically merged: Aug 14, 2024

This shinchan origin game is a 16mb eeprom save type, while translation is a rom exceed 16mb where can't be read noramlly. That is why game running and save may have errors.
For mgba and some other emulator, it skip this limit, so you can run eeprom rom exceeding 16mb normaly.
For supercard, it patch rom from eeprom to sram, which also can read things ecxeeding 16mb.
For ezo(de), it auto mode read save type list stored in kernel to run it as 16mb eeprom 8KB, which have error read things exceeding 16mb. Use gbata to patch rom to sram type, then set ezo(de) save type to sram is an easy way to play game.

Post automatically merged: Aug 14, 2024

For ezo(de), it also has save type for 32mb eeprom 8KB. Besides from origin 32 eeprom 8KB games in auto mode, if rom larger than 0x01200000 and set save type to eeprom 8KB, it will change eeprom address for 32mb eeprom 8KB.
However, like what i said before,
'It depends on both software save rw
function in gba rom and hardware how eeprom chips connecting to cartridge.'
Making rom larger than 0x01200000 and set save type to eeprom 8KB can simulated solve hardware in ezo(de), but can't solve software side in rom.

Post automatically merged: Aug 14, 2024

I'm now working on solving software side. And has already made some successful results on fan translated eeprom game which exceeding 16mb. you can see my codes here for some specific games.
https://github.com/Wokann/EEPROM_Fix_For_GBA_Exceeding_16MB
And I'm also trying to make a common eeprom_fix_patcher for any 16mb eeprom game which wants to hack or translate, but have to exceed 16mb. It will take times to complete it.

Post automatically merged: Aug 14, 2024

I just made an eeprom fix version for english translation of 'Shin chan - Aventuras en Cineland (Spain)'. This is an ups patch need to apply on origin spain version.
It now can be saved normally as eeprom 8KB in ezo(de) (Must set save type on EEPROM 8KB, not AUTO mode), openFPGA on analogue pockect etc.
It also contain SRAM support if EEPROM hardware check not pass on your running device. Which means you don't need to additionally use GBATA to add SRAM patch on rom for other use (such as burn rom onto sram reproduction cartridge)