<benjaminh-13>
I'm trying to implement a NaxRiscv-based SoC on FPGA but synthesis fails, as when instantiating the NaxRiscv, the SoC's top level module tries to connect to port which do not exist. Precisely, I'm trying to add a JTAG debug module within the Nax, which thus exposes I/O ports in the Nax's top level, but for some reason, when integrating the Nax in
<benjaminh-13>
the SoC's top level, Litex seems to change the name of the JTAG ports to some other name, which thus causes an error during synthesis.
<benjaminh-13>
Therefore, I was wondering where in the Litex flow (and in its code base) are ports from a module retrieved ? I think figuring out how does Litex recover the port name of an instance would help me save this issue.
<benjaminh-13>
Thanks,
cr1901 has quit [Read error: Connection reset by peer]
benjaminh-13 has quit [Quit: Client closed]
benjaminh-13 has joined #litex
cr1901 has joined #litex
so-offish has joined #litex
so-offish has quit [Remote host closed the connection]