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

Building IMBLIG for WinCE

David Meixner
Expert 4010 points

I've been working with Linux on OMAP3 for a while, but I'm new to WinCE.  So far, I've been able to build the WinCE DVSDK and run those demos.  Now, I would like to build the IMGLIB demos and run them on WinCE.  Can anyone give me some advice on how to this?  Are there any resources on how to take a Linux project and build it for WinCE?

Thanks,
David

  • TI__Genius 9185 points

    David,

    I'm not very familar with how IMGLIB is called from Linux. Can you clarify whether you are using Codec Engine iUniversal or some other way to access the library on the DSP from the ARM? The DSP part should be pretty much the same between Linux and WinCE. (for e.g, the Codec Server used in OMAP35x Linux DVSDK is same as the one in WinCE DVSDK. Just a recompile to take care of DSPLINK dependency). Details for building codec server is covered in the WinCE DVSDK Getting Started Guide. 

    I have not come across any doc that details taking a Linux project and building it for WinCE. But if you look at Codec Engine or DSPLINK builds in WinCE vs the one in Linux it may  give you some idea on how to proceed. 

    Jatin

     

  • in reply to Jatin Jain
    TI__Expert 4010 points

    Hi Jatin,

    Thank you for your reply.  IMGLIB is a DSP only application, so after building it, you end up with a .out file.  Is there a method for running .out files in WinCE?  Or somehow wrapping this into a .exe?

    The build systems for Codec Engine and DSPLINK are fairly complex, so it's hard to compare them.

    Thanks,
    David

  • in reply to David Meixner
    TI__Genius 9185 points

    Let me understand what you are trying to do a bit better.

    So you end up with a DSP image (.out or .x64p which i believe is equivalent) and you want to run it from the ARM side? Running .out on WinCE does not make sense (WinCE is only supported on the ARM and .out is for the DSP). So I guess what you really want to do is to download to the DSP from the ARM side and let the DSP run without any further communication with the ARM.  We don't have any other (simpler) standalone WinCE application that will load the DSP. DSPLINK gives that capability but that will need you to write a simple app that talks to DSPLINK to do that (there are some DSPLINK examples especially readwrite test app that show what needs to be done).

    In your current setup with Linux, how do you run the DSP image?

  • in reply to Jatin Jain
    TI__Expert 4010 points

    Jatin,

    Thanks for putting up with my ramblings.  I think I was trying to run before I could walk.  After looking through the DVSDK a little more, I found the WinCE build instructions for the Codec Engine examples.  I think this is the type of tutorial I was looking for.  Hopefully after running through this, I'll have a better idea of how to leverage the IMGLIB algorithms from a WinCE app.

    Thanks for your help,
    David