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

Investigate VPD, FSDB Support #769

Open
harrisonliew opened this issue Jun 16, 2022 · 3 comments
Open

Investigate VPD, FSDB Support #769

harrisonliew opened this issue Jun 16, 2022 · 3 comments
Assignees
Labels
bug Cadence Specific to a Cadence tool help wanted high priority No workaround exists, many people blocked, chip-breaking issues

Comments

@harrisonliew
Copy link
Contributor

  1. From ASAP7 tutorial power-par error chipyard#1173, it looks like Voltus 21.12 is unable to read VPDs written by VCS S-2021.09 (throws syntax error). Converting the waveform to VCD works instead.
  2. From previous tests, Voltus' FSDB reader was a few releases behind the equivalent VCS release, causing version compatibility issues.

This likely affects other Cadence tools that can read activity files (Joules, Tempus, etc.).

TASK: find out compatibility matrix + potential workarounds (e.g. hard dependency on Xcelium, older VCS versions).

@harrisonliew harrisonliew added high priority No workaround exists, many people blocked, chip-breaking issues help wanted bug labels Jun 16, 2022
@harrisonliew
Copy link
Contributor Author

Cadence FSDB compatibility findings: from documentation of Verdi <-> FSDB versions, it appears that Cadence uses an FSDB version that is approx. 2 years older.

To check this: HammerTool needs to implement has_setting so that we can check against sim.vcs.version if the waveform file is detected as an fsdb.

@dpgrubb13
Copy link
Contributor

To clarify, the Verdi version and Cadence tool version seems to generally match the same year. However, the correct vcs version must be used (ie. a vcs version from the same year as the Cadence tool).

@dpgrubb13
Copy link
Contributor

Also to follow up, it appears that the available Cadence tools don't use above FSDB version 5.8 as of now.

@harrisonliew harrisonliew transferred this issue from ucb-bar/hammer-cadence-plugins Mar 16, 2023
@harrisonliew harrisonliew added the Cadence Specific to a Cadence tool label Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Cadence Specific to a Cadence tool help wanted high priority No workaround exists, many people blocked, chip-breaking issues
Projects
None yet
Development

No branches or pull requests

2 participants