You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@vertrex, it looks like the reason you need 96MHz is because you are not using a double-line buffer, but a single line. I think you are trying to fill all the line data during blanking in a single buffer and then dump it during the active time.
That approach, although doable, was not the standard one at the time. Even today, there is no benefit in doing it that way as you will still allocate a whole 1kB of BRAM, not the 256 bytes you explicitly declared.
Instead of doing that, follow what the other cores do. There is a module that already implements the dual memory and synthesizes well across the different platforms. From the point of view of the core, it is straight forward to use it. You have a full line time to draw the sprites in one buffer, while data is dumped from the other buffer. This will allow you to go down to 48MHz.
The text was updated successfully, but these errors were encountered:
@vertrex, it looks like the reason you need 96MHz is because you are not using a double-line buffer, but a single line. I think you are trying to fill all the line data during blanking in a single buffer and then dump it during the active time.
That approach, although doable, was not the standard one at the time. Even today, there is no benefit in doing it that way as you will still allocate a whole 1kB of BRAM, not the 256 bytes you explicitly declared.
jtcores/cores/toki/hdl/sprite.v
Line 29 in e63a12e
Instead of doing that, follow what the other cores do. There is a module that already implements the dual memory and synthesizes well across the different platforms. From the point of view of the core, it is straight forward to use it. You have a full line time to draw the sprites in one buffer, while data is dumped from the other buffer. This will allow you to go down to 48MHz.
The text was updated successfully, but these errors were encountered: