| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
The 200 MHz SRAM seems to finally work.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Apparently generate if statements with declarations in both branches
can make Quartus II think that the register is unused (duplicate?)
Thus drop it and (suboptimally) always disable design rule D104. It
would still be possible to fix this by duplicating the synchronizer
code, but that's for later.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
|
|
|
|
|
|
|
| |
No need to have a filter that will only used for a synchronizer at the
top level, now when synchronizer should only be used from the
synchronize wrapper module.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
|
|
|
|
|
|
| |
Add appropriate modules for both synchronizer and stabilizer, with the
appropriate attribute magic for both.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
|
Infrastructure for changing the SRAM timing to add another shared
device (intended to be the Neopixel driver.) This means upping the
SRAM state machine clock to 200 MHz; move video_clk to pll2 to be able
to generate that output. It actually gets closer to proper VGA
timing, but at the expense of needing a synchronizing FIFO for the fg
unit.
This also clears a lot of timing warnings.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|