That's the idea anyway... Now, how to keep track of the progression of what is being displayed is something that I will have to investigate by trial and error which will be the fun part!
Code: Select all
OS OS OS
SRAM SRAM
U3 U2
OS FPGA OS
U9 U7 U1 U4
+======== I/O ========+
I know, I'm a stinker for even bringing it up at this stage of the game, but that little engineer in my head wouldn't leave me alone!
Mike
I had focused on keeping the traces to the RAMs as close as possible, everything else was secondary. Those long traces you see are primarily for the RGB data in and RGB data out. PVBV2 design closely follows the original PVB design... And now that I think about it, those long traces may have been contributing to some things that were happening but didn't realize at the time. i.e. some colors appeared to be 2 pixels wide IIRC. I was also using a slow videoDAC, ADV7125 rated @ 140MHz when the pixel clock was ~150MHz. I'm sure both were contributing... However thinking about it further now, if the Pixelclockout trace length was close to the RGBout trace lengths, maybe there would be no issue with the length? Irregardless, shortening the trace lengths of these critical signals cannot be a bad thing!
I'm also investigating a free PCB layout tool called FreePCB, where one can just start laying down parts.