Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relevant information missing from the VDP registers view #148

Open
sdsnatcher opened this issue Jan 29, 2023 · 1 comment
Open

Relevant information missing from the VDP registers view #148

sdsnatcher opened this issue Jan 29, 2023 · 1 comment

Comments

@sdsnatcher
Copy link

sdsnatcher commented Jan 29, 2023

There are two very relevant information for debugging that are missing from the VDP registers view:

  1. The value of the internal VRAM pointer register, and its configured I/O direction (read or write)
  2. 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.

@sdsnatcher
Copy link
Author

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.

openMSX_VDPregsWindow_Mockup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant