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
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:
****assign el2_mem_export.dccm_wr_ecc_bank[i] = dccm_wr_fdata_bank[i][pt.DCCM_FDATA_WIDTH-1:pt.DCCM_DATA_WIDTH];
assign dccm_bank_fdout[i] = {el2_mem_export.dccm_bank_ecc[i], el2_mem_export.dccm_bank_dout[i]};****
if (DCCM_INDEX_DEPTH == 32768) begin : dccm
ram_32768x39 dccm_bank (
// Primary ports
.ME(el2_mem_export.dccm_clken[i]),
.CLK(el2_mem_export.clk),
.WE(el2_mem_export.dccm_wren_bank[i]),
.ADR(el2_mem_export.dccm_addr_bank[i]),
.D(dccm_wr_fdata_bank[i][pt.DCCM_FDATA_WIDTH-1:0]),
.Q(dccm_bank_fdout[i][pt.DCCM_FDATA_WIDTH-1:0]),
.ROP ( ),
// These are used by SoC
`EL2_LOCAL_DCCM_RAM_TEST_PORTS
.*
);
end
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: