Skip to main content
godlyblade
Associate II
December 6, 2019
Solved

How to run STM32CubeProgrammer on MacOS Catalina 10.15.1 (19B88)

  • December 6, 2019
  • 13 replies
  • 10023 views

I have installed STM32CubeProgrammer V2.2.1 (https://www.st.com/en/development-tools/stm32cubeprog.html) on my MacBook without problems.

When I try to run the application, the programmer icon appears in the dock for about half a second and disappears immediately.

So I tried to open the application via terminal:

Last login: Fri Dec 6 15:40:05 on ttys000
➜ ~ /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -version
java version "1.8.0_221"
Java(TM) SE Runtime Environment (build 1.8.0_221-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.221-b11, mixed mode)
➜ ~ java -version
java version "13.0.1" 2019-10-15
Java(TM) SE Runtime Environment (build 13.0.1+9)
Java HotSpot(TM) 64-Bit Server VM (build 13.0.1+9, mixed mode, sharing)
➜ ~ sudo open /Applications/STMicroelectronics/STM32Cube/STM32CubeProgrammer/STM32CubeProgrammer.app
Password:
LSOpenURLsWithRole() failed with error -10810 for the file /Applications/STMicroelectronics/STM32Cube/STM32CubeProgrammer/STM32CubeProgrammer.app.

And I can see error code -10810...

What can I do now?

Best regards!

This topic has been closed for replies.
Best answer by godlyblade

Okay, its quite easy to get it to work (tested with macOS Catalina 10.15.1 (19B88))

Please see my post at SO!

1. To be sure you use the right java version deinstall all java versions first

~ java -version 
No Java runtime present, requesting install.

2. Now install " jdk-8u231-macosx-x64 "

3. After that the terminal should look like this

~ java -version
java version "1.8.0_231"
Java(TM) SE Runtime Environment (build 1.8.0_231-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.231-b11, mixed mode)

4. Go to the directory where the STM32CubeProgrammer installer is located. For example

~ cd /Users/myName/Desktop/en

5. Install the STM32CubeProgrammer

en sudo java -jar SetupSTM32CubeProgrammer-2.2.1.exe

6. The result should be

Command line arguments: 
====================
Installation started
Framework: 1.6.0_65-b14-468 (Apple Inc.)
Platform: mac_osx,version=10.15.1,arch=x86,symbolicName=null,javaVersion=1.8.0_231
Installation finished

7. Now you can open the programmer app

Hope this helps!

Best Regards!

13 replies

CBrad.3
Visitor II
October 26, 2021

I've just installed on Monterey macOS 12.0.1

Just do as the 2nd post says.

Install " jdk-8u231-macosx-x64 "

Go to the directory where the STM32CubeProgrammer installer is located.

Probably your downloads folder.

Open Terminal

Type:

cd downloads
cd en

then type this (substitute the version number if yours is different / newer):

sudo java -jar SetupSTM32CubeProgrammer-2.8.0.exe

Once the app has finished installing, you're NOT finished yet.

Open the folder where STM32 programmer was installed.

Right click on the SetupSTM32CubeProgrammer-2.8.0 file (NOT the exe), and click "Show Package Contents".

Now drag the "jre" folder from your downloads en folder, in to the package contents you're just opened.

Close the folder and double click on the app.

It should run. It did for me.

Update 31st Oct 2022:

I've just successfully used the same installation steps with -

macOS Ventura 13.0

jdk-11.0.16.1

SetupSTM32CubeProgrammer-2.11.0

eos1d3
Associate II
October 31, 2021

Hi,

Thanks a lot for your help.

I incorrectly copied jre to wrong location of the application. From you reply, I now copy it to the same level as Contents of STM32CubeProgrammer.

I do not use the JAVA version you mentioned. I tried Java 1.8.0_302 and 11.0.12. Both work during installation and also connecting ST-Link V2.

Sines
Visitor II
December 22, 2021

Also hitting a wall in Big Sur, got the following when following the steps above to a T.

I can launch STMCubeProgrammer, but when selecting JTAG as an interface and attempting to connect, I crash every. single. time.

Have any ideas? Toying with an upgrade to Monterey, just to make life more complicated.

sines@scale-MBP en.stm32cubeprg-mac_v2-9-0_v2.9.0 % cd /Applications/STMicroelectronics/STM32Cube/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/MacOs/bin 
sines@scale-MBP bin % java -jar STM32CubeProgrammer
Buffer size finally used for transfers: 8192 bytes
jar:file:/Applications/STMicroelectronics/STM32Cube/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/MacOs/bin/STM32CubeProgrammer!/fxml/Config.fxml
73 external Loader list
 
/Applications/STMicroelectronics/STM32Cube/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/MacOs/bin
CubeProgrammer version: 2.9.0
Path CubeProgrammer version: : /Applications/STMicroelectronics/STM32Cube/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/MacOs/bin/version
Updater version:1.0.0
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000135da7a57, pid=2954, tid=0x000000000001fbdf
#
# JRE version: Java(TM) SE Runtime Environment (8.0_231-b11) (build 1.8.0_231-b11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.231-b11 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# C [libCubeProgrammer_API.dylib+0x9a57] connectStLink+0x787
#
# 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:
# /var/folders/k2/0cbgkk2x46b30zg8yb82196m0000gn/T//hs_err_pid2954.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
zsh: abort java -jar STM32CubeProgrammer
sines@scale-MBP bin % java -version 
java version "1.8.0_231"
Java(TM) SE Runtime Environment (build 1.8.0_231-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.231-b11, mixed mode)

eos1d3
Associate II
December 22, 2021

Do you have target board connected? For me, when there is no target board, connecting using SWD or JTAG just crash. I do not have any board to test JTAG right now.

But Windows version does not have this issue.