Open alex96295 opened 1 day ago
It seems that the axi_id_serialize updated in v0.39.4 axi release prevents Linux from booting properly on cheshire - FPGA port; my educated guess comes from these three CIs:
axi_id_serialize
v0.39.4
v0.39.2
main
v0.39.3
Proper debugging is required to narrow down the issue, which may contradict the guess above
@paulsc96
alex96295
commented
1 day ago
It seems that the
axi_id_serializeupdated inv0.39.4axi release prevents Linux from booting properly on cheshire - FPGA port; my educated guess comes from these three CIs:v0.39.4(fromv0.39.2, the one currently used inmain) in Cheshire leads to a boot failure on both boards: https://iis-git.ee.ethz.ch/github-mirror/cheshire/-/pipelines/93469v0.39.3leads to a boot success on both genesys2 and vcu128: https://iis-git.ee.ethz.ch/github-mirror/cheshire/-/pipelines/93482v0.39.4, where I use the older version of the id serializer, also leads to success but only on genesys2, while on vcu128 the timing is not closed so implementation fails: https://iis-git.ee.ethz.ch/github-mirror/cheshire/-/pipelines/93489Proper debugging is required to narrow down the issue, which may contradict the guess above