Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Can not set initial contents of trueDualPortRAM #2199

Open
lmbollen opened this issue May 10, 2022 · 1 comment · May be fixed by #2204
Open

Can not set initial contents of trueDualPortRAM #2199

lmbollen opened this issue May 10, 2022 · 1 comment · May be fixed by #2204
Labels
enhancement

Comments

@lmbollen
Copy link
Member

The trueDualPortRAM component (https://hackage.haskell.org/package/clash-prelude-1.6.3/docs/Clash-Explicit-BlockRam.html#v:trueDualPortBlockRam) has no API to set the initial contents like blockRam (https://hackage.haskell.org/package/clash-prelude-1.6.3/docs/Clash-Explicit-BlockRam.html#v:blockRam).

As far as I know there is no technical reason to not be able to define the initial contents and the added value of this functionality seems very significant to me.
@DigitalBrains1
Copy link
Member

Note that our asynchronous RAMs also only have undefined initial contents. It could be worthwhile to add it there as well.

@hydrolarus hydrolarus linked a pull request May 11, 2022 that will close this issue
Draft
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add version of trueDualPortBlockRam that sets the initial RAM contents clash-lang/clash-compiler
3 participants
@DigitalBrains1 @lmbollen @alex-mckenna