Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

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.

CCSTUDIO3: Errors in newly imported project

Part Number: CCSTUDIO3
Other Parts Discussed in Thread: C2000WARE

A co-worker zipped 2 CCS 11.1.0 based projects and put them in a shared folder.

I opened CCS and opened a new workspace folder.

Then I copied the extracted projects to the new workspace.

I imported one with no problems.

This was a working project. However when I attempted a build without making any modifications I got this error  and variantsrepeatedly:

"C:/Work_ZipTest/MPGM/mpgm.h", line 321: error #148: declaration is incompatible with "void __error__(char *, uint32_t)" (declared at line 51 of "C:\ti\c2000\Archive\C2000Ware_4_00_00_00\driverlib\f2838x\driverlib\debug.h")
"../ioExpanderDriver.c", line 35: warning #552-D: variable "returnStatus" was set but never used
1 error detected in the compilation of "../ioExpanderDriver.c".

My co-worker in Far Far Away Land does not get these errors. What could be the cause?

Thanks,

John

  • Update:

    I am using C2000Ware 4.1, checking the project product details it looks like he was using 4.0. Don't know if that matters.

    C2000Ware v4.0.0.00

         Install location:           C:/ti/c2000/Archive/C2000Ware_4_00_00_00
         Product-type ID:            c2000ware_software_package
         Dependencies:               <none>

  • John,

    Which example you imported from C2000Ware?

    Just to make sure I understand the sequence, I am reiterating 

    • Imported the C2000Ware example to one workspace : it compiled and build Ok
    • Created a new workspace, and reimported the project from previous workspace without making any change in project or files and it does not compile

    Is my understanding correct?

  • Hi Santosh and Happy Friday.

    I do not know if it was started from an example. But it is a project my coworker in Virginia has worked on for many months.

    It was working for him and he saved it to a zip file on a network folder.

    A little later I retrieved the zip file and extracted the projects.

    I created a new workspace folder while starting CCS 11.1.

    I copied the project into the new folder.

    Next I imported it.

    Then I tried to build it without making any changes.

    The errors mentioned above occurred during the first build attempt.

  • John,

    I will try to reproduce it today. and let you know.

  • John,

    I will request CCS team to take a look. 

  • I will try to reproduce it today. and let you know.

    Santosh - were you able to reproduce the error? I suspect the issue is related to a mismatch with the C2000Ware version.

  • Ki,

    I was not able to reproduce it.

    Here are the sequence I followed:

    • Imported an example led_ex1_blink on MacOS
    • Compiled and built successfully
    • Closed, CCS on Mac, zip the project folder in workspace and then copied to uBuntu Linux machine in tmp folder
    • On Ubuntu machine, I unzipped the project in tmp folder
    • Started CCS 12.2 on uBuntu and reimported the project from tmp.
    • It compiled and built without any issue.

    Regards, Santosh

  • Thanks guys,

    I cannot get the archive directories removed from the discovery path. Should I move the directory out of the c:\ti tree or delete it?

  • I cannot get the archive directories removed from the discovery path. Should I move the directory out of the c:\ti tree or delete it?

    CCS will automatically scan in C:/ti for packages and I believe it will search up to three levels deep (though not sure on this). You can try burying it deeper in C:/ti though perhaps it is best just to move it out completely.

    However, I am still confused why CCS keeps changing the package version on you if you have both version installed. It should always default to the original version first if both are available.