Open povik opened 7 months ago
@mmicko I would guess this a problem with some clock routing resources being missing so some DCCs aren't working properly, would you be able to look into this?
Problem occurs when there are no constraints, so promote_globals
work fine and add DCC and route trough it, but later place_globals
fails, since there are no constraints (BEL attribute).
Can we make the global placement robust enough that it works even in this case? I imagine the same case of unconstrained position would occur e.g. with a global driven from a fabric clock divider (sure, often bad practice, but still sometimes useful).
Ah. Missed the comment. Will need to think more about possible solution.
On nextpnr 4a7e58a, trellis 36c615, trellis-db 4dda149 I got the following
when routing a simple design with a registered multiplier
If I increase the dimension of the multiplier, the routing stops failing, which suggests to me this is a bug in nextpnr. Attaching logs and the JSON result of synthesis.
log.txt multest.json