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.

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

SRAM instance export #145

Open
calebofearth opened this issue Dec 11, 2023 · 2 comments
Open

SRAM instance export #145

calebofearth opened this issue Dec 11, 2023 · 2 comments

Comments

@calebofearth
Copy link
Contributor

Request that SRAM instances (ICCM, DCCM, ICache) be moved outside of the VeeR core. Connections from internal modules should be exported to allow integrators to connect proprietary SRAM components. This could be done similarly to how Caliptra has implemented it with a SystemVerilog interface.

As part of this feature change, we also request that the SRAM interface be refactored to make the separation between data and ECC more clear. This request tracks chipsalliance/caliptra-rtl#125. Currently, the internal memories have multiple banks, with data and ecc aggregated into a single data bus for each bank, which makes the integrator's job more difficult when implementing system level reliability checks.

@algrobman
Copy link

there would be better way to use proprietary SRAMs RTL memories library modules can be replaced with custom onces, instantiating memory vendors verilogs ...

@algrobman
Copy link

does this really work?
see #163

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants