SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world.
And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download two short videos (registration required) highlighting:

System Workbench for STM32

SW Crashes after hitting Run or Debug

Hey Guys,

just installed SW on my Mac running High Sierra. At first everything seems to work out fine, but after a while the workbench started to crash nearly everytime when I wanted to debug or run the program. The really annoying thing about this is that there is no Error message or anything comparable... Any ideas? Thanks in advance!


Hi cylegis,

Sorry to read that.. AFAIK SW has not been tested on High Sierra.
Could you attach the JRE crash log to this thread?
It is usually dumped into SystemWorkbench.app/Contents/MacOS/hs_err_pidxxxx.log
Edit: application logfile (workspace/.metadata/.log) would be welcome too.


Hey Julien thanks for your response! Just attached the error log. It says core dumping must be enabled and als advices to use the “ulimit -c unlimited” command before starting java. But the SW still crashes although the command has been used before... Any further tips? Thanks!

Thanks for the crash log, there is nothing related to SW.
For the time, I quickly googled the problem and it seems that many users are reporting issues with Eclipse on High Sierra.

Hi cylegis,

I toke the opportunity to have a Mac running High Sierra (10.13.1) to try to reproduce this crash, however Debug/Run work just fine.

Anyway I am not saying that there is no issue, because of many similar problems found on Eclipse bugzilla (crashes on native execution of org.eclipse.swt.internal.cocoa.OS.NSCopyBits(..)).
Most of them refer to https://bugs.eclipse.org/bugs/show_bug.cgi?id=502711Question which is fixed in Oxygen, version of Eclipse not yet integrated into SW ...

Also note that some topics claim on a bug on Apple side (AppKit), please check that your OSX is up-to-date.

I forgot to mention that the system log might also be useful, check if there is something interesting
in Console.app when the crash happens.

Hope this helps.

Hey Julien, thanks for your continuing help, really appreciate it!
Just attached the user report from the console.app... do you see anything I missed? However, the error seems to be not really deterministic... SW had done well during the first hours after the installation and then suddenly started to behave strange. In addition to this, the crash doesn’t occur every time, but randomly.
I also remember getting an error during the installation process. The error said something like “Failed to install the bundled Java Runtime”. I chose to continue using a preinstalled Java version... Is it possible that I’m having a Java issue?


cylegis wrote:
I also remember getting an error during the installation process. The error said something like “Failed to install the bundled Java Runtime”. I chose to continue using a preinstalled Java version... Is it possible that I’m having a Java issue?

Ok, so it looks really similar than an issue in another topic, occurring also on High Sierra:

And indeed the JRE in use is not the bundled one, from your log it is:


Can I ask you to reinstall again SW in console mode (./install_sw4stm32_macos_64bits-v2.3.run -c) to see if any message helps us to locate the issue ?

Also the error message contains a code helping in that way:

Failed to install the bundled Java Runtime Environment into System Workbench for STM32 (error ERRORCODE)
Application runtime will attempt to refer any already installed JRE

What is the value of ERRORCODE in your message ?

Hey Julien,

I just re-installed the SW using the console. Good News: This time no error occurred during the installation process! Bad News: the workbench still crashes randomly... What has changed: After re-opening the program, a dialog window opens claiming “Eclipse unexpectedly terminated” and also offering an error report, which I attached to this message. It seems to be the same as the sys log.

Thanks for your help!

At this time there is no solution from SW point of view as long as Eclipse/SWT have not backported the exiting fix on Neon.
I am in the loop if SWT moves in this direction, and will keep you informed through this topic.

Anyway feel free to get Oxygen by your own (C/C++ Developers package):

And install the SW4STM32 plugins suite as described here:

It should work but has not been tested right now since Oxygen integration is not in short terms plan.

Hope you will finally able to get working with SW4STM32 soon !

Edit: just made a quick sniff test (HighSierra_10.13.1 + Oxygen_4.7.1a + SW4STM32_2.3.1) and simple Debug works as expected.

I can report that I have had the same problem since upgrading to High Sierra on my Macbook Pro.

Building works for me if i select the “Problems” tab. If the “Console” tab is open it crashes after the first build.

Thank you, jLn_38, for the tip about installing Oxygen and the plugins separately. I will try that and see how it works.

I can the same problem reported, it crashes randomly, some times after a build or after try to debug, but most of the time is after debug. I search for a while, but I did not find any solution.
I’ll try to use Oxygen and see if works to.

Just had this happen to me twice in a half hour span, both times when clicking the debug button.

Eclipse version details:

Version: Neon.3 Release (4.6.3)
Build id: 20170314-1500

Installed from install_sw4stm32_macos_64bits-v2.4.run

I’ll attach crash report output in subsequent posts.

Has anyone find a solution?
I looked all over and did not find any solution.

I download the eclipse oxygen and install the SW4STM32 plugin and did not crash anymore.

Hey Luiz, that’s good news!

Can you let me know where to download the plugin(s) and how to add them to Eclipse Oxygen?

Awesome! Thanks Luiz for those instructions!

I actually jumped one version later and downloaded Photon, but the package installation is just the same and the issue is fixed in that version too.

Thanks again!

Hi sergeyzwezdin,
For the time being I can’t suggest you better solution than the one explained above, and pretty well describe by LuizRoque on 2018-07-17 12:45

I’m having the same problem on mac now and there is no clean solution, the latest suggested solution messes up the arm compiler paths. The latest independent installer is for 2017 which is very very outdated. The page that explains installing from eclipse claims it is compatible with 2019-12 version but cannot handle the PATH and doesn’t find the arm suite.

Well, the solution is not to use this piece of crap.
Try CLion for this, it’s paid, but much much better.
The problems that couldn’t be solved for years tells us - “do you this in production project”.