If Backup Ram Cartridge was set correctly, the Backup Ram switched(press the R or L button) with no issue,FYIView attachment 7572View attachment 7573
0.127 can not work on real hardware
emu ok
If Backup Ram Cartridge was set correctly, the Backup Ram switched(press the R or L button) with no issue,FYIView attachment 7572View attachment 7573
0.127c can work on real hardware.I got a 512K file,Thank you very much! I will optimize it more for next version, as there is already few ideas how to cut instructions per byte count.
Please, may you attach this file? And what it shows at cart_id and [1] id and size?0.127c can work on real hardware.I got a 512K file,
but , the 4M memory card file is only 512K,Incompatible with SSF,yaba....,this file needs 1024K in EMU
void spi_send_byte(unsigned char byte_to_send)
{
int i;
unsigned char mask[8] = {0x80, 0x40, 0x20, 0x10, 0x08, 0x04, 0x02, 0x01};
for(i=0; i<8; i++) // Unroll the loop may be a bit faster
{
if(byte_to_send & mask[i])
{
PDR1 = constant_value1; // CS=0, MOSI=1, CLK=0
PDR1 = constant_value2; // CS=0, MOSI=1, CLK=1
}
else
{
PDR1 = constant_value3; // CS=0, MOSI=0, CLK=0
PDR1 = constant_value4; // CS=0, MOSI=0, CLK=1
}
}
}
Yes, by setting address and data lines to mimic jedec eeprom erase/write sequences it is possible to write onboard eeprom, and if /we properly decoded on cart. But it is a feature for later version.Is possible to write action replay?
The files dumped by 0.127d-bug & 0.2a cannot be directly used by the yabasanshiro,and the items are still lost. need to use the segasaturn RAM Backup parser 0.9.9 to convert them to SH2 and 512 for normal recognition。New version 0.2a. Hits 60kb/sec transfer speed now! No more need to place files for saving, SDLoader will create it if needed.
Changed fat library. It is only test release. But basic functions works ok (load and run binaries, dumping internal backup ram)
Just for test, dumped simple action replay cart (without backup ram) with this version (of course, modified a little), 256kb rom mapped at 0x02000000. It dumped fine in few seconds and after transfering to pc, running fine in Yabause without issues. So, i hope, it will dump your 4mbit backup ram now without errors, tzmwx.
Please, try this build (sdloader_test) with external cart backup ram viewer (UP/DOWN to scroll) and tell if its show header and saves ok or same as in your dumps? Because, on Yabause it works without errors, and dump exactly 1:1 as ext backup ram (i may only suspect that at real hw byte accessing to even adresses at cs1 cause some exception, which affect integrity of dump - if it is, than just need to align reading to only odd bytes. But anyway, byte read at even addresses of internal sram didnt caused any problems, maybe its smpc involving while access to cs1. Anyway, lets see what this build will show about reading extram)The files dumped by 0.127d-bug & 0.2a cannot be directly used by the yabasanshiro,and the items are still lost. need to use the segasaturn RAM Backup parser 0.9.9 to convert them to SH2 and 512 for normal recognition。
sdloader-test:Update:
v0.21 - added aligned access to external ram cart (tzmwx, check this build too)
Please, try this build (sdloader_test) with external cart backup ram viewer (UP/DOWN to scroll) and tell if its show header and saves ok or same as in your dumps? Because, on Yabause it works without errors, and dump exactly 1:1 as ext backup ram (i may only suspect that at real hw byte accessing to even adresses at cs1 cause some exception, which affect integrity of dump - if it is, than just need to align reading to only odd bytes. But anyway, byte read at even addresses of internal sram didnt caused any problems, maybe its smpc involving while access to cs1. Anyway, lets see what this build will show about reading extram)