EZ-Flash Omega DE RTC not working randomly

[moon_rabbit]

Time is accurate, but sometimes it resets occasionally

1. Remove the battery and clean the battery terminals
2. If the battery voltage is low, replace the battery

I changed battery and cleaned terminals
It doesn't reset now and it's okay.

 

[CorporateP]

@ghjfdtg
Sorry for reviving this old thread, but I'm encountering some weird issues with my Rev.B EZ-Flash Omega DE while playing Pokémon Emerald.

After a period of playing and saving multiple times, I suddenly get an error:
"The backup memory is damaged, or the internal battery has run dry. You can still play, but not save."
Temporarily, I can fix this by loading the save in an emulator, saving there, and exporting it back to the cart. However, the error eventually returns.

I've validated the save file with PKHex and RecoverSaveGen3, no errors found, and the issue persists. This makes me suspect the problem lies with the cart itself, not the save file. The ROM itself is intact and matches the MD5 reported from no-intro when checked on the SD card directly.

The built in EZ-Flash cart tester (SELECT during boot) does not show any errors.

I ran your custom ROM test tool (clean boot mode A). It reports:

• A completely different SHA1 than the filename and every time I rerun it, it has a new SHA1 hash. This is true even if I directly try to recompute the hash during the same boot of the file (press B then A again). The file itself when hashed from the computer has the correct SHA1.
• ROM padding errors with mismatches.

Interestingly, when I copy the ROM test tool to NOR and do a clean direct boot in mode A it reports:

• An almost exact match in SHA1 except for two zeros in the middle of the hash, just like this post reported: /threads/ez-flash-omega-that-does-not-want-to-save-128kb-games-hates-advance-wars-and-other-bizarre-occurrences.623782/post-10035308
  • The SHA1 I see on screen has 38 characters, so the two zeros are missing weirdly.
• No ROM padding errors.

The issue persists across several kernel versions. I've also reformatted my 32GB SanDisk card twice using proper tools, so I doubt the SD card is the cause. Could this be a sign that my PSRAM is having issues, and can this be fixed or should I contact the offical dealer I bought from and request a replacement?

Would you or @EZ-Flash2 have any advice on how to proceed?
Thanks in advance!

Edit 1:
Running the RTC Checker ROM and the Aging Cartridge ROM reveals no errors as far as I can see.

Edit 2:
Switching mode B to RAM and running the MemtestARM for DS for SLOT 2 reveals that there is an error (see image with white textbox and green background.

 

[moon_rabbit]

@ghjfdtg
Sorry for reviving this old thread, but I'm encountering some weird issues with my Rev.B EZ-Flash Omega DE while playing Pokémon Emerald.

After a period of playing and saving multiple times, I suddenly get an error:
"The backup memory is damaged, or the internal battery has run dry. You can still play, but not save."
Temporarily, I can fix this by loading the save in an emulator, saving there, and exporting it back to the cart. However, the error eventually returns.

PSRAM is broken.
You need to get an S98 chip and replace it, but it's hard to find and requires soldering tools.
I recommend everdrive GBA instead.
Latest version of the everdrive GBA has dual RTC.

 

[EZ-Flash2]

@ghjfdtg
Sorry for reviving this old thread, but I'm encountering some weird issues with my Rev.B EZ-Flash Omega DE while playing Pokémon Emerald.

After a period of playing and saving multiple times, I suddenly get an error:
"The backup memory is damaged, or the internal battery has run dry. You can still play, but not save."
Temporarily, I can fix this by loading the save in an emulator, saving there, and exporting it back to the cart. However, the error eventually returns.

I've validated the save file with PKHex and RecoverSaveGen3, no errors found, and the issue persists. This makes me suspect the problem lies with the cart itself, not the save file. The ROM itself is intact and matches the MD5 reported from no-intro when checked on the SD card directly.

The built in EZ-Flash cart tester (SELECT during boot) does not show any errors.

I ran your custom ROM test tool (clean boot mode A). It reports:

• A completely different SHA1 than the filename and every time I rerun it, it has a new SHA1 hash. This is true even if I directly try to recompute the hash during the same boot of the file (press B then A again). The file itself when hashed from the computer has the correct SHA1.
• ROM padding errors with mismatches.

Interestingly, when I copy the ROM test tool to NOR and do a clean direct boot in mode A it reports:

• An almost exact match in SHA1 except for two zeros in the middle of the hash, just like this post reported: /threads/ez-flash-omega-that-does-not-want-to-save-128kb-games-hates-advance-wars-and-other-bizarre-occurrences.623782/post-10035308
  • The SHA1 I see on screen has 38 characters, so the two zeros are missing weirdly.
• No ROM padding errors.

The issue persists across several kernel versions. I've also reformatted my 32GB SanDisk card twice using proper tools, so I doubt the SD card is the cause. Could this be a sign that my PSRAM is having issues, and can this be fixed or should I contact the offical dealer I bought from and request a replacement?

Would you or @EZ-Flash2 have any advice on how to proceed?
Thanks in advance!

Edit 1:
Running the RTC Checker ROM and the Aging Cartridge ROM reveals no errors as far as I can see.

Edit 2:
Switching mode B to RAM and running the MemtestARM for DS for SLOT 2 reveals that there is an error (see image with white textbox and green background.

The issue which looks like a glitched PSRAM, which is sometimes caused by poor power supply.

Try testing again while connected to the power source, or use a fully charged battery.

 

[CorporateP]

I’ve ran the test ROM on a DS Lite and a stock GBA and both exhibited the same problem of diffing SHA1 hashes. Both on almost fully charged batteries.

I visually inspected the board and could not see any damage or potentially undone connections between the chips and board.

I contacted the distributor and they will kindly replace the unit with a new one.

Thanks to both of you for the answers!

 

[liquidgykill]

@EZ-Flash2

Update:
Got the replacement cart and everything works this time. The self hashing test ROM also gives the correct hash now when written to NOR (clean) and direct booted from there so the NOR flash or a solder ball of the NOR was also faulty. I don't know if this was also the cause of the RTC giving invalid values between minutes.

One problem that is not solved is the Aging cartridge test freezing roughly 15 minutes after the battery indicator goes red. Since the new cart has the same problem it might indeed be the battery but i repeated the test with the charger plugged in. It survived 6 hours and 29 minutes before it froze. I don't think it should freeze with the charger plugged in at all.

edit::
A small correction. The ROM hash test i was doing still fails if the test ROM is written to the upper half of the NOR flash. Can it be that i got a faulty cart again?

edit2:
Found out what's wrong. NOR erase and/or write is unstable. I can see single bit errors in the written ROM data.

edit3:
Attached my ROM test tool so you can experiment with it. It uses the fastest ROM wait states used by original games. The ROM hash is in its file name.

Hey, I just found your post while investigating my own issues with Ez Flash Omega
I dont play Poekmom so I dont know if my RTC works but I have game corruption and white screens while playing games from the SD card. The same games seems to work properly on NOR.
I documented my issues here: https://gbatemp.net/threads/ez-flash-omega-white-screen-on-games.673178/

I ran your test ROM from the SD Card and I got a hash very similar to yours except from 2 zeros in 90609 (I dont have those zeros).

your hash: 2ff7978fdad0c3e90609c63c5a1924d859c4a5e0
mine: 2ff7978fdad0c3e969c63c5a1924d859c4a5e0

ROM padding says no mismatches found, I ran the test on both my DS Lite and GBA SP with my EZ Flash Omega from the SD Card.

Please help me to interpret this
is the PSRAM damaged or is it something else?
thanks.