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

repacker changes internal feedback path to external feedback #1671

Open
rs-dhow opened this issue May 16, 2024 · 0 comments
Open

repacker changes internal feedback path to external feedback #1671

rs-dhow opened this issue May 16, 2024 · 0 comments

Comments

@rs-dhow
Copy link

rs-dhow commented May 16, 2024

The .net file may specify an "internal feedback" path in a CLB. This means an FLE output has been selected in a "mux" or "complete" construct all inside one block.

That FLE output also drives an OPIN. That OPIN may then connect through 1 or more SBs and then a CB to an IPIN on the same block.

In this case, the OpenFPGA repacker may alter the "mux" or "complete" to select the IPIN instead of the internal feedback.

This makes the path slower (due to the extra SB(s) and CB now in it). The original timing report may no longer apply.

Any of these would be preferable:

  1. Never do this.
  2. Have an option to follow .net exactly.
  3. Write out a new .net to show what OpenFPGA did.

Due to the effect on timing, (3) is not really adequate in this case.

This observed strange behavior seems to imply that OpenFPGA repacking decisions are not costed, i.e., satisfaction of the constraints is the only goal. The result still works; it may have its timing significantly changed.

Thanks.

To Reproduce
Steps to reproduce the behavior:

  1. Clone OpenFPGA repository and checkout commit id:
  2. Execute OpenFPGA task or your own example:
  3. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Enviornment (please complete the following information):

  • OS:
  • Compiler:
  • Version:

Additional context
Add any other context about the problem here.

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

No branches or pull requests

1 participant