Independent CPU/VIC-II setup

From: tokafondo <tokafondo_at_gmail.com>
Date: Sat, 29 May 2021 12:37:29 -0500 (CDT)
Message-ID: <1622309849930-0.post_at_n4.nabble.com>
I've been thinking to put the VIC-II to work /independently/ of the CPU, and
I mean that the CPU won't get its clock from the VIC-II but from the clock
source itself.

I have a '816 CPU and the chips of a non working C64.

The idea is to have 64K of memory exclusive to the VIC-II mapped into the
memory address of the '816. The '816 would be running code outside of that
memory range, that would update the data that the VIC-II will use to render
the bitmap that will be used later to the final video output.

I know that in the C64 the VIC-II stops the CPU when needed to access the
memory to read the data. That should be still done in this setup, to avoid
bus contention -- or maybe a dual port RAM would be useful here, but out of
scope.

So help me with this:

my logical thinking says that if I run the '816 at ~8mhz or even ~14mhz (fed
by one of the clocks the VIC-II is also fed with), for everytime the VIC-II
does /one/ memory accesses, the '816 would be able to do eight or fourteen
times that memory accesses.

Is it like that?

Also, I'm thinking that a sort of address decoding mechanism could be used
in a way that the VIC-II would be only allowed to stop the '816 for its
additional fetches /when they both are accessing the same memory locations/,
but not when the '816 is somewhere else, like doing I/O or calculations in
some other memory space.

What do you think?



--
Sent from: http://cbm-hackers.2304266.n4.nabble.com/
Received on 2021-05-29 20:00:03

Archive generated by hypermail 2.3.0.