How chasep255/nexys-4-ddr-ethernet-mac works
This is an RMII Ethernet MAC IP core for the Nexys 4 DDR. User logic sends and receives packet bytes through native or AXI-stream interfaces; the core handles Ethernet framing and CRC, while SMI/MDIO provides PHY register access and link-status outputs. The README documents these capabilities but no source excerpts were supplied, so internal module connections are shown only as unverified dashed relationships. The simple board example is omitted as an example rather than a core subsystem.
Main entry points: eth_mac.v MAC core · eth_smi.v SMI / MDIO · eth_status.v Link status · eth_rx.v RX engine
Components 12
Packet interfaces
- MAC core
rtl/eth_mac.v - Native RX
rtl/eth_mac.v - Native TX
rtl/eth_mac.v - RX AXI adapter
rtl/rx_axis_adapter.v - TX AXI adapter
rtl/tx_axis_adapter.v
PHY control
- SMI / MDIO
rtl/eth_smi.v - Link status
rtl/eth_status.v
Other components
- User logic
- Ethernet PHY
Connections 15
- User logic → MAC core: sends packets
README.md - MAC core → User logic: delivers packets
README.md - MAC core → Ethernet PHY: RMII transmit/receive
README.md - MAC core → SMI / MDIO: provides register access
- SMI / MDIO → Ethernet PHY: reads/writes registers
README.md - User logic → Native RX: receives native bytes
README.md - User logic → Native TX: sends native bytes
README.md - RX AXI adapter → Native RX: adapts interface
README.md - TX AXI adapter → Native TX: adapts interface
README.md - RX engine → CRC32: checks frames
- TX engine → CRC32: generates CRC
- MAC core → RX engine: receives frames
- MAC core → TX engine: transmits frames
- Link status → SMI / MDIO: checks PHY status
- Link status → User logic: reports link state
README.md