I've been having hit-or-miss results with the Genesis save ram support. I have four games with valid saveram that I wanted to copy:
Phantasy Star 2 = Works (yay!)
Sonic 3 & Knuckles = can't rip; see other thread
Light Crusader
Beyond Oasis
The latter two games still have valid saves on them (I plugged into the Genesis to confirm). However, when copying with the retrode into the directory where my emulator expects saveram, the emulator then runs the game as if it had no save. I cleaned and re-tried, only to end up with the exact same copy as the first attempt. Since the game itself copied flawlessly, I don't think it's a dirt issue.
I'm having the same problem with phantasy stars 3 and 4. The srm file copies over just fine. I've taken the files out of read only, tried putting the srm in the same folder with the bin file, pointing the emu directory... nothing seems to pick up on them. I've tried RetroCopy, GENS and Fusion. I was able to successfully copy over Zelda from the SNES cart and zsnes picks up on the save games just fine.
Have you tried the 16-bit mode? (see RETRODE.CFG)
same problem here with phantasy star iv so far. changing to 16-bit mode doesn't help. neither kega nor regen recognize my sram. :( any news on this?
In case you're talking about Wonder Boy In Monster World, it's probably not SRAM; see my reply in your other thread.
so Phantasy Star IV is using EEPROM as well? Because according to this site, it's using something called "SRAM bankswitch hardware" http://code.google.com/p/genplus-gx/wiki/Features
Ah, I just found some information (http://cgfm2.emuviews.com/txt/gen-hw.txt):
Quote4.3) Phantasy Star 4
Phantasy Star 4 is a 24 megabit game with 16k of battery backed RAM
mapped to $200001-$203FFF. (odd addresses used) It has ROM in the same
area where the RAM is. I've observed that the game will always write
$01 to $A130F1 before accessing the RAM, and then write $00 when
done. It could be that bit 0 of $A130F1 controls ROM/RAM banking at
that location.
Jeff Quinn has tested this and confirmed it to work, and also reported
an area of the game where supporting banked SRAM is important; when
your characters encounter a GEROTLUX below the town of Tyler on Dezolis,
the game will try to access the ROM data that is obscured by SRAM.
Got to give that a try whenever I find the time for it.
@Pat1986: Thanks for confirming that Firmware v0.17g (http://www.retrode.org/firmware) reads PS4 SRAM fine.
You're welcome. Now all i need is support for EEPROM and the ability to dump Super Skidmarks. ;)
Don't know what's the matter with Super Skidmarks, and finding out will be a bit more troublesome. Do you have a continuity tester or multimeter with "beeping" functionality?
Nope, sorry.
Hey there!
Just got the Retrode in, and it works perfectly. Just dumped my copy of Sonic3&Knuckles and the SRAM, works perfect in Fusion 3.51 ! :D
I updated to the Retrode .17h firmware by following the instructions with FLIP, then changed the setting in CFG:
[segaSram16bit] 1
Otherwise the SRAM does not work. I also cleaned all the connectors before doing this. Hope this helps anyone else.
Great work Matthias, thank you!
EDIT: I'd also like to mention that copying the save game back after playing in KEGA does work, so long as it is still in segaSram16bit . Checked it on my MegaDrive and the save is updated! Amazing.
I just got my Retrode today, but my PS4 save (or more appropriately Phantasy Star: The End of the Millennium save) didn't copy (in 0.17g). I have the Japanese version, and I don't know if that has something to do with it, but it does get detected as NoName.7667.bin, so I'm wondering if there's some special autodetection of the specific cart that doesn't exist for the Japanese version and thus doesn't copy the save correctly. It may be worth noting that the ROM copies fine.
I'd appreciate any input!
Is the cart clean? Does it still give the NoName filename after resetting the Retrode with the cart in?
I will give it a thorough cleaning when I get home.
It DOES still give the NoName filename after resetting the Retrode. Also, the NoName file does get detected as a good dump of Phantasy Star: The End of the Millennium by GoodGen. It's just the save file that does not work (the only option is to start a new game, while the cart itself WAS confirmed to still have proper save data).
Okay, more questions:
- Is there a .srm file in the same directory? (That would be the save ram. Opening it in a hex editor will reveal whether or not there's any data in it)
- Have you set the correct path for SRAM in your emulator? (It must point to Retrode's drive letter)
Yes, there is an srm file, but no, I haven't had a chance to try and open it in a hex editor. I will do that as well when I get home.
I did not change my emulator settings, but I also did not use the Retrode drive's srm file directly. I copied it into my Genesis roms directory (and yes, the filename matches that of the rom aside from the extension). Does that not work or something?
The emulator needs to find the file in its SRAM search path upon loading the ROM. If you prefer to copy the srm file over to your ROM directory, you may still have to point the emulator config to that location.
Quote from: Matthias_H on 18/Sep/2012 07:13:26 PM
The emulator needs to find the file in its SRAM search path upon loading the ROM. If you prefer to copy the srm file over to your ROM directory, you may still have to point the emulator config to that location.
Sure, yeah. I will double-check when I get home to make sure the particular emulator I used was set up to use the same directory the roms are stored in for sram. I'm pretty sure it is, but I hadn't used it in a while, so it won't hurt to check.
Okay, results. I cleaned the cart connector thoroughly. Still the srm file doesn't work, and opening it in a hex editor (right from the Retrode drive) - revealed all "FFFFFF", so no data.
Running it on the console (with a Game Genie to make the cart fit), everything is still normal, so the saves aren't deleted; the Retrode just isn't picking them up for some reason.
Okay. Seems that PS4 memory mapping isn't quite as simple as I thought. I'll put it on my "things to investigate" list. Thanks for your info and testing.