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

About c6run-tool and XDC-tool

Fang Jain-Ping
Prodigy 110 points


Hello! I read document about c6run-tool. This tool can use "c6runapp-cc" compile C code for DSP. What is the difference between c6run-tool and XDC-tool? If I use c6run-tool to compile my C code for DSP , the Codec-Engine and Codec-Server is non-necessary?
  • 0
    TI__Genius 17355 points

    The C6Run tool does not use the Codec Engine framework. It provides a simplified mechanism to build and run C code from the ARM/Linux command prompt, with execution being handled transparently by the DSP core.  The C6Run tools are not directly related to Codec Engine or the XDC tools.

    I would encourage you to read the documentation available on the TI embedded processors wiki and post any further questions here.

    Regards, Daniel

  • 0 in reply to Daniel Allred
    Prodigy 110 points

    HI~ Daniel Allred !

    Thank your reply and suggestion .

     

    So user can use own Library  *.h  to make C code  with c6run-tool too ?

  • 0 in reply to Fang Jain-Ping
    TI__Genius 17355 points

    Yes, the intention is that the user can supply their own C files and header files and compile them with the C6Run tools to run on the DSP.  The programs are run from the ARM/Linux command prompt, but execution takes place on the DSP without the user having to know much about the communication that takes place between the two cores to make that happen.

    There are two use cases right now.  The C6RunApp case moves all of the user application code to the DSP, including the main() function.  Any C I/O operations (such as printf, scanf, fopen, fread, etc) will be sent to the ARM and the results will then be returned to the DSP.  The second use case, C6RunLib, allows the user to move only certain C files to the DSP by creating a separate library that is then linked in at build time with the remainder of the user's code which runs on the ARM.  Any calls that are made into that library are then executed on the DSP and the results are returned to the ARM.

    I hope the above description helps. Much more detail can be found on the TI embedded processor wiki.

    Regards, Daniel

  • 0 in reply to Daniel Allred
    Prodigy 110 points

    HI~ Daniel Allred

    Thank you so much .