SPRUJH3 April   2025 TMS320F2800132 , TMS320F2800133 , TMS320F2800135 , TMS320F2800137 , TMS320F2800152-Q1 , TMS320F2800153-Q1 , TMS320F2800154-Q1 , TMS320F2800155 , TMS320F2800155-Q1 , TMS320F2800156-Q1 , TMS320F2800157 , TMS320F2800157-Q1 , TMS320F280021 , TMS320F280023 , TMS320F280023C , TMS320F280025 , TMS320F280025C , TMS320F280034 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037C , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039C , TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041C , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049C , TMS320F28076 , TMS320F28374D , TMS320F28374S , TMS320F28375D , TMS320F28375S , TMS320F28376D , TMS320F28376S , TMS320F28377D , TMS320F28377S , TMS320F28378D , TMS320F28378S , TMS320F28379D , TMS320F28379S , TMS320F28384D , TMS320F28384S , TMS320F28386D , TMS320F28386S , TMS320F28388D , TMS320F28388S , TMS320F28P550SG , TMS320F28P550SJ , TMS320F28P559SG-Q1 , TMS320F28P559SJ-Q1 , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Configuring the Boot Mode
    1. 2.1 Standalone Boot
      1. 2.1.1 Boot Mode Select Pins (BMSP)
      2. 2.1.2 Boot Definition Table (BOOTDEF)
      3. 2.1.3 Boot ROM OTP Configuration Registers
      4. 2.1.4 CPU2 Boot Flow
    2. 2.2 Emulation Boot
  6. 3Programming the Flash
    1. 3.1 Flash API
    2. 3.2 Flash Kernels
  7. 4Bootloading Code to Flash
    1. 4.1 C2000 Hex Utility
    2. 4.2 Common Boot Modes
      1. 4.2.1 Boot to Flash
      2. 4.2.2 SCI Boot
      3. 4.2.3 CAN Boot
      4. 4.2.4 CAN-FD Boot
      5. 4.2.5 USB Boot
  8. 5FAQ
    1. 5.1 Selecting the BMSP GPIOs with a Software-based Implementation
    2. 5.2 Running a Flash Kernel from the Flash Instead of the RAM
    3. 5.3 No Symbols Defined When Debugging Boot ROM
    4. 5.4 Writing Values in the OTP Using the On-Chip Flash Tool
    5. 5.5 Writing Values in the OTP Using the Flash API Plugin
  9. 6Summary
  10. 7References

5.3 No Symbols Defined When Debugging Boot ROM

Question: When I debug the boot ROM, the ROM states there is a break in the boot ROM with no debug information available, or outside of program code. What am I missing?

Answer: Users can step through the device boot ROM by loading the boot ROM symbols (.out file) to the device. Loading symbols can be a valuable debug method. This option adds the symbols available in the generated project .out file for debugging purposes instead of loading the actual .out program onto the core by CCS. This is also why users can use this method with the boot ROM or built-in bootloaders to debug and get enhanced visibility.

  1. Open CCS to a workspace.
  2. Select View > Target Configurations.

    Opening the Target Configuration Menu in CCS

    Figure 5-6 Opening the Target Configuration Menu in CCS
  3. Users can import a project for this device to CCS and use that to connect to the device, or copy the target configuration file (.ccxml) from C2000Ware (C2000Ware_x_xx_xx_xx > device_support > DEVICE_FAMILY > common > targetConfigs) to the User Defined target configurations in this window (View > Target Configurations). Either way, find the device target config and manually launch by right-clicking:

    Launching a Target Configuration in CCS

    Figure 5-7 Launching a Target Configuration in CCS
  4. When CCS brings up the debug window, select the intended CPU and connect to the target.

    Connecting to the Target Core in CCS

    Figure 5-8 Connecting to the Target Core in CCS
  5. At this point, a window pops up stating there is a break in the boot ROM with no debug information available, or outside of program code.

    CCS View When No Boot ROM Symbols Are Loaded
    Figure 5-9 CCS View When No Boot ROM Symbols Are Loaded
  6. Navigate to the toolbar and click the button to Load Symbols.

    Navigating to Load Symbols in CCS
    Figure 5-10 Navigating to Load Symbols in CCS
  7. Load the boot ROM .out file. This can be found in C200Ware at:
    1. C2000Ware_x_xx_xx_xx > libraries > libraries > boot_rom > DEVICE_FAMILY > REV# > rom_sources > CPU# > ccs_files > Release
  8. If a window pops up stating the source file cannot be found, then users can select Locate File and find in C2000Ware at:
    1. C2000Ware_x_xx_xx_xx > libraries > boot_rom > DEVICE_FAMILY > REV# > rom_sources > CPU# > DEVICE_FAMILY_ROM > bootROM > source

      Locating the Boot ROM Source Files
      Figure 5-11 Locating the Boot ROM Source Files

The file opens to show the current instruction in the boot ROM and users can go through how to debug, reset and restart the device.