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.

RTOS/EVMK2G: pdkProjectComplete.bat fails with "!ERROR: No products of type 'com.ti.rtsc.SYSBIOS' are currently installed!"

Part Number: EVMK2G
Other Parts Discussed in Thread: MATHLIB, 66AK2G02, SYSBIOS, AM3359

Tool/software: TI-RTOS

Following "Processor_SDK_RTOS_Getting_Started_Guide#Peripheral_Driver_Examples",

I installed "ti-processor-sdk-rtos-k2g-evm-04.00.00.04-Windows-x86-Install" into the default paths.

I ran into trouble following the directions for "Rebuilding_The_PDK"

Does anyone have a suggestion?

Thank you all,

Bob

log:

C:\ti\pdk_k2g_1_0_6\packages>pdksetupenv
**************************************************************************
Environment Configuration:
LIMIT_SOCS : k2g
LIMIT_BOARDS : evmK2G iceK2G
PDK_INSTALL_PATH : /ti/PDK_K2~1/packages
C6X_GEN_INSTALL_PATH : C:/ti/ti-cgt-c6000_8.1.3
TOOLCHAIN_PATH_GCC : C:/ti/gcc-arm-none-eabi-4_9-2015q3
TOOLCHAIN_PATH_A15 : C:/ti/gcc-arm-none-eabi-4_9-2015q3
TOOLCHAIN_PATH_A8 : C:/ti/gcc-arm-none-eabi-4_9-2015q3
TOOLCHAIN_PATH_A9 : C:/ti/gcc-arm-none-eabi-4_9-2015q3
TOOLCHAIN_PATH_M4 : C:/ti/ti-cgt-arm_16.9.2.LTS
TOOLCHAIN_PATH_Arm9 : C:/ti/ti-cgt-arm_16.9.2.LTS
TOOLCHAIN_PATH_EVE : C:/ti/arp32_1.0.8
CL_PRU_INSTALL_PATH : C:/ti/ti-cgt-pru_2.1.5
UTILS_INSTALL_DIR : C:/ti/xdctools_3_32_01_22_core/bin
FPULIB_PATH : C:/ti/gcc-arm-none-eabi-4_9-2015q3/lib/gcc/arm-none-eabi/4.9.3/fpu
CROSS_TOOL_PRFX : arm-none-eabi-
XDC_INSTALL_PATH : C:/ti/xdctools_3_32_01_22_core
BIOS_INSTALL_PATH : C:/ti/bios_6_46_05_55
IPC_INSTALL_PATH : C:/ti/ipc_3_46_00_02
EDMA3LLD_BIOS6_INSTALLDIR : C:/ti/edma3_lld_2_12_04_28
NDK_INSTALL_PATH : C:/ti/ndk_2_25_01_11
IMGLIB_INSTALL_PATH : C:/ti/imglib_c66x_3_1_1_0
DSPLIB_INSTALL_PATH : C:/ti/dsplib_c66x_3_4_0_0
MATHLIB_INSTALL_PATH : C:/ti/mathlib_c66x_3_1_1_0
UIA_INSTALL_PATH : C:/ti/uia_2_00_06_52
CG_XML_BIN_INSTALL_PATH : C:\ti\cg_xml\bin
**************************************************************************
Changing to short name to support directory names containing spaces
current directory: /ti/PDK_K2~1/packages
PDK BUILD ENVIRONMENT CONFIGURED
**************************************************************************

C:\ti\PDK_K2~1\packages>pdkProjectCreate K2G
=========================================================================
Configuration:
SOC : K2G
BOARD : all
ENDIAN : little
MODULE : all
PROCESSOR : arm
PDK_SHORT_NAME : C:\ti\PDK_K2~1\packages\
=========================================================================
Checking Configuration...
Complete
=========================================================================
PDK_PARTNO : 66AK2G02
PDK_ECLIPSE_ID : com.ti.pdk.k2g
RTSC_PLATFORM_NAME : ti.platforms.evmTCI66AK2G02
RTSC_TARGET : gnu.targets.arm.A15F
CCS_DEVICE : "Cortex A.66AK2G02"
*****************************************************************************
Detecting all projects in PDK and importing them in the workspace C:\ti\pdk_k2~1\packages\MyExampleProjects
Detected Test Project: cppievmK2GArmBiosTestProject

--------------------------------------------------------------------------------
Creating project 'cppievmK2GArmBiosTestProject'...

!ERROR: No products of type 'com.ti.rtsc.SYSBIOS' are currently installed!

Copying macro.ini
The system cannot find the path specified.
0 file(s) copied.
Detected Test Project: EMAC_BasicExample_evmK2G_armBiosExampleProject

--------------------------------------------------------------------------------
Creating project 'EMAC_BasicExample_evmK2G_armBiosExampleProject'...

!ERROR: No products of type 'com.ti.rtsc.SYSBIOS' are currently installed!

Copying macro.ini
The system cannot find the path specified.
0 file(s) copied.
Detected Test Project: EMAC_BasicExample_iceK2G_armBiosExampleProject
Copying macro.ini
0 file(s) copied.
Terminate batch job (Y/N)? y

C:\ti\PDK_K2~1\packages>

  • Hi Bob,

    It seems that you don't have the SYSBIOS exported in the path.

    Make sure that you've installed the SDK correctly (all components are installed on your pc).
    Revisit your host & target setup, as described here: processors.wiki.ti.com/.../Processor_SDK_RTOS_FAQ

    Go through the FAQ wiki:
    processors.wiki.ti.com/.../Processor_SDK_RTOS_FAQ

    Best Regards,
    Yordan
  • Bob,

    Your BIOS component (bios_6_46_05_55) is not discovered in CCS Products.

    to check that the components are discovered, Open CCS and go to windows->Preference->Code composer Studio -> Products and check to see if BIOS version is present there. as you can see here:

    Hope this helps.

    Regards,

    Rahul

  • Thank you for your help.

    I tried to paste in screen shots of the Preferences window, but it didn't work.

    In the discovery path I have:

    c:/ti

    c:/Program Files/Texas Instruments

    c:/ti/processeor_sdk_rtos_k2g_4_00_00_04

    c:\ti\pdk_k2g_1_0_6

    c:/ti/bios_6_46_05_55

    In Installed Products I  have only:

    XDCtools

    3.50.2.20_core

    3.32.2.25.core

    Rediscover didn't help. It brought up a whole list of things that it thought were already installed, but clicking install didn't add them to CCS.

  • Hi Yordan,
    Thank you for your help.
    I reviewed they data in your links.
    I saw one place I deviated from the path described in the FAQ.
    I'm experimenting with both the AM3359 and the 66AK2G.

    I wanted to use git to switch between the am3359 and the 66AK2G so I could keep the default directory structure for each, and not type in custom paths.
    I made a git repository of all of C:\ti and committed after installing each ccsv7, SDK, and PDK for the am3359
    I worked on the AM3359 first and successfully complied and ran an example from pdk_am335x_1_0_7
    Then I git checked out the ccsv7 installation and installed the SDK and PDK for the 66AK2G.
    I was able to install the SDK and to run the FFT example, but when I run the build pdk .bat it errors out as shown above.
    Thank you again for your help.
  • Bob,

    If you are working with 2 different version of the SDK, we recommend installing the packages in different locations and switching the Preference based on the device you are using. This is important because the SDK builds are done for specific devices, they build from the same source but the build macors are set to build libraries for certain devices so you run the risk of overwriting some files.

    Hope this helps.

    Regards,
    Rahul