Jump to content
IGNORED

VDP read/write timing


Asmusr

Recommended Posts

Starting a new thread to keep this out of the Sabre Wulf thread.

 

I believe Tursi is right when he concluded that the only way to overrun the VDP is "if you set the address then immediately read the data port, but running with no wait states"

See http://atariage.com/forums/topic/164410-vdp-overrun-revisited/page-2?do=findComment&comment=2038835

 

The weird thing is that Classic99 is giving warnings in the debugger about "reading the VDP too quickly" if you just run Extended Basic. ;)

Link to comment
Share on other sites

Can't fix it if nobody tells me ;)

 

That said, you /can/ overrun the VDP in the case it's tracking.

 

But, software pushes the rules. That's not unusual. If you go look at the parts it's complaining about, you'll see setting an address, then reading VDP data on the next instruction. ;)

  • Like 1
Link to comment
Share on other sites

Right. I believe Tursi's statement (see post #1) to be true; his research was very extensive. It's probably just a glich in Classic99. Personally, I'd like a switch to enable/disable VDP overrun detection. Something in Classic99.ini would be fine, no need to mod the GUI for it.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...