• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 382 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 Codec sample code of Linux on Windows CCS ver3.3

Cholnam Kim
Prodigy 195 points

Hi, everyone.

I'd like to build the sample program for evmdm365 of using jpeg codec with ccs ver3.3, but the sample code is for Linux.
I think I can build it on Windows, I mean with CodeComposerStudio ver3.3
The followings are what I did.

1. Download the codec 'dm365_jpegdec_01_00_00_04_production.exe' setup file from SpectrumDigital.
2. Install it and extract.
3. Launch the Code Composer Studio ver3.3
4. Create new project and add the source files from the folder that the archive was extracted.
    There is one problem. This is sample code for linux(the user's guide says), so there is no ccs project file. So I create a project.
5. Add header files(*.h) from the same folder above mentioned.
6. Build the project.
7. Then 8 errors display and all the errors are same, that is, <"alg_control.c", line 36: fatal error: could not open source file "alg.h">( that line is #include).
    But if click the items correspongs to each header file on the 'Fileview' tab of treeview control, then the file opens.

So, what's the problem? Why does the compiler say that it can not open the header file?
And also, can I build that sample code on windows?

Please tell me if anyone knows about this problem.
Thank you.
Cholnam, Kim./

  • 0
    TI__Mastermind 37340 points

    maybe you need to add a directory to the project path in order for CCS to find the file..

    With regards to building in Windows... a couple of things come to mind.

    1) The Windows-CCS ARM compiler is not the same as the Linux MontaVista Compiler included with DVSDK.  We only test with DVSDK; therefore we cannot guarantee things will work correctly on Windows...

    2) Assuming the compiler differences are minor and things work as expected (after coying over all necessary files to windows), CCS 3.3 is not Linux aware, thus you be debugging things at a very low-level and perhaps will not be able to enable the Virtual Memory Manager (common in General Purpose Processors such as ARM) as this would confuse CCS, which knows how handle physical addresses but does not handle virtual addresses well.  Keep in mind that much of the demos interface to Linux Standardized drivers (e.g. video capture/display), since CCS 3.3 does not support Linux, this likely means you will need to write lots of code to come up with your own low-level software layer (peripheral drivers) and make the demo software interface to your new non-Linux based software architecture.

     

  • 0
    TI__Mastermind 41665 points

    Juan is right on here, for the specific error you have with the missing header file you need to add a search path in your project -> build options to that particular file, in particular you can add the path in the box in the screen shot below.

    However as general feedback, as the DM365 software stack is designed around Linux, it is a good idea to do all your work within Linux, as Juan suggests we do not have software collateral for any i/o with a CCS project for DM365.

  • 0 in reply to Bernie Thompson TI
    Prodigy 195 points

    Thank you Juan & Bernie.

    I've setup build options for my project.
    So I forwarded a little.
    But the compiler still says it can not compile.
    It says it can not open the include file <ti/xdais/ialg.h>
    I didn't find any files like ialg.h in my ccs folder.

    So what should I do now?
    Please tell me.

    Regards.
    Cholnam, Kim./