Bluemsx reports potential data loss in VRAM I/O on MSX1, but it seems not able to distinguish between active area and borders (am I wrong ?)
Is there something more accurate e.g. in openmsx ?
Login or register to post comments
Bluemsx reports potential data loss in VRAM I/O on MSX1, but it seems not able to distinguish between active area and borders (am I wrong ?)
Is there something more accurate e.g. in openmsx ?
AR, I don't know about active area and/or borders. If I understood correctly, I bet the test makes no difference.
Anyway, when I was debugging the conversions, I have used this openMSX feature:
MSX1 VDP I/O speed
Fire up some MSX1 machine, like the National CF-3000
Pause it on the MSX boot screen (press the Pause key on PCs, or cmd+P on Macs)
Open the openMSX console (press F10 on PCs, or cmd+L on Macs)
Type toggle_vdp_access_test
Remove the pause by pressing Pause or cmd+P again.
As your program runs, this script will then nicely summarize all the addresses that do I/O to the MSX1 VDP at a higher speed than allowed. You don't have to worry about turbo speeds on this test: the turbo machines required to provide some mechanism to allow the proper I/O speed, either by lowering the CPU clock on each VDP I/O (MSX1, MSX2) or by generating the necessary waitstates when needed (MSX2+, MSX Turbo-R).
Don't you have an account yet? Become an MSX-friend and register an account!
