7 Manual Settings to the LDRA Install Needed by the User

1. If the user has already installed LDRAunit-TI-Qual_C_CPP_9.4.3 for HALCogen, then the compiler option must be changed using the “compiler options” executable from the
   LDRAunit-TI-Qual_C_CPP_9.4.3 (run this program in administrative mode). Figure 4 and Figure 5 explain how to change the compiler options.
Figure 4. Select the Compiler Options
Figure 5. Select Compiler
2. Open the file LDRA_execute.bat under the LDRA installation directory (typically C:\Program Files (x86)\LDRA\LDRAunit-TI-Qual_C_CPP_9.4.3\Compiler_spec\Ticcs50\Rm48l950_hercules_serial\).
   • In the beginning of the file, find a line similar to the following:
     cd “C:\Program Files (x86)\LDRA\LDRAunit-TI-Qual_C_CPP_9.4.3\Utils\Comporter”
   • Change the above line to:
     “cd /d C:\Program Files (x86)\LDRA\LDRAunit-TI-Qual_C_CPP_9.4.3\Utils\Comporter”

NOTE

The software may require administrative privileges to change this file. Changing the file is necessary because the CD only works when trying to change the directory in the current working drive. If the TAU is installed in another drive other than C: drive, the CD fails to change the directory.

3. Connect the device board to the system (PC) for test, depending on the Target Board HW configuration, using either of the following:
   1. USB cable on the SCI port, as SCI is used for testing with XDS100/XDS110 USB emulator integrated on board
   2. USB-JTAG External Debugger XDS510 connected using the JTAG lines on board
   .
4. When selecting a HALCoGen project or modifying an existing project under demo_app\HALCoGen, take care to see that the SCI continue on suspend bit (bit 17 in SCI Global Control Register 1 (SCIGCR1) in the SCI module) is enabled.
5. If LDRAunit-TI-Qual_C_CPP_9.4.3 for HalCogen has already installed, then the compiler option must be changed using the compiler, which is executable from the LDRAunit-TI-Qual_C_CPP_9.4.3 file.
6. In cases where issues occur when building and running test cases, the user may have a corrupt LDRAunit-TI-Qual_C_CPP_9.4.3 work area. To fix the issue, delete the existing sets (an LDRA work item) as shown in Figure 6 through Figure 8, and then start running the test cases again.
Figure 6. Open LDRAunit
Figure 7. Select Multiple Files
Figure 8. Delete the Set for the Device Under Test
(Here RM46x Software Diagnostic Library is Selected Here)
7. Sometimes when the system hangs, the test execution is halted and the source code may be corrupted. That is, the user may leave the source code in an instrumented state (LDRA instrumentation). In that case, LDRA creates the source backup folder in:
   <installation directory>\safety_library\source
   Replace the corrupted source code using this backup.
8. The RTS libraries used for building the .out file for the test cases may sometimes be missing in the compiler. Automatic build of the RTS libraries may fail when the environment variables are not correctly set for the shell that is used for building the RTS library. The user must ensure that the required RTS libraries are available in the compiler.
9. In some cases, for example: forcibly closing test execution, ending the test automation task, or due to a power loss when the test execution is running, the LDRA analysis may lock (see Figure 9). This lock must be deleted to allow successful execution of test cases.
Figure 9. LDRA Analysis Lock