lowRISC / lowRISC/opentitan

[DV] No source code shown when opening fsdb generated by Xcelium

Open
#12,995 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component:DV Earlgrey-PROD Triaged Priority:P3 Tool:dvsim
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

When we open fsdb generated by Xcelium, there is no source code shown in Verdi.
We could use verdi -f filelist to load source code, but the waves and source code don't link correctly.

Contacted AE for this issue. Here is the answer.

Unlike with VCS where you use VCS compiler to generate Verdi kdb database, you will have to explicitly compile for Verdi when using 3rd party simulators.
You will need to recreate the simulator compile commands for Verdi, and pass the same options. The goal here is to have 0 errors when loading into Verdi. With VCS the unified front end takes care of this automatically.

In order to solve this issue, here are the items we need to complete

  1. need to involve verdi to load filelist correctly - go to need to default/sim-vcs and load filelist -f *scr
  2. clean up all the Verdi errors
  • provide all the Xcelium compile options for Verdi. We can use command vericom to identify and map verdi options to Xcelium command line options.
  • set required env variables used in compile options.
  1. enable this support in dvsim

cc: @sriyerg

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in default/sim-vcs and inspect how the filelist is loaded with -f *scr. Recreate the Xcelium compile options for Verdi using vericom, set the required environment variables, and clean up Verdi errors; done means waves and source code link correctly and the support is enabled in dvsim.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.