Dear MBDT Team. We are using MATLAB2023a scripts to generate code after compiling Simulink models, then call eclipsec.exe to perform headless background compilation. Once the build is completed, a hyperlink is created in the Simulink Diagnostic Viewer to directly open the workspace corresponding to the compiled project. This workflow worked perfectly with S32DS 3.4. However, after upgrading to S32DS 3.5.8, two issues have occurred: Issue 1: Clicking the hyperlink that's created by Simulink will launch the background process s32ds.exe, which then pops up and exits immediately. We have tried several solutions like adding the parameter "-vm \bin\javaw.exe" to s32ds.ini (this has no effect on s32ds.exe), and prioritizing the JDK 11 path in system environment variables. None of these attempts resolved the problem. Issue 2: As previous described, calling eclipsec.exe via MATLAB scripts triggers the error shown in the screenshot: Java was started but returned exit code=1. We set "\bin\javaw.exe" and JDK 11 path at the top of system environment variables. The Command Prompt correctly displays Java 11 (64-bit), yet Simulink compilation still attempts to load jvm.dll. After deleting "client\jvm.dll" or "server\jvm.dll", the program will locate java.exe instead, but still reports an error with exit code=4. In addition, manual compilation remains successful in all cases. All the related files and settings will be uploaded for your reference. Please help give your advice to fix this. Thank you.
