2016-11-09 06:03 AM
Hello,
as I understood, x-cube-cryptolib is a plugin for the cubemx software, isn't it?But when I run SRM32CubeMX, Version 4.17.0 and use Help->Install new libraries-> from local and select en.x-cube-cryptolib.zip, I get this error:This Package version is not managed on this version of STM32CubeMX.What's wrong? #cubemx2016-11-09 07:16 AM
Hi The Grue,
X-cube-cryptolib is not a plugin for the STM32CUBEMX, I will raise you request to our MX team -Syrine-2017-05-05 12:54 AM
Hello,
Sorry for the late reply.
Here is the user manual on the crypto lib
that is very usefull and detailed and find hereafter thehttp://www.st.com/en/embedded-software/x-cube-cryptolib.html
on ST website for the crypto lib.Hope it will help you.
BR. Eric
2017-07-24 07:54 AM
The original issue reported remains a problem with STM32CubeMX v4.21. This is the case despite the 'hereafter' link provided in the last post which links to v3.1.0 of the crypto library.
I'm confused why a library named X-CUBE-CRYPTOLIB is not a plugin for STM32CubeMX. If not CubeMX, then for which tool is the library a plugin?
2017-08-08 12:52 PM
Hi!
You can check this, hope to be useful:
2023-07-17 11:48 AM - edited 2023-07-17 11:54 AM
This is a dead link. So far the discussion in this thread does not address the original question: X-CUBE-CRYPTOLIB is distributed as a .zip file and is named following the same standards of many other STM32Cube packages, yet does not include the necessary metadata inside the .zip file to be treated as an STM32Cube expansion package. When STM32Cube opens the .zip file, it scans the file looking for this information and gives an error since it is not present.
If you look at the documentation tab for X-CUBE-CRYPTOLIB (https://www.st.com/en/embedded-software/x-cube-cryptolib.html#documentation) you will see the following:
This is the official documentation listed under X-CUBE-CRYPTOLIB. They all strongly suggest that X-CUBE-CRYPTOLIB is a software expansion package for STM32Cube, yet it fails to install as such.
This is very frustrating. I can unzip it and copy the files around manually and get it to work, but I'm quite certain that this is not how STMicro envisions its customers to use its resources. Can someone from ST Please answer these questions *directly* and *clearly*:
It is absolutely beyond comprehension how this is still an issue SIX YEARS after the original question was asked!
edit: Apparently expanding the .zipfile and manually moving things around is exactly how they expect this "expansion pack" to be used, contrary to their other software packs. See this wiki page which appears to be current: https://wiki.st.com/stm32mcu/wiki/Security:Getting_started_with_the_Cryptographic_Library
2024-05-29 01:16 AM - edited 2024-05-29 01:18 AM
Expressing my wish also to get it solved.
It is possible to integrate X-CUBE-CRYPTOLIB into your project by manual downloading, extracting, copy-pasting, configuring the linker in Eclipse (STM32CubeIDE) to find the library file, setting header files path and then just using it, but....
If you do it "nicely" by placing STM32_Cryptographic into the Middlewares folder then next time you let CubeMX/IDE generate your HAL, etc. files it will delete the STM32_Cryptographic library. If you change the settings and do not allow delete previous files, then HAL and other things can get polluted.
I appreciate ST making two nice things (CubeIDE/MX and free crypto library) but it would be much nicer if they fit together.