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.

System Analyzer Tutorial7 CCSv53 Launch Configuration

From Texas Instruments Wiki
Jump to: navigation, search

System Analyzer Tutorial 7 - CCSv5.3 Launch Configuration[edit]

Here's how to configure a launch in CCSv5.3 that will automatically load the OpenMP project into CPU 0, symbols into all other cores and start System Analyzer:

Configuring the Launch[edit]

  • Launch the .ccxml file for your target
  • From the CCS menu select Views / Target Configurations, then right click on your target's .ccxml file entry and select Launch Selected Configuration
  • In the debug view, right click on a core and select "Edit <name of your .ccxml file>"

For the master CPU (CPU 0):

  • click on the Program tab
  • Ensure that the Device drop-down list is set to C66xx_0
  • Click on the Workspace button to the right of the Program text box and browse to the .out file you wish to load
  • ensure that the Loading options for CPU 0 is set to Load program

For each of the slave CPUs (CPU 1-7):

  • click on the Program tab
  • Ensure that the Device drop-down list is set to the next CPU to configure (e.g. C66xx_1)
  • Click on the Workspace button to the right of the Program text box and browse to the .out file you wish to load
  • ensure that the Loading options for CPU 0 is set to Load symbols only

For all CPUs

  • Click on the Target tab
  • Select the CPU to configure from the Device drop-down list (e.g. C66xx_1)
  • In the left-hand pane, select Program / Memory Load Options
  • Uncheck Halt at program termination (requires setting a breakpoint)
  • Uncheck Enable CIO function use (requires setting a breakpoint)
  • Check Reset the target on a connect
  • Uncheck Reset the target on a program load or restart
  • Check Restart the target on a symbol load as well as a program load
  • Tutorial7 LoadOptions.gif
  • In the left-hand pane, select Misc/Other Options, accept defaults except:
  • Uncheck Allow software breakpoints to be used.
  • EditCcxmlToDisableSWBkpts.gif

For the master CPU (CPU 0):

  • Click on the Target tab
  • Ensure that the Device drop-down list is set to C66xx_0
  • In the left-hand pane, select Auto Run and Launch Options, accept defaults except:
  • in the text box for Run to symbol, ensure that it says main
  • Check On a program load or restart
  • Check Connect to the target on debugger startup
  • Uncheck Restore breakpoints from previous session
  • Check Continue debug launch if target connection or program load fails
  • Tutorial7 AutoRun Core0.gif

For each of the slave CPUs (CPU 1-7):

  • Click on the Target tab
  • In the left-hand pane, select Auto Run and Launch Options, accept defaults except:
  • in the text box for Run to symbol, ensure that it says main
  • Uncheck On a program load or restart
  • Check Connect to the target on debugger startup
  • Uncheck Restore breakpoints from previous session
  • Check Continue debug launch if target connection or program load fails
  • Tutorial7 AutoRun Core1.gif
  • Click the Apply button


Click the Continue button and the launch configuration dialog will close.
In the Debug view, select all of the slave cores (CPU 1-7), right click and select "Group core(s)" from the context menu.

Then terminate the existing Debug session by clicking on the red square in the Debug View toolbar Tutorial7 Terminate.gif.


After following the above instructions, when you launch, CPU 0 will be loaded with the program and symbols will be loaded into the slave cores.

  • If you find CPU 0 is already at main upon launch, click the restart button in the Debug View toolbar Tutorial7 restartButton.gif. It should start running, and wait for the slave cores to start.
  • Click on the group node that the slave cores are in and click the run button.
  • if any of the slave cores halt at c_int00 before CPU 0 halts at main, click the run button again. What is happening behind the scenes is that the master CPU is restarting the slave CPUs and sometimes this causes the IDE to display the core's state as having been halted.
  • Once all of the slave cores are up and running, CPU 0 should halt at main, indicating that it has established IPC communication with the slave cores.
  • With the group node selected, click the Halt button in the debug view to halt all of the slave cores
  • Start System Analyzer (Tools / System Analyzer / Live) and click the Start button in the System Analyzer dialog.
  • In the Debug View, select CPU 0 and click the run button, then select the slave group and click the run button.

Back to System Analyzer Tutorial 7

Links[edit]

E2e.jpg {{
  1. switchcategory:MultiCore=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article System Analyzer Tutorial7 CCSv53 Launch Configuration here.

Keystone=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article System Analyzer Tutorial7 CCSv53 Launch Configuration here.

C2000=For technical support on the C2000 please post your questions on The C2000 Forum. Please post only comments about the article System Analyzer Tutorial7 CCSv53 Launch Configuration here. DaVinci=For technical support on DaVincoplease post your questions on The DaVinci Forum. Please post only comments about the article System Analyzer Tutorial7 CCSv53 Launch Configuration here. MSP430=For technical support on MSP430 please post your questions on The MSP430 Forum. Please post only comments about the article System Analyzer Tutorial7 CCSv53 Launch Configuration here. OMAP35x=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article System Analyzer Tutorial7 CCSv53 Launch Configuration here. OMAPL1=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article System Analyzer Tutorial7 CCSv53 Launch Configuration here. MAVRK=For technical support on MAVRK please post your questions on The MAVRK Toolbox Forum. Please post only comments about the article System Analyzer Tutorial7 CCSv53 Launch Configuration here. For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article System Analyzer Tutorial7 CCSv53 Launch Configuration here.

}}

Hyperlink blue.png Links

Amplifiers & Linear
Audio
Broadband RF/IF & Digital Radio
Clocks & Timers
Data Converters

DLP & MEMS
High-Reliability
Interface
Logic
Power Management

Processors

Switches & Multiplexers
Temperature Sensors & Control ICs
Wireless Connectivity