Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

If you want to try out our example implementation of Interactive Timing Analysis, you can use this guide:

Steps for setup:

  1. Download KIELER with Interactive Timing Analysis here (Under construction: Link coming soon!).
  2. Get the experimental KTA timing analysis tool here. You can use the Download ZIP link.
  3. Make sure "ocaml" and "make" are installed on your system, so that you can compile the KTA timing analysis tool.
  4. Extract the zip folder you downloaded in Step 2 and compile the KTA timing analysis tool running make in the kta-master folder.
  5. Install the gcc MIPS compiler (mcb32tools, mipsel-mcb32-elf-gcc), which is used by the KTA timing analysis tool.
  6. Start up KIELER, go to Preferences -> Interactive Timing Analysis and enter the absolute paths in your system to the folder that
    contains the KTA tool binary or the gcc MIPS compiler, respectively (click image to enlarge):

 

How to use the Interactive Timing Analysis:

You can use this selection of example models to get you started: TimingTestFiles.

  1. Create a Project in your Project Explorer (right click -> New -> Project).
  2. Copy the files and folders contained in the TimingTestFiles folder into the Project.
  3. Make sure the folders that contain the .sct and .asu file of the models and the tpp.h file are on one level, like in the TimingTestFiles folder.
  4. Open any of the .sct files in the editor (right click the file). The Diagram view should open automatically and show you an image of the model. If that does not work, open that view by choosing Window -> Show View -> Other -> KIELER Lightweight Diagrams -> Diagram
  5. Choose your desired Timing Analysis Options in the Diagram Options bar (click image to enlarge):



    You can switch between percentage, cycles and milliseconds for the timing value display.
  6.  As a first step you can play around with the timing assumptions on function calls you find in the .asu files for the models (note that FunParc2 has no function calls, so choose something else). How do the values and the Hotspot Highlighting change?


 

If you encounter problems trying out the Interactive Timing Analysis, please contact Insa Fuhrmann: ima@informatik.uni-kiel.de

 

 

  • No labels