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/CODECOMPOSER: XGConf editor error

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: CCSTUDIO, TM4C1294NCPDT, SYSBIOS

Tool/software: Code Composer Studio

Hi,

I am using code composer studio version 10.1.0.00010 in windows 10 Pro 64 bit and when I try to edit the .cfg file with XGConf editor, I received the following error message:

"C:\ti\ccs1010\xdctools_3_32_00_06_core\xs.exe: error: can't create session manager: can't find a JVM; the environment variable 'XDCTOOLS_JAVA_HOME' is set, but does not appear to be a directory 

containing a 32-bit Java Runtime Environment (1.7 or greater); e.g., 'C:\Program Files (x86)\Java\jre7".

I checked in the project settings and XDCTOOLS_JAVA_HOME is set to C:\ti\ccs1010\ccs\utils\jre32 which includes a jre.

I tried downloading the same version of xdctools that includes a jre and set XDCTOOLS_JAVA_HOME to that jre but had still the same error.

Any ideas about this issue?

Thanks for your help,

Sam

  • Hi Sam,

    Sam Frank said:
    I checked in the project settings and XDCTOOLS_JAVA_HOME is set to C:\ti\ccs1010\ccs\utils\jre32 which includes a jre.

    Try setting it to: C:\ti\ccs1010\ccs\eclipse\jre

    That is the 64-bit JRE required by XDCtools.

    Thanks

    ki

  • Hi Ki,

    I changed to C:\ti\ccs1010\ccs\eclipse\jre and had the same error. Please note that I am using xdctools version 3.32.00.06. Does this version require a 32bit or 64bit jre?

    Thanks,

    Sam

  • Sam Frank said:
    Please note that I am using xdctools version 3.32.00.06. Does this version require a 32bit or 64bit jre?

    Based on the below post, it appears to require a 64-bit JRE:

    https://e2e.ti.com/support/legacy_forums/embedded/tirtos/f/355/p/523925/1904682#1904682

    However, I am not an expert. I will bring this thread to the attention of the TI-RTOS experts

    ki

  • Sam,
    3.32.00.06 requires a 32-bit JVM, so you are pointing to the right directory. But, when you are using an XDCtools release that comes with a JRE you don't need to set XDCTOOLS_JAVA_HOME. Can you unset that variable, and instead of using XGConf, just try to build the project by Project Properties->Build Project. Verify that the project is being built with XDCtools that includes a JRE. Does that work or you are getting the same error? 

  • Hi Sahsa,

    I don't use XDCtools release that comes with a JRE with my project. I just downloaded it in a separate folder to try pointing to its JRE. I have installed the version of XDCtools release without JRE within code composer studio (after spending hours browsing to figure out why a TI provided project downloaded from resource explorer give me errors while compiling....). If you think that the  XDCtools release that comes with a JRE must be installed within code composer studio, kindly let me know how to proceed.

    Thanks,

    Sam

  • Sam,
    I misunderstood your post. You don't need to use the XDCtools version with JRE in CCS. Can you try building your project the way I described in my previous post, but use the version of XDCtools 3.32.00.06 without JRE? Please post the complete console output.

    Also, you can try the following. Open a Windows command window and set XDCTOOLS_JAVA_HOME there using
    > set XDCTOOLS_JAVA_HOME=...

    Then start CCS from the window:
    > C:\ti\ccs1010\ccs\eclipse\ccstudio.exe

    Do you see anything different when building the project or running XGConf?

  • Hi Sasha,

    When I unset XDCTOOLS_JAVA_HOME in my project, I get the following console output:

    Building file: "../empty.cfg"
    Invoking: XDCtools
    "C:/ti/ccs1010/xdctools_3_32_00_06_core/xs" --xdcpath="C:/ti/tirtos_tivac_2_16_00_08/packages;C:/ti/tirtos_tivac_2_16_00_08/products/tidrivers_tivac_2_16_00_08/packages;C:/ti/tirtos_tivac_2_16_00_08/products/bios_6_45_01_29/packages;C:/ti/tirtos_tivac_2_16_00_08/products/ndk_2_25_00_09/packages;C:/ti/tirtos_tivac_2_16_00_08/products/uia_2_00_05_50/packages;C:/ti/tirtos_tivac_2_16_00_08/products/ns_1_11_00_10/packages;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4F -p ti.platforms.tiva:TM4C1294NCPDT -r release -c "C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-arm_20.2.2.LTS" --compileOptions "-mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --include_path=\"D:/Workshops/Ti-RTOS/Workspace/test\" --include_path=\"D:/Workshops/Ti-RTOS/Workspace/test\" --include_path=\"C:/ti/tirtos_tivac_2_16_00_08/products/TivaWare_C_Series-2.1.1.71b\" --include_path=\"C:/ti/tirtos_tivac_2_16_00_08/products/bios_6_45_01_29/packages/ti/sysbios/posix\" --include_path=\"C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-arm_20.2.2.LTS/include\" --define=ccs=\"ccs\" --define=PART_TM4C1294NCPDT --define=ccs --define=TIVAWARE -g --gcc --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi " "../empty.cfg"
    subdir_rules.mk:19: recipe for target 'build-842810465-inproc' failed
    C:\ti\ccs1010\xdctools_3_32_00_06_core\C:/ti/ccs1010/xdctools_3_32_00_06_core/xs: error: can't create session manager: can't find a JVM; the environment variable 'XDCTOOLS_JAVA_HOME' is set, but does not appear to be a directory containing a 32-bit Java Runtime Environment (1.7 or greater); e.g., 'C:\Program Files (x86)\Java\jre7'.
    gmake[1]: *** [build-842810465-inproc] Error 1
    gmake: *** No rule to make target 'build-842810465', needed by 'configPkg/compiler.opt'.
    gmake: *** No rule to make target 'build-842810465', needed by 'configPkg/linker.cmd'.
    gmake: *** No rule to make target 'build-842810465', needed by 'configPkg/compiler.opt'.
    gmake: *** No rule to make target 'build-842810465', needed by 'configPkg/compiler.opt'.
    gmake: Target 'all' not remade because of errors.

    **** Build Finished ****

    When  XDCTOOLS_JAVA_HOME  is set to C:\ti\ccs1010\ccs\utils\jre32, the project builds without error, here is the build output:

    **** Build of configuration Debug for project hello_EK_TM4C1294XL_TI ****

    "C:\\ti\\ccs1010\\ccs\\utils\\bin\\gmake" -k -j 16 all -O

    Building file: "../hello.cfg"
    Invoking: XDCtools
    "C:/ti/ccs1010/xdctools_3_32_00_06_core/xs" --xdcpath="C:/ti/tirtos_tivac_2_16_00_08/packages;C:/ti/tirtos_tivac_2_16_00_08/products/tidrivers_tivac_2_16_00_08/packages;C:/ti/tirtos_tivac_2_16_00_08/products/bios_6_45_01_29/packages;C:/ti/tirtos_tivac_2_16_00_08/products/ndk_2_25_00_09/packages;C:/ti/tirtos_tivac_2_16_00_08/products/uia_2_00_05_50/packages;C:/ti/tirtos_tivac_2_16_00_08/products/ns_1_11_00_10/packages;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4F -p ti.platforms.tiva:TM4C1294NCPDT -r release -c "C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-arm_20.2.2.LTS" --compileOptions "-mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --include_path=\"D:/Workshops/Ti-RTOS/Workspace/hello_EK_TM4C1294XL_TI\" --include_path=\"D:/Workshops/Ti-RTOS/Workspace/hello_EK_TM4C1294XL_TI\" --include_path=\"C:/ti/tirtos_tivac_2_16_00_08/products/TivaWare_C_Series-2.1.1.71b\" --include_path=\"C:/ti/tirtos_tivac_2_16_00_08/products/bios_6_45_01_29/packages/ti/sysbios/posix\" --include_path=\"C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-arm_20.2.2.LTS/include\" --define=ccs=\"ccs\" --define=PART_TM4C1294NCPDT --define=ccs --define=TIVAWARE -g --gcc --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi " "../hello.cfg"
    making package.mak (because of package.bld) ...
    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
    configuring hello.xem4f from package/cfg/hello_pem4f.cfg ...
    generating custom ti.sysbios library makefile ...
    Starting build of library sources ...
    making D:/Workshops/Ti-RTOS/Workspace/hello_EK_TM4C1294XL_TI/src/sysbios/sysbios.aem4f ...
    gmake[1]: Entering directory `D:/Workshops/Ti-RTOS/Workspace/hello_EK_TM4C1294XL_TI/src/sysbios'
    clem4f C:/ti/tirtos_tivac_2_16_00_08/products/bios_6_45_01_29/packages/ti/sysbios/BIOS.c ...
    asmem4f C:/ti/tirtos_tivac_2_16_00_08/products/bios_6_45_01_29/packages/ti/sysbios/family/arm/m3/Hwi_asm.sv7M ...
    asmem4f C:/ti/tirtos_tivac_2_16_00_08/products/bios_6_45_01_29/packages/ti/sysbios/family/arm/m3/Hwi_asm_switch.sv7M ...
    asmem4f C:/ti/tirtos_tivac_2_16_00_08/products/bios_6_45_01_29/packages/ti/sysbios/family/arm/m3/IntrinsicsSupport_asm.sv7M ...
    asmem4f C:/ti/tirtos_tivac_2_16_00_08/products/bios_6_45_01_29/packages/ti/sysbios/family/arm/m3/TaskSupport_asm.sv7M ...
    arem4f BIOS.obj m3_Hwi_asm.obj m3_Hwi_asm_switch.obj m3_IntrinsicsSupport_asm.obj m3_TaskSupport_asm.obj ...
    gmake[1]: Leaving directory `D:/Workshops/Ti-RTOS/Workspace/hello_EK_TM4C1294XL_TI/src/sysbios'
    Build of libraries done.
    clem4f package/cfg/hello_pem4f.c ...
    "package/cfg/hello_pem4f.c", line 15109: warning #112-D: statement is unreachable
    "package/cfg/hello_pem4f.c", line 15595: warning #112-D: statement is unreachable
    "package/cfg/hello_pem4f.c", line 15869: warning #112-D: statement is unreachable
    "package/cfg/hello_pem4f.c", line 16050: warning #112-D: statement is unreachable
    Finished building: "../hello.cfg"

    1 file(s) copied.
    making ../src/sysbios/sysbios.aem4f ...
    gmake[1]: Nothing to be done for 'all'.
    Building file: "../hello.c"
    Invoking: ARM Compiler
    "C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-arm_20.2.2.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --include_path="D:/Workshops/Ti-RTOS/Workspace/hello_EK_TM4C1294XL_TI" --include_path="D:/Workshops/Ti-RTOS/Workspace/hello_EK_TM4C1294XL_TI" --include_path="C:/ti/tirtos_tivac_2_16_00_08/products/TivaWare_C_Series-2.1.1.71b" --include_path="C:/ti/tirtos_tivac_2_16_00_08/products/bios_6_45_01_29/packages/ti/sysbios/posix" --include_path="C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-arm_20.2.2.LTS/include" --define=ccs="ccs" --define=PART_TM4C1294NCPDT --define=ccs --define=TIVAWARE -g --gcc --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi --preproc_with_compile --preproc_dependency="hello.d_raw" --cmd_file="configPkg/compiler.opt" "../hello.c"
    Finished building: "../hello.c"

    Building file: "../EK_TM4C1294XL.c"
    Invoking: ARM Compiler
    "C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-arm_20.2.2.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --include_path="D:/Workshops/Ti-RTOS/Workspace/hello_EK_TM4C1294XL_TI" --include_path="D:/Workshops/Ti-RTOS/Workspace/hello_EK_TM4C1294XL_TI" --include_path="C:/ti/tirtos_tivac_2_16_00_08/products/TivaWare_C_Series-2.1.1.71b" --include_path="C:/ti/tirtos_tivac_2_16_00_08/products/bios_6_45_01_29/packages/ti/sysbios/posix" --include_path="C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-arm_20.2.2.LTS/include" --define=ccs="ccs" --define=PART_TM4C1294NCPDT --define=ccs --define=TIVAWARE -g --gcc --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi --preproc_with_compile --preproc_dependency="EK_TM4C1294XL.d_raw" --cmd_file="configPkg/compiler.opt" "../EK_TM4C1294XL.c"
    Finished building: "../EK_TM4C1294XL.c"

    making ../src/sysbios/sysbios.aem4f ...
    gmake[2]: Nothing to be done for 'all'.
    Building target: "hello_EK_TM4C1294XL_TI.out"
    Invoking: ARM Linker
    "C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-arm_20.2.2.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --define=ccs="ccs" --define=PART_TM4C1294NCPDT --define=ccs --define=TIVAWARE -g --gcc --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi -z -m"hello_EK_TM4C1294XL_TI.map" --heap_size=0 --stack_size=512 -i"C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-arm_20.2.2.LTS/lib" -i"C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-arm_20.2.2.LTS/include" --reread_libs --diag_wrap=off --display_error_number --warn_sections --xml_link_info="hello_EK_TM4C1294XL_TI_linkInfo.xml" --rom_model -o "hello_EK_TM4C1294XL_TI.out" "./EK_TM4C1294XL.obj" "./hello.obj" "../EK_TM4C1294XL.cmd" -l"configPkg/linker.cmd" -l"C:/ti/tirtos_tivac_2_16_00_08/products/TivaWare_C_Series-2.1.1.71b/grlib/ccs/Debug/grlib.lib" -l"C:/ti/tirtos_tivac_2_16_00_08/products/TivaWare_C_Series-2.1.1.71b/usblib/ccs/Debug/usblib.lib" -l"C:/ti/tirtos_tivac_2_16_00_08/products/TivaWare_C_Series-2.1.1.71b/driverlib/ccs/Debug/driverlib.lib" -llibc.a
    <Linking>
    Finished building target: "hello_EK_TM4C1294XL_TI.out"

    **** Build Finished ****

    However, as I initially mentioned, the issue happens when I want to open the empty.cfg file using XGConf (i.e. in project explorer, right click on empty.cfg and select "open with" and the select XGConf. Then the following error message is displayed:

    C:\ti\ccs1010\xdctools_3_32_00_06_core\xs.exe: error: can't create session manager: can't find a JVM; the environment variable 'XDCTOOLS_JAVA_HOME' is set, but does not appear to be a directory
    containing a 32-bit Java Runtime Environment (1.7 or greater); e.g., 'C:\Program Files (x86)\Java\jre7'.

    I also tried to set  XDCTOOLS_JAVA_HOME as a Windows environment variable as you suggested and the same error as above happened when trying to open empty.cfg with XGConf.

    Thanks for your help,

    Sam

  • Sam,
    I was able to replicate the problem. The bug only exists for older versions of XDCtools. XGConf works fine with XDCtools 3.61.

    It could take some time for me to figure out the cause of the bug. I would recommend that you copy the directory jre from your full 3.32 installation to your 3.32 installation without JRE.

    That worked for me. Let me know if that doesn't work for you.

  • Hi Sasha,

    I copied the jre folder from the full installation of XDCtools version 3.32.00.06 to C:\ti\ccs1010\ccs\utils\jre32 folder and still the same issue happened.

    Thanks for your help,

    Sam

  • Sam,

    what I meant is to copy 'jre' from the full installation to the non-JRE installation of XDCtools 3.32, so that non-JRE installation has a directory 'jre' under 'xdctools_3_32_00_06_core'.

  • It worked!

    Thank you!

    Sam