Closed michael-etzkorn closed 3 years ago
This actually had to do with my misunderstanding of what the wrangler should be. If I add an overlay for a new system clock, create a new clock group and wrangler, and hook up to a 250Mhz clock sink node, I see activity on the board.
It's possible I set this up wrong. I've removed the MSI interrupts from the overlay. I'm using Chipyard's generator to generate my harness. I've placed the overlay which I've customized a little bit. The only "custom" part is that the overlayoutput doesn't return the interrupt node.
I've added two mmio ports and a slave port to the rocket chip system. I'm using Chipyard's SD bootrom. I don't see any activity on the bootrom when I hook up the overlay.
Here's my harness:
And here's my config:
Compilation seems fine. The .graphml shows all the connections are being made between the system and ports. The ports corresponding outer master/slave seem to connect fine to the XDMA overlay. Yet the core fails to show any activity it normally does through the bootrom UART print statements and there seems to be no activity on the PCIe edge when analyzed with a protocol analyzer. I've used the default XDMA configuration that configures it as a root port and tried configuring it as an endpoint instead. The result seems to be the same. I can try using an ILA to analyze the state of the fpga further. I can try isolating the issue by testing this separately from the chipyard system.