• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 387 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.

Difference between regular binary and _ti appended binary?

Gregg Schroeder
Intellectual 375 points

When building the apps in Starterware, what is the difference between the regular binaries and the ones appended with the _ti?  (ie. dmtimerCounter.bin vs dmtimerCounter_ti.bin)  Are the _ti appended ones the only ones that work to rename to "app" and use that way with Starterware's MLO?

Thanks

  • 0
    TI__Intellectual 1480 points

    Hi,

    Binary with _ti.bin has TI header appended to the actual binary(.bin). This header information in app is used by bootloader to determine the load address, e.t.c. Bootlader expects _ti.bin for MMCSD boot medium/src.

    Regards,

    Ramesh D

  • 0
    Genius 5820 points

    Gregg Schroeder said:
    Are the _ti appended ones the only ones that work to rename to "app" and use that way with Starterware's MLO?

    Yes, exactly. The _ti variant contains the additional header that is read by MLO in order to load the binary to correct address.

    Btw: when you're using CCS with Linux you have to be careful, there the Makefile does not work as expected, the generated _ti file is always from previous compilation, not from current one.