You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two very relevant information for debugging that are missing from the VDP registers view:
The value of the internal VRAM pointer register, and its configured I/O direction (read or write)
The state of the VDP.DW+1 port latch (aka 99h port latch)
Yes, for (1) I know that there's the decoded "Access Address" at the bottom right of the screen. But, just like all other decoded pointers in the bottom area (Pattern Name Table, Color Table, etc) it's better to also have all the raw registers that compose it at the top area of the window.
But the decoded "Access Address" should also show the configured I/O direction (read or write), as this information is missing.
In case of (3) I'm not sure if I could explain it well, but it's the latch of the I/O port that decides if you're writing the register value or its index. This subtle information is utterly important to debug misbehaving VDP write routines. Without it, it can take hours to find such a problem.
The text was updated successfully, but these errors were encountered:
I made a somewhat crude mockup to illustrate how the VDP registers view window would look with the additional information requested. Please don't mind the flaws in design as that would need refining.
There are two very relevant information for debugging that are missing from the VDP registers view:
Yes, for (1) I know that there's the decoded "Access Address" at the bottom right of the screen. But, just like all other decoded pointers in the bottom area (Pattern Name Table, Color Table, etc) it's better to also have all the raw registers that compose it at the top area of the window.
But the decoded "Access Address" should also show the configured I/O direction (read or write), as this information is missing.
In case of (3) I'm not sure if I could explain it well, but it's the latch of the I/O port that decides if you're writing the register value or its index. This subtle information is utterly important to debug misbehaving VDP write routines. Without it, it can take hours to find such a problem.
The text was updated successfully, but these errors were encountered: