NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

Template:LAUNCHXL2-570LC43 RM57L-BUILDING-DEMO

From Texas Instruments Wiki
Jump to: navigation, search

Building The Demo (Project 1)[edit]

Required Software[edit]

  1. CCS (Code Composer Studio) v6.1 or Later
  2. HALCoGen v. 4.0.4 or Later
  3. Hercules SafeTI™ Diagnostic Library 2.20

After installing CCS please confirm the version of the following CCS Components:

  • TI Emulators 5.1.641.00 or Later
  • Hercules Emulation 6.0.7 or Later

Download the Project 1 Files[edit]

File:Proj1 launchxl2 rm57l 570lc43.zip

Save this .zip file in a temporary folder. You don't need to extract the files as this will be done when importing the project into your CCS workspace.

Import the correct project into a CCS Workspace[edit]

  • Launch CCS.
  • From the Project Menu, select Import CCS Project.
  • The Import CCS Eclipse Projects wizard opens.
  • Check the 'Select Archive File' button and then press "Browse" to find the project .zip file.
  • You should see that the zip file contains 2 projects -

Update the Path Variable SAFETY_LIB[edit]

With the project imported, you can right click on the project from CCS's project explorer pane, and select "Properties" to examine the build properties.

Within the project properties, go to the Resource->Linked Resource node in the properties tree, and select the tab labeled "Path Variables". There should be a path variable with the name "SAFETY_LIB".

This path variable needs to point to the correct location on your build machine where you have installed the SafeTI Diagnostic Library. For example, it may point to C:\ti\Hercules\SafeTI Diagnostic Library\2.2.0 (make sure to include the version # in this path variable). This variable is used to include header files from the SafeTI Diagnostic Library - as well as to point to the '.lib' library object file.

You can see which folders from the safety library are included by navigating within the project properties to the Build->Arm Compiler->Include Options node of the tree and inspecting the "Add dir to #include search path" box. You should see these entries that are external to the project:

  • "${SAFETY_LIB}/hal/include"
  • "${SAFETY_LIB}/safety_library/include"

You can also check the Build->Arm Linker->File Search Path node of the properties and see that one of the pre-built library binaries is included in the link options. For example,

  • "${SAFETY_LIB}/libs/SafeTILib_TMS570LC43_BE.lib" is linked with Project1_LAUNCHXL2_570LC43
  • "${SAFETY_LIB}/libs/SafeTILib_RM57L_LE.lib" is linked with Project1_LAUNCHXL2_RM57L

There other paths within the project are project-relative and should not need to be adjusted.

With the path variable updated to match the location where you have installed the safety library - you should be able to rebuild the project successfully. Note that the project uses linker generated ECC, so you also need to adjust the Flash download settings in CCS or you may get errors when attempting to program. See this page for help if needed.

My Personal Favorite Tip[edit]

Within project properties, on the "Build" node and the "Behaviour" tab, check the box "Enable parallel build" if your build machine has a multicore CPU. Thank you gmake!