• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 721 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

HET IDE Simulator not recognizing VCD input

Aaron Law
Prodigy 40 points


I've been trying to get the HET IDE to use an input VCD as a stimuli input, and so far have not been able to get HET IDE to recognize the input.  I did not receive a license for WaveFormer Pro, so the VCD input should not be ignored.

 

I couldn't even get the VCD input tutorial to work.  I specified the input VCD file, assembled and loaded the program, ran the program, and WaveViewer Free did not recognize the drive signals (they weren't in the hidden signals).

 

I'm running HET IDE 3.3 on Windows 7.  I've set HET IDE and WaveViewer to run in compatibility mode with Windows XP SP3, and have tried multiple input VCD files, and multiple devices.  When the VCD files are opened with WaveViewer on their own the waveforms show up, but they are not recognized by HET IDE. 

 

Thanks,

Aaron

 

 

  • 0
    TI__Guru 59540 points
    Hi Aaron,

    I have forwarded your post to our HET IDE expert. They should get back with you shortly.

    In the meantime, can you have a look at this thread and see if the update file posted there are able to solve your problem?

    e2e.ti.com/.../316332
  • 0 in reply to Chuck Davenport
    Prodigy 40 points
    I have indeed tried that. It didn't alleviate the problem for me. I don't think it's a problem connecting to the simulator.
  • 0 in reply to Aaron Law
    TI__Guru 59540 points
    Hello Aaron,

    Can you send us one of the failing VCD files so we can try it on our end as well? The naming of signals within the files is very critical and can sometimes prevent loading so we would like to see what you have in order to eliminate this as a possibility.
  • 0 in reply to Chuck Davenport
    Prodigy 40 points

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/312/1781.tut2_5F00_input_5F00_vcd.7z

    This is the tutorial 2 code and VCD file archived in a .7z archive provided with the HET IDE.  None of the drive lines show up in WaveViewer after running the simulation, and are not in the hidden signals.

  • 0 in reply to Aaron Law
    TI__Guru 68930 points

    Thanks Aaron, I didn't try your exact files, but I tried the files installed in my HET IDE folder and MyDocuments\TexasInstruments folder following the instructions in the tutorial PDF file.  (The user's guide isn't step-by-step for this tutorial example).

    The tutorial worked fine for me.    Screenshot below to compare with what you are seeing.

    Could it be that you were expecting 0x1aaa or 0x0aaa to show up on the bus of 32- pins?

    That could be confusing - poor choice of signal identifier ;(.    The 'aaa' is actually the signal identifier for the first HET data pin:

    $scope module hetm $end
$scope module drive_0 $end
$var wire    1  aaa in       $end
$upscope $end

    So this line:

    #3500000
1aaa

    Means to drive a '1' onto hetm.drive_0.in  signal which happens to not exactly match the name that shows up in the waveformer.   That's why we thought it might be a naming problem - you always have to go to the docs to get the exact naming and it's not as intuitive as I'd have liked it to be.

    So given that - you can see in my screenshot that I am seeing the pin 0 toggle at 3.5us, 6us, 12us, just like the stimulus file shows - see how that pin goes from 0 to 1 then to 0 again?   Hopefully it's as simple as us not picking some obscure char for the signal identifier like a $ or a # as you normally see in VCD files but if not let us know and we can continue to debug...

  • 0 in reply to Anthony F. Seely
    Prodigy 40 points

    Ah.  I was looking for the wrong names.  I was looking for hetm.drive_x.in, not hetm.watch_x.in.

     

    I think that answers all of the questions I have for the moment.  Thanks :)