-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for memories with N read-only ports + 1 write-only port? #153
Comments
You can already do this: simply request the appropriate amount of read ports by calling |
Hmm. One would have to check that carefully (I remember problems with ISE a long time ago), though this would be one of many issues that would disappear if we let Yosys synthesize memories for all FPGA families. |
According to IRC conversation with @cr1901, ISE and Vivado can do that. |
Rationale: The default config file of |
Closing; please reopen if there are actual toolchain bugs we need to work around. |
One trick I've used several times to implement a memory with several (typically N=2...4) read ports plus one write port is to use N dual-port memories with, for each memory, one port used for reading and one port used for writing. The individual write ports are connected in parallel to form the write port into what is the equivalent of a N+1-port memory with N read-only port and 1 write-only port.
Should nMigen automatically implement this pattern when applicable, or should this be done manually by the user?
The text was updated successfully, but these errors were encountered: