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
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.
The text was updated successfully, but these errors were encountered:
there would be better way to use proprietary SRAMs RTL memories library modules can be replaced with custom onces, instantiating memory vendors verilogs ...
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.
The text was updated successfully, but these errors were encountered: