<whitequark[cis]>
joseng: okay, so i see two kinds of violated paths in that report
<whitequark[cis]>
the first one is in sys_clk<>hdmi_clk. those clocks aren't intended to be related, are they?
<whitequark[cis]>
you need to add a set_clock_groups constraint for those domains
<whitequark[cis]>
the second kind is reset deassertion violation. you might want to put a BUFG on that net with a fanout of 1600
<whitequark[cis]>
* on that reset net with
<whitequark[cis]>
sys_rt
<whitequark[cis]>
* sys_rst
FabM has quit [Ping timeout: 268 seconds]
Guest59 has joined #litex
Guest59 has quit [Client Quit]
kw has joined #litex
kw has quit [Client Quit]
kw00 has joined #litex
<kw00>
hi
<kw00>
I started using litex and it is great. I managed to apply some fpga configuration to colorlight board with vexriscv and run application in rust. I have colorlight hardware revision 8.2 which is not yet supported. I would like to figure out fpga pin names and pins on hub75 connectors like described here for previous revision