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 (registration required) various documents highlighting:

System Workbench for STM32

[SOLVED] Arch Linux: CUBE crashes with SIGSEGV


I’m getting the following on the console after executing either code generation or code documentation generation:


A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x00007f39e5597b2c, pid=3721, tid=0x00007f39f273d700

JRE version: OpenJDK Runtime Environment (8.0_102-b14) (build 1.8.0_102-b14)
Java VM: OpenJDK 64-Bit Server VM (25.102-b14 mixed mode linux-amd64 compressed oops)
Problematic frame:
C libgdk-x11-2.0.so.0+0x4eb2c gdk_display_open+0x5c

Failed to write core dump. Core dumps have been disabled. To enable core dumping, try “ulimit -c unlimited” before starting Java again

An error report file with more information is saved as:

(Eclipse:3721): Gdk-WARNING **: XSetErrorHandler() called with a GDK error trap pushed. Don’t do that.

If you would like to submit a bug report, please visit:
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.


The code does get generated, I can import it and compile, and it runs as expected based on changes made in CUBE. The documentation is generated as well, Eclipse crashes *after* these tasks.

Eclipse Neon 4.6.0
CubeMX 4.17.0
OpenJDK Runtime Environment (8.0_102-b14)

Attached is the log file after crash after documentation generation.

Any hints as to what the problem is will be aprreciated!


Hi Bernard,

Thanks a million! I can confirm that displaying Settings for C/C++ Build options also caused Eclipse to hang, and now running Eclipse after export SWT_GTK3=0 did the trick. I can see the settings and generate code in Cube.

Maybe you (someone?) could add my case to the FAQ you mentioned - it seems another symptom for the same problem.