You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
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
The text was updated successfully, but these errors were encountered: