2026-05-07 5:00 AM
Hello.
I installed a new version of the IDE, exactly this:
st-stm32cubeide_2.1.1_28236_20260312_0043_x86_64
The problem is that the menu option "Manage embedded packages" is missing:
I checked this on two computers with Windows 10.
During the installation, there were no error messages.
What can be done about this?
Solved! Go to Solution.
2026-05-07 7:25 AM
Hello @xx111
STM32CubeMX 6.17.0 is no longer integrated into STM32CubeIDE 2.1.1. Instead, the two tools are now interoperable.
For more details , please check the following LINKs:
STM32CubeMX download Link:STM32CubeMX | Software - STMicroelectronics
STM32CubeIDE 2.0.0 workflow tutorial - STMicroelectronics Community
STM32CubeIDE 2.0 release - early heads-up! - STMicroelectronics Community
THX
Ghofrane
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.
2026-05-07 7:25 AM
Hello @xx111
STM32CubeMX 6.17.0 is no longer integrated into STM32CubeIDE 2.1.1. Instead, the two tools are now interoperable.
For more details , please check the following LINKs:
STM32CubeMX download Link:STM32CubeMX | Software - STMicroelectronics
STM32CubeIDE 2.0.0 workflow tutorial - STMicroelectronics Community
STM32CubeIDE 2.0 release - early heads-up! - STMicroelectronics Community
THX
Ghofrane
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.
2026-05-07 9:03 AM - edited 2026-05-08 11:58 PM
But does that mean I don't necessarily have to install packages in CubeIDE?
I'm talking about packages like STM32CubeU5.
It seemed logical for me that since the libraries contain Low-Layer APIs and CMSIS, they would be more needed by CubeIDE than by MX.
But I see that I was mistaken.
2026-05-11 2:45 AM
@xx111 wrote:does that mean I don't necessarily have to install packages in CubeIDE?
Yes: the packages are used by CubeMX - not directly by CubeIDE.
@xx111 wrote:It seemed logical for me that since the libraries contain Low-Layer APIs and CMSIS, they would be more needed by CubeIDE than by MX.
CubeIDE deals only with source files - it neither knows nor cares whether they came from ST (as a "Pack", via CubeMX), or from the user.