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

about the full_o of IDcounter #238

Open
hdu-lpl opened this issue Jun 30, 2022 · 1 comment
Open

about the full_o of IDcounter #238

hdu-lpl opened this issue Jun 30, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@hdu-lpl
Copy link

hdu-lpl commented Jun 30, 2022

Regarding the full_o of IDcounter, why is full_o set to 1 when the count value of any ID is full, and the counter no longer counts,what is the reason for this?

@andreaskurth
Copy link
Contributor

Thanks for your question, @hdu-lpl.

Your observation is correct: axi_demux_id_counters currently indicates itself as full when the count value for any ID has reached the maximum. This is because there is no input to "ask" axi_demux_id_counters which ID would be relevant for determining the full state.

The counter can be increased on both the push_ and the inject_ inputs; one option would be to have a full output associated with each of them.

@andreaskurth andreaskurth added the enhancement New feature or request label Jul 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants