• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 818 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.

Automate downloading binaries into custom TIVA board

Rakesh Ranjan1
Prodigy 190 points

Hi,

We have a Contiguous Build Server through which we compile code for TIVA periodically. I'm able to compile the code and generate .out from the source files through a custom makefile on command line.

I believe this contains lot of meta information and the binary that goes into TIVA is somehow generated from this out file. I plan to use LM Flash Programmer command line to program the part using XDS100v2 JTAG or preferably serial.

Any info on how to convert out file to the one needed for download will be appreciated.

Thanks 

Rakesh Ranjan

  • 0
    Guru 86755 points

    Hi,

        I think what you mean is to convert .out to .bin file? See, link below.

        http://processors.wiki.ti.com/index.php/Projects_and_Build_Handbook_for_CCS#Pre_and_Post_Build_Steps

        You can also see this post build steps at one of the example programs from Tivaware.

    - kel

  • 0 in reply to Markel Robregado
    Prodigy 190 points
    Thanks kel for your reply.

    I'm a bit confused. When we normally debug using CCS and use the xds100v2 to download and debug code, there is no such post build step required. Then why is such a step needed when we want to directly download the out file into TIVA.

    Really appreciate your help.

    Thanks
    Rakesh Ranjan
  • 0 in reply to Rakesh Ranjan1
    Guru 86755 points
    Hi,

    From what I know when debugging from CCS the code is loaded and executed in RAM. When you power cycle your Tiva MCU the code does not remain to execute on power up.

    If you load the .bin file at your Tiva MCU, the .bin will be placed in FLASH memory. At next power cycle, the program in FLASH memory will run.

    - kel
  • 0 in reply to Markel Robregado
    Prodigy 190 points
    Hi Kel,

    In my experience if you power off the board while debugging in CCS and then close CCS directly without stopping the debug session and disconnect the xds100v2 probe; in subsequent power ups the code on TIVA starts to execute. Thus, in my view the code is flashed on internal flash while debugging. This is also true because the ZRB part that i use has 32kb SRAM and my code is larger than that.

    I'm trying to understand what does CCS debugger do to convert the out file into a format that is loaded into TIVA. Also there is a Memory Allocation window in CCS which displays amount of Flash and SRAM consumed so far. To display this information there has to be a step which converts out file into something that corresponds to TIVA part.

    What do you think ?

    Thanks
    Rakesh Ranjan
  • 0 in reply to Rakesh Ranjan1
    TI__Guru**** 464181 points
    Hi Rakesh,
    If the out file is correctly built to be loaded into an area of memory that is flash, then CCS will automatically program the code to flash when your load the outfile with CCS. This is because the out file itself is a combination of debug symbols and actual code. CCS will read the symbols to know where to load/flash the the part of the out file that is the code. There is no actual conversion going on.

    Thanks
    ki