Can not use command line to generate automatically config from .mex file on S32DS 3.5

ManhTieuVan — Wed, 03 Aug 2022 15:56:08 GMT

Hi everyone, now I am using S32DS 3.5 and I am using the command line to support generating automatically config from .mex file. I used it on S32DS and it is ok but when using S32DS 3.5 then have some problem

Command: C:/NXP/S32DS.3.5/eclipse/eclipsec.exe -noSplash -application com.nxp.swtools.framework.application --launcher.ini C:/NXP/S32DS.3.5/s32ds.ini consoleLog -HeadlessTool Peripherals -Load C:/NXP/S32DS.3.5/eclipse/output/K1.mex -ExportSrc C:/NXP/S32DS.3.5/eclipse/output

Error:

!SESSION 2022-08-02 23:23:44.087 -----------------------------------------------
eclipse.buildId=3.5.0.202207261815
java.version=11.0.11
java.vendor=AdoptOpenJDK
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86_64

!ENTRY org.eclipse.equinox.preferences 4 2 2022-08-02 23:24:35.938
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences".
!STACK 0
java.lang.IllegalStateException: The instance data location has not been specified yet.
at org.eclipse.core.internal.runtime.DataArea.assertLocationInitialized(DataArea.java:59)
at org.eclipse.core.internal.runtime.DataArea.getStateLocation(DataArea.java:141)
at org.eclipse.core.internal.preferences.InstancePreferences.getBaseLocation(InstancePreferences.java:47)
at org.eclipse.core.internal.preferences.InstancePreferences.initializeChildren(InstancePreferences.java:212)
at org.eclipse.core.internal.preferences.InstancePreferences.<init>(InstancePreferences.java:62)
at org.eclipse.core.internal.preferences.InstancePreferences.internalCreate(InstancePreferences.java:224)
at org.eclipse.core.internal.preferences.EclipsePreferences.create(EclipsePreferences.java:352)
at org.eclipse.core.internal.preferences.EclipsePreferences.create(EclipsePreferences.java:340)
at org.eclipse.core.internal.preferences.PreferencesService.createNode(PreferencesService.java:395)
at org.eclipse.core.internal.preferences.RootPreferences.getChild(RootPreferences.java:63)
at org.eclipse.core.internal.preferences.RootPreferences.getNode(RootPreferences.java:98)
at org.eclipse.core.internal.preferences.RootPreferences.node(RootPreferences.java:87)
at org.eclipse.core.internal.preferences.PreferencesService$5.run(PreferencesService.java:620)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.preferences.PreferencesService.getNodes(PreferencesService.java:600)
at org.eclipse.core.internal.preferences.PreferencesService.getString(PreferencesService.java:686)
at com.nxp.s32ds.ext.rcp.datacollection.DataCollectionService.<init>(DataCollectionService.java:31)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.apache.felix.scr.impl.inject.internal.ComponentConstructorImpl.newInstance(ComponentConstructorImpl.java:312)
at org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:286)
at org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:115)
at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:1000)
at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:973)
at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:776)
at org.apache.felix.scr.impl.manager.AbstractComponentManager.enableInternal(AbstractComponentManager.java:674)
at org.apache.felix.scr.impl.manager.AbstractComponentManager.enable(AbstractComponentManager.java:437)
at org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.enableComponents(ConfigurableComponentHolder.java:667)
at org.apache.felix.scr.impl.BundleComponentActivator.initialEnable(BundleComponentActivator.java:305)
at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:554)
at org.apache.felix.scr.impl.Activator.access$200(Activator.java:70)
at org.apache.felix.scr.impl.Activator$ScrExtension.start(Activator.java:421)
at org.apache.felix.scr.impl.AbstractExtender.createExtension(AbstractExtender.java:196)
at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:169)
at org.apache.felix.scr.impl.AbstractExtender.addingBundle(AbstractExtender.java:139)
at org.apache.felix.scr.impl.AbstractExtender.addingBundle(AbstractExtender.java:49)
at org.osgi.util.tracker.BundleTracker$Tracked.customizerAdding(BundleTracker.java:475)
at org.osgi.util.tracker.BundleTracker$Tracked.customizerAdding(BundleTracker.java:1)
at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:450)
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:945)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:151)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:232)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:138)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:130)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:217)
at org.eclipse.osgi.container.Module.publishEvent(Module.java:499)
at org.eclipse.osgi.container.Module.start(Module.java:486)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1849)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1842)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1747)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1669)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)

!ENTRY org.eclipse.equinox.preferences 4 0 2022-08-02 23:24:35.948
!MESSAGE Error occurred while accessing preference scope.
!STACK 0
java.lang.IllegalStateException: The instance data location has not been specified yet.
at org.eclipse.core.internal.runtime.DataArea.assertLocationInitialized(DataArea.java:59)
at org.eclipse.core.internal.runtime.DataArea.getStateLocation(DataArea.java:141)

Re: Can not use command line to generate automatically config from .mex file on S32DS 3.5

mikedoidge — Tue, 09 Aug 2022 16:46:34 GMT

Hello @ManhTieuVan,

The S32 Configuration Tools depends upon RTD. Which RTD package are you using? I ask this because I think as of today, only S32Gxxx, S32K396, S32R41, SAF85xx are supported by RTD for S32DS 3.5. If you have no RTD installed, then you will get an error.

Best Regards,

Mike

Re: Can not use command line to generate automatically config from .mex file on S32DS 3.5

ManhTieuVan — Thu, 11 Aug 2022 16:02:34 GMT

Hi mikedoidge, I found the root cause that Defxclipse.java-modules.dir is not receiving the correct jre path of S32DS. I need to update path to absolute path.

ManhTieuVan_0-1660233455738.png

topic Re: Can not use command line to generate automatically config from .mex file on S32DS 3.5 in S32 Design Studio

Can not use command line to generate automatically config from .mex file on S32DS 3.5

Re: Can not use command line to generate automatically config from .mex file on S32DS 3.5

Re: Can not use command line to generate automatically config from .mex file on S32DS 3.5