**************************************************...
# caravel
m
****************************************************************************** <!channel> We've just discovered that a bug in the litex implementation of Caravel has made it onto MPW2, 3 & 4. This bug limits the wishbone user address space from 0x3fff_ffff to 0x3010_0000. https://github.com/efabless/caravel_mgmt_soc_litex/issues/21 Please let us know if your project is affected by this. Because of the amount of work required to validate the management SoC after fixing the bug, we're not sure if the fix will be in for MPW5, so please check your designs for MPW5. ******************************************************************************
d
This will impact all my MPW-2/MPW-3/MPW-4/MPW-5 submission as my design expect at 0x3000_0000 to 0x30FF_FFFF address range for user space. Not sure why Caravel SOC level simulation with user_project_wrapper is not broken ? Is it because caravel simulation setup for MPW2/MPW3/MPW4 uses picorv32.v instead of litex core ?
m
I was worried about yours Dinesh. It's because after MPW1 issues, the management core was retroactively swapped out. So we tested our designs with picorv32 and they were actually taped out with litex vexrisc
i
Hi My project in MPW-2 uses from the 0x3000_0000 to 0x3010_007F. So the part from 0x3010_0000 to 0x3010_007F will be broken?
m
what will happen is that an access above 0x3010_0000 will not generate the cycle/strobe line so your project won't respond or ack and the cpu will hang
d
Is it possible to re-submit MPW-3/MPW-4 tapeout ?
m
yes
i
Ok so this affects our ability to access one part of our design. But is a redundant way to access. So the impact will be minimal.
d
@User I assume this will be caravel fix and user need not required to adjust the address space.
s
@User, I have used address spaces 0x3001_0000 to 0x300A_0000. Its okay right?
d
@User Your address with 0x3000_0000 to 0x300F_FFFF, it should be good for you
@User This issue look like already reported on 1 Jan 2022 itself https://github.com/efabless/caravel_mgmt_soc_litex/issues/10 look like no one given attention to this? Due to Multiple MPW5 tool setup issues, I was also using MPW-4 caravel RTL for simulation and not noticed this issue.
👀 1
@User I am bit confused with MPW-5 shuttle email saying caravel address map issue will not be fixed ? Is it means I need re-submit the my MPW-2/MPW-3/MPW-4 project in MPW-5 with address fix?
m
@User, what was the plan for people affected by this?