Embedded Peripherals IP User Guide

ID 683130
Date 10/24/2025
Public
Document Table of Contents
1. Introduction 2. Avalon® -ST Serial Peripheral Interface Core 3. SPI Core 4. SPI Agent/JTAG to Avalon® Host Bridge Cores 5. Intel eSPI Agent Core 6. eSPI to LPC Bridge Core 7. Ethernet MDIO Core 8. Intel FPGA 16550 Compatible UART Core 9. UART Core 10. Lightweight UART Core 11. JTAG UART Core 12. Intel FPGA Avalon® Mailbox Core 13. Intel FPGA Avalon® Mutex Core 14. Intel FPGA Avalon® I2C (Host) Core 15. Intel FPGA I2C Agent to Avalon® -MM Host Bridge Core 16. EPCS/EPCQA Serial Flash Controller Core 17. Intel FPGA Serial Flash Controller Core 18. Intel FPGA Serial Flash Controller II Core 19. Intel FPGA Generic QUAD SPI Controller Core 20. Intel FPGA Generic QUAD SPI Controller II Core 21. Interval Timer Core 22. Intel FPGA Avalon FIFO Memory Core 23. On-Chip Memory (RAM and ROM) Intel FPGA IP 24. On-Chip Memory II (RAM or ROM) Intel FPGA IP 25. PIO Core 26. PLL Cores 27. DMA Controller Core 28. Modular Scatter-Gather DMA Core 29. Scatter-Gather DMA Controller Core 30. Video Sync Generator and Pixel Converter Cores 31. Intel FPGA Interrupt Latency Counter Core 32. Performance Counter Unit Core 33. Vectored Interrupt Controller Core 34. System ID Peripheral Core 35. Intel FPGA GMII to RGMII Converter Core 36. HPS GMII to RGMII Adapter IP 37. Intel FPGA MII to RMII Converter Core 38. HPS GMII to TSE 1000BASE-X/SGMII PCS Bridge Core IP 39. Intel FPGA HPS EMAC to Multi-rate PHY GMII Adapter Core 40. Intel FPGA MSI to GIC Generator Core 41. Cache Coherency Translator IP 42. Altera ACE5-Lite Cache Coherency Translator

29.3.3. Error Conditions

The SG-DMA core has a configurable error width. Error signals are connected directly to the Avalon® -ST source or sink to which the SG-DMA core is connected.

The list below describes how the error signals in the SG-DMA core are implemented in the following configurations:

  • Memory-to-memory configuration

    No error signals are generated. The error field in the register and descriptor is hardcoded to 0.

  • Memory-to-stream configuration

    If you specified the usage of error bits in the core, the error bits are generated in the Avalon® -ST source interface. These error bits are hardcoded to 0 and generated in compliance with the Avalon® -ST agent interfaces.

  • Stream-to-memory configuration

    If you specified the usage of error bits in the core, error bits are generated in the Avalon® -ST sink interface. These error bits are passed from the Avalon® -ST sink interface and stored in the registers and descriptor.

    The table below lists the error signals when the core is operating in the memory-to-stream configuration and connected to the transmit FIFO interface of the Intel FPGA Triple-Speed Ethernet IP core.

    Table 461.   Avalon® -ST Transmit Error Types
    Signal Type Description
    TSE_transmit_error[0] Transmit Frame Error. Asserted to indicate that the transmitted frame should be viewed as invalid by the Ethernet MAC. The frame is then transferred onto the GMII interface with an error code during the frame transfer.

    The table below lists the error signals when the core is operating in the stream-to-memory configuration and connected to the transmit FIFO interface of the Triple-Speed Ethernet IP Core.

    Table 462.   Avalon® -ST Receive Error Types
    Signal Type Description
    TSE_receive_error[0] Receive Frame Error. This signal indicates that an error has occurred. It is the logical OR of receive errors 1 through 5.
    TSE_receive_error[1] Invalid Length Error. Asserted when the received frame has an invalid length as defined by the IEEE 802.3 standard.
    TSE_receive_error[2] CRC Error. Asserted when the frame has been received with a CRC-32 error.
    TSE_receive_error[3] Receive Frame Truncated. Asserted when the received frame has been truncated due to receive FIFO overflow.
    TSE_receive_error[4] Received Frame corrupted due to PHY error. (The PHY has asserted an error on the receive GMII interface.)
    TSE_receive_error[5] Collision Error. Asserted when the frame was received with a collision.

    Each streaming core has a different set of error codes. Refer to the respective user guides for the codes.