Debug and Compare Waveforms Expanded from Multiple Essential Signal Dump (ESD) FSDB Files
Sometimes it is desirable to debug and compare waveforms expanded from multiple Essential Signal Dump (ESD) FSDB files using one or more nWave windows and the expectation is that the debug functionality available for multiple full dump FSDB files (e.g. easily drag and drop to any nWave window) would also be available for multiple ESD FSDB files.
Starting in 2009.01, the SilotiTM Visibility Automation System will support multiple Data Expansion contexts in a single session with each context associated with one Essential Signal Dump FSDB file. The Siloti system will operate as if the ESD FSDB files were full dump FSDB files and signals can be added to any nWave window without first changing the primary window. When the active FSDB file changes, the Data Expansion context will smoothly switch from the one associated with the old FSDB to the one associated with the new FSDB.
To enable support for expanding multiple FSDB files, set the following environment variable to 1 before invoking the Siloti system:
% setenv DE_MULTI_FSDB 1
Then, when a runtime signal is added into an nWave window, the signal will be expanded based on the FSDB file associated with that window (or the active FSDB file). Signals in non-nWave windows (e.g. nTrace, nSchema, TFV, etc.) are always associated with the primary FSDB. Values shown in the nTrace window (and other applications except nWave) will be expanded from the primary FSDB and when the primary FSDB changes, the values are updated.
The initial Data Expansion (DE) setup is always associated with the primary FSDB (from the nTrace DE setup or the command line options). When the multiple FSDB support is enabled option (via environment variable initially), the DE setup for the non-primary FSDB files will be triggered automatically whenever the FSDB files are needed for Data Expansion. For example, when the first runtime signal is dragged and dropped into a secondary nWave window, DE setup for the FSDB file associated with that nWave window will be performed and the DE setup progress bar will be displayed.
When Data Expansion for the primary FSDB is manually re-setup from the GUI or TCL, all existing DE contexts may need to perform DE setup again due to possible DE option changes. Values and waveforms shown on all windows need to be refreshed. Similarly, reloading the design or re-doing Behavior Analysis will trigger all existing DE contexts to re-do DE setup. When DE is disabled by pushing the [E] button, all DE contexts will be disabled. When DE is enabled again, all disabled DE contexts will be enabled as well. Closing the design will delete all existing DE contexts. Re-loading the FSDB file only requires the DE context associated with the reloaded FSDB to do DE setup again. Closing the FSDB file will remove the associated DE context.
See the detailed steps below for an example:
1. Load the design and first ESD FSDB file, execute Behavior Analysis and enable Data Expansion and Verdi for debug, e.g.
%> siloti -f run.f -ssf ess1.fsdb -ba -ba_mode msba -de -verdi -sigexp
2. Add some signals to the nWave window via drag and drop from nTrace or the Get Signals window.
3. Click the New Waveform icon on the nTrace tool bar to open a second nWave window.
4. In the second (non-primary) nWave window, invoke File > Open to load the second ESD FSDB file.
NOTE: The subsequent Essential Dump FSDB files need to be generated from the same design and the same simulation executables. The only difference should be the options used for the simulation executable or the test stimulus.
NOTE: Instead of loading the second ESD FSDB file in a new nWave window, it can be loaded in the same nWave window.
5. Add the same signals to the second nWave window through drag and drop. DE will be setup again.
6. To change the source for Active Annotation in other windows (e.g. nTrace), invoke Window > Change to Primary in the second (non-primary) nWave window to make it the primary window. In the lower right corner of the nWave window you'll see a red square indicating this is the primary window.
NOTE: If both ESD FSDB files are loaded in the same nWave window, you need to invoke File > Set Active command in nWave and then select the desired file and enable the Apply to Active Annotation option. DE will be setup again and signals can be added to the active file. You would invoke the Set Active command whenever you wanted to change the active file.
With this new capability you can easily debug multiple Essential Signal Dump FSDB files in the same Siloti session as if they were full dump FSDB files. You can also perform a waveform comparison on the expanded data.
Contact your local sales and support team with any questions regarding DE with multiple ESD FSDB files.
Read more about SpringSoft's Verification Enhancement Solutions
