AnsweredAssumed Answered

Java error in MCUxpresso IDE

Question asked by dave408 on Nov 27, 2018
Latest reply on Jan 24, 2019 by Fang Li

We're moving to MCUxpresso with our Kinetis-based products, and currently we have a project on our build server that is "failing" with the following Java error:


[15:48:59]Java was started but returned exit code=1
[15:48:59]-os win32
[15:48:59]-ws win32
[15:48:59]-arch x86
[15:48:59]-launcher C:\nxp\MCUXpressoIDE_10.2.1_795\ide\mcuxpressoidec.exe
[15:48:59]-name Mcuxpressoidec
[15:48:59]--launcher.library C:\nxp\MCUXpressoIDE_10.2.1_795\ide\\plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.551.v20171108-1834\eclipse_1630.dll
[15:48:59]-startup C:\nxp\MCUXpressoIDE_10.2.1_795\ide\\plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
[15:48:59]-application org.eclipse.cdt.managedbuilder.core.headlessbuild
[15:48:59]-data MCUX_VF1_Workspace
[15:48:59]-cleanBuild MCUX_VF1/Debug
[15:48:59]-import nxp\MCUX_VF1
[15:48:59]-vm C:\nxp\MCUXpressoIDE_10.2.1_795\ide\jre\bin\client\jvm.dll
[15:48:59]Process exited with code 1

The strange thing is that the code is still compiled and the binary is generated.


I've read in the Eclipse forums that in order to solve this problem, we have to match the "bitness" of the JDK and MCUxpresso.  I can't definitively find this information for MCUxpresso.  In the output above, I can't tell if -arch x86 refers to the JDK or the IDE.


Is anyone else having this problem?  We see it on our build server, but not on developer PCs.