Closed MrJake222 closed 6 months ago
Hi,
Here i can see a violation, a ibus rsp comming without the cmd having fired :
Did you configured the ibus cmd fork to be persistant ? https://github.com/SpinalHDL/VexRiscv/blob/457ae5c7e5c8183f0ba7c51f7f0301d05eb8ced1/src/main/scala/vexriscv/plugin/IBusSimplePlugin.scala#L225
Did you configured the ibus cmd fork to be persistant ?
Thank you. I've set it to persistent now and the issue is fixed. Now i see the docs saying it's risky and widely unsupported. I question why is it set in demos then?
The reason was that those demo were designed to be as small as possible in terms of ressources. Non persistant instruction cmd allow to avoid some "expensive" buffers.
Hi, I'm trying to hook VexRiscV small and productive variant to my own SoC, and (after fighting a lot of bus errors) I'm at a loss now. Why earlier (270us) shift works and after some time at 410 us same instruction causes
icmd_valid
to go low?WORKS
DOESN'T WORK
Code being executed:
Is something obviously wrong here? Any help appreciated. cvrisc_read_data.vcd.zip