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.
One of our developers is getting an error during build: "This project was created for a device-variant that is not currently recognized: TMS320C28XX.TMS320F2808. Please install the device-variant descriptor, or migrate the project to one of the supported device-variants."
This is odd because we store projects on SVN. It builds fine on two other development boxes, but when he pulls the files, including the .cdtproject, .ccsproject, and .cdtbuild, he gets an error. This has worked fine in the past. He's tried to build versions of the software that he could previously build with the same result.
From the other posts with this error, we've tried restarting, clearing the workspace and re-importing the project, and we've verified that the .cdtbuild file is the same as what compiles on the other boxes. (We've also pulled the files from SVN again, just to be sure)
We're on 4.2.3.00004, and we cannot upgrade.
Philip Haubrich said:"This project was created for a device-variant that is not currently recognized: TMS320CS8XX.TMS320F2808
Do you know which version of CCS the project was originally created with?
On the machines where this same project builds fine, is the same verion of CCS installed - 4.2.3?
Did you try both deleting the .metdata folder as well as starting out with a new workspace as recommended here?
http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#General_IDE
Yep, that was a typo. It was indeed "TMS320C28xx.TMS320F2808".
In the .cdtbuild file we have:
<listOptionValue builtIn="false" value="DEVICE_CONFIGURATION_ID=TMS320C28XX.TMS320F2808"/>
I'm not sure what version the project originated on, but it's been built using 4.2.3.00004 since I signed on, which we're all using.
Yes, we tried deleteing the .metdata. We also deleted/re-imported the project.
We haven't tried launching with -clean though.
...
And I'd love to try it, but he decided to re-install CCS4. Which solved the issue and he can build now.
Thanks for the help, but apparently we're good to go.
Thanks for the update and glad to hear you're good to go after the reinstall.