2020-01-29 04:16 PM
I can't seem to get CubeMX to install the CMSIS package. I have tried downloading directly from CubeMX, downloading .pack file and installing it from local (from Keil, arm, and even ST's github).
I get an error "Problem during load of selected file... Unzip attempted beyond top-level directory:
I tried both before and after the 5.5.0 update to no avail.
And to make things worse I'm trying to migrage from Keil to IAR and really need the LL drivers to keep me from having to re-write a large portion of my code.
Any help is greatly appreciated
2020-01-30 12:27 AM
Hello @SAllr.1
Thanks for your feedback , It will be internally checked.
Best Regards,
Khouloud.
2020-05-16 05:47 PM
Hi @Khouloud ZEMMELI. There is still an issue
This is the build information I have
STM32CubeIDE
Version: 1.3.0
Build: 5720_20200220_1053 (UTC)
OS: Linux, v.5.4.0-29-generic, x86_64 / gtk 3.24.18, WebKit 2.28.2
Java version: 1.8.0_242
I have attached an image of the error.
When can we expect this to be fixed?
2020-05-16 06:57 PM
Same thing happens for me on Win10 with CubeMX 5.6.1. *shrug*
However, this is a different error than the one in the original post.
2020-07-18 06:12 PM
Before you close the dialog box, you will find the pack file in the <repo directory>/Packs/ARM/CMSIS/5.7
Unzip the file so you have the following files residing in the same location as the .pack file
This should work. I only just tried this myself and it appears to work.
For the ST Employee: Why is this issue still hanging around 6 months later? Why is this considered an error - maybe this should just be a warning, or silently ignored as you don't have any M55 based cores in the STM32 lineup, which is probably why it doesn't exists in your schema.
Does ARM have a schema that you could use for validation?
2021-07-30 03:56 AM
This problem is not six (6) months delinquent, but rather about eighteeen (18) months delinquent. The same or similar flaws exist, and today (in 2021) I tried to install the file:
en.STM32CubeExpansion_Crypto_v4.0.1.zip
...downloaded from the page:
https://www.st.com/en/embedded-software/x-cube-cryptolib.html
It failed in a similar way with this printed to the console:
2021-07-30 12:28:46,107 [WARN] PackLoader:238 - Cannot read IP mode file for STMicroelectronics.X-CUBE-GNSS1.5.2.0
2021-07-30 12:28:46,112 [INFO] ThirdParty:915 - Integrity check success = true
2021-07-30 12:28:46,112 [INFO] IntegrityCheckThread:94 - exiting critical section [integrity check]
2021-07-30 12:28:46,112 [INFO] IntegrityCheckThread:97 - End integrity checks thread
2021-07-30 12:28:48,128 [INFO] About:244 - Db Path : /home/user/STM32CubeMX//db/
2021-07-30 12:28:48,128 [INFO] About:251 - Version : DB.6.0.30
2021-07-30 12:29:45,088 [INFO] CheckServerUpdateThread:112 - End of CheckServer Thread
2021-07-30 12:30:31,408 [ERROR] FileExtend:450 - File entry not found
2021-07-30 12:30:31,408 [ERROR] CmsisPacksFileManager:118 - Missing pdsc file within cmsis pack : Invalid pack file
2021-07-30 12:30:31,408 [ERROR] LoadLocalFilesThread:310 - Cmsis pack invalid or pdsc file is missing.
So it seems that ST engineers are waiting a few years to solve the problem I guess?
Or is there a secret way to installing packages like the X-CUBE-CRYPTOLIB and if so, what is the value of withholding this information from the users?