Forum Discussion
New ContributorExported MSI conduit on A10 PCIe AVMM IP is non-functional
KhaiY,
I'm sorry, due to ITAR, IP and other matters, this design cannot be shared. Although it's easy enough to put together your own simple design. The fact is, the MSI conduit interface simulates properly in version 18.1, it's the actual hardware that don't work. Another interesting fact is that in earlier versions of Quartus the MSI conduit simulation did not work, which back then, when you could, I pulled a Altera ticket. So I'm not surprised to see the hardware non-functional.
New ContributorKhaiY,
I'm sorry, due to ITAR, IP and other matters, this design cannot be shared. Although it's easy enough to put together your own simple design. The fact is, the MSI conduit interface simulates properly in version 18.1, it's the actual hardware that don't work. Another interesting fact is that in earlier versions of Quartus the MSI conduit simulation did not work, which back then, when you could, I pulled a Altera ticket. So I'm not surprised to see the hardware non-functional.
New ContributorKhaiY,
I disconnected the MSI conduit conduit from my interrupt handler and made another build, but still monitored it using signal tap. This time the conduit worked and took on the values of the MSI configuration registers after enumeration. I then modified my interrupt handler by adding additional input registers to isolate the conduit interface and made another build. Once again, the MSI conduit worked! With all these builds and testing, I never regenerated the Qsys block, only my application code of the interrupt handler. I can only hope this conduit interface sticks on future builds.
