Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make LiteEthMACCore clock domain crossing TX/RX fifo depths configurable #80

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rprinz08
Copy link
Contributor

Commit 72dd7bf reduced buffering from 64 to 32 which affects a design. So make it configurable to be flexible.

@enjoy-digital
Copy link
Owner

Thanks @rprinz08, can you provide more information on the affected design? (especially the sys_clk_freq of the SoC and speed of the Ethernet Link)

@rprinz08
Copy link
Contributor Author

The design runs with sys_clk_freq=100MHz and uses a LiteEthPHYRMII with external 50MHz clock and a LiteEthMACCore. Interface runs at 100Mbit full duplex. With reduced CDC depth, no last signal is issued by LiteEthMACCore source when a network packet was completely received.

@enjoy-digital
Copy link
Owner

@rprinz08 Thanks for the info. Rather than exposing the FIFO depths, I would like to understand the real cause of the issue but it seems design similar to yours are working correctly (ex the Digilent Arty has a very similar config: 100MHz sys_clk_freq, RMII PHY, 100Mbit full duplex). Could you provide a way to observe the issue so that I investigate on the Digilent Arty? Thanks.

@rprinz08
Copy link
Contributor Author

Thx for the answer. I will create an example design sohwing the problem (in the next weeks). It actually happens when capturing longer (>1000 bytes) packets into a memory for further processing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants