• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 54 subscribers
  • Views 1310 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.

CCSv4 project migration problem: ERROR: Cannot open command file

Eddie3909
Guru 10385 points


Hi

I imported my CCSv3.3 project to CCSv4 and it compiles with the error below. I

C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake -k all
'Building file: ../src_tracker/ByteOrder.c'
'Invoking: C6000 Compiler'
"C:/Program Files/Texas Instruments/C6000 Code Generation Tools 6.1.12/bin/cl6x" -mv64+ -g -O3 --fp_mode=strict --define="_DEBUG" --define="CHIP_DM648" --include_path="C:/Program Files/Texas Instruments/C6000 Code Generation Tools 6.1.12/include" --include_path="C:/Program Files/Texas Instruments/xdais_6_23/packages/ti/xdais" --include_path="C:/CCSTUD~1.3/C6000/csl/include" --include_path="../inc" --include_path="../inc_tracker" --include_path="C:/dvsdk_1_11_00_00_DM648/pspdrivers_1_10_00/packages" --include_path="C:/dvsdk_1_11_00_00_DM648/pspdrivers_1_10_00/packages/ti/sdo/pspdrivers/soc/dm648/dsp" --include_path="C:/Program Files/Texas Instruments/ccsv4/c6400/dsplib/include" --include_path="C:/Program Files/Texas Instruments/ccsv4/c6400/imglib/include" --include_path="c:/dvsdk_1_11_00_00_DM648/edma3_lld_1_05_00/packages" --include_path="../config/xdcconfig/package/cfg" --quiet --diag_warning=225 --sat_reassoc=off --fp_reassoc=on --mem_model:const=data --mem_model:data=far_aggregates --obj_directory="../obj" --cmd_file="../src_tracker/=C:/Work/CloudCap/DSP/TASE_VPS_LT_DSP/VPS-CCSv4.0/config/xdcconfig/compiler.opt" --preproc_with_compile --preproc_dependency="src_tracker/ByteOrder.pp"  "../src_tracker/ByteOrder.c"
>> ERROR: Cannot open command file '../src_tracker/=C:/Work/CloudCap/DSP/TASE_VPS_LT_DSP/VPS-CCSv4.0/config/xdcconfig/compiler.opt': Invalid argument
'Finished building: ../src_tracker/ByteOrder.c'

This is most likely due to the migration log error:

!ERROR: This project has DSP/BIOS content. No DSP/BIOS tools are currently installed. Please install DSP/BIOS tools prior to migrating this project.

So I installed the BIOS:

12/15/2009  03:11 PM    <DIR>          .
12/15/2009  03:11 PM    <DIR>          ..
12/10/2009  12:29 PM    <DIR>          bios_6_20_02_43
12/15/2009  03:12 PM    <DIR>          bios_6_21_00_13
10/29/2009  05:43 PM    <DIR>          C6000 Code Generation Tools 6.1.12
12/10/2009  12:36 PM    <DIR>          ccsv4
12/10/2009  12:30 PM    <DIR>          ipc_1_00_03_55
12/10/2009  12:36 PM         3,506,176 revert.dat
09/16/2009  02:07 PM         3,075,507 revert.exe
07/31/2009  12:33 PM    <DIR>          SoCAnalyzer1_1
12/10/2009  12:32 PM    <DIR>          xdais_6_23
12/10/2009  12:32 PM    <DIR>          xdctools_3_15_04_70

But I still get the same "Cannot open command" error! Its strange that it won't build the xdc stuff either when I select "Rebuild Active Project".

Is there a way to tell if CCSv4 can see the DSP/BIOS install (like CCSv4 had with its "component manager")

Any help would be welcome.

Cheers

 

  • 0
    TI__Guru* 84285 points

    It looks like something went wrong with the import.  It looks like two distinct options got mangled together, corrupting the pathname of the command file.  Try reviewing all of the pathnames in your options.

  • 0 in reply to Archaeologist
    TI__Guru**** 162945 points

    There is a way to tell CCS where BIOS is located.  We should create a wiki topic on it but it is almost exactly like the procedure for telling CCS where a new compiler is, just select RTSC in the preference dialog instead of Code Generation tools.

    http://tiexpressdsp.com/index.php/Compiler_Installation_and_Selection

     

    John

  • 0 in reply to JohnS
    Guru 10385 points

    Hi

    Thanks for the info. I checked the RTSC and the nothing was selected. I then selected the BIOS version and XDC version (I didn't select an interprocessor communication version since I'm on the dm648).

    I tried the build all and it still didn't compile xdc or rtos (it proceeded to build the swap byte.c file as in my first discussion item.

    I then tried re-importing the .pjt file (after deleting all the CCSv4 generated files in the folder) and it said ("xxxx project already exists in workspace folder). Since I couldn't find where that workspace folder was, I shut down CCSv4, reopened it and selected a different folder.

    This time when I import I get:

    "Unexpected exception encountered whil migrating project(s). Please see the Eclipse log file for details."

    I searched the ccsv4 install directory for *.log and couldn't find anything other than the install.log file

    !CONFIGURATION 1260478224441 Thu Dec 10 12:50:24 PST 2009
    !ACTIVITY 1260478279217 Dec 10, 2009 12:51:19.217 file:/C:/Program Files/Texas Instruments/bios_6_20_02_43/eclipse/ site-install success
    !ACTIVITY 1260478279217 Dec 10, 2009 12:51:19.217 file:/C:/Program Files/Texas Instruments/xdctools_3_15_04_70/eclipse/ site-install success
    !ACTIVITY 1260478279217 Dec 10, 2009 12:51:19.217 file:/C:/Program Files/Texas Instruments/ccsv4/eclipse/ site-install success
    !ACTIVITY 1260478279217 Dec 10, 2009 12:51:19.217 file:/C:/Program Files/Texas Instruments/ipc_1_00_03_55/eclipse/ site-install success
    !ACTIVITY 1260478279217 Dec 10, 2009 12:51:19.217 file:/C:/Program Files/Texas Instruments/xdais_6_23/eclipse/ site-install success

    !CONFIGURATION 1260918875762 Tue Dec 15 15:14:35 PST 2009
    !ACTIVITY 1260918875621 Dec 15, 2009 15:14:35.621 file:/C:/Program Files/Texas Instruments/bios_6_21_00_13/eclipse/ site-install success

    Should I try CCSv4.1 beta? If should, do I uninstall 4.0 or will the ccsv4.1 installer take care of that detail?

    Thanks again for your help. I had hoped that this wouldn't be a painful migration.

    Update: I created a new image of my ccsv3 project files and tried the import from scratch. I got the same exception.

     

  • 0 in reply to Eddie3909
    TI__Guru**** 162945 points

    Eddie,

    I think part of the problem is that you are importing a BIOS5.x based project and only have BIOS6.x installed.  CCSv4 includes installs for both BIOS5.4 and BIOS6.2.  When importing a CCSv3.3 project it normally automatically uses BIOS5.4 but I think in your case it is not installed so things start to get messed up.

    Where to start from here?  A reinstall would likely be a good idea.  You could try the CCSv4.1 beta if you want, you can even install it in a separate directory.  If you choose to uninstall CCSv4 first, after the uninstall delete the main directory to clear out anything left behind.  At this point I would suggest just installing 4.0.2 and then in Jan update to 4.1.

    Remember when installing don't uncheck the boxes for BIOS5.40 or XDC.  You might as well install BIOS6 as well just in case at a later date you want to update to that.  I don't recommend trying to do it all in one shot.

    Other notes:

    • If you want to reimport the same project you either need to delete from your workspace or switch workspaces.  You can do that from the File menu.  A workspaces is essentially a folder.  If you are doing a new install when it prompts you for a workspace the first time you launch CCS just pick a new folder for your workspace.
    • There is a good topic on the mediawiki called Eclipse Concepts that explains a lot about how some things work in CCSv4.

    Regards,

    John

     

  • 0 in reply to JohnS
    Guru 10385 points

    Hi

    I'm going to try installing BIOS5.4 first, change my ccsv3.3 project to use it, then import it to ccsv4.

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/index.html

    Also going to review the Eclipse Concepts

    http://tiexpressdsp.com/index.php/Eclipse_Concepts

    Update to follow shortly.

    Cheers

  • 0 in reply to Eddie3909
    Guru 10385 points

    Dang. Attempt #1 didn't work. (install bios 5.41.xxx and update ccsv3.3 project to 5.41.xxx)

    I installed bios 5.4 for ccsv3.3 and v4.0, changed ccsv3.3 to use bios 5.4 and saved the project file. Then imported into ccsv4.0 and at one point I thought I had success because it asked me to select the bios5.4 (before it hadn't). But after several more "next" selections, I got the same exception.

    Time to uninstall ccs4.0 and re-install.

    Cheers
    Eddie

  • 0 in reply to Eddie3909
    Guru 10385 points

    Dang again. Attempt #2 failed. (re-install ccsv4)

    Uninstalled and re-installed CCSv4. Version: 4.0.2.01003 

    Verified bios 5.41.xxx was selected in RTSC.

    Imported project and got the same exception. ARG!

    Now to try CCSv4.1 (thats a LLLLOOOOOOONNNNNGGGGG download)

    I tried attached my ccsv3 .pjt file. You could you try importing it (I don't it gets to the point where it will notice missing files)

    But using the "insert media" button just hangs the pop up window when I try inserting the .pjt file.

    Cheers

  • 0 in reply to Eddie3909
    Guru 10385 points

    Attempt #3 (install ccsv4.1)

    This time when I started ccs, I thought I'd use the default workspace and guess what, no EXCEPTION when importing the project! Yeah!

    But if I use the folder directly above the folder that has my .pjt project, CCS crashes with an exception. Thats a nice feature.

    It must be something with the eclipse environment that I don't understand.....yet.

    Anyhow, now to get rid off all the migration.log errors about -vc6 errors and it not being able to find my xdcpaths.dat and .cfg file. (this certainly ain't an easy import).

  • 0 in reply to Eddie3909
    TI__Guru**** 162945 points

    Eddie,

    If you were importing before into a directory above where your pjt was located what will happen is that Eclipse includes all the subdirectories in your project.  Basically he project environment is file system based, if there is a something in your project folder or below then it is in your project unless you explicitly exclude it.  Takes a while to get used to.

    John