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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |