SPMU373A March   2021  – August 2022 TM4C1230C3PM , TM4C1230D5PM , TM4C1230E6PM , TM4C1230H6PM , TM4C1231C3PM , TM4C1231D5PM , TM4C1231D5PZ , TM4C1231E6PM , TM4C1231E6PZ , TM4C1231H6PGE , TM4C1231H6PM , TM4C1231H6PZ , TM4C1232C3PM , TM4C1232D5PM , TM4C1232E6PM , TM4C1232H6PM , TM4C1233C3PM , TM4C1233D5PM , TM4C1233D5PZ , TM4C1233E6PM , TM4C1233E6PZ , TM4C1233H6PGE , TM4C1233H6PM , TM4C1233H6PZ , TM4C1236D5PM , TM4C1236E6PM , TM4C1236H6PM , TM4C1237D5PM , TM4C1237D5PZ , TM4C1237E6PM , TM4C1237E6PZ , TM4C1237H6PGE , TM4C1237H6PM , TM4C1237H6PZ , TM4C123AE6PM , TM4C123AH6PM , TM4C123BE6PM , TM4C123BE6PZ , TM4C123BH6PGE , TM4C123BH6PM , TM4C123BH6PZ , TM4C123BH6ZRB , TM4C123FE6PM , TM4C123FH6PM , TM4C123GE6PM , TM4C123GE6PZ , TM4C123GH6PGE , TM4C123GH6PM , TM4C123GH6PZ , TM4C123GH6ZRB , TM4C123GH6ZXR , TM4C1290NCPDT , TM4C1290NCZAD , TM4C1292NCPDT , TM4C1292NCZAD , TM4C1294KCPDT , TM4C1294NCPDT , TM4C1294NCZAD , TM4C1297NCZAD , TM4C1299KCZAD , TM4C1299NCZAD , TM4C129CNCPDT , TM4C129CNCZAD , TM4C129DNCPDT , TM4C129DNCZAD , TM4C129EKCPDT , TM4C129ENCPDT , TM4C129ENCZAD , TM4C129LNCZAD , TM4C129XKCZAD , TM4C129XNCZAD

 

  1.   Read This First
    1.     About This Manual
    2.     Glossary
    3.     Related Documentation From Texas Instruments
    4.     Support Resources
    5.     Trademarks
  2. 1Introduction to TivaWare SDK
    1. 1.1 TivaWare SDK Folder Breakdown
  3. 2TivaWare Example Projects
    1. 2.1 TivaWare Development Board Examples
    2. 2.2 TivaWare Peripheral Examples
    3. 2.3 How to Import an Example Project into CCS
  4. 3Linking Files and Libraries into a TivaWare Project in Code Composer Studio
    1. 3.1 Linking Files in CCS
    2. 3.2 Linking Libraries in CCS
  5. 4How to Debug a TivaWare Library
    1. 4.1 How to Direct Code Composer Studio to a Source File
    2. 4.2 How to Rebuild TivaWare Libraries
  6. 5How to Add TivaWare to an Existing CCS Project
    1. 5.1 Path Variables
    2. 5.2 Include Paths
    3. 5.3 Predefined Variables
    4. 5.4 Library Linking
  7. 6TivaWare Boot Loader
    1. 6.1 Modifying a TivaWare Project for Boot Loading in Code Composer Studio
    2. 6.2 How to Boot Load with LM Flash Programmer
  8. 7Software Best Practices
    1. 7.1 Stack / Heap Settings and Stack Overflow
    2. 7.2 Interrupt Service Routines
      1. 7.2.1 Best Practices
      2. 7.2.2 TivaWare Vector Tables and IntDefaultHandler
    3. 7.3 TivaWare Hardware Header Files
    4. 7.4 ROM and MAP TivaWare Prefixes
  9. 8TM4C Resources
  10. 9Revision History

4.1 How to Direct Code Composer Studio to a Source File

If there is a need to access the source file for a library call while debugging code then CCS needs to be pointed to the source code file. This can be achieved during debug with a combination of using breakpoints and code stepping techniques to prompt the IDE to try and find the file that can then be manually located on the local file system.

The first step will be to set a breakpoint on the exact function call that needs to be debugged. This can be done by double-clicking on the grey space next to that line of code or by right-clicking the line of code and selecting 'Breakpoint' at the top of the menu that pops up. When the breakpoint is set, a small blue orb will appear in the grey space next to the line of code as seen in Figure 5-1.

Tip: If the function is called with a MAP or ROM prefix, remove the prefix to avoid any ROM library calls as these cannot be accessed by the debugger.
GUID-20210113-CA0I-CL4V-DJBL-GMJRPBPZBQLL-low.jpg Figure 4-1 Setting a Breakpoint on a DriverLib Call

 

Once the breakpoint is set, execute code until the breakpoint is triggered. Once that occurs, the execution of the code will stop, and the toolbar at the top will have the options seen in Figure 5-2. Use the 'Step Into' feature, highlighted in the figure or keyboard shortcut F5, to trigger the IDE to search for the source code file.

GUID-20210113-CA0I-VFC9-DNBN-9QSJ2ZGSCBZK-low.jpg Figure 4-2 CCS Debug Control Options

 

Once the IDE is prompted to look for the source file, it will not be able to locate the file and will pop-up a notification (Figure 5-3). As part of this pop-up, the user is given the option to 'Locate File...' and this is what is used to help direct the IDE to the right files. After clicking on 'Locate File...', navigate to the DriverLib folder on the local file system and select it. The entire folder is selected for this, not an individual file, so there is no need to know exactly what source code file is needed. The IDE will search all files in the folder and bring up the correct one automatically.

GUID-20210113-CA0I-1QCM-KLSH-9W3JM125QC17-low.jpg Figure 4-3 Locate File Pop-Up

 

After providing the directory for the source code, then the pop-up will go away and the source code file will be opened up and the cursor will be placed inside of the function that was being stepped into as shown in Figure 5-4. Debugging can continue from here like normal.

GUID-20210113-CA0I-PC46-W2D0-LBDTPDMJKNLS-low.jpg Figure 4-4 DriverLib Source Code File Successfully Located and Loaded