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.
Tool/software: Code Composer Studio
Hello,
I have tried to install and use the (currently) latest CCS version 7.1.0.00015.
After all installations completed, when i imported projects for Cortex M4 (Using TDA3xx SOC) i get the following warning:
“Target name 'ti.targets.arm.elf.M4' could not be verified. Your project may not build as expected.”
With CCS version 7.0.0.00043 everything seems to be OK and NO warnings are issued.
Can anyone help resolve this issue with version 7.1.0.00015 ? (is it some bug in the new version)
Thanks,
Guy
Guy Mardiks said:After all installations completed, when i imported projects for Cortex M4 (Using TDA3xx SOC) i get the following warning:
“Target name 'ti.targets.arm.elf.M4' could not be verified. Your project may not build as expected.”
With CCS version 7.0.0.00043 everything seems to be OK and NO warnings are issued.
Could you compare the TI-RTOS products installed by both versions of CCS to see if they match up? You can check this under Window->Preferences->Code Composer Studio->Products. My suspicion is that a required RTSC/TI-RTOS package is not installed/detected in CCS 7.1.0. If that is the case you can have CCS rediscover products from that dialog, or if the TI-RTOS product is in a path that is not already listed under Product Discovery path, you can add the path to it and then have CCS rediscover.
Let us know if this helps.
Hi,
Specifically for the project you mentioned, it seems to have been built with much older tools than the ones present in the Vision SDK.
To verify this, the document <nsp_gmacsw_4_13_00_00_release_notes.html> under the directory VISION_SDK_02_08_00_00\ti_components\networking\nsp_gmacsw_4_13_00_00 shows the dependencies of this package. It states that several components are older than the ones installed by this SDK:
- SYSBIOS 6.40.03.39 was used (the SDK ships with SYSBIOS 6.42.02.29).
- XDCTools 3.30.03.47_core (the SDK ships with 3.31.02.38_core).
Also, when importing the project I get an error that the component UIA 2.0.0.28 is not installed.
Therefore for this project to be properly built it seems you will have to manually download and install these components separately.
We at the CCS forum can't necessarily explain why this project's dependencies are so different than the components provided with the SDK, but I will try to contact some people that could make additional comments about this.
I apologize for the inconvenience,
Rafael
P.S. Just for your information and if you haven't done so, if you intend to create projects inside CCS with the SDK you are using, you have to add the products to your environment the following way.
Go to menu Window --> Preferences, navigate to the path below and add the highlighted directories:
In the above screen, click on Rediscover and the new products will be shown. Select the highlighted ones below and click on Install:
CCS will ask to be restarted. After doing this, go back to menu Window --> Preferences, go to the options below and add the path highlighted.
Now your CCS has all the necessary products to allow building SDK projects.
Guy,
Sorry about the delay in getting back to you on this.
In summary, the warning you are seeing is due to a change made in CCS 7.1, whereby the User Interface tries to verify the project's target/platform name against a list of known names and if it cannot be verified then it shows the warning. The warning, in itself, does not necessarily mean that the target-name is incorrect. Especially in this case where we are looking at a known good project, it is likely showing up because the known target-names list it is checking against is incomplete. Hence I would treat the warning as harmless and ignore it.
We had some internal discussions about this, and since this appears to be causing some confusion we have decided to remove the warning in the next release of CCS.
Thank you again for your patience while we sorted out the details of this issue.