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.

Can't import CCS 5.3 6670 project into CCS5.4

Other Parts Discussed in Thread: SYSBIOS

Hi

I have made a clean install of:

CCS 5.4.0.00091

MCSDK 03_00_00_10

emupack_keystone2 1.0.0.3

When I attempt to import our existing 6670 project I get:

"Unrecognized product of type 'com.ti.biosmcsdk.pdk.C6670' is required by project '<snip>' - please install at least one product of this type before building this project"

How should I resolve this problem please?

BR

David

  • David,

    These issues are usually common when a specific product is not installed and added to CCSv5 (the error message indicates the PDK cannot be found). However, since this release of MCSDK is still beta, I will move this thread to the C66x Multicore forum as they are more knowledgeable about this software package and can be made aware in case of a product bug that needs to be fixed in time for the production release of this MCSDK.

    Regards,

    Rafael

  • Hi David,

    As Rafael mentioned this seems to be related to CCS not finding a product. 

    Could you please go to the CCS menu 'Window --> Preferences --> Code Composer Studio --> RTSC --> Products' and check whether the path where you have this PDK installed is present here and in fact the PDK is listed under the 'Discovered tools' list. If it is not there, please use the 'Add' button to include the Tool Discovery Path and then restart CCS. 

    Once CCS has restarted, delete your project and import it again into CCS. Now right click on the project, go to Properties, and select 'General --> RTSC --> Products and Repositories' and make sure that the PDK shows up here and is checked. 

    Please let us know what you observe; if the problem persists please include a snapshot of both windows mentioned above.

  • Thanks for your help.  I have partially resolved this issue by doing a clean install of CCS 5.4 followed by an install of MCSDK 2.0.3.15, which my project uses.

    CCS 5.4 complained that xdctools_3_22_01_21 could not be installed due to a dependency error.  It seems that CCS 5.4 installed a later version of xdctools which prevents 3.22.01.21 from being installed.  So I deselected that tool at the auto-discovery stage. Is that reasonable?

    Only problem is that I will be prompted to install xdctools_3_22_01_21 every time I start CCS unless I turn off auto-discovery.

    I then still get a build error with my project:

    js: "C:/ti/uia_1_03_00_02/packages/ti/uia/runtime/UIAMetaData.xs", line 1414: XDC runtime error: ti.sysbios.BIOS: no property named 'getCpuFrequency'

        "C:/ti/uia_1_03_00_02/packages/ti/uia/runtime/UIAMetaData.xs", line 1472

        "C:/ti/uia_1_03_00_02/packages/ti/uia/runtime/UIAMetaData.xs", line 1505

    Is the bottom line that CCS5.4 is not compatible with MCSDK 2.0.3.15 ?

    David

  • Hi David,

    Yes it is reasonable to deselect a later version of XDC tools if you would like to use the earlier version.

    For MCSDK 2.0, the MCSDK team suggests that you upgrade to the latest version of MCSDK 2.0 (BIOS-MCSDK 2.1.2 from http://www.ti.com/tool/bioslinuxmcsdk) that is available for better compatibility with CCS v5.4, since it was regression tested with a beta version of CCS v5.4. The next release of MCSDK 2.0 (upcoming) that the team releases will iron out any further dependency issues with CCS v5.4

  • Hi Uday

    I'm a bit confused. The link you gave points to MCSDK 2.0.0.63.  We are already using MCSDK 2.1.2.6 on another project.

    What is the latest, current MCSDK release that is compatible with CCS 5.4?

    If another release is imminant that will iron out any dependency issues, what will the release number be and when is it expected?

    BR

    David

  • Hi David,

    When you go to the link I provided, you need to select the BIOS-MCSDK for C66x, which is version 2.1.2.6. Here's a direct link: http://software-dl.ti.com/sdoemb/sdoemb_public_sw/bios_mcsdk/latest/index_FDS.html This should point you to MCSDK 2.1.2.6 installers for both Windows and Linux PCs. As this version of the MCSDK release mentions, it has been tested with CCS 5.2. However, if you'd like to use CCS 5.4, you can, and as per the MCSDK team, 2.1.2.6 should work with CCS 5.4.

    You might see that some software components (like BIOS, XDC, etc)  that came with CCS 5.4, have version numbers that are higher than what came with MCSDK. It is OK if those newer versions are discovered. Just make sure you check the right version numbers (MCSDK versions) when you go to the project properties for your CCS project. 

    I believe the next release will be MCSDK 2.1.3, and is supposed to be tested with CCS 5.4 or higher. Currently, this release is anticipated in early Q3.

  • Hi Uday,

    We are waiting for the release of the BIOS-MCSDK 2.1.3 release for about 5 months. Can you inform us about the new schedule of the next MCSDK release for Keystone I devices.

    Best Regards,

    Hasan

  • Hi Hasan

    I believe there's been a delay in this release for BIOS-MCSDK 2.1.3. It is now anticipated end of Q1 and will be released for CCSv5.5.