• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 1065 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/TMS320C6657: Problem with pdk_c665x_2_0_6

Alex Kozlov
Prodigy 165 points
Part Number: TMS320C6657

Tool/software: Code Composer Studio

Hi,

I'm having trouble after trying to switch from "pdk_C6657_1_1_2_6" to "pdk_c665x_2_0_6".

After trying to compile my project with pdk_c665x_2_0_6, I'm getting the following error:

"

subdir_rules.mk:12: recipe for target 'build-1779453503-inproc' failed

xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND: C:\ti\pdk_c665x_2_0_6\packages\ti\platform\evmc6657l\package.xdc found along the package path, but no schema file was found. Ensure that the package 'ti.platform.evmc6657l' is completely built.

"

I am using CCS 7.1.0.00016, as required by pdk_c665x_2_0_6...

I got the same error even when i tried to use pdk_c665x_2_0_0, so i'm guessing it's not a bad installation of the pdk...

Please help me solve this issue.

Thanks,

Alex

  • 0
    TI__Guru** 114410 points

    If you compare the platform package in the 2 PDK versions, you will notice that the platform library doesn`t contain the RTSC packaging files as the older library.

    Option 1: build the XDC package using 

    cd pdk_c665x_2_0_6\packages\ti\platform\evmc6657l

    <SDK_INSTALL_PATH>\xdctools_3_32_01_22_core\xdc release XDCPATH=<SDK_INSTALL_PATH>\bios_6_46_04_53\packages;<SDK_INSTALL_PATH>\xdctools_3_32_01_22_core\packages;<SDK_INSTALL_PATH>\pdk_c667x_2_0_5\packages

    this generates the package and the required schema files. 

    Refer: http://rtsc.eclipse.org/docs-tip/Command_-_xdc#Building_a_package

    Option 2: 

    To bypass this issue can you remove the  xdc.usModules from the configuration file and manually link in the platform library to you project.

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Prodigy 165 points
    Hi Rahul,
    I used option 2 and this solved my issue. Thank you!