2025-02-28 8:17 AM - edited 2025-03-03 2:05 AM
We are pleased to announce that the release 6.14.0 of STM32CubeMX is available.
What is new in 6.14.0:
Main fixed issues in 6.14.0:
Refer to the STM32 microcontroller wiki at:
https://wiki.st.com/stm32mcu/wiki/Category:STM32CubeMX_errata
Known problems and limitations in 6.14.0:
Refer to the STM32 microcontroller wiki at:
https://wiki.st.com/stm32mcu/wiki/Category:STM32CubeMX_errata
How to get STM32CubeMX 6.14.0:
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.
2025-03-03 1:03 AM
I'm not sure where to give feedback for the new version of CubeMX, so I answere here.
I noticed that CubeMX will generate a CMakeLists.txt inside stm32cubemx folder, with ${CMAKE_SOURCE_DIR} variable instead of relative path. Which is actually a good improvement, but if the CMake project is added as a subdirectory in another directory, the path will be wrong.
An example:
- workspace_folder
- CMakeLists.txt - with add_subdirectory(GeneratedCMakeProject) and add_subdirectory(AnotherCMakeProject)
- GeneratedCMakeProject
- CMakeLists.txt - CubeMX generated project
- AnotherCMakeProject
- CMakeLists.txt - CubeMX generated project
I found that in that case the ${PROJECT_SOURCE_DIR} is more suitable.
Also I have multiple generated projects in my workspace (VS Code) but in this case the generated targets have the same name (stm32cubemx) and cmake fails to configure. Currently I modified the generated CMakeLists.txt to add a suffix to the generated target, i.e. stm32cubemx-GeneratedCMakeProject.
Is there another way to have more generated projects in one workspace?
2025-03-08 10:17 PM
Hi, failed for me if install with `-console`
./SetupSTM32CubeMX-6.14.0 "-console"
Check exe path on linux
FullExe path1 is: /tmp/makepkg/stm32cubemx/src/SetupSTM32CubeMX-6.14.0
Exe path is: /tmp/makepkg/stm32cubemx/src
Search java from relative path ----
Checking java in /tmp/makepkg/stm32cubemx/src/./jre/bin/java
current working dir : /tmp/makepkg/stm32cubemx/src
av[0] ./SetupSTM32CubeMX-6.14.0
chdir to :/tmp/makepkg/stm32cubemx/src/.
New current working dir /tmp/makepkg/stm32cubemx/src
Full command: /tmp/makepkg/stm32cubemx/src/./jre/bin/java
-args[0] java
-args[1] -jar
-args[2] SetupSTM32CubeMX-6.14.0
-args[3] -console
Command line arguments: -console
────────────────────────────────────────────────────────────────────────────────
Welcome to the Installation of STM32CubeMX 6.14.0
────────────────────────────────────────────────────────────────────────────────
Starting STM32CubeMX 6.14.0 installation
The homepage is at: https://www.st.com/stm32cube
Press 1 to continue, 2 to quit, 3 to redisplay
1
Please read the following information:
────────────────────────────────────────────────────────────────────────────────
STM32CubeMX License agreement
────────────────────────────────────────────────────────────────────────────────
SOFTWARE PACKAGE LICENSE AGREEMENT
Please indicate your acceptance or NON-acceptance by selecting "I ACCEPT" or "I DO NOT ACCEPT" as indicated below in the media.
BY INSTALLING COPYING, DOWNLOADING, ACCESSING OR OTHERWISE USING THIS SOFTWARE PACKAGE OR ANY PART THEREOF (AND THE RELATED DOCUMENTATION) FROM STMICROELECTRONICS INTERNATIONAL N.V, SWISS BRANCH AND/OR ITS AFFILIATED COMPANIES (STMICROELECTRONICS), THE RECIPIENT, ON BEHALF OF HIMSELF OR HERSELF, OR ON BEHALF OF ANY ENTITY BY WHICH SUCH RECIPIENT IS EMPLOYED AND/OR ENGAGED AGREES TO BE BOUND BY THIS SOFTWARE PACKAGE LICENSE AGREEMENT.
Under STMicroelectronics' intellectual property rights and subject to applicable licensing terms for any third-party software incorporated in this software package and applicable Open Source Terms (as defined here below), the redistribution, reproduction and use in source and binary forms of the software package or any part thereof, with or without modification, are permitted provided that the following conditions are met:
1. Redistribution of source code (modified or not) must retain any copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form, except as embedded into microcontroller or microprocessor device manufactured by or for STMicroelectronics or a software update for such device, must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of STMicroelectronics nor the names of other contributors to this software package may be used to endorse or promote products derived from this software package or part thereof without specific written permission.
4. This software package or any part thereof, including modifications and/or derivative works of this software package, must be used and execute solely and exclusively on or in combination with a microcontroller or a microprocessor devices manufactured by or for STMicroelectronics.
5. No use, reproduction or redistribution of this software package partially or totally may be done in any manner that would subject this software package to any Open Source Terms (as defined below).
6. Some portion of the software package may contain software subject to Open Source Terms (as defined below) applicable for each such portion ("Open Source Software"), as further specified in the software package. Such Open Source Software is supplied under the applicable Open Source Terms and is not subject to the terms and conditions of license hereunder. "Open Source Terms" shall mean any open source license which requires as part of distribution of software that the source code of such software is distributed therewith or otherwise made available, or open source license that substantially complies with the Open Source definition specified at www.opensource.org and any other comparable open source license such as for example GNU General Public License (GPL), Eclipse Public License (EPL), Apache Software License, BSD license and MIT license.
7. This software package may also include third party software as expressly specified in the software package subject to specific license terms from such third parties. Such third party software is supplied under such specific license terms and is not subject to the terms and conditions of license hereunder. By installing copying, downloading, accessing or otherwise using this software package, the recipient agrees to be bound by such license terms with regard to such third party software.
8. STMicroelectronics has no obligation to provide any maintenance, support or updates for the software package.
9. The software package is and will remain the exclusive property of STMicroelectronics and its licensors. The recipient will not take any action that jeopardizes STMicroelectronics and its licensors' proprietary rights or acquire any rights in the software package, except the limited rights specified hereunder.
10. The recipient shall comply with all applicable laws and regulations affecting the use of the software package or any part thereof including any applicable export control law or regulation.
11. Redistribution and use of this software package partially or any part thereof other than as permitted under this license is void and will automatically terminate your rights under this license.
THIS SOFTWARE PACKAGE IS PROVIDED BY STMICROELECTRONICS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS, IMPLIED OR STATUTORY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT OF THIRD PARTY INTELLECTUAL PROPERTY RIGHTS ARE DISCLAIMED TO THE FULLEST EXTENT PERMITTED BY LAW. IN NO EVENT SHALL STMICROELECTRONICS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE PACKAGE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
EXCEPT AS EXPRESSLY PERMITTED HEREUNDER AND SUBJECT TO THE APPLICABLE LICENSING TERMS FOR ANY THIRD-PARTY SOFTWARE INCORPORATED IN THE SOFTWARE PACKAGE AND OPEN SOURCE TERMS AS APPLICABLE, NO LICENSE OR OTHER RIGHTS, WHETHER EXPRESS OR IMPLIED, ARE GRANTED UNDER ANY PATENT OR OTHER INTELLECTUAL PROPERTY RIGHTS OF STMICROELECTRONICS OR ANY THIRD PARTY.
SLA0048 - Rev 4 - March 2018 For further information contact your local STMicroelectronics sales office. www.st.com
Press 1 to accept, 2 to reject, 3 to redisplay
1
I have read and understood the ST Privacy Policy (https://www.st.com/content/st_com/en/common/privacy-policy.html) and ST Terms of Use (https://www.st.com/content/st_com/en/common/terms-of-use.html).
Press Enter to continue, X to exit
ST int N.V (as data controller) collects and uses anonymous features usage statistics (directly or by ST affiliates) when you use the application for the purpose of continuously improving the application.
You can stop the collection of your features usage statistics when you use the application at any time with effect for the future
or update your preferences via the menu
Help > User Preferences > General Settings
Press anything to continue
Analytics service enabled
SEVERE: Cannot invoke "java.lang.CharSequence.toString()" because "s" is null
[ Console installation FAILED! ]
WARNING: Cannot invoke "java.util.List.iterator()" because "this.files" is null
greetings
2025-03-19 2:11 PM
I realize this may not change anything, but I’d like to ask regardless: please avoid using ${CMAKE_SOURCE_DIR} in CMake-generated files. Instead, use ${CMAKE_CURRENT_LIST_DIR} or other relative-path variables. I had a workaround that allowed me to skip the CMake ExternalProject module (used in dual-core projects), but recent changes have broken that approach. As a result, I’m forced to revert to a previous version. The ExternalProject module breaks VS Code IntelliSense and disrupts VS Code’s build-system integration. Thank you!
2025-03-20 1:55 AM
Hi @peterdonchev,
It's unrelated, but how did you do that if I can ask?
Currently I need two different cmake project one for the MCU code and one for unit tests (local build). CMake cannot handle multiple toolchains, so I solved this with VS Code multi-root workspaces (*.code-workspace file). But I'm not 100% satisfied with my solution, so I'm open to any suggestions.