• State Resolved
  • Locked Locked
  • Replies 20 replies
  • Subscribers 55 subscribers
  • Views 1869 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.

CCS: trouble with adding NDK to existing project

Richard Dobbis
Intellectual 460 points
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

using: CCSv5.5

bios: 6.35.4.50 (C6674)

I am trying to add the NDK to a project that has been building and in use (without ethernet) for quite a while. I am trying to match the version of NDK and NSP correctly for the BIOS I am using. I am limited in my choices but the problem is more related to CCS initially finding and/or loading the package.

First, I downloaded NDK 2.22.03.20 and uncompressed into my top level directory C:\ti - and then started CCS. CCS did not find the new package as I did not get a window, allowing me to choose to install the package, nor does the package show up in my properties -> RTSC list. 

Then I downloaded NDK 2.21.2.43, unzipped it, and started CCS. CCS found the new package and loaded it just fine!! The problem is that the matching NSP 1.10.1.6 will not load due to an error (I downloaded it, unzipped it, and CCS finds it, so...). The error follows:

Problems downloading artifact: osgi.bundle,com.ti.rtsc.NSP.product_1.10.1.06,1.10.1.06.

File has invaled content:C:\Users\rdobbis\AppData\Local\Temp\signatureFile1750817143005571917.jar

Invalid contect:plugin.xml

The file "plugin.xml" in the jar "C:\Users......." has been tampered!

Any help would be appreciated!!

Richard

  • 0
    Guru 26200 points
    Hello Richard,

    I am not familiar with CCS5.5.
    CCS 7.x and 8.x has Windows -> Preferences -> CCS -> Products and than "Rediscover..." feature.
    Do you have / did you tried this feature?

    Which java version do you have?
  • 0
    Guru 26200 points

    In case of CCS6.x I see

    Windows -> Preferences -> CCS -> Products and than "Search Now..." feature.
    Using it, no issue to discover NDKs.

    NSP 1.10.1.6 is a real issue.

    I head no issue installing NSP 1.10.2.9.
    According to its Release Notes:

    you should find a path you need.

    I do recommend to escape from CCS5.5 .

  • 0 in reply to Tomasz Kocon
    Intellectual 460 points
    The 'Refresh' feature is also present in CCSv5 - it is essentially the same thing that is run when I startup CCS, so as expected, I ran the 'Refresh' and it did NOT find the NDK in question (but did find the NSP that won't load properly.
    Java 8 Update 181
    Thanks for your time!!
    Richard
  • 0 in reply to Richard Dobbis
    Guru 26200 points
    I do recommend you to move to a newer CCS.
  • 0 in reply to Tomasz Kocon
    Intellectual 460 points
    Thanks Tom, I don't have the time right now.
  • 0 in reply to Richard Dobbis
    Guru 26200 points

    No time does not resolve your/any issue.
    Sorry for saying that.

  • 0 in reply to Tomasz Kocon
    TI__Guru**** 161600 points
    Hi,

    This seems to be an issue with the versions of the SW. NDK 2.21.2.43 corresponds to a specific BIOS, CCS, XDCTools version, this should be noted in the download link of the NDK (or its release notes). You need to migrate your project to the matching tools versions.

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Guru 26200 points
    Hello Yordan,
    NSP 1.10.1.6 is problematic.
    It cannot be installed.
  • 0 in reply to Tomasz Kocon
    TI__Guru**** 161600 points
    Hi Tom,

    I see that NSP 1.10.2.9 has no problem being installed.

    NSP 1.10.01.06 is problematic. But the requirements for it are: CCS 5.4, NDK 2.22.03.20, XDCTools 3.25.00.48, BIOS 6.35.01.29.

    And I see you're trying to use it with CCSv5.5, NDK 2.21.2.43 and bios: 6.35.4.50... I am not sure how compatible are all of these with each other. What I recommend is settle the BIOS release and then use the recommended NDK, NSP and CCS for it, and adapt the application to the new environment, not the other way around.

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Intellectual 460 points
    My first question is: Does the version numbers of ANY of these components matter to CCSv5 when asked to FIND and INSTALL the package ? Yes, I understand that versions need to be aligned to BUILD and RUN the NDK but the original question had simply to do with the initial package not even being recognized by CCSv5 at startup (NDK 2.22.3.20) and a package loading issue with NSP 1.10.1.6

    I hear you both say that NSP 1.10.01.06 is problematic so I will not try to load it anymore. Thanks for the more specific answer on this one. Perhaps the requirement for CCSv4 really means that CCSv5 isn't backward compatible....

    I loaded NSP 1.10.2.9 without any problem. The requirement is for NDK 2.22.3.20 (or better). THIS is where CCSv5 fails to even recognize the package when I start CCS up (downloaded and unzipped twice). Is there a specific fix, or test, or workaround, for this ? This requirement is taken from the NDK download page. Is that page wrong ? The requirement is for bios: 6.35.01.29 (or better) and I am using bios: 6.35.4.50 - is that an issue ? The requirements say "or better" and I am meeting that, or am I ?

    Thanks for helping
    Richard
  • 0 in reply to Richard Dobbis
    TI__Guru**** 161600 points
    Hi,

    THIS is where CCSv5 fails to even recognize the package when I start CCS up (downloaded and unzipped twice). Is there a specific fix, or test, or workaround, for this ?


    Do you install the package in the same path, where CCSv5 is installed? It should be ~/ti/.

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Intellectual 460 points
    Yes, I did install it at the proper place. Any other suggestions ? Please ?
  • 0 in reply to Richard Dobbis
    Guru 26200 points

    Richard,

    having no time for experiments with newer CCS versions I would try this workaround:

    1. install CCS8.2 with all MCUs, CPUs and debug probes
    a) path c:\ti\ccs820 - it is an option during an installation
    b) create a separate for the new CCS8.2
    c) download and install SDKs and NDKs needed

    2. build what you need without testing

    The above 2 steps would take time but should not require a special attention.

    3. After successful build I would compare CCS compiler include and linker paths for both CCS versions
    and based on differences I would update your CCS5.5 setting.

    A few printouts and a text text highlighter would save time and help to eliminate errors.

    I keep my fingers crossed!

  • 0 in reply to Tomasz Kocon
    Intellectual 460 points
    OK, Tom, thanks
    I was hoping for something more definitive concerning the current tools I am using but I see that perhaps no one else has seen this issue.
    I can't mark this as resolved because it did not resolve the issue, but again, thanks for all you help and suggestions!!
    Perhaps I will post further down the line, should I have more time to experiment with other tool versions.
    Richard
  • 0 in reply to Richard Dobbis
    Guru 26200 points
    Richard,
    do not say thanks for nothing!
    Just try my proposal, test something else and say what you have achieved.
    Cheers!
  • 0 in reply to Tomasz Kocon
    TI__Guru* 95265 points
    Richard,

    The C6674 DSP is the Keystone I family and we have Processor SDK RTOS supports for this. The latest software is available from: software-dl.ti.com/.../index_FDS.html. It is Rel 5.1

    The software packages we used are: software-dl.ti.com/.../Release_Specific.html
    NDK 3.40.1
    NS 2.40.1
    XDCTOOLS 3.50.07.20
    SYS/BIOS 6.73.0.03
    CCS 8.1

    With those toolset combinations, the NDK should be able to be detected by the CCS. Using CCS 8.2 version should also work. The Processor SDK RTOS installer have all the packages except CCS, which you need install separately.

    If you are not comfortable to use NDK+NS, you can get the Processor SDK RTOS C667x release 5.0 (it just uses NDK), software-dl.ti.com/.../index_FDS.html.
    It use:
    NDK 2.26.0.0
    SYS/BIOS 6.52.0.12
    XDCTOOLS 3.50.03.33
    CCS 8.0

    Those are the TI C667x official releases and fully tested.

    Regards, Eric
  • 0 in reply to lding
    Guru 26200 points
    Iding,

    issue is that Richard uses CCS5.5 and an NDK is not recognized.
  • 0 in reply to Tomasz Kocon
    TI__Guru* 95265 points
    Tom/Richard,

    There may be CCS and NDK version incompatibility issue. The last BIOS MCSDK for C667x is Release 2.1.2.6 (released in 2013, obsolete then migrated to Processor SDK RTOS), the CCS we used is Ver 5.2.1.

    The first Processor SDK RTOS is version 2.0.1 (now is 5.1), where we used CCS 6.1.2 (now CCS 8.1).

    For each of the release, we have a specific CCS + NDK + SYSBIOS + XDC versions tested. The CCS 5.5 was not used in any MCSDK/Processor SDK RTOS release. It is possible that it has problem to detect a NDK package.

    My suggestion is to update the software packages to a verified release bundle. If you need to use CCS 5.5 for any reason, I will ask the CCS team for help.

    Regards, Eric
  • 0 in reply to lding
    Intellectual 460 points
    Marking this as resolved. I am building a hodgepodge right now but I can ping the target and that's a first step. Once I clean up and finish with the other parts of the NDK I will go back and work on updating all my tools and package versions (a project in itself). Thanks everyone
  • 0 in reply to lding
    Guru 26200 points
    Iding,

    Richard has tried NSP 1.10.1.6 ver.
    It cannot be installed on my laptop also and shows something like this:
    File has invaled content:C:\Users\rdobbis\AppData\Local\Temp\signatureFile1750817143005571917.jar
    Invalid content:plugin.xml
    The file "plugin.xml" in the jar "C:\Users......." has been tampered!

    Could you fix it or remove from NDK/NSP download page?