2021-11-24 06:21 AM
Hi:
I've installed STM32CubeProgrammer and when connecting to the STLink debug programmer it worked ok.
But now, it just crashes. I've tested three different probes, on two different computers.
Both computers are running Linux (Arch Linux), kernel version:
Linux devmachine 5.15.4-arch1-1 #1 SMP PREEMPT Sun, 21 Nov 2021 21:34:33 +0000 x86_64 GNU/Linux
The crash report:
jar:file:/opt/STM32/stm32.programmer/bin/STM32CubeProgrammerLauncher!/fxml/Config.fxml
72 external Loader list
2.8.0
1.0.0
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fc9464320a3, pid=26309, tid=0x00007fc92825e640
#
# JRE version: OpenJDK Runtime Environment (8.0_265-b01) (build 1.8.0_265-b01)
# Java VM: OpenJDK 64-Bit Server VM (25.265-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libCubeProgrammer_API.so+0x500a3] connectStLink+0x293
#
# Core dump written. Default location: /opt/STM32/stm32.programmer/bin/core or core.26309
#
# An error report file with more information is saved as:
# /opt/STM32/stm32.programmer/bin/hs_err_pid26309.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.
#
./STM32CubeProgrammer: line 4: 26309 Aborted (core dumped) $DIR/jre/bin/java -jar $DIR/STM32CubeProgrammerLauncher
To rule out the Java, I've also tested with Oracle JDK/JRE 1.8-301 version, but same issue.
Any ideas?
2022-02-19 05:02 PM
I had this same error and for me the issue was the connection from my device (black pill) to the ST-Link. After following the instructions here it started working for me: https://waterpigs.co.uk/articles/black-blue-pill-stm32-st-link-connection/