• Locked Locked
  • Replies 10 replies
  • Subscribers 52 subscribers
  • Views 2626 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCSv5.4 - does not automatically discover RTSC products

Eddie3909
Guru 10385 points
Other Parts Discussed in Thread: MATHLIB

Hi

XP, CCSv5.4, C6472

I installed ccs 5.4 and it cannot see any RTSC products even though I have them installed in c:\Program Files\Texas Instruments. (see screenshot)

Its able to find my build tools, but not the rtsc

Proof that the RTSC folders exist.

C:\Program Files\Texas Instruments>dir
Volume in drive C has no label.
Volume Serial Number is 8892-3591

Directory of C:\Program Files\Texas Instruments

07/18/2013 11:52 AM <DIR> .
07/18/2013 11:52 AM <DIR> ..
12/13/2011 10:51 AM <DIR> bios_5_41_11_38
07/17/2013 03:31 PM <DIR> bios_5_42_01_09
12/13/2011 09:14 AM <DIR> bios_6_31_04_27
12/13/2011 08:31 AM <DIR> bios_6_32_02_39
12/13/2011 10:52 AM <DIR> bios_6_32_05_54
08/06/2012 08:33 AM <DIR> bios_6_33_05_46
06/07/2013 12:29 PM <DIR> bios_6_33_06_50
10/23/2012 11:01 AM <DIR> bios_6_34_02_18
07/18/2013 12:05 PM <DIR> bios_6_35_01_29
07/03/2012 10:41 PM 131,028,136 bios_setupwin32_6_33_06_50.exe
01/02/2013 02:34 PM <DIR> C6000 Code Generation Tools 6.1.5
12/13/2011 09:09 AM <DIR> C6000 Code Generation Tools 7.2.6
07/18/2013 12:12 PM <DIR> ccsv4
07/18/2013 01:26 PM <DIR> ccsv5
06/07/2013 12:46 PM <DIR> cg_xml
06/02/2011 11:30 AM 30,167,504 cg_xml-v2_30_00-Setup.exe
07/18/2013 01:25 PM 1,931 Code Composer Studio v5.lnk
01/06/2012 10:51 AM <DIR> csl_c6472_03_00_06_03
02/28/2012 05:38 PM <DIR> csl_c6472_src_03_00_06_03
01/06/2012 03:02 PM <DIR> csl_c64xplus_intc_03_00_05_06
10/12/2012 11:08 AM <DIR> dsplib_c64Px_3_1_0_0
03/05/2013 04:10 PM <DIR> dsplib_c66x_3_0_0_7
05/04/2011 04:46 AM 37,161,439 dsplib_c66x_3_0_0_7_Win32.exe
06/07/2013 12:44 PM <DIR> dsplib_c66x_3_1_0_0
10/19/2011 09:32 AM 9,898,445 dsplib_c66x_3_1_0_0_Win32.exe
12/13/2011 01:19 PM <DIR> eclipse
03/05/2013 03:53 PM <DIR> edma3_lld_02_11_01_02
06/07/2013 12:18 PM <DIR> edma3_lld_02_11_05_02
03/05/2013 04:02 PM <DIR> imglib_c66x_3_0_1_0
04/29/2011 11:33 AM 12,152,492 imglib_c66x_3_0_1_0_Win32.exe
06/07/2013 12:41 PM <DIR> imglib_c66x_3_1_1_0
06/04/2012 09:18 AM 7,056,830 imglib_c66x_3_1_1_0_Win32.exe
12/13/2011 09:11 AM <DIR> ipc_1_22_03_23
03/05/2013 03:59 PM <DIR> ipc_1_22_05_27
12/13/2011 08:33 AM <DIR> ipc_1_23_02_27
12/13/2011 10:54 AM <DIR> ipc_1_23_05_40
08/06/2012 08:53 AM <DIR> ipc_1_24_03_32
03/23/2011 09:24 AM 67,801,205 ipc_setupwin32_1_22_05_27.exe
05/22/2012 04:56 PM 94,340,893 ipc_setupwin32_1_24_03_32.exe
07/17/2013 11:27 AM <DIR> license
10/12/2012 10:56 AM <DIR> mathlib_c66x_3_0_0_0
06/07/2013 12:45 PM <DIR> mathlib_c66x_3_0_1_1
02/06/2012 05:37 PM 4,692,557 mathlib_c66x_3_0_1_1_Win32.exe
10/12/2012 10:58 AM <DIR> mathlib_c674x_3_0_0_0
03/05/2013 04:15 PM <DIR> mcsdk_2_00_00_beta2
06/07/2013 12:46 PM <DIR> mcsdk_2_01_02_06
03/05/2013 03:52 PM <DIR> ndk_2_20_03_24
06/07/2013 12:24 PM <DIR> omp_1_01_03_02
06/07/2013 12:24 PM <DIR> openem_1_0_0_2
06/07/2013 12:13 PM <DIR> pdk_C6657_1_1_2_6
03/05/2013 03:49 PM <DIR> pdk_C6670_1_0_0_9_beta2
03/05/2013 03:48 PM <DIR> pdk_C6678_1_0_0_9_beta2
06/07/2013 12:09 PM <DIR> pdk_C6678_1_1_2_6
05/03/2013 05:05 PM 330,880 SrioPortError_core0_errorOccured.bi
10/22/2012 07:11 PM <DIR> ti
05/17/2011 03:35 PM 52,885,366 ti_dvt_setup_3.1.0.04076.exe
12/13/2011 10:56 AM <DIR> uia_1_00_03_25
07/18/2013 12:07 PM <DIR> uia_1_03_00_02
12/13/2011 08:38 AM <DIR> xdais_7_10_00_06
07/18/2013 12:06 PM <DIR> xdais_7_21_01_07
12/13/2011 09:08 AM <DIR> xdctools_3_20_08_88
12/13/2011 08:37 AM <DIR> xdctools_3_22_01_21
12/13/2011 10:50 AM <DIR> xdctools_3_22_04_46
08/06/2012 08:03 AM <DIR> xdctools_3_23_02_47
06/07/2013 12:38 PM <DIR> xdctools_3_23_04_60
07/18/2013 12:02 PM <DIR> xdctools_3_25_00_48
07/09/2012 07:45 PM 171,338,618 xdctools_setupwin32_3_23_04_60.exe

CCSv4 is able to find all my bios, ipc and xdc tools

Any idea what I need to do to get this working?

Cheers2u

  • TI__Guru*** 130875 points

    Hi,

    two things to check/try

     1- anitivirus interference

    2 - try making a copy of the bios folder somewhere other than the program files directory (ie c:/ti) and try again. 

    Please keep us informed.

    Best Regards,
    Lisa 

  • in reply to Lisa TI
    Guru 10385 points

    Arg. CCSv5 can find the files when I copy the bios, ipc, etc to the c:\ti folder

    Its disappointing that TI has decided to switch to c:\TI after using CCSv4 c:\Program Files\Texas Instruments as the installation. I really don't have the memory on my PC to make duplicates of all the RTSC tools.

    Can you please file an bug/enhancement request on this?

    Cheers2u

  • in reply to Eddie3909
    Guru 10385 points

    This is amazing.

    After it found the RTSC files in c:\TI, I shut down ccs

    Then I started it again and it said it found c:\Program Files\Texas Instruments (thats it, nothing else)

    So I re-started as it requested.

    Then it finds ALL my RTSC stuff in c:\Program Files\Texas Instruments

    Now I hope its not going to complain that there are now two instances of RTSC elements in c:\TI and another in c:\Program Files\Texas Instruments

    Cheers

  • in reply to Eddie3909
    Guru 10385 points

    Arg2

    Now it complains

    Operation details
    Your original request has been modified.
    "SYS/BIOS (IDE Client)" is already installed, so an update will be performed instead.
    "IPC (Multicore and I/O) (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)" is already installed, so an update will be performed instead.
    Cannot complete the install because of a conflicting dependency.
    Software being installed: RTSC/XDCtools (IDE Client) 3.25.0.48 (org.eclipse.rtsc.xdctools.product.ui.feature.group 3.25.0.48)
    Software being installed: RTSC/XDCtools 3.20.8.88 (org.eclipse.rtsc.xdctools_3.20.feature.group 3.20.8.88)
    Only one of the following can be installed at once:
    Eclipse Plug-in 3.23.4.60 (org.eclipse.rtsc.xdctools.ui 3.23.4.60)
    Eclipse Plug-in 3.22.1.21 (org.eclipse.rtsc.xdctools.ui 3.22.1.21)
    Eclipse Plug-in 3.25.0.48 (org.eclipse.rtsc.xdctools.ui 3.25.0.48)
    Eclipse Plug-in 3.22.4.46 (org.eclipse.rtsc.xdctools.ui 3.22.4.46)
    Eclipse Plug-in 3.20.8.88 (org.eclipse.rtsc.xdctools.ui 3.20.8.88)
    Eclipse Plug-in 3.23.2.47 (org.eclipse.rtsc.xdctools.ui 3.23.2.47)
    Cannot satisfy dependency:
    From: RTSC/XDCtools (IDE Client) 3.25.0.48 (org.eclipse.rtsc.xdctools.product.ui.feature.group 3.25.0.48)
    To: org.eclipse.rtsc.xdctools.ui [3.25.0.48]
    Cannot satisfy dependency:
    From: RTSC/XDCtools 3.20.8.88 (org.eclipse.rtsc.xdctools_3.20.feature.group 3.20.8.88)
    To: org.eclipse.rtsc.xdctools.ui [3.20.8.88]

  • in reply to Eddie3909
    Guru 10385 points

    I think the bug in CCSv5 is that it doesn't see anything below the first listed item c:\TI if that directory does not exist. Once I created it, it could then find the c:\Program Files\Texas Instruments directory.

    Cheers

  • in reply to Eddie3909
    Guru 10385 points

    Arg3: I deleted the files in c:\TI and rebooted. Now I get the error below 

    Operation details
    Cannot complete the install because of a conflicting dependency.
    Software being installed: RTSC/XDCtools 3.20.8.88 (org.eclipse.rtsc.xdctools_3.20.feature.group 3.20.8.88)
    Software being installed: RTSC/XDCtools 3.22.1.21 (org.eclipse.rtsc.xdctools_3.22.1.21.feature.group 3.22.1.21)
    Only one of the following can be installed at once:
    XDCtools core 3.22.1.21 (org.eclipse.rtsc.xdctools.core 3.22.1.21)
    XDCtools core 3.25.0.48 (org.eclipse.rtsc.xdctools.core 3.25.0.48)
    XDCtools core 3.20.8.88 (org.eclipse.rtsc.xdctools.core 3.20.8.88)
    Cannot satisfy dependency:
    From: RTSC/XDCtools 3.20.8.88 (org.eclipse.rtsc.xdctools_3.20.feature.group 3.20.8.88)
    To: org.eclipse.rtsc.xdctools.core [3.20.8.88]
    Cannot satisfy dependency:
    From: RTSC/XDCtools 3.22.1.21 (org.eclipse.rtsc.xdctools_3.22.1.21.feature.group 3.22.1.21)
    To: org.eclipse.rtsc.xdctools.core [3.22.1.21]

  • in reply to Eddie3909
    TI__Guru*** 130875 points

    Hi Eddie,

    glad to hear that you are past the issue and thanks for that feedback.    Due to the odd permissions windows sets and to work towards standarizing, yes the default directory has been changed.

    All the best with development.

    Best Regards,
    Lisa 

  • in reply to Eddie3909
    Guru 10385 points

    Arg4: I thought I was home free, but now I realize that CCSv5 wont automatically discover the RTSC products I deleted in c:\TI

    I tried putting the RTSC products back into c:\TI and it still doesn't automatically discover them.

    Looks like I'm forced to install ccsv5 in c:\TI  (couldn't TI have gotten this right be now!!)

    This is painful!

  • in reply to Eddie3909
    TI__Guru*** 130875 points

    Hi Eddie,

    yes, fortunate or not, as mentioned, yes c:/ti is now the directory we use and recommend.

    Best Regard,
    Lisa 

  • in reply to Eddie3909
    Guru 10385 points

    Eddie3909 said:
    doesn't see anything below the first listed item c:\TI if that directory does not exist. Once I created it, it could then find the c:\Program Files\Texas Instruments directory.

    Not only does it have to exist, it needs to have an RTSC product in it. I did a complete install in c:\Program Files\Texas Instruments and then created c:\TI. CCS still couldn't find the RTSC products.

    I tried installing in c:\TI, but then I get a bunch on conflict errors with my RTSC packages in c:\Program Files\Texas Instruments. It seems CCSv5 autodetect does not like more than on copy of rtsc products in the c:\program files\texas instruments. 

    This was not a problem with CCSv5.1. CCSv5.4 is a step backwards when it comes to RTSC package detection.

    The solution may be to turn off automatic update. This would require a new install so I'm going to skip that experiment - I've installed CCS 5xs now.