• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 416 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/TM4C123GH6PZ: Unable to debug properly in CCS with different FLASH origin address in .cmd file

JOYAL JOSE
Prodigy 10 points

Part Number: TM4C123GH6PZ
Other Parts Discussed in Thread: EK-TM4C123GXL

Tool/software: Code Composer Studio

Unable to debug properly in CCS with different FLASH origin address in .cmd file.

When the APP_BASE address is 0x00000000 it works fine, but when it is a different value (eg: 0x00001000) for bootloader support, unable to step over as debug points jumps to random lines/files

#define APP_BASE 0x00001000
#define RAM_BASE 0x20000000

MEMORY
{
FLASH (RX) : origin = APP_BASE, length = 0x0003F000
SRAM (RWX) : origin = RAM_BASE, length = 0x00008000
}

  • 0
    TI__Guru**** 191886 points

    Hi,

      Do you have the bootloader starting at 0x0? If you have bootloader in the flash starting at 0x0 and the app in the flash starting at 0x1000, make sure you load the symbols for both images before you debug. I will also suggest you try out the bootloader examples in the TivaWare. You might start with the C:\ti\TivaWare_C_Series-2.2.0.295\examples\boards\ek-tm4c123gxl\boot_serial (this is a bootloader starting at 0x0) and C:\ti\TivaWare_C_Series-2.2.0.295\examples\boards\ek-tm4c123gxl\boot_demo1 (this is an application starting at 0x2800). Also make sure when you start your application (e.g. 0x1000) it does not overwrite the areas that is occupied by the bootloader. In another word, if the bootloader occupies memory beyond 0x1000 then your application will overwrite it.