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.

Can't find JVM when building TI RTOS Projects: XDCTOOLS_JAVA_HOME error

Hi all,

I'm having a problem right not trying to build one of the TI RTOS example projects, specifically UART Echo, on the MSP432. My machine is running Ubuntu 16.04 and I'm using CCS 6.1.3.00033. Building regular projects in CCS works fine, but the errors I get for all RTOS projects are below:


/home/henry/ti/xdctools_3_32_00_06_core/xs.x86_64U: 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 64-bit Java Runtime Environment (1.7 or greater); e.g., '/usr/lib/jvm/java-7-openjdk-amd64'.
gmake: *** No rule to make target 'configPkg/linker.cmd', needed by 'configPkg/compiler.opt'.
gmake: *** No rule to make target 'configPkg/linker.cmd', needed by 'configPkg/compiler.opt'.
gmake: Target 'all' not remade because of errors.

I have looked at a few other pages about this, like this that looks very similar to my problem. e2e.ti.com/.../510357

I have tried redefining the environment variable in CCS to no avail. Concerning some things addressed in the page I linked just above, I also don't have a /usr/lib/jvm/java-7-openjdk-amd64/jre path, jvm doesn't exist under /usr/lib. I'm not sure if this means that I don't actually have a 64 bit version installed or not. I tried to install openjdk-7-jre and it told me the package is not available. When I try to change XDCtools version from to 3.31.3.43_core from 3.32.0.06_core as a temporary fix under the project Properties it gives me an error saying "none of the currently selected products supplies value for Target."


Any thoughts or possible work around?

Thanks

  • I had the same problem with XDCTools 3.32.00.06. I got out by switching to 3.31.03.43 (lower version) which needs a 32 bit JVM. The environment variable, if you set it in shell or elsewhere is not taking effect, that might flummox you for a while. You have to set it up at Properties->CCS Build->Environment tab or hand-edit your <project>/.settings/org.eclipse.cdt.core.prefs file. You can point the Java Home to CCS Eclipse directory (e.g. /proj/CCS/eclipse in my case, under which a directory 'jre' exists; do not include 'jre' in the path given to the CCS!). I have posted details in the CCS forum, you can look for a post by Bill Mill, to which I was replying. Hope that helps.
  • Thanks for the reply. I tried setting the environment variable specifically under the project properties, but I am getting the same response. One thing I noticed when I changed XDCtools version is that the "Target" field goes blank and never returns to its initial value "ti.targets.arm.elf.M4F". I tried copying and pasting this in after I switched to XDCtools version 3.31.3.43 from 3.31.0.06 and it compiled. But because this couldn't be that easy, the debug probe sends the error "Error connecting to the target: (Error-260@0x0) An attempt to connect to the XDS110 failed....." I'm guessing that maybe I didn't put in the right target for the 3.31.3.43 XDCtools version.
  • Hi Henry,

    As mentioned in the link that you posted, XDCtools 3.32.00.06 requires 64 bit java while CCS 6.1.3 ships with 32 bit java version. I have tried successfully installing 64 bit openjdk-7 and setting up a symlink, and also I was able to fall back to the older version of XDCtools and build TI-RTOS projects. I tried these steps using CCS 6.1.3 on Ubuntu 14.04.

    I ran the command documented in this link: openjdk.java.net/.../ for installing openjdk-7-jre. Before running it, I ran "sudo apt-get update".

    Can you please post a screenshot of the error for the XDCtools version change issue? I am guessing that TI-RTOS under "Products and Repositories" tab was not selected, so CCS was not able to find the "Target" and "Platform" required for the project.

    Vikram
  • Hi Henry,

    Were you able to resolve the issue?

    If yes, please mark this thread answered.

    Thanks,
    Vikram
  • Hi Vikram,

    Sorry I'm getting back late, but yes that did solve the building problem! I installed the openjdk-8 rather than 7 and right after created the same symlink, but again with -8 not -7. But there is still an error with connecting to the target with XDS110 USB Debug Probe for me.
  • That's great to hear.

    Please create a new thread for the XDS110 Debug Probe issue with details.