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
@mithro I'm afraid this is not sorting issue, but rather a bug in the tim2json script. It seems it does not handle correctly very complicated timings definitions as we have in e.g. GTPE2_CHANNEL.
By complicated I mean a timing which includes number of properties. I think the above timing should in fact be:
So from RXCHBONDI input to RXUSRCLK2 clock. with GEN_RXUSRCLK property set to true and RX_DATA_WIDTH set to 16
It looks like the script confused inputs with parameters
It looks like we are still not sorting everything in the SDF output which is causing diffs in the output, see the patch below;
Related #776 and #815.
The text was updated successfully, but these errors were encountered: