This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS570LS3137: HET IDE VCD Stimuli Signal identifiers

Part Number: TMS570LS3137

I can not find a reference for the signal identifiers to use when creating systemc input stimuli.

I know from the tutorial7 that  'aaa' is the signal identifier for the first HET data for example.

Can you point me to a TI document where I can get those identifiers?

PD: I have tried spnu485c, spnu483a, TMS570 Reference manual

  • Appendix A, Table 1 of SPNU483A, right most column has the names if you manually create them.
    I would try creating it this way:
    - first draw one of your input signals in Synapticad like the tutorials show
    (in synapticad you definitely use the name in the table...)
    - save your stimulus as a VCD
    - simulate to make sure it's working as expected.

    Then you can look at this VCD as a reference to get the names right plus all the other VCD structure stuff...

    I think you are getting confused by looking at a VCD file which has something like this:

    $scope module SystemC $end
    $var wire 1 aaa HETCLK $end
    $var wire 1 aab LOOP_RESOLUTION_CLK $end
    $var wire 1 aac HIGH_RESOLUTION_CLK $end
    $var wire 32 aad A [31:0] $end
    ...
    $upscope $end

    $dumpvars
    1aaa
    0aab
    1aac
    b0 aad
    b0 aae
    b0 aaf

    So you need to interpret like this: aaa is abbreviation in THIS VCD OUTPUT for HETCLK and that's defined by:
    $var wire 1 aaa HETCLK $end

    The line:
    $scope module SystemC $end

    Is not a set of column headers for $var, $wire, 1 aaa ...

    It's more of a :

    module SystemC
    wire HETCLK;
    wire LOOP_RESOLUTION_CLK;
    endmodule

    type structure that is represented by this.

    Might be worth finding a reference for the VCD file format if you want to manually create the VCD file...

    But again Synapticad knows how to hook it up and some of what you see in naming has to do with the (invisible) underlying system C model that instantiates HET in a wrapper for Syncad so it's not really obvious what name to put when you manually make the VCD.

    I can confirm 100% though that the names in Appendix A Table 1 right most column will work if you create them as a signal in Synapticad as the tutorial shows for drawing your stimulus - and then saving that as a VCD will show you if any prefixes are added/removed when going to VCD.
  • I had already tried what you suggest and saddly it did not work.

    Finally I figured it out but there are several inconsistencies in the documentation.
    I am refering to this materials:
    Tutorial example HET IDE\03.05.01\Tutorials\tut7_input_vcd
    Literature Number: SPNU485C -- May 2010–Revised August 2016
    Literature Number: SPNU483A -- November 2011

    The table you refer is for WATCH signals not for DRIVE signals.

    The same document section 8.1.2 (SPNU485c) the correct reference is hetm.drive_0.in, but then again, in the example SystemC code the names are synapticad_port_0.out.
    The name synapticad_port_0.out I can confirm that does not work.
    The tutorial has the exact same names, which again, does not work.

    The tutorial PDF has a screen shot of the stimuli in WaveViewer where the names are hetm.drive_0.in (same as the text, not the example of section 8.1.2).


    Only when I used this port/signals declaration it finally worked.

    $scope module hetm.drive_1 $end
    $var wire 1 aaa in $end
    $upscope $end
    $upscope $end
    $enddefinitions $end
  • Thanks - great job figuring that out and tying it all together.  

    So I think you found two documentation issues for us both with the Nov 2011 User's Guide.

    It looks like that guide is a little out of date and not matching the 2016 release of the HET IDE

  • I am giving you trouble because I'm in the course of developing a SIL3 application with a TMS570 and I need to develop automated testing which involves Test Vector generation. I need complete documentation to justify my testing/design decisions, I can fill in the gaps (which I have already). It would be great if this thread can be of any help to somebody else in the future (in a similar situation).

    Maybe I don't have the latest document, but I have only been able to find SPNU483 RevA (2011).

    Regards,

    Santiago Rodriguez
    Modutram Mexico