Header_mem overflow #195
Open
Header_mem overflow #195
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When udp_checksum_gen_64 is outputing a long packet, and enough 1-word packets are entering into this module, the last one is written into FIFO but it's header is never being written into the header_mem because it's full
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When udp_checksum_gen_64 is outputing a long packet (on m_udp_payload_axis_t...) , and enough 1-word packets are entering into this module (on s_udp_payload_axis_t...) so it fills up the header memory, the last short packet is written into FIFO but it's header is never being written into the header_mem because it's full.
Header_fifo_full (and so header_fifo_ready) is updated one cycle too late.