NESDev and Strangulation Records messageboards
Forum Index | FAQ | New User | Login | Search

Previous ThreadView All ThreadsNext ThreadShow in Flat Mode*


SubjectRe: NES hardware development  
Posted byAnonymous
Posted on1/3/03 1:34 PM
From IP130.236.226.110  



> See my previous post on this subject.
>
> But just to be clear, the PPU & CPU buses have mutually exclusive memory
> access cycles (2.68 MHz for PPU; 1.79 MHz for CPU). So there would be no way
> of sharing a common bus between the PPU & CPU (espically since there ARE
> cycles when both the PPU & CPU disable their respective bus read enable
> control lines simultaniously).

Please correct me if I'm wrong, but shouldn't it nevertheless be possible to emulate a dual-port SRAM chip that could function as *both* CPU-memory and PPU-memory by using a single large fast SRAM chip along with equally fast buffering logic that could handle the accesses made by the CPU and the PPU?

Since the PPU runs at 21.47727Mhz (on an NTSC NES), the maximum number of nanoseconds between accesses to this general-purpose memory would be 1 / 21.47727*10^6 = 46.7 ns. Today we have SRAMs with access times as fast as 20 ns. So if such an SRAM chip was used, it could be accessed on *every* CLK cycle generated by the main clock. So if the CPU would read/write the memory during the exact same CLK cycle when the PPU is reading it, then the PPU would be favored and get its data immediately as usual, while the CPU's read/write would be buffered and delayed until the next CLK clock, when the PPU would no longer access the memory. Considering that the M2 clock is either 1/12th or 1/16th of the main CLK clock, shouldn't the CPU get its read data in time if only the buffering logic used would be fast enough?...

// Michel Iwaniec (bananmos_uv@hotmail.com)



-
Entire Thread
Subject  Posted byPosted On
*NES hardware development  Anonymous12/8/02 08:14 AM
.*Re: NES hardware development  Betaman1/3/03 02:31 AM
..*Re: NES hardware development  Anonymous1/3/03 12:55 PM
.*Re: NES hardware development  LegalStuff12/31/02 3:00 PM
..*Re: NES hardware development  Betaman12/31/02 4:51 PM
...*Re: NES hardware development  LegalStuff1/1/03 12:17 PM
.*Re: NES hardware development  Betaman12/27/02 07:50 AM
.*Re: NES hardware development  Betaman12/25/02 5:22 PM
.*Re: NES hardware development  Anonymous12/22/02 08:04 AM
..*Re: NES hardware development  Memblers12/22/02 3:17 PM
...*Re: NES hardware development  Betaman12/22/02 5:14 PM
....*Re: NES hardware development  Betaman12/22/02 10:04 PM
.....*Re: NES hardware development  Memblers12/23/02 05:25 AM
......*Re: NES hardware development  Big Time12/23/02 08:10 AM
....*Re: NES hardware development  Betaman12/22/02 7:22 PM
.....*Re: NES hardware development  Big Time12/23/02 08:24 AM
.......Re: NES hardware development  Anonymous1/3/03 1:34 PM
.......*Re: NES hardware development  Big Time1/3/03 10:56 PM
......*Re: NES hardware development  Betaman12/23/02 6:02 PM
.......*Re: NES hardware development  Memblers12/24/02 1:39 PM
........*Re: NES hardware development  Big Time12/24/02 11:03 PM
.........*Re: NES hardware development  Memblers12/24/02 11:18 PM
........*Re: NES hardware development  Betaman12/24/02 8:28 PM
.........*Re: NES hardware development  Memblers12/24/02 11:06 PM
.*Re: NES hardware development  mcmartin12/14/02 06:41 AM
.*Re: NES hardware development  RoboNes12/8/02 09:04 AM
Jump to

Memblers' homepage             Contact Me

Forums powered by WWWThreads Demo