SPNU633 January   2020 RM42L432 , RM44L520 , RM44L920 , RM46L430 , RM46L440 , RM46L450 , RM46L830 , RM46L840 , RM46L850 , RM46L852 , RM48L530 , RM48L540 , RM48L730 , RM48L740 , RM48L940 , RM48L950 , RM48L952 , RM57L843 , TMS570LC4357 , TMS570LC4357-EP , TMS570LC4357-SEP , TMS570LS0332 , TMS570LS0432 , TMS570LS0714 , TMS570LS0714-S , TMS570LS0914 , TMS570LS1114 , TMS570LS1115 , TMS570LS1224 , TMS570LS1225 , TMS570LS1227 , TMS570LS2124 , TMS570LS2125 , TMS570LS2134 , TMS570LS2135 , TMS570LS3134 , TMS570LS3135 , TMS570LS3137 , TMS570LS3137-EP

 

  1.   HALCoGen-CSP Without LDRA
    1.     Trademarks
    2. 1  Introduction
    3. 2  Software Requirements
    4. 3  HALCoGen TAU Tool Restrictions
    5. 4  HALCoGen CSP Contents
      1. 4.1 Below is a List of Items Supplied With the HALCoGen Compliance Support Package
    6. 5  Terminologies Used in HALCoGen TAU
      1. 5.1 What is Unit Testing?
      2. 5.2 What is Functional Testing?
      3. 5.3 What is a Test Sequence?
      4. 5.4 What is a Test Case File (TCF)?
      5. 5.5 What is Code Coverage?
      6. 5.6 What is a Regression Report?
    7. 6  Functional Blocks of HALCoGen TAU
    8. 7  HALCoGen TAU Test Flow
    9. 8  How to Use HALCoGen TAU? A Walkthrough
    10. 9  Inputs to HALCoGen TAU
      1. 9.1 HALCoGen Project Folder
      2. 9.2 HALCoGen Directory
      3. 9.3 Target Configuration File
      4. 9.4 Build Options File
    11. 10 How to Add Your Test Cases?
    12. 11 Reports
      1. 11.1 Regression Report
      2. 11.2 Dynamic Coverage Analysis Report
    13. 12 FAQ
      1. 12.1  Why Does the Application Show “Code Generation Failed"?
      2. 12.2  Why Does the TCF Generation Fail?
      3. 12.3  What are the Possible Reasons for Build Failure?
      4. 12.4  From Where Do I See the Instrumented Code?
      5. 12.5  Is the Source Code Backed Up Before LDRA Instruments the Code During TAU Execution?
      6. 12.6  How do I Include a Folder or a Library in my Project?
      7. 12.7  Is the Tool Compatible Only With HALCoGen v04.02.00? Can I Test a Project Generated With an Older Version?
      8. 12.8  Why are the Functional Tests Disabled by Default?
      9. 12.9  How Do I Know Which Functional Tests are Applicable for my Configuration?
      10. 12.10 Does the Tool Optimize the HALCoGen Code While Compiling?
      11. 12.11 It Says Test Execution Completed. But I Cannot Find the Report in the Reports Folder.
      12. 12.12 Test Execution Hung, What to Do? What is the Reason?
      13. 12.13 Can I Use HALCoGen TAU to Test Source File Other Than HALCoGen Generated Files?
      14. 12.14 I Have Full Version of LDRA Tool Suite Instead of LDRAUnit. Can I Use This Tool With This License?
      15. 12.15 How to Get LDRA Unit and Setting up the License After Downloading HALCoGen-CSP From TI?

8 How to Use HALCoGen TAU? A Walkthrough

  1. Create a HALCoGen project using HALCoGen (v04.02.00 or higher) (see Figure 4).
    2. HALCoGen_proj_spnu605.gifFigure 4. HALCoGen Project Selection
  2. Do the necessary configuration, save the project and close HALCoGen (see Figure 5).
    3. HALCoGen_module_spnu605.gifFigure 5. HALCoGen Module Configuration
  3. Open the HALCoGen TAU tool (see Figure 6).
    4. HALCoGen_TAU_GUI_open_spnu605.gifFigure 6. HALCoGenTAU GUI Open Page
  4. Browse the folder containing the HALCoGen project and click the Add Testcases button (see Figure 7).
    5. HALCoGen_proj_selec_ADD_testspnu605.gifFigure 7. HALCoGen Project Selection and Add Test Case

    Clicking the Add Testcases button adds a new folder Test in the selected HALCoGen Project folder. The test cases for the enabled modules are added to the folder.

  5. Browse for the HALCoGen directory, target configuration file and build options file (see Figure 8).

    6. Click here to know more about target configuration file and build options file. (Sample target configurations files and the build options file are provided in the <install_dir> \TargetConfiguration and <install_dir>\BuildOptions folders, respectively).

    target_build_option_spnu605.gifFigure 8. Target and Build Option Selection
  6. Select the tests to be run and click the Run button (see Figure 9).
    7. test_case_selec_run_spnu605.gifFigure 9. Test Case Selection and Run

    Once the build is successful and .out is created, the tool starts executing the test cases. The details of the test case execution is shown in a new pop-up window

    NOTE

    Make sure the target Board is powered and connected with JTAG Emulator before hitting Run.
  7. Test Execution (see Figure 10).
    8. test_execution_spnu605.gifFigure 10. Test Execution

The reports generated are saved in the <HALCoGen project folder>\Reports folder.

NOTE

Do not close the HALCoGen TAU window until the test execution is completed or successfully terminated after clicking the Stop button. Never kill the process while the test sequence is under analysis.

A copy of the build options file and the target configuration file is saved in the “Test” folder inside your HALCoGen project folder. The next time you open this project, these fields will be automatically updated with these files.

HALCoGen TAU will compile files within the <HALCoGen_Project>\source folder generated by HALCoGen and the respective test folder. The test folder can be UnitTest, FuncTest or the custom folder added by the user inside the <HALCoGen_Project>\test\<Module> folder.