STM32 CubeMX - Generate Code fails on a Mac
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2024-12-01 2:43 AM
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.
Solved! Go to Solution.
- Labels:
-
Bug-report
-
STM32CubeMX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2024-12-13 3:45 AM
Using CubeIDE for project generating was the only possible solution. I just updated my macOS to 15.2 (24C101) yesterday, but someone else mentioned 15.1.1 as well. A downgrade of CubeMX didn't worked for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2024-12-13 5:32 AM
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
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2024-12-22 6:28 PM
Hello, what is the latest progress?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2024-12-29 12:33 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2025-01-02 11:08 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2025-01-03 5:41 AM
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.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2025-01-16 4:35 PM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2025-01-20 11:38 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2025-01-21 1:01 AM - edited 2025-05-20 6:17 AM
Hello @chairdeng
I am happy to announce the issue was fixed in STM32CubeMX.
You just need to download the installer form st.com and make a fresh install of STM32CubeMX 6.14.0.
KR,
Semer.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2025-01-21 10:02 AM
@Semer CHERNI- did you guys release a fix with the same version number?
