Closed algrobman closed 2 months ago
@algrobman this issue with testbenches was likely fixed in https://github.com/chipsalliance/Cores-VeeR-EL2/pull/194. Do you still get these errors after the change?
I'm closing this issue due to lack of activity, but feel free to reopen if the problem occurs again.
I'm trying to simulate it with Xcellium and getting whole design in Xs after first access to DCCM. It seems to me that the memories moved to TB are not connected/wrongly connected to design:
dccm_bank_fdout - is memory output, but it is driven by interface signal in above assign statement
dccm_wr_fdata_bank is the memory input, but it used to drive the el2_mem_export interface ????
More questions: why were the memories moved from design? why do you keep sized memories macroes? They were used originally to include vendor's real memories of specific technology into RTL design for synthesis, but once they were moved out why do you need them?
Also why do you moved out only ICCM/DCCM memories and not IC mems?
Are you ever simulated this design with commercial simulators?
Also your picolibc stuff does not compile, even if I want to run just hello_world ( asks for multilibs and ninja) could you guys, please, separate all these nice to have things from basic stuff, so people will not need to install all this SW to just try this design?