I took a look at your files. The data behind it seems odd.Hello，check zip file ！The file（Bksv4m.bin）cannot be used by yabasanshiro & SSF through your converter.
About half of the items have been lost.
Another file（Bksv4m256to512.bin）can be used by yabasanshiro & SSF after being converted to 512 through SS RAM Backup parser0.9.9.the items have not been lost.
yabasanshiro V 3.4.2I took a look at your files. The data behind it seems odd.
Your first block of data is correct where the first 0x100 bytes are filled with the term Backup Format. But your second block seems to have data in it when it should be completely empty. Then your third block does not begin with a save file, although this could be due to constant erasing and saving.
May I ask, how did these save files get generated? What version of Yabasanshiro?
1.items lostok, I think the problem is you are on an old version of Yaba sanshiro.
The newer versions work with your 256 save file after converted.
You need to pick External/yabashiro_<filename>
View attachment 7670
@Murzik If you have time, check the second block of your save files. This block should be all zeroes.
SDLoader have nothing to do with it, as it just reading memory regions and dump them as they are. If there is something in flash, it will be in the dump. We already confirmed it with tzmwx, using memory viewers (in SDLoader and with Charles MacDonald's memory viewer) on his saturn to check second block of flash.@Murzik If you have time, check the second block of your save files. This block should be all zeroes.
Error:Write check failedThank you!
Here is v0.31
Added data polling to check sector write status, and use frt to timeout it if something goes wrong. And traditionally - didnt tested on real hw yet. Hope it works and 4m cart restoring became little faster.
This is not an ODE. need a modchip and boot disc（burn SDLoader.iso to the disc）Quick question, does this boot without a modchip or boot disc? Can it boot off a stock Saturn? From the videos I have seen from @tzmwx it looks like he goes into the memory menu then exits out and it boots the SD Loader software. I made my own adapter and it is not doing anything like I have seen in the videos nor is it explained in the initial post. Thanks for any info regarding this.
tzmwx, i enabled restore function for your backup ram cart in v0.302. You may try it at your own risk As i not tested it on real hw (dont have at29c040a based backup ram cart). Only one thing will not fail for sure, restoring speed will be very slow, as i currently not implemented data polling for checking succesfull sector writes, and just use blocking delays equal to Twc. But I added simple progress counter just before build (but it will begin to iterate only after first 32k buffer readout, will fix in next release, so you will need to wait even for progress counter to appear ). Any way, please dont interrupt it in restoring process. And also, i get as an assumption, that your flash dont have SDP enabled (probably it is what if unchecking option "Protect" in programmer soft do). So, every sector write will be without leading SDP disable commands.
I may only suggest, if you will decide to test it - just get backup first, then, maybe try to delete one save (or copy any additional save to it), and try to restore backup, to see if it reverts to original state.
And may the force be with you.
SDLoader have nothing to do with it, as it just reading memory regions and dump them as they are. If there is something in flash, it will be in the dump. We already confirmed it with tzmwx, using memory viewers (in SDLoader and with Charles MacDonald's memory viewer) on his saturn to check second block of flash.
Btw, tried to patch Yabause for 256b sector, here is screenshots of Yabause with your BKSV4M.BIN (256 sector not converted) in attachment
In real hw, bios reading cartid, and if there is unknown bup cart id (as in case of tzmwx bup cart, where it is "0x1"), it issuing read vid/did commands to detect flash and set sector size. And in Yabause, flash commands only decoded for cs0 region, and for cs1 region every command will just be written as is into memory. And, as you select 4Mbit bup cart option in Yabause, it sets cartid to standard 4Mbit id (0x21), and bios use it to set 512b sector.
You need to patch and rebuild yabause from sources. It requires to replace cart id for 4mb backup to 0x01 and set device id for it as 0xa4, and add FlashCs1writes/reads for bup4mb (look at how it is done for FlashCs0), so, bios, when it get cartid 0x01 will start to probe rom at cs1 and when it get 0xa4 it will set sector to 256b. Files to modify: bios.c and cs0.c. I still have modified source, if you will plan to rebuild, i may provide diff patchHow to make yaba use 256b sector files? I tested version pro 1.9.2 and still can't use it directly.