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.

c6000 omapl138 printf, fopen

Other Parts Discussed in Thread: OMAPL138

Hi, I am looking to compile a cross platform program to run on the dsp chip of an OMAPL138 LCDK. Linux will be running on the arm chip. I have 2 other threads that have been some help but was recommended to ask again in the compiler forum.

http://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/112/t/374466.aspx

http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/p/374211/1317674.aspx#1317674

The dsp program requires access to stdout on the linux caller, and to print to files using the normal fopen(), fprintf() c library functionality. I read in the SPRU187U.pdf document, included with the cl6x compiler, that cio functions are supported (pg 250), and that a 'debugger' and an 'appropriate driver' are required to be running on the host system.

Could you please direct me to documentation or examples of this functionality in action? I would assume for the LCDK/OMAPL138 systems that there would be the appropriate drivers/debuggers available, but I have not been able to locate them through google, the ti website, the doc, or the ti wiki. 

Our previous implementation was using c6runapp-cc to perform this, but as it is now no longer supported by ti, I am wondering what the correct new technique is for the c6run equivalent functionality.

Thanks

  • Evan Benn36 said:
    I would assume for the LCDK/OMAPL138 systems that there would be the appropriate drivers/debuggers available

    I am not aware of anything that is available at this time.

    You could create your own solution.  You could implement your own device driver level functions for interacting with Linux executing on the ARM.  Those functions have to conform the interface described in the section titled Device-Driver Level I/O Functions in the C6000 compiler manual.  You collect those functions together into a device driver with a call to the function add_device as described in the section titled Adding a User-Defined Device Driver for C I/O.  

    I suspect this is not the answer you want.  But that is where things stand at this time.

    Thanks and regards,

    -George