• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 551 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.

MSPM0C1104: how to create ELF files directly as additional compile/build output in CCS 20.x using TI arm C language project ?

Martin Vernhout
Prodigy 20 points

Part Number: MSPM0C1104

Tool/software:

Subject: How to Generate ELF Output File for Ozone Debugger (MSPM0 + CCS 20.x)

Hi all,

This is probably a beginner question, but I haven’t found a clear answer yet. :-( 

I’m using the latest Code Composer Studio (20.x) with a working MSPM0 project. I’ve successfully built and flashed the firmware,
but now I’d like to generate a standalone .elf file to use with the SEGGER Ozone debugger.

Using the TI C lang toolchain. 

Could someone provide a step-by-step guide on how to configure the project to output an ELF file? Specifically:

  • Which settings need to be enabled in the linker configuration?

  • Any specific fields or tickboxes I need to fill in?

Any help or screenshots would be greatly appreciated.

Best regards,
Martin

  • +1
    TI__Intellectual 1320 points

    Hello Martin, 

    I remember seeing a similar issue in one thread where the .out file was simply renamed to .elf and it worked. Can you verify if that works in your scenario? 

    Regards, Jojo

  • 0 in reply to JOJO ARTHUR
    Prodigy 20 points

    Hi Jojo,

    THANKS !

    Read it. Eyebrowses raised a bit, first impression "Don't like it, feels odd..." 

    But checked it anyway. Opening a .out file in text editor shows it indeed has an ELF header notation !
    so it is actually an ELF file in disguise :-)

    Was really thinking the .out is the binary only, not a container which includes much much more. 

    Used https://elfy.io/ to check content. 

    What get's embedded in an ELF is normally to some extend configurable, and now
    out file = elf file do I have some form of control on what get's included, going to play with 
    settings in linker configuration and experiment some more.


    Maybe get source code used for ozone debugging  added in the ELF container :-)

    Martin.

  • 0 in reply to Martin Vernhout
    TI__Intellectual 1320 points

    Hello Martin, 

    You are much welcome and thank you for the detailed description! Also, make sure to loop me in on that adventure ;)

    Regards, Jojo

  • 0 in reply to JOJO ARTHUR
    Prodigy 20 points

    That’s a pleasant surprise!

    Just update your linker settings so the output file has a .elf extension—no other changes are necessary. All of the sections Ozone needs are already included by default. Blush