I hope this has not been asked a million times before but here it goes.
How can I with assembly access the SRAM on the turbo-R ST and GT models? Can I write to it as if its memory etc etc.
Login or register to post comments
I hope this has not been asked a million times before but here it goes.
How can I with assembly access the SRAM on the turbo-R ST and GT models? Can I write to it as if its memory etc etc.
Not so difficult I see. Thanks
So I need to put slot 3-3 into page 1 and write 128 to $6800 then I have SRAM on adress $4000. Can I then simply read and write to it as if its memory so I can ldir to it and such?
Looks like it yes. The “closing value” is probably to page it out after accessing it so that RAM detection routines etc. won’t corrupt the data.
I think it is to get the kanji rom back since the RAM is on page 3-0 in my situation switching the subslot should suffice.
Wow.... it actually works!! It is indeed THAT easy as it is stated in the documentation. In the future however I will drop the sram and continue research on writing data to a more accessible format which everyone can have. This is purely to test the load and save function of the project.
I have noticed however that neither openmsx or bluemsx seems to handle the sram well. On the real machine it works like a charm but in the emulator the SRAM always returns $FF on all adresses. I have offcourse used the turboR roms and turboR setting in both emulators. Propably the SRAM is some setting in the emulators?
It's not some setting in openMSX.
When I start up the GT with firmware enabled, I can access drive D: (which is the SRAM) fine. And copy files to it, etc.
It would be helpful to have runnable code that demonstrates the problem and works on real turboR.
It would be helpful to have runnable code that demonstrates the problem and works on real turboR.
I will isolate the code I got and see how it turns out. If the difference remains I will send you the isolated code so you can see for yourself.
Great, thanks
Manuel you have mail.
Should be fixed (thanks Wouter!) in the latest development build (6c784ce). Please verify
Don't you have an account yet? Become an MSX-friend and register an account!
