• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 1408 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.

Automatic XDS Updates Zapped AM335x Processor SDK

Victor Wheeler61
Expert 2215 points

Background:

Windows 7 64-bit
CCS v6.1.2.00015

About a 10 days or so ago I installed the processor SDK for AM335x (product PROCESSOR-SDK-RTOS-AM335X, which installs from file  ti-processor-sdk-rtos-am335x-evm-02.00.01.07-Windows-x86-Install.exe).  I was working with examples under CCS and the ones I had worked with up to that point compiled correctly.

Then about 4-5 days ago, there were several automatic updates to several versions of XDCTOOLS.  I only saw this briefly when I launched CCS and did not pay close attention to the entire list that was updated, but XDCTOOLS I remember.

From that point on, I could not get ANY examples to compile.

The following are the consistent set of errors that come up (I'm pasting in the example errors from the UART_BasicExample_evmAM335x_armExampleProject project:

Description    Resource    Path    Location    Type
Product 'am335x PDK' v1.0.1 is not currently installed and no compatible version is available. Please install this product or a compatible version.    UART_BasicExample_evmAM335x_armExampleProject        UART_BasicExample_evmAM335x_armExampleProject    Problems
Product 'EDMA3 Low Level Driver' v2.12.1 is not currently installed and no compatible version is available. Please install this product or a compatible version.    UART_BasicExample_evmAM335x_armExampleProject        UART_BasicExample_evmAM335x_armExampleProject    Problems
Product 'NDK' v2.24.3.35 is not currently installed and no compatible version is available. Please install this product or a compatible version.    UART_BasicExample_evmAM335x_armExampleProject        UART_BasicExample_evmAM335x_armExampleProject    Problems

It does not seem to matter if I import and compile the project in place (in the installation directory), or import them in a way that copies into my own workspace:  the errors are the same.

Yet the following is the directory tree showing they were installed.  The directories with the arrows were all directories (products) that came with the PDK.

If I re-run    ti-processor-sdk-rtos-am335x-evm-02.00.01.07-Windows-x86-Install.exe    it seems like it goes through the installation all over again.  Yet whether I re-run this .EXE or not, I still get the following in the Project Properties (note the red "X's" for the corresponding "not installed" products -- which were previously registered as installed -- I was working with the examples before the XDCTOOLS update).

So I have 3 questions:

1.  How do I uninstall products that I know I will not be using (example:  old versions of XDCTOOLS that do not have an "uninstall.exe" in the top-level directory for the project, nor do they have a record in the "Uninstall or change a program" list under  Windows OS > Control Panel > Uninstall a Program)?

2.  How do I get CCS to re-register the PDK, NDK and EDMA3 products as being installed?

3.  How do I properly uninstall any product that is registered as installed with CCS?

Kind regards,

Vic

  • 0
    Guru 92251 points

    Victor Wheeler said:
    Then about 4-5 days ago, there were several automatic updates to several versions of XDCTOOLS.  I only saw this briefly when I launched CCS and did not pay close attention to the entire list that was updated, but XDCTOOLS I remember.

    From that point on, I could not get ANY examples to compile.

    I haven't seen an XDCTOOLS installation "zap" the  AM335x Processor SDK.

    However, I did have PROCESSOR-SDK-RTOS-AM335X and PROCESSOR-SDK-RTOS-AM437X in a working CCS 6.1.1 installation under Linux, and when CCS was updated to CCS 6.1.2 (used the same directory and run the CCS 6.1.2 installer and pointed at the original installation) I had the same symptoms of CCS reporting that the PROCESSOR-SDK-RTOS-AM335X and PROCESSOR-SDK-RTOS-AM437X products were no longer installed when attempted to compile projects.

    I didn't keep detailed notes of how I fixed the problem, but I remember going to Help -> About Code Composer Studio -> Installation Details and and selecting to "Uninstall..." the PROCESSOR-SDK-RTOS-AM335X and PROCESSOR-SDK-RTOS-AM437X products before reinstalling them.

  • 0 in reply to Chester Gillon
    Expert 2215 points

    Hi, Chester!

    Like I said, I don't remember the exhaustive list of updates that occurred, and an update to CCS COULD have been part of them.  What I know is that I started CCS, it behaved in a manner similar to when you install new software and then start CCS -- it asks to do the already-selected list of "installations".  Executing the installations (updates?) took less than about 5 seconds to do the updates, and then requested the usual re-start of CCS.  And then immediately after that, I started having the above problem.

    My compliments on your tip!  That was worth GOLD!  I kept some notes on what I did.  I'm not out of the woods yet, but the above-listed problems were indeed solved.

    1.  CCS > Help > About Code Composer Studio > Installation Details.  I selected (one at a time, though it may be possible to do this in a group as well, not sure yet):  am335x PDK, NDK (IDE Client), NDK (Target Client), and EDMA3 and uninstalled them.  I answered YES to re-starte CCS between each one except for the two NDK items, which I did back to back and then accepted the re-start.

    2.  CCS > Window > Preferences > Code Composer Studio > RTSC > Products > Installed Products:  > [Install New...] button, and then I selected the already-existing directories for the above, namely:

       c:\ti\pdk_am335x_1_0_1

       c:\ti\ndk_2_24_03_35

       c:\ti\edma3_lld_02_12_01_22

    one at a time, re-starting CCS between each one.

    Now my Project Properties look like this:


    ...which is MUCH better.  Now I have another set of errors, but I'll take those up separately.  The problem I described above is certainly solved.

    Thanks a TON!

    Kind regards,

    Vic