STM32 CubeMX - Generate Code fails on a Mac

[chairdeng]

Hi All

I have installed STM32 CubeMX on a Mac and I get the following error when trying to generate code:

The Eclipse executable launcher was unable to locate its companion shared library.

[Souhaib MAZHOUD]

Hello @chairdeng 

What version of macOS are you using?

KR,Souhaib

[chairdeng]

I use 15.1.1

[Ether]

I encountered exactly the same issue. I’m trying to compile STM32 projects on a Mac using CubeMX and CLion, but every time I click “Generate Code” in CubeMX, it throws this error, causing CLion to fail to compile. It shows the message: “No project sources generated. Run Generate Code in CubeMX.” MacBook Air M1.

[mƎALLEm]

Same issue as this thread.

[Souhaib MAZHOUD]

Hello @chairdeng @zuojaing 

This could be an issue related to the unzipping of STM32CubeIDE.
Could you please try this command line that removes extended attributes in macOS:
xattr -c /Applications/STM32CubeIDE.app

 

KR, Souhaib

[zuojaing]

Hi, after following your solution and running sudo xattr - c/Applications/STM32CubeIDE.app on the terminal, the problem persists. Are there any other solutions?

*This post has been translated from Chinese to comply with the ST Community guidelines.

[Souhaib MAZHOUD]

Could you try the same command line with ~/STM32CubeMX-6.13.0.app or try to uninstall CubeMX and reinstall it again and make sure to unzip the package using an official macOS® application such as the default graphical archive application, or the ditto tool in the command line:
$ditto -x -k setupArchive.zip

If the problem persists, please attach your IOC and log file to further investigate the issue.

[zuojaing]

When I uninstalled CubeMX and re-downloaded the CubeMX 6.13 installation package, both the macOS official extraction tool and the command sudo ditto -x -k en.stm32cubemx-mac-v6-13-0.zip ./STM32CubeMX failed to extract the file or reported an error: Couldn't read pkzip signature.

[Souhaib MAZHOUD]

Hello,

This behavior is under investigation by development team and tracked by the Ticket 198693 (for internal follow-up) and that will be fixed as soon as possible.
STM32CubeIDE can be used for project generation on macOS 15.1 and 15.2 as a temporary solution.

KR,

Souhaib

[denysbondar]

Unfortunately, as written here before, going back to version 6.12.1 does not fix the situation. The work has stopped. Please give this problem priority time.

[sirin]

Use Volume-Shared Virtual Machine applications (e.g. Parallels Desktop or something else) to run CubeMX on Windows to generate initial code might be a temporary workaround for this issue.

[Semer CHERNI]

Hello

We apologize for the issues created by the misbehavior of STM32CubeMX.
We are currently analyzing the root cause and we are given it high priority in order to provide a solution ASAP.

BR,
Semer.

[bdill.1]

pse.equinox.launcher.cocoa.macosx.x86_64_1.2.800.v20231003-1442/eclipse_11802.so' (code signature in <66ADAB06-1B30-301C-8ECA-7EDC8C31724D> '/Applications/STMicroelectronics/STM32CubeMX.app/Contents/Resources/third_parties_plugins/binaries/STM32CubeIDE-MX-services/revA/pool/plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.2.800.v20231003-1442/eclipse_11802.so' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs)
2025-01-16 16:32:31.766 eclipse[6342:15132672] WARNING: Secure coding is not enabled for restorable state! Enable secure coding by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState: and returning YES.

 

That's from the logs.... seems the most recent OSX requires a change/addition to the CubeMX

[bdill.1]

This worked as a stop gap for me, from my terminal history after a fresh install of CubeMX:

 

sudo codesign --force --deep --sign - /Applications/STMicroelectronics/STM32CubeMX.app
sudo codesign --force --deep --sign - /Applications/STMicroelectronics/STM32CubeMX.app/Contents/MacOs
sudo codesign --force --deep --sign - /Applications/STMicroelectronics/STM32CubeMX.app/Contents/MacOs/STM32CubeMX
sudo codesign --force --deep --sign - /Applications/STMicroelectronics/STM32CubeMX.app/Contents/MacOs/jre
sudo codesign --force --deep --sign - /Applications/STMicroelectronics/STM32CubeMX.app/Contents/Info.plist
codesign -vvv /Applications/STMicroelectronics/STM32CubeMX.app
codesign -vvv /Applications/STMicroelectronics/STM32CubeMX.app/Contents/Info.plist
codesign -vvv /Applications/STMicroelectronics/STM32CubeMX.app/Contents/MacOs/STM32CubeMX
codesign -vvv /Applications/STMicroelectronics/STM32CubeMX.app/Contents/MacOs/jre
sudo spctl --add /Applications/STMicroelectronics/STM32CubeMX.app
sudo spctl --add /Applications/STMicroelectronics/STM32CubeMX.app/Contents/Info.plist
sudo spctl --add /Applications/STMicroelectronics/STM32CubeMX.app/Contents/MacOs/STM32CubeMX
sudo spctl --add /Applications/STMicroelectronics/STM32CubeMX.app/Contents/MacOs/jre
sudo spctl --enable /Applications/STMicroelectronics/STM32CubeMX.app
sudo spctl --enable /Applications/STMicroelectronics/STM32CubeMX.app/Contents/Info.plist
sudo spctl --enable /Applications/STMicroelectronics/STM32CubeMX.app/Contents/MacOs/STM32CubeMX
sudo spctl --enable /Applications/STMicroelectronics/STM32CubeMX.app/Contents/MacOs/jre

Then launch it:
/Applications/STMicroelectronics/STM32CubeMX.app/Contents/MacOS/STM32CubeMX