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.

CCS5.4.0.00091_linux bios_mcsdk problem

Other Parts Discussed in Thread: CCSTUDIO

Hello,

I install the new CCS5.4.0.00091_linux but when I try to install bios_mcsdk_02_01_02_06_setuplinux I get the following error:

Operation details
  Your original request has been modified.
    "SYS/BIOS (IDE Client)" will be ignored because a newer version is already installed.
    "Third-Party Components for GMF Runtime" will be ignored because a newer version is already installed.
    "RTSC/XDCtools (IDE Client)" will be ignored because a newer version is already installed.
  Cannot complete the install because some dependencies are not satisfiable
    com.ti.biosmcsdk.pdk.C6670.p2.feature.group [1.1.2.6] cannot be installed in this environment because its filter is not applicable.

Install logs:

If it is a bios_mcsk team bug, please redirect to them.



  • Hi Iiya,

    have you tried adding the package using Window->Preferences->code composer studio->RTSC->products?  This is a better way to manage your mcsdk and bios versions.   There are dependancies you do need to be careful with ... but if specific questions on those arise I recommend the bios forum.

    Also note since you are running linux .. we have found updates and packages should be installed with the same permissions and account used to install ccs.  ie if you installed ccs as user .. also do the udpates as user.  the main thing in consistancy.

    Please keep us informed.

    Best Regards,
    Lisa

  • Hi Lisa,

    i think it is the same problem like in this post:

    Link

  • Hello, Mehly

    You are right. The problem is the same. Exactly. I couldn't install pdk_c6678 library. There is a log when I try to install it. And some other components has the same behaviour.

    Operation details
      Cannot complete the install because some dependencies are not satisfiable
        com.ti.biosmcsdk.pdk.C6678L.p2.feature.group [1.1.2.6] cannot be installed in this environment because its filter is not applicable.

    Should I open the new one task?

  • Hello, Lisa,

    Thank you for your help. But could you try to reproduce the problem on you own environment?

    You need to do the following steps for that:

    Remove old version Code Composer
    Install the brand new version of CCS (5.4.00091 for now)
    Install the last one bios-mcsdk version
    And try to add pdk_c6678 in RTSC products and get an error

    With best Regards, Ilya.

  • I try to install it on Windows 7 system and have success. Everything is fine. I suggest that it's a bug in linux build.

  • Hi Ilya,

    have you tried from Window-PReferences-code composer studio-rtsc-products?

    I only have Ubuntu here so have limited resources to try this myself.  I can confirm that we are investigating mcsdk update issues at the moment but hopefully an independent installation should be fine.

    Please keep us informed.

    Best Regards,
    Lisa

  • Hello Lisa,

    Yes, I tried it. But have no result. Some products didn't add in product list some one successfuly add. Such as ndk, pdk, was failed.

    With best Regards, Ilya

  • I also hit the same problem. I am using UBUNTU 12.04. Anyone found the solution. 

  • Manisha, Llya, could you try to install in another path? not the default one which if I remember correctly was c:/TI... you can try to install on your user (for example c:/home/pcarrillo/ti..). Let me know if this helps.

    thanks,

    Paula 

  • Paula,

    I have installed it in my /home/user/MCSDK dierctory and not the default ti directory and it shows the error mentioned above when launching CCS.

    Regards,

    Manisha

  • Hello, Paula

    We both use Linux. I tried to set up in /home/username/ti.
     

  • Hello everyone,

    after some digging here I have had it confirmed that in Linux some mcsdk components have win32 filters in P2 metadata that prevent them to be installed on anything other than windows.

    This is expected to be fixed in coming versions.

    Best Regards,

    Lisa

  • Is there any news concerning this problem?

    I cannot install the pdk on CCS5.4 linux version which render the platform useless...

    Sylvain.

  • Hi Sylvain,

    This is fixed in the upcoming BIOS-MCSDK 2.1.3 release, which is currently targeted for the  late August-September timeframe.

    Best Regards,
    Lisa 

  • Hi Lisa,

    Are we able to modify these filters in the current distribution? Is there another way to work around this problem?

    Thanks,

    Chad

  • Hi Chad,

    sorry, there is no existing work around.   The next version, as I mentioned will be having a fix built in so this will disappear when that version is ready for release.

    Best Regards,

    Lisa

  • hello lisa,

    I also have to build my environment under linux. but I got exactly the same problem. is there the update version?

    if yes could you please send me the link. I cant find it on the website.+

    Best regards,

    Wendy

  • HI Wendy,

    if you can hold on until next week, I believe v5.5 should be out.

    Best Regards,

    Lisa

  • Hello,

    we have the same issue here. We installed CCS and MCSDK for keystone devices on Ubuntu 12.10 64 Bit and cannot add the discovered products (at least one with the message of an unsatisfied environment/filter).

    Any solution or workaround would be great. In case of an update we'd be interested in the steps we have to take now (what do we have to install/uninstall/update in which order and in which version ? CCS ? MCSDK ? Anything else ?)

    Would it be recommended to better develop TI software on Windows instead of Linux ? We're free to choose and if Windows has a better test coverage we can switch the OS.

    Thank you,
    Roelof Berg

     

  • Hi Roelof,

    First I would always recommend a fresh post.  I would also recommend, if it makes no difference to use to use the Windows version.  We are usually always ahead on that version with features and support.

    V5.5 which should have the MCSDK dependency items fixed, will be released this week.  I would suggest starting fresh on windows with that once it is released.

    Best Regards,
    Lisa 

  • Hi Lisa,

    thank you for the fast response. I installed CCS V5.5.0.00077 and see the error "com.ti.biosmcsdk.feature.group [2.1.2.6]" cannot be installed in this environment because the filter is not applicable". We will follow your recommendation to move to Windows.

    Best Regards,
    Roelof

     

  • Hi Lisa.

    This problem was not fixed with CCS V5.5.0.00077 for linux.

    For some reason, we can't use Windows here. Is there any workaround exist other then downgrade to CCS 5.3?

    Update.

    As we didn't see any support from CCS team to resolve for this issue, while this component is really impotent to build projects for c66x architecture, I tried different ways and finally managed to install MCSDK 2.1 for linux version of CCS V5.5.

    To do that, I simply replaced some files in 'eclipse' directory with ones from MCSDK 1.0 and made some changes according to my understanding of those Eclipse files. On the next start CCS warned on component unsigned contents, but after confirmation installed MCSDK without any filter error.

    Regards.

    Dmitry.

  • Dmitry,

    thanks for the update. How did you obtain the MCSDK 1.0 files? I attempted to download the setup for that version but actually received the 2.1 setup.

    Thanks,

    Dan

  • Hi there,

    I am having the same problem... I don't see how it can be marked solved as the latest CCS still suffers from the same issue

  • Hi Lisa,

    I've gone through a fresh install with CCS5.5.0.77 and (patched) MCSDK 2.1.2.6. It would seem that none of the MCSDK components are compatible with CCS in Linux. Are you able to confirm? Any suggested workaround?

    Thanks,

    Chad

  • Hi Lisa,

    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 all!

    It seems that the problem hasn't been solved so far. Is it going to be fixed at all? By the way it is not always possible to switch from Linux to Windows or vise verse. 

  • Hi All.

    Just to inform, that the problem is still here with latest CCS v6 release (CCS6.0.0.00190_linux).

    Dmitry

  • Hi All,

    I can confirm that MCSDK for Keystone I can not be used with latest CCSv6 release under linux.

    (@ Windows only NDK is not working - I think this is another problem an it exists for linux and windows)


    by the way see here http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/297968.aspx

    There is a hint to remove ws="win32" line from several .xml file.

    @TI stuff this problem remains since 1 year or longer!!!
    Is there a bug report in your internal database and can you support this link here.

    Best regards
    Mehly

  • Hi.

    Mehly said:
    There is a hint to remove ws="win32" line from several .xml file.

    I tried this. It didn't help for me.

    Regards

    Dmitry.

  • Hi,

    also ws="gtk" is not working ;-(

    Best regards
    Mehly

  • After a couple of hours of hair-tearing...
    The basic advice to remove the ws=win32 flags from the feature.xml and plugin.xml files (for mcsdk and pdk) as per [url=http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/297968/1040381.aspx#1040381]this post[/url] is correct.
    However Eclipse seems to maintain a private cache of information from these files (I haven't found it yet!) and thus if they are corrected after a failed installation attempt Eclipse does not pick up the changes.
    There is a workaround, which is to create a subdirectory of in your TI installation directory, and move the now-modified mcsdk_2_01_02_06  pdk_C6678_1_1_2_6 directories into it. Then tell CCS to scan this directory for new products.
    In CCS6 which I'm using, this can be done in the Preferences window (Window->Preferences), under Code Composer Studio->RTSC->Products: add your new directory to the Product Discovery Path.

    I believe that it should be possible to remove the dud repositories from Eclipse - which most likely eliminates the need to create a subdirectory - but haven't yet found a way to do so.

  • Mark Honman said:
    The basic advice to remove the ws=win32 flags from the feature.xml and plugin.xml files (for mcsdk and pdk) as per [url=http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/297968/1040381.aspx#1040381]this post[/url] is correct.
    However Eclipse seems to maintain a private cache of information from these files (I haven't found it yet!) and thus if they are corrected after a failed installation attempt Eclipse does not pick up the changes.

    To clear the Eclipse cache run "ccstudio -clean".

    I found the following helped with mcsdk_2_01_02_06 with CCS v6.0.1 under Linux:

    1) Edit the mcsdk_2_01_02_06 .xml files to remove all the ws="win32"

    2) Run "ccstudio -clean"

    3) Scanning the mcsdk_2_01_02_06 products then removed the errors of the form:

    Operation details   Cannot complete the install because some dependencies are not satisfiable     com.ti.biosmcsdk.pdk.C6678L.p2.feature.group [1.1.2.6] cannot be installed in this environment because its filter is not applicable.

    However, the NDK still won't install with the following error reported:

    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:/tmp/signatureFile2599926968597614314.jar
          Invalid content:plugin.xml
          The file "plugin.xml" in the jar "/tmp/signatureFile2599926968597614314.jar" has been tampered!

    I get the same error trying to install NDK 2.21.1.38 under both Windows and Linux, so must be a different problem (as has already been noted by others in this thread)

  • Thank you so much. This has been really helpful. I had the same problem and this fixed them. Nice to know that someone is on the ball with this.