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.

Experiences with MATLAB Embedded Coder output in XDAIS codec implementation?

Other Parts Discussed in Thread: OMAPL138

Hi all,


I'm currently getting up to speed with implementing an XDAIS-compliant codec on the OMAPL138, using the Codec Engine and XDC tools provided with the DVSDK (04.03.00.06) and CCSv5.

I am looking to do some image processing on the DSP, and have already started looking at the IQMath and DSPLib libraries. My team was wondering if MATLAB Embedded Coder would be useful in quickly converting existing MATLAB scripts to a C implementation. In our application, the ARM will be passing off images to the DSP to encode, and the DSP will return encoded images to the ARM.

Has anyone tried this, and mind sharing some experiences? Specifically, I'm wondering if the code output from Embedded Coder requires significant modifications in order to roll things up into a nice XDAIS compliant codec for the OMAPL138. (i.e. does it generate usable code in this situation, or does it wind up being more trouble than it's worth?)

Thanks!

Jon

  • Hi Jon,

    I don't believe that anyone in TI has any experience with this scenario.  I'd like to invite people from the community to chime in if they think they have any relevant information...

    Dave

  • Hi Dave,

    I'm a bit bummed to hear that -- hopefully some other folks around here might have some insights.  Unfortunately, I'm not sure how to pose or rephrase my question any better. 

    Basically, I'm curious to hear if the code it spits out has dependencies upon specific TI package versions or interacts with the DSP, CPU, DSPBIOS, etc. in ways that a good XDAIS codec should avoid.

    Link to MATLAB Embedded Coder page:

    http://www.mathworks.com/products/embedded-coder/index.html?s_cid=0909_webg_9b_ccslink_trans_268513

  • No experience with that tool, but one common issue to look out for is any runtime memory alloc/free calls (a no-no for XDAIS) and/or any binding to an OS (e.g. pthread) or hardware (e.g. cache).

    Chris