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.

TMS320F280049-Q1: CCS real-time debug for images with a bootloader and an application

Part Number: TMS320F280049-Q1

Dear Champs,

I am asking this for our customer.

The user can use CCS real-time debug for their application-only image programmed on flash.

That is, they can program the application image first onto the flash, run it, and then connect JTAG (without reset), load symbol, and then use CCS real-time debugging function.

However, they found when they firstly programmed a bootloader image, then they fail to use real-time control.

Bootloader starts at 0x80000 (flash entry point) and then jump to application at 0x82000.

There are two projects/images bootloader.out and application.out here.

Questions:

1. Do you have any comment how they use real-time debug for their application debugging if they firstly have bootloader image on 0x80000?

2. If they can combine both booloader.out and application.out into one integrated all.out, and then load symbol by this all.out, can they use CCS real-time debugging?

Wayne

  • Hi Wayne,

    I will get back to you on the query in couple of days time.

    Thanks and regards, Pawan

  • Hi Wayne,

    However, they found when they firstly programmed a bootloader image, then they fail to use real-time control.

    What is happening here? Are you able to attach JTAG (without reset) and load symbols or it fails to connect?

    1. Do you have any comment how they use real-time debug for their application debugging if they firstly have bootloader image on 0x80000?

    The steps you mentioned should work. Basically, after writing the image to flash, power cycle the board and connect JTAG (without reset), and the address of PC is wrong?

    2. If they can combine both booloader.out and application.out into one integrated all.out, and then load symbol by this all.out, can they use CCS real-time debugging?

    If the binary running on target and the symbols being loaded in CCS are matching then it should work.

    Regards, Santosh

  • Dear Santosh,

    OK, I will ask the user to try to combine both .out and try it.

    Wayne

  • Okay. Let us know if it resolves the issue.

  • Dear Santosh,

    Would you please confirm how to combine the .out?

    Is it like this? or any suggestion?

    hex2000.exe --load_image app_1.out app_2.out --load_image:file_type=executable -o app_combined.out

  • I will take a look today and get back you by tomorrow.

  • I was referring to combining in the code-base to generate one out file. I do not think hex2000 file can combine the two .out file.

  • Dear Santosh,

    I am confused.

    Would you please make this clearer? 

    "I was referring to combining in the code-base to generate one out file."

  • Wayne,

    I was referring to merge the source code and generate single out file. I am not familiar if two .out files can be combined.

    Regards, Santosh

  • Dear Santosh,

    But there is a problem here to merge the two source code. For example, there are two main...

    The prerequisite of this post is that there are two projects (two .out / two images) here.

    I think even if two .out can be combined, there is still an issue because there are two kinds of symbols here.

    I tried to use CCS to load two .out as symbols separately, and CCS can always load one .out at one time.

    That is, we could only debug only one project at a time, even the two images are programmed on the same flash.

    Therefore, we wonder if there is any way to solve this except using one combined project?

    OR the answer is NO?

  • Strong,

    No, I am not familiar with any other solution.