• Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 991 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.

c66x imglib installation/discovery issues on Linux and Windows

Kevin Halloran
Expert 1345 points

Other Parts Discussed in Thread: MATHLIB

Posted this on TI RTOS forum and was asked to post it here...  I am having a problem with the c66x imglib installations on Linux and Windows (CCS 6.1.2) as follows:

xdctools_3_31_02_38_core (33 and 24 are also installed but not referenced by projects)

CCS 6.1.2

Linux:

imglib_c66x_3_1_1_0:  Installs and works properly, image_processing demo on AM572x EVM built and tested fine.

imglib_c66x_3_2_0_1:  Installs but not discovered.  Trying to add using Windows->Preferences...->RTSC did not work (see imglib_c66x_3_1_1_0 under Windows 10 on how attempted to set as 'other Repository' as well).

Windows 10 64 bit:

imglib_c66x_3_1_1_0:  Installs but not automatically discovered by CCS, had to go to Windows->Preferences...->RTSC and add it as other Repository and then it automatically added it correctly under IMGLIB C66X.  Had to manually extract components archive and drop ti/imglib into imglib_c66x_3_1_1_0\inc to build properly.  After changed imported image_processing demo for AM572x EVM built fine for ARM and DSPs other than a .cfg issue with loadCapsule (see other posts).

imglib_c66x_3_2_0_1:  Installs but not discovered.  Trying to add using Windows->Preferences...->RTSC did not work.

Am installing in same sub-directory area as all the other components, C:\ti on Windows and /home/user/ti on Linux.  Numerous other component installs were automatically discovered by CCS.  Microsoft Security Essential is the virus protection environment on Windows and it was disabled during install but given have the same problem on Linux it probably has nothing to do with that.

Installed components in ti directory:

bios_6_42_02_29

ctoolslib_2_0_0_0

dsplib_c66x_3_4_0_0

edma3_lld_02_12_01_22

framework_components_3_40_01_04

imglib_c66x_3_1_1_0

imglib_c66x_3_2_0_1

ipc_3_40_01_08

mathlib_c66x_3_1_1_0

ndk_2_24_03_35

pdk_am57xx_1_0_0

processor_sdk_rtos_am57xx_2_00_00_00

uia_2_00_03_43

xdais_7_24_00_04

xdctools_3_31_00_24_core

xdctools_3_31_01_33_core

xdctools_3_31_02_38_core

I have also installed any updates available.

  • TI__Guru**** 173310 points

    Kevin,

    Were the imglibs installed in a particular order, (ie) imglib_c66x_3_1_1_0 first and then imglib_c66x_3_2_0_1, or vice versa?

    For each version, did they come from a SDK package (if so, which one?) or from a standalone installer?

    I'd like to see if I can reproduce the behavior. 

  • in reply to AartiG
    Expert 1345 points

    Linux:

    imglib_c66x_3_1_1_0 initially came from the SDK package and  imglib_c66x_3_2_0_1 was installed standalone afterwards.

    Windows 10;

    imglib_c66x_3_1_1_0 initially came from the SDK package and  imglib_c66x_3_2_0_1 was installed standalone afterwards.  I then deleted imglib_c66x_3_1_1_0 and tried to re-install from standalone to see if it made a difference and it did not.  That is when I found I could manually discover it and to get it working unzipped the components and placed them under the inc directory.

     imglib_c66x_3_2_0_1  does not seem to work on either platform, even if try to manually discover it.  Had no problem with imglib_c66x_3_1_1_0 on Linux, only Windows.

  • in reply to Kevin Halloran
    TI__Guru**** 173310 points

    Kevin Halloran said:
    imglib_c66x_3_2_0_1  does not seem to work on either platform, even if try to manually discover it.  

    I just installed the standalone package of  imglib_c66x_3_2_0_1 and see the same issue that CCS is not able to discover it.

    Digging into the installation, I noticed that the \eclipse folder within imglib_c66x_3_2_0_1 is missing the \features and \plugins sub-folders. These folders are there in the imglib_c66x_3_1_1_0 installation. I suspect this is the reason CCS is not able to detect the 3.2.0.1 package. Can you confirm if you see the same thing in your installation?

    Note that I only installed the Windows installer on a Windows 7 system, but I suspect it is the same on your Linux install as well. Can you confirm? 

    If this is the root cause, then it is a packaging issue and I would need to forward it to the device team that creates this package.

  • in reply to AartiG
    Expert 1345 points

    I'm sure that is what it is with 3_2_0_1.  I installed using the same package.  I'll verify it but I won't be back in the office till Tuesday.

    Thanks,

    Kev

  • in reply to Kevin Halloran
    TI__Guru**** 173310 points

    Kevin,

    I have added this information to your other thread here: https://e2e.ti.com/support/arm/sitara_arm/f/791/p/481649/1742555#1742555