Tools/SCViewer
Tools
/
SCViewer
10
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
475 Commits 7 Branches 69 Tags 240 MiB
F* 90.1%
Java 5.4%
C 4.4%
Go to file
Eyck Jentzsch 78faab404c apply UI fixes 
* wrong arrow target of transaction
* wrong zomm factor calculation for zoom fit
* streams and waveforms not visible if at root level
 		2021-03-25 20:18:50 +00:00
.launch add maven launch configs 2021-01-10 13:16:28 +01:00
features update version numbers 2021-02-27 19:13:28 +00:00
plugins apply UI fixes 2021-03-25 20:18:50 +00:00
products/com.minres.scviewer.e4.product update version numbers 2021-02-27 19:13:17 +00:00
releng update version numbers 2021-02-27 19:13:17 +00:00
tests/com.minres.scviewer.database.test apply UI fixes 2021-03-25 20:18:50 +00:00
.gitignore fix display bug 2021-02-17 20:24:25 +00:00
.project add maven launch configs 2021-01-10 13:16:28 +01:00
LICENSE Create LICENSE 2016-10-20 07:08:35 +02:00
README.md Updated documentation 2018-11-06 12:07:23 +01:00
pom.xml update version numbers 2021-02-27 19:13:17 +00:00
signal.xcf Initial version of E4 based SC Viewer application 2015-10-22 00:05:29 +02:00

README.md

SCViewer

SCViewer is composed of a set of eclipse plugins to display VCD and transaction streams created by the SystemC VCD trace implementation and the SystemC Verification Library (SCV). For further description of the SCV please refer to http://www.accellera.org/activities/committees/systemc-verification.

If you encounter issue when running on Linux please try running as SWT_GTK3=0 scviewer as there exist issues wiht GTK3.

The viewer has the following features

  • support of VCD files (compressed and uncompressed)
  • real numbers
  • showing vectors and real numbers as analog (step-wise & continuous)
  • various value representations of bit vectors
  • support of SCV transaction recordings in various formats
  • text log files (compressed and uncompressed)
  • sqlite based
  • visualization of transaction relations

To build the plugins the Eclipse SDK or PDE can be used. In both cases the Groovy eclipse plugin (http://groovy.codehaus.org/Eclipse+Plugin or Market) has to be installed.

TODO

  • add more tests
  • move to feature based product to allow automatic updates
  • improve graphics
  • catch-up e3 plugin to functionality of e4 product
  • add calculated traces