Setting CubeMX Files as Reference not generated project files

[Varadharajan V]

When Creating STM32Cube Project ,

While Selecting Code Generation Option as "Add necessary library files as reference in the toolchain project configuration file"

Then giving Finish will result the following

"Code Generation could not be done because the necessary firmware package is missing

Not able to complete STM32Cube project creation"

I am using

STM32CubeIDE V1.0

STM32Cube_FW_F4 1.24.1

Kindly rectify this

[Markus GIRDLAND]

I don't get the same thing, but we've had multiple threads over the past few days about path issues when there's a space involved. So this is just a guess but if you use a repository that doesn't have a space in it (I see your user is named Varadharajan V) does anything change?

[andrew.lanham]

I'd like to confirm the ongoing presence of this issue for the F4 v1.24.1 library. Some details:

>No spaces in my directory names. Adding or removing spaces seems to make no difference.

>Firmware library v1.24.1 is downloaded as Part Number Patch-CubeF4 (see https://www.st.com/en/embedded-software/stm32cubef4.html)

>Enclosed firmware library v1.24.1 appears to be mislabeled. When unzipping Patch-CubeF4 (en.patch_cubefw_f4.zip), the enclosed folder is labeled STM32Cube_FW_F4_V1.24.0. Changing to 1.24.1 makes no difference in resolving issue.

I think everything works when using v1.24.0, but would be nice to be updated to latest version!

Andrew

[Reactor]

Got the same error on STM32CubeIDE V1.1.0.

So how it can be solved?

[Cartu38 OpenDev]

F4_V1.24.0 is main FW pack delivery ... F4 V1.24.1 is only kind on patch to be applied on main delivery. If you have a look to .zip file size (or extracted material) you will confirm F4 V1.24.1 is missing some material ....

 Please have a try to unzip within same directory.

See maybe too : https://community.st.com/s/question/0D50X0000BeZi12SQC/code-generation-could-not-be-done-firmware-package-v1241-can-not-be-unzipped

[Cartu38 OpenDev]

About FW pack install issue possibly some local issue (FW pack locked by another process or ?) Good trick if facing back issue could be to get a try purging your current repository (i.e. here removing first any *F4_V1.24* material)