3197 - LatticeECP3: Why some interrupts do not reach from PCIe core to CPU, while giving 1 ms interrupt signal to “inta_n” of PCIe core, and then monitoring interrupts at CPU side? 

Out of 1000 interrupts, approximately 300 reaches to CPU, when PCIe core’s interrupt assert and de-assert gap is 8 clock duration of wb_clk.

When the IP detects that inta_n is asserted low, it needs 8 clocks to create the ASSERT_INTA packet. In case of de-assertion, inta_n should not be de-asserted immediately following the 8 cycle.

Rather, user logic should detect whether the interrupt has been serviced before de-asserting the interrupt.

Also, status of the MSI interrupts, when using inta_n (legacy) interrupt, these interrupts should be disabled.

Related Articles
3515 - PCIe of LatticeECP3: How many MSI (Message Signaled Interrupt) interrupts can be implemented using Lattice PCIe (Peripheral Component Interconnect Express) Endpoint IP core?
The Peripheral Component Interconnect Express (PCIe) endpoint IP we have currently can support only up to 8 Message Interconnect Express (MSI) interrupts. This number of MSI interrupts available for the user can be checked in 'Multiple Message ...
7193 - PCIe for Nexus FPGAs: How to generate MSI Interrupts with PCIe x1 IP core?
Solution: To successfully use the MSI Interrupt, the user needs to perform the workaround below. Uncheck the box for "Disable Legacy Interrupt" to enable the Legacy Interrupt. This is a controller code requirement. 'MSI pending bit' = 1 alone does ...
1792 - [LatticeECP3]: Can I connect both the "mem_rst_n" and "rst_n" signals in the Lattice DDR3 IP core together to a system reset to meet the JEDEC initialization requirement?
The "rsn_n" signal resets both the DDR3 memory controller and the DDR3 memory devices while the "mem_rst_n" signal resets only the DDR3 memory devices. The JEDEC specification has two different cases of reset initialization. Power-up reset ...
4012 - [Lattice ECP3] PCI Express Endpoint Core IP: How does the Lattice PCIe (Peripheral Component Interconnect Express) IP core issue multiple MSI (Message Signaled Interrupts) when multiple MSI request bits are set in the end application?
Description: The Lattice PCIe (Peripheral Component Interconnect Express) IP (Intellectual Property) core asserts all MSI one after the other. The Lattice PCIe (Peripheral Component Interconnect Express) IP (Intellectual Property) can handle up to 8 ...
1102 - All FPGAs: Does Lattice PCIe IP support SERDES pins polarity inversion and PCIe lanes reversal?
Description: The PCIe specification provides a dedicated layout of the PCIe lanes on the connector. Due to the fixed location of the SERDES pins on Lattice device packages aligning package pins to PCIe lanes can either work perfectly or create a ...

3197 - LatticeECP3: Why some interrupts do not reach from PCIe core to CPU, while giving 1 ms interrupt signal to “inta_n” of PCIe core, and then&nbsp;monitoring interrupts at CPU side?&nbsp;

3197 - LatticeECP3: Why some interrupts do not reach from PCIe core to CPU, while giving 1 ms interrupt signal to “inta_n” of PCIe core, and then&nbsp;monitoring interrupts at CPU side?&nbsp;

Related Articles

3515 - PCIe of LatticeECP3: How many MSI (Message Signaled Interrupt) interrupts can be implemented using Lattice PCIe (Peripheral Component Interconnect Express) Endpoint IP core?

7193 - PCIe for Nexus FPGAs: How to generate MSI Interrupts with PCIe x1 IP core?

1792 - [LatticeECP3]: Can&nbsp;I&nbsp;connect both&nbsp;the "mem_rst_n" and&nbsp;"rst_n" signals in the Lattice DDR3 IP core together&nbsp;to&nbsp;a&nbsp;system reset to meet the JEDEC&nbsp;initialization requirement?

4012 - [Lattice ECP3] PCI Express Endpoint Core IP: How does the Lattice PCIe (Peripheral Component Interconnect Express) IP core issue multiple MSI (Message Signaled Interrupts) when multiple MSI request bits are set in the end application?

1102 - All FPGAs: Does Lattice PCIe IP support SERDES pins polarity inversion and PCIe lanes reversal?

3197 - LatticeECP3: Why some interrupts do not reach from PCIe core to CPU, while giving 1 ms interrupt signal to “inta_n” of PCIe core, and then monitoring interrupts at CPU side?

3197 - LatticeECP3: Why some interrupts do not reach from PCIe core to CPU, while giving 1 ms interrupt signal to “inta_n” of PCIe core, and then monitoring interrupts at CPU side?

1792 - [LatticeECP3]: Can I connect both the "mem_rst_n" and "rst_n" signals in the Lattice DDR3 IP core together to a system reset to meet the JEDEC initialization requirement?