• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 2529 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Got errors while building the migrated CCS4 projects ( from old CCS v3.3 DM6437 project)

Weilong Chen
Intellectual 390 points
Other Parts Discussed in Thread: CCSTUDIO

CCS newbie here.

Got 2 errors while building the migrated CCS4 projects ( from old CCS v3.3 DM6437 project).

1) > ERROR: Cannot open command file '.../xdcconfig/compiler.opt': Invalid argument

There is a "xdcconfig" folder in the old project but not in the migrated project folder.  The files in " xdcconfig" were generated by CCS V3.3, am I right? The above "compiler.opt" file is invoked by the ".opt" files in the "Debug" folder. 

 

2) ".../project/src/video_preview.c", line 23: fatal error: could not open source file "ti/sdo/ce/CERuntime.h"

I already included the searching path of the above file, but still got the this error.

 

Appreciate your help!

 

 

  • 0
    TI__Guru**** 169754 points

    Hi,

    Just checking: are you trying to build the example <dm6437_demo.pjt> located in the directory \dvsdk_1_01_00_15\dm6437_demo_1_30_00?

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 390 points

    Hi Rafael,

    No. I am building an "working" dm6437 pjt from CCS v3.3.  

     

    The pjt is from another party. Actually I also have problems with the CCS v3.3 installed.  I can build the pjt and load program into the dm6437 evm on CCS v3.3. But I cannot run/debug into the source code. I even installed CCS v3.3 on different PCs to try out. All have such problem. That's why I tried to migrate it to CCS4. Surprisingly I can run/debug on CCS4 by loading the old .out file. But I cannot build the pjt on CCS4.

    frustrated.

     

  • 0 in reply to Weilong Chen
    TI__Guru**** 169754 points

    Hi,

    I don't know for sure why CCSv3.3 is not able to debug your code, especially because you already tried in several computers.

    Also, without the project it is very difficult to pinpoint the exact cause why CCSv4 is not able to import it correctly. The reason I mentioned the DM6437 dvsdk project is because back then these projects had so many dependencies and intricacies to their structure that some developers adopted the option of building their code in 3.3 and debugging it in v4.

    The fact that v4 is able to load the .out file is not surprising; the executable binaries are independent of the IDE and therefore can be used across versions. The only thing I would do to debug is reference the source code in v4 to perform proper source-code debugging. The source files can be added after the code is loaded to the target - check slide 35 of the Tips and Tricks presentation (link here)

    Hope this helps,

    Rafael

     

  • 0 in reply to desouza
    Intellectual 390 points

    Hi Rafael

    Thanks for your reply and helpful information provided.

    Since there are a lot of dependencies as your mentioned, I think it would be better to use ccs v3.3 for our development. 

    I found that I can debug the test code under c:\CCStudio_v3.3\boards\evmdm6437_v2\tests. But I have problems with example code under c:\dvsdk_1_01_00_15\examples.

    Could it be related to DSP/BIOS? I don't know how to troubleshoot this. I reinstalled CCStudio_v3.3 and dvsdk again, problem still cannot be resolved.

     

    Weilong

     

  • 0 in reply to Weilong Chen
    TI__Guru**** 169754 points

    Weilong,

    The DVSDK examples are more involving and require a lot more resources from the device itself, therefore I would first make sure to include a GEL script in CCSetup to perform proper initialization of the device typically located at:

    C:\CCStudio_v3.3\boards\evmdm6437_v2\gel

    My second step would be to build a simpler DSP/BIOS example and see if it runs fine in your board; they can be found typically at:

    C:\CCStudio_v3.3\bios_5_31_02\packages\ti\bios\examples

    After checking that you can properly run this example, then I would start debugging the DVSDK example itself. Check if you can reach main(), as lots of initialization routines take place before that, and then start calling the functions one-by-one until you reach a state where you find an unexpected output or behaviour of your system.

    I would also carefully check the DVDP Getting Started Guide to make sure all the steps for rebuilding the demo target software are being closely followed - including DIP switches on the board (a commonly overlooked detail).

    If the demo code does not properly work, I would ask in the Embedded Software forum as they are more knowledgeable about the software itself.

    Hope this helps,

    Rafael