We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome,
Internet Explorer 11,
Safari. Thank you!
AR# 42860: 13.2 EDK, AXI_Ethernet v3.00.a - Known Issues with v3.00.a of the core released with EDK 13.2
13.2 EDK, AXI_Ethernet v3.00.a - Known Issues with v3.00.a of the core released with EDK 13.2
The patch linked to in this Answer Record addresses the following issues:
CR 614581 - When using a system with the soft TEMAC and 1000 Base-X PHY interface, auto-negotiation fails and the interface does not work. This issue affects only Spartan-6 and Virtex-6 families since only these devices support this interface in this release.
CR 614668 - When using a system with the soft TEMAC and a minimum inter-frame gap between messages, occasionally the RX logic calculates an RX frame byte count that is one less than it should be. This value is sent across RX AXI Stream status bus usually to the AXI_DMA in most implementations. If the axi_dma is using this value to determine how many bytes are coming across the AXIStream data bus (C_SG_USE_STSAPP_LENGTH = 1), it generates an error condition and interrupt (DMAIntErr in the S2MM_DMASR Register) and halts. If the axi_dma is calculating its own byte count instead of using the value coming across the AXIStream status bus (C_SG_USE_STSAPP_LENGTH = 0), no error, interrupt, or halt occurs and the DMA calculated correct byte count gets stored in the DMA buffer descriptor instead of the incorrect one from the axi_ethernet; this is a potential work-around. The fix affects one file in the axi_ethernet_v3_00_a core and this file is not encrypted.
CR 615071 -There is a TX AVB issue that affects soft TEMAC and Virtex-6 hard TEMAC implementations and all device families and PHY interfaces. This is an issue when AVB is enabled, and it can occur often if certain internal design conditions are met. When it fails, AXI Ethernet continually transmits the same byte of data.
A tactical patch has been created to address the issues described above: