• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 307 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

PROCESSOR-SDK-AM437X: CCS to generate _ti.bin file

inno
Expert 1700 points
Part Number: PROCESSOR-SDK-AM437X

Hello,

we are developing a product with a Sitara AM437x. We want to be able to boot our product via QSPI flash. CCS generates the following files as part of the compilation process:

1) *.out
2) *.bin
3) app

It is stated in the processor SDK development guide, that the application image, which resides on the QSPI flash, has to be in *_ti.bin format (this file includes a preceding length and entry point information).

How can I instruct CCS in a way, that the following command is being triggered automatically in the post compile process:

Most likely something needs to be added here:





Can you please tell me which instruction to use?

Another thing, can somebody please correct the path information on the following website:

 software-dl.ti.com/.../index_Foundational_Components.html


Thanks,

Inno

  • 0
    Expert 1700 points

    Hello,

    I just checked the "app" file. Obviously this file is already in the "_ti.bin" file-format. If this is the case, then please ignore my question about generating the "_ti.bin" file and just check my point about correcting the documentation on the "Processor SDK RTOS Software Developer’s Guide" website.

    Thanks,

    Inno

  • 0 in reply to inno
    TI__Mastermind 40455 points

    Hi Inno,

    You're right. The "app" file generated by CCS build is the _ti.bin mentioned in the documentation - script "pdkAppImageCreate.bat" has the following line:

    %PDK_PATH%/ti/starterware/tools/ti_image/tiimage.exe 0x80000000 NONE %APP_NAME%.bin app

    Thank you for pointing out the path problem in the documentation. I'll make sure it gets fixed.

    Regards,

    Jianzhong