Jump to content
  • entries
    53
  • comments
    536
  • views
    68,392

Scanline timing diagram


Guest

714 views

I don't know if this has been done before, but this diagram is the secret to my time-sensitive kernels. It shows every clock and every cycle of the scanline. No more adding up cycles. If you know what your kernel needs to do at a particular point, the code almost writes itself!I've attached a blank diagram, and an example filled out for the main part of Marble Jumper. I'll take suggestions for improvement, and if it seems useful to enough people, it could go in the MiniDig.stak.zip stak.zip

5 Comments


Recommended Comments

That's a really nice diagram, Zach.

 

It might be nice to add arrows (or something) for when graphics writes need to happen. E.g., I'm pretty sure that you need at least a cycle lead time when writing to PF0, PF1, or PF2. In other words, writing to PF1 at cycle 28 will be too late; the write to PF1 needs to happen by cycle 27. This also applies to GRP0 and GRP1.

 

That doesn't apply to color writes, as far as I've been able to tell.

Link to comment
What I've done in the past is to put it in a simple spreadsheet which then makes it easier to shift sections of code around.

 

Once upon a time I used a Macintosh paint program to draw up a timing sheet with 76 cycles across, and with the playfield pixels marked. I may somewhere have a paper timing diagram from my first kernel which I did back in 1995 or thereabouts.

Link to comment
Guest
Add a comment...

×   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...