7. CCS Setup for J742S2

Code Composer Studio is an integrated development environment (IDE) that supports TI’s Micro controller and Embedded Processors portfolio. It provides useful tools to develop and debug embedded applications.

Please visit Code Composer Studio product (https://www.ti.com/tool/ccstudio) for more information.

Important

• Below screen shots and examples show paths and instructions for Linux. The same applies for Windows except use Windows file/folder paths instead.

• In Linux+RTOS mode, SPL/uboot bootloader loads the R5F, C7x, A72 binaries

  • CCS is needed to debug the software on R5F, C7x (and A72 when in RTOS mode).

• In RTOS only mode, CCS is needed to load and run the binaries on different CPU cores in the SoC.

• The CCS emulation pack and CSP (Chip Support Package) needs to be downloaded separately.

7.1. CPU names used in PSDK RTOS vs CCS

Below table shows the mapping of names in PSDK RTOS and CCS

CPU name in PSDK RTOS	CPU name in CCS
mcu1_0 / mcu1_1	MCU_Cortex_R5_0 / MCU_Cortex_R5_1
mcu2_0 / mcu2_1	MAIN_Cortex_R5_0_0 / MAIN_Cortex_R5_0_1
mcu3_0 / mcu3_1	MAIN_Cortex_R5_1_0 / MAIN_Cortex_R5_1_1
mcu4_0 / mcu4_1	MAIN_Cortex_R5_2_0 / MAIN_Cortex_R5_2_1
mpu1	CortexA72_0_0
c7x_1	C71x_0
c7x_2	C71x_1
c7x_3	C71x_2

7.2. Step 1: Install CCS

1. Install CCS v12.4 : CCS can be downloaded from https://www.ti.com/tool/download/CCSTUDIO/12.4.0

2. CCS installation details are available on https://dr-download.ti.com/software-development/ide-configuration-compiler-or-debugger/MD-J1VdearkvK/12.4.0/CCS_12.4.0_ReleaseNotes.htm

3. This release is tested on below CCS version 12.4.0.00007

4. During installation, there is a ‘Setup’ step where you can select components. Be sure to select: “TDAx Driver Assistance SoCs & Jacinto DRAx Infotainment SoCs” as shown below:

   

   Fig. 7.1 CCS: Download Components

5. Here after we’ll be referring to the CCS installation directory as ${CCS_INSTALL_PATH}

   In Linux, this will be

   ${HOME}/ti/ccsv1240/ccs
   

   In Windows, this will be

   C:\\ti\\ccsv1240\\ccs\
   

7.3. Debugging with HLOS running on A72 (Linux / QNX)

Important

• This section is applicable only if you are loading a HLOS (Linux or QNX) application. To debug RTOS cores using CCS when not running Linux or QNX on A72, refer section CCS_A72_RTOS.

• CCS cannot be used to debug applications on the A72. For Linux, it is recommended to use gdb which comes preinstalled on the filesystem. For QNX, it is recommended to use QNX Momentics.

7.3.1. Step 4: Setup CCS target configuration

1. Install CCS, CCS emulation packs and the CSP as per Step 1: Install CCS.

2. Create a CCS target config, you can name it “J42S2_NO_GEL.ccxml”.

   • Select Connection as Texas Instruments XDS110 USB Debug Probe, if you are using on board debugger (J1 usb connector)

   • Select Connection as Spectrum Digital XDS560V2 STM USB Emulator, if you are using Spectrum digital XDS560 USB debugger connected to JTAG Mipi connector (J23)

   • Select the Board as J784S4_TDA4VH shown below

     

     Fig. 7.2 CCS: Target Configuration

   • Remove the gel file path from CORTEX_M4F_0 under SMS_TIFSM if it is not blank already.

7.3.2. Step 5: Load RTOS core firmware symbols thru CCS

1. Load the debug version of the firmware binaries on the HLOS file system, and boot device.

2. Launch the target config file created

   

   Fig. 7.3 CCS: Target Configuration launched

3. Now you can connect to the required non-A72 core (i.e R5, C7x_0 etc)

   

   Fig. 7.4 CCS: Connect to non-A72 core

4. After connecting, you can load the symbols of the debug version of the application binary.

   

   Fig. 7.5 CCS: Load symbols in the connected non-A72 core

5. Now you can put breakpoints wherever required and debug as usual.