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

DM355 Codec Engine Package

Ravindra
Intellectual 870 points

All,

We are trying to integrate the JPEG Decoder on Dm355 using the Codec Engine 2.24.

We see a number of library packages under the dm355_codecs_1_13_000\packages\ti\catalog\hwa\imcop\lib folder, such as the libimx.a, libcosl.a, libdm355mm.a and libimcopcsl.a. While the source-code for libdm355mm is available, the source for the other libraries are not available.

I assume that the other libraries are the binary code that gets loaded into the MJCP Engine of DM355 for JPEG Decoding functionality. Does anyone know the relevance of each of these libraries?

Do these libraries require any porting when running Codec Engine on a different OS Platform like WinCE apart from Linux.

Thanks

  • 0
    TI__Mastermind 41665 points

    Ravindra said:
    Do these libraries require any porting when running Codec Engine on a different OS Platform like WinCE apart from Linux.

    I only really work with Linux so I am not sure, but I suspect they are portable, you probably want to ask  your Windows CE BSP provider regarding this.

  • 0 in reply to Bernie Thompson TI
    Intellectual 870 points

    Bernie,

    Thanks for the response. We are trying to integrate the JPEG Decoder in Codec Engine 2.24 which already supports WinCE and as per the supported device list DM355 is also included.

    So, we do know if the libraries still require porting. Do you know the significance of these libraries?

    What is the mechanism used to configure/program the MJCP Engine? All these libraries libimx.a, libimcopsl.a have specific role to play with the working of the MJCP Engine?

    Ravi