new beta version released. Beta 0.963

41 views
Skip to first unread message

dan_fabrizio

unread,
Jun 27, 2013, 8:45:13 PM6/27/13
to timinga...@googlegroups.com


This is mostly a bug fix release except for one new feature that in the initial stages.   VCD AnalogSignals can be displayed and are converted to a timing diagram AnalogSignal.  This happens automatically when opening a VCD file as before.  See list of fixes and changes below for a little more info.

   

  • Fixed Edge fall time – Signals were using one value for rise and fall times.
  • Fixed Locale settings to english and US. This should override any settings made by the JVM. This Locale is displayed if started from the command line.

  • Added VCD Analog Signals. Try sine_waves.vcd in example dir. VCD files get converted automatically to timing diagrams so this is the start of AnalogSignal for timing diagrams. 

    More capabilities will be added in future versions. Recommendations and suggestions welcome from users. Looking for VCD file examples from users to help test this feature.

  • Started the clean-up of the examples directory. There where many examples from previous versions of the TimingAnalyzer that were not working.

    • cnstrnt_err.tim
    • cram_read.tim
    • pci_bus_master_mem_read.tim
    • pci_bus_master_mem_write.tim
    • pci_io_read.tim
    • pci_io_write.tim
    • sine_waves.vcd

Ed Carstens

unread,
May 27, 2015, 1:56:58 PM5/27/15
to timinga...@googlegroups.com
The VCD converter is a great idea. I tried it, though, and had a few problems. The signal names include the entire scope so they are quite long. Also, I had dumped a VCD from simvision with a small time interval, but when it got converted to TA it still showed time starting at zero. I wasn't able to zoom in to that time window and the timestamps seemed to be incorrect.

-Ed Carstens

Ed Carstens

unread,
May 27, 2015, 2:39:40 PM5/27/15
to timinga...@googlegroups.com
Found what looks to be a bug. The final time in my VCD file was 355.510ns or 355510ps. The .tim file had End_Time set to 355510. I changed it to 355.510 and it now shows the correct window of time. I noticed Time_Scale = 1.0E-12 and Time_Per_Division is 27. If the scale is in ps, the End_time is correct and it is the Time_Per_Division that must be fixed.

Dan Fabrizio

unread,
May 27, 2015, 8:15:33 PM5/27/15
to timinga...@googlegroups.com
Hi Ed,

Can you send me the vcd file?  

Thanks, Dan

--
You received this message because you are subscribed to the Google Groups "TimingAnalyzer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to timinganalyze...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Dan Fabrizio
The TimingAnalyzer
www.timing-diagrams.com

Reply all
Reply to author
Forward
0 new messages