• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 605 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/TMS320F2808: CCS v6.2.0 debugging

user4318460
Intellectual 620 points

Part Number: TMS320F2808

Tool/software: Code Composer Studio

Hello all,

I would like to ask you for an advice. I have a custom control board with TMS320F2808 dsp and

flash memory of this dsp contains custom bootloader and application. I need to debug the application

but as soon as I start the debug session in the Code Composer Studio v6.2.0 program execution 

enters into the bootloader at first. Can anybody tell me what is necessary to do in the debug configuration

to force entery directly into the application? For completeness: I have been using XDS100v2 JTAG.

Thank you in advance.

  • 0
    TI__Guru**** 173310 points

    user4318460 said:

    I have a custom control board with TMS320F2808 dsp and flash memory of this dsp contains custom bootloader and application.

    Are the bootloader and application loaded as two separate executables or are they combined into a single executable?

    There are settings in the CCS debugger that control the auto run options. You can try to let it auto-run to a symbol within your main application.
    More information can be found here: http://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_debug-main.html#auto-run-and-launch-options

     

  • 0 in reply to AartiG
    Intellectual 620 points

    Hello AartiG,

    thank you for your reaction. Bootloader and application are two separate executables.

  • 0 in reply to AartiG
    Intellectual 620 points

    Hello AartiG,

    I have tried to set the Auto Run Options in bellow given manner:

    where the EALLOW is a C language symbolic constant 

    #define  EALLOW asm(" EALLOW") and it is the very first

    instruction in the main function. As soon as I started the Debugger

    and connected to the target the program execution stoped at the

    address 0x3ffb50. Based on the below mentioned table (copied from 

    document SPRU722C page 8) it seems to me that program execution

    stopped in the factory programmed bootloader.

     

    I do not understand why program execution does not continue to "my" (unfortunately I

    have not written it) bootloader. Do you have any idea what could be the reason? Thank you.

  • 0 in reply to user4318460
    TI__Guru**** 173310 points

    user4318460 said:

    where the EALLOW is a C language symbolic constant 

    #define  EALLOW asm(" EALLOW") and it is the very first instruction in the main function.

    Typically the entry point is set to a function like main, not a C macro like EALLOW.

    user4318460 said:

    As soon as I started the Debugger and connected to the target the program execution stoped at the address 0x3ffb50. Based on the below mentioned table (copied from document SPRU722C page 8) it seems to me that program execution stopped in the factory programmed bootloader.

    I do not understand why program execution does not continue to "my" (unfortunately I have not written it) bootloader.

    Details and guidelines about the bootloader process are best answered by the experts in the C2000 device forum. I would suggest starting a new post in the C2000 forum, provide them details about where your bootloader and main application are linked to, and they should be able to guide you in the right direction.