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
Hi.
I tried to change AXI data width (AxiDataWidth : from 64 to 128).
However, this occurs several errors and it seems that cva6 cache system only allow 64bit data width.
When I tried to fix them with AXI_downsizer module between CVA6 (64bit) and AXI-bar (128bit), it is blocked at booting stage.
I wonder Cheshire support that change via parameter, now.
Thank you.!
The text was updated successfully, but these errors were encountered:
Thanks for reporting this issue. In principle, AXI data widths of more than 64 bits should be supported, but we indeed did not test this extensively. I assume the issue lies with the fairly new data width parameterization support of CVA6, since all other AXI IPs are inherently designed to not be datawidth-specific.
We will look into this at the earliest convenience.
Apologies for the delay. If I understand correctly, the write-back (WB) data cache of CVA6 indeed does not support different datawidths, only the write-through (WT) cache. You should be able to switch to the WT by changing your Bender flags accordingly.
If you want or need to use the WB cache, a datawidth converter should work. You mentioned using an axi_dw_downsizer but if you are injecting traffic into a wider (128-bit) crossbar, you would need an axi_dw_upsizer instead. In any case, I would simply instantiate an axi_dw_converter to avoid issues.
Do you have an example for a branch using datawidth conversion that does not work? If so, I can look into it.
Hi.
I tried to change AXI data width (AxiDataWidth : from 64 to 128).
However, this occurs several errors and it seems that cva6 cache system only allow 64bit data width.
When I tried to fix them with AXI_downsizer module between CVA6 (64bit) and AXI-bar (128bit), it is blocked at booting stage.
I wonder Cheshire support that change via parameter, now.
Thank you.!
The text was updated successfully, but these errors were encountered: