Hi all,
Is there any known differences between the way that openMSX is managing the V9990 commands such as LMMM and the real hardware. I've the impression that LMMM is working fine in P1 mode on all the operations on PLAN A, but not on PLAN B.
I've setup a copy data example likr this one sx:512, xy:512 dx:512 dy:416 nx:256 ny:32 and, on screen the result is stange (black filled squares appears in the result on real hardware, in open-msx it's as expected).
I'm using the G9K Library CopyXYToXY method , I've tryed other pieces of code (out of G9K), and the results are always the same.
Is there any issue with the V9990 vram to vram copy actions after the VRAM 0h40000.
PS: same method is working well on plan A ( < #40000)
<>
G9kWriteReg G9K_ARG,0
G9kWriteReg G9K_LOP,G9K_LOP_WCSC
LD HL,#ffff
CALL SetCmdWriteMask
ld hl, copyWaterAnimData
call CopyXYToXY
copyWaterAnimData:
DW 512 ; SX
DW 512 ; SY
DW 512 ; DX
DW 416 ; DY
DW 256 ; NX
DW 32 ; NY
If somebody can help on that because I'm totally puzzled by the VDP behaviour, thanks
:)