yol / ethernet_mac Goto Github PK

There are quite a few Ethernet MAC cores, but mostly in Verilog. I've a project written in VHDL, use GHDL, and therefore looked for a core written in VHDL, and found this project.
The core was tested with a Spartan-6, thus with legacy ISE and uses the MII interface. One possible application would be with a Digilent Arty board (with Artix-7). Another application would be a different Artix-7 board with a LAN8720 based PHY attached via a Pmod. Such a Pmod, e.g. from Waveshare, offers an RMII interface.

Two questions:

• was this core ever tested with Vivado ?
• it it possible to adapt it for an RMII interface ?

I'm trying to compile the design using QuestaSim.

I'm getting an error when trying to compile tx_fifo.vhd
the error says: "# Error: ** Error: (vcom-11) Could not find work.ethernet_mac_tx_fifo_xilinx."

I cannot find any component in the project files named "ethernet_mac_tx_fifo_xilinx"
Is this missing ?

The system I am trying to implement is to send the data stored in the FPGA block RAM to the PC via ethernet at a data rate of 100Mbps. The evaluation board I'm using is ML605. I know that it is different from the board you used, but if you change only ucf it will work the same. (I feel very grateful to you.) However, it looks like your post does not have main.vhd. I need a main entitiy which consists of several components for Ethernet communication. I can not see the file. Can I get the file?

In addition, you have framed the pad, CRC, etc. directly, why did you use IP_CORE provided by xilinx without using it?

Thank you.

Sincerely,

I have Ubuntu 16.04, and have installed ghdl and its dependancies.
I ran the following command:
make prepare ISE_DIR=/opt/Xilinx/14.7/ISE_DS/ISE/
This works.

However trying make check gives several warnings of the form "port x of entity y is not bounded" and the following error:-

./ethernet_mac_tb --stack-max-size=20M --ieee-asserts=disable
make: ./ethernet_mac_tb: Command not found
Makefile:11: recipe for target 'check' failed
make: *** [check] Error 127