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:
- Product Specifications: DB2660 describes this as a software expansion package.
- User Manuals: UM2312 is the "development checklist" for STM32Cube expansion packages
User Manuals: UM2285 is the "Development guidelines" for STM32Cube expansion packages - UM2388 is the "development guidelines" for STM32Cube firmware packs
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*:
- How does one install X-CUBE-CRYPTOLIB?
- Where is the documentation that explains #1 above?
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
