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.

MCSDK and CCS 5.4

 Hi,

I have a problem with MCSDK installation.

I've just installed CCS 5.4 and after that MSCDK for C66xx (released on: 2/8/2013). But after launching CCS program finds new products and can't install it:

"An error occurred while collecting items to be installed
session context was:(profile=epp.package.cpp, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Problems downloading artifact: osgi.bundle,com.ti.rtsc.NDK.product_2.21.1.38,2.21.1.38.
File has invalid content:C:\Users\1\AppData\Local\Temp\signatureFile1217961879339858267.jar
Invalid content:plugin.xml
The file "plugin.xml" in the jar "C:\Users\1\AppData\Local\Temp\signatureFile1217961879339858267.jar" has been tampered!"

 I've tried to install even on two different computers and I've had the same result.

I would be pleased if you could help me.

 

Best Regards,

Kathleen.

 

  • Kathleen,

    I have faced some glitches when installing the MCSDK 2.1.2.6 on my CCSv5.4 - a few threads explain this in details:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/252192.aspx

    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/265638/934274.aspx#934274

    What I found is that the NDK package supplied with the base MCSDK is incompatible with v5.4, but the patch installs a slightly newer version where the incompatibility ceases to exist.

    Hope this helps,

    Rafael

     

  • Hi Rafael

    Thanks for reply. This links say that MCSDK 2.1.2 is compatible with CCS v5.4. I installed MCSDK 2.1.2.6 from the link below (which is given in the links you gave)

    http://software-dl.ti.com/sdoemb/sdoemb_public_sw/bios_mcsdk/latest/index_FDS.html

    Furthermore, this version of MCSDK was installed correctly on one computer and wasn't on another and the only difference I can see is operation system. First is 64-bit windows 7 and second is 32-bit. I don't think it has some influence on installation but I have no idea what's going on.

    Best regards,

    Kathleen

  • Kathleen,

    Kathleen Pn said:

    Furthermore, this version of MCSDK was installed correctly on one computer and wasn't on another and the only difference I can see is operation system. First is 64-bit windows 7 and second is 32-bit. I don't think it has some influence on installation but I have no idea what's going on.

    I am not 100% sure why the different installs are yielding different results, as the datapath size of the OS has very little to do with the Product Discovery tool. However, since CCSv5.3 does not show the NDK error (at least on my installation), I can't help but think the CCS installed in the 32-bit machine was either v5.3 or it was updated from v5.3 to v5.4 - can you confirm that?

    All that said, this issue is not critical: as the release notes for the MCSDK patch mention, to work with CCSv5.4 you simply need to use the newer NDK instead.

    Check the attached screen to see how to get rid of the invalid product discovery message every time you open CCS.

    Hope this helps,

    Rafael

  • Rafael,

    Yes, it was my fault, I thought that the installation of the latest versions of CCS and MCSDK causes the installation of the latest version of NDK so I didn't check it. But it is not.

    No, I can't confirm that, there wasn't any CCS on that machine and I installed CCS 5.4 for sure. But the problem has solved.

    Thank you!

    Best Regards,

    Kathleen

     

     

     

     

     

     

     

  • Kathleen,

    Thanks for reporting back your conclusions.

    Cheers,

    Rafael