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

Magic bitstream #39

Open
guilhermerc opened this issue Oct 24, 2024 · 0 comments
Open

Magic bitstream #39

guilhermerc opened this issue Oct 24, 2024 · 0 comments

Comments

@guilhermerc
Copy link
Contributor

guilhermerc commented Oct 24, 2024

We've been facing undefined behavior with the latest commits' builds. These behaviors aren't deterministic: they only occur on some controllers. Some examples are:

  • Not being able to write the correction matrix;
  • Not being able to write the filters' coefficients;
  • Not being able to sync DCC network;
  • Some correctors having "pulsating" current readings.

The main hypothesis at the moment is a lack of timing constraints which is only revealed when the design becomes more congested.

There is a bitstream which is functionally identical to master (c86a1ea) and works well, but it was built with a local commit that doesn't belong to git history anymore. I've pushed its branch and I'm attaching the bitstream to this issue.

afcv4_ref_fofb_ctrl-2024-05-10-a46b56a4b4.zip

@guilhermerc guilhermerc pinned this issue Oct 24, 2024
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