Tools/SCViewer
Tools
/
SCViewer
10
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
393 Commits 7 Branches 69 Tags 240 MiB
F* 90.1%
Java 5.4%
C 4.4%
Go to file
Eyck Jentzsch 8700e2fdde Improve loading performance 2021-01-08 15:05:24 +01:00
.settings update feature definition 2020-06-21 12:23:34 +02:00
com.minres.scviewer.target cleanup build 2021-01-03 17:44:52 +01:00
features fix track and relation handling 2021-01-04 17:39:11 +01:00
p2repositories/com.minres.scviewer.updateSite update version numbers 2020-11-29 09:52:20 +01:00
plugins Improve loading performance 2021-01-08 15:05:24 +01:00
products update version numbers 2020-11-27 09:34:12 +01:00
tests/com.minres.scviewer.database.test fix track and relation handling 2021-01-04 17:39:11 +01:00
.gitignore re-arrange directory structure 2020-10-04 18:30:18 +02:00
.project update feature definition 2020-06-21 12:23:34 +02: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 re-arrange directory structure 2020-10-04 18:30:18 +02: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