#Target code zero Pc
#Target code zero plus

This method creates a Target Configuration File by manually invoking the Target Configuration Editor.

The Verify button performs a test routine to validate the configuration chosen, similarly to what is shown in the section Test Connection below.

Several example projects already create this file automatically.

This method is very simple as it automatically assigns the correct device and set it as the Active target configuration for the project.

The file is placed in a subdirectory named targetConfigs inside the project directory.

Simply search for the part number of your development board and find out the appropriate setting.

Common selections for the Connection can be found at the page Common Target Configurations.To create it, simply find out which Debug Probe model (XDS, ICDI, MSP-FET) and interface (USB, Ethernet) is used by your hardware and set this parameter in the drop-down menu Connection in the New Project Wizard or Project settings. This method automatically creates a Target Configuration File when creating a project or modifying its properties. The Device XML file contains the internal JTAG structure of the device and can optionally include several Module XML files, which describe a device’s peripheral registers.ĭespite the complexity, there are two simple ways to create the Target Configuration File: Automatically or Manually.

#Target code zero plus

ccxml extension, that contains all the necessary information for a debug session: the type of Debug Probe, the target board or device (or even multiple devices), and (optionally) a path to a GEL (General Extension Language) script, which is responsible for performing device and/or hardware initialization.Īs shown above, the Target Configuration File includes one or more connection XML files (one per each core and JTAG entity, but all of them tied to the chosen Debug Probe) and either a Board XML file (which contains a Device XML file plus the GEL script for the board) or a Device XML file directly (which may or may not contain a GEL script). The Target Configuration File is a plain text XML file, with a. Once the Target Configuration File is created and all the appropriate hardware is connected and powered up, the debugger is ready to be launched.Īs mentioned in the Debug Overview section, Target Configuration Files are responsible for describing the physical aspects of the debugging environment. This file also contains the exact specification of the Device or Board being used.

This file is populated with the appropriate Debug Probe type (XDS, ICDI or MSP-FET) and host interface (USB or Ethernet). To properly make CCS aware of the physical aspects of the debugging environment, a Target Configuration File must be created.

#Target code zero Pc

This setup, when used with CCS, allows the host PC to communicate with the target, load data and code, control the execution of the program loaded via breakpoints/watchpoints and step operations, as well as read data back to the host PC to be displayed in views such as Expressions/Memory/Disassembly. Throughout this document, it will be called the target.

The Board or Device is the hardware that contains one or more devices required for the executable to run.

Throughout this document, the connection will also be called the Debug Probe.

The connection is the piece of hardware between the host PC that runs CCS, and the device or board where the code is supposed to be executed.

The physical debugging setup is shown above, with the two main components involved during a debug session: