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?

9.4 Build Options File

Build Options file is a text file in the following format:

Compiler Options: Linker Options: Run time Library: CG Tool Root Path:

Compiler Options: Linker Options: Run time Library: CG Tool Root Path: <HALCoGen TAU install directory>\BuildOptions. Users can use it as is in their project.

  • Compiler Options:

    • ARM compiler options can be obtained from Code Composer Studio‘s appropriate device project file as in Step1.

  • Linker Options

    • ARM linker options can also be obtained from Code Composer Studio as in Step 2.

  • Run time Library

    • Runtime support library used for the CCS project as in Step 3.

  • CG Tool Root Path

    • The path where CCS compiler is installed

  1. Select compiler option (see Figure 11).
    2. comp_option_select_spnu605.gifFigure 11. Compiler Option Select
  2. Select linker option (see Figure 12).
    3. link_option_select_spnu605.gifFigure 12. Linker Option Select
  3. Select runtime Library (see Figure 13).
    4. runtime_library_select_spnu605.gifFigure 13. Runtime Library Select