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/TMS570LS3137: bootloader jumps to .bin image, but jump to the .out image fails

Part Number: TMS570LS3137

Tool/software: Code Composer Studio

I have app.out and  app.bin files generated via CCS 8.2. Both are generated at the same time from the same project.

app.bin is generated at post-build step.

Custom bootloader writes app.bin to flash at address 0x20040 and jumps to app.bin image via pointing to this address and app starts running successfully.

However when the bootloader burns app.out at the same address and then attemps to jump to the same address, consecutive resets occur, app fails to run.

is this because app.out file starts with some non-executable nonsense?

Any other reason?

Application images are supposed to come in .out format. Any input/help?

  • I wonder if expecting app.out work in this scheme is wrong at the first place.
    I wonder if app.out would work only if app.out was written at address 0x0 and linker file was accordingly.
    Do the application images have to be in .bin format so that the custom bootloader can jump to the app?

    thank you,
  • Hello,

    A Bin file is a pure binary file with no memory relocation, more than likely it has explicit instructions to be loaded. CCS8.x out file uses ELF file format. An elf file contains the bin information but it is surrounded by lots of other information: debug info, symbols, etc.

    The TI bootloader example only supports binary file. If you want to use elf file, please modify the bootloader to follow the elf format:
    en.wikipedia.org/.../Executable_and_Linkable_Format