• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 408 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.

Original question:

CODECOMPOSER: Building example project for CC2642 fails with 'Can't find the platform package 'ti.platforms.simplelink''

CODECOMPOSER: CC2652 ti.products.simplelink not found

Seth Hammond
Prodigy 111 points

Part Number: CODECOMPOSER

Hi,

I am trying to use the latest version of the CC2652 SDK but am finding problems when trying to build. When I use the older version (6.10.0.29) I am able to build, but when I change to the latest version (6.40.0.13) I encounter the following error:

Description Resource Path Location Type
xdc.tools.configuro: Error: Can't find the platform package 'ti.platforms.simplelink'. TI platforms are no longer shipped as part of XDCtools (C:\ti\xdctools_3_62_01_15_core). Please ensure you are either using a pre-3.30 version of XDCtools or you have added a product that includes your platform support along the path 'C:/ti/simplelink_cc13xx_cc26xx_sdk_6_40_00_13;C:/ti/xdctools_3_62_01_15_core/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_40_00_13/source;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_40_00_13/kernel/tirtos/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_40_00_13/kernel/tirtos7/packages;C:\ti\xdctools_3_62_01_15_core/packages'. Check that this path names a directory containing the necessary platform support and that the platform name is properly spelled. .xdchelp /ble_igsprinkler line 52 C/C++ Problem

I do not change the XDCtools at all and just change back to the old version and it works just fine.

Here are some screenshots:

This works:

This does not:

Let me know what you all think, I appreciate the responses.

  • 0
    TI__Guru** 101570 points

    Hi,

    Thank you for your question.

    The issue may be caused by an invalid path passed to the tool chain. Actually the SDK and XDC paths get merged leading to this bad include

    I am not sure where the issue should be corrected, but you can start by double checking project Properties > Resource > Linked Resources > Path Variables. Then you can verify in Properties > Build > Arm Compiler > Include Options

    Please let us know your findings.

    Best regards,

  • 0 in reply to Clément
    Prodigy 111 points

    Hi,

    Thank you for the response. Not sure how all these paths got the way they are but clearly they are messed up. What we ended up doing is creating a new project and porting over to it with the new SDK. Looks like all is working now and we upgraded to CCS12.

    Thanks!