Use en.x-cube-cryptolib in stm32cubemx

[mgrunwald9]

Posted on November 09, 2016 at 15:03

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?

 

#cubemx

[Nesrine M_O]

Posted on November 09, 2016 at 16:16

Hi The Grue,

X-cube-cryptolib is not a plugin for the STM32CUBEMX, I will raise you request to our MX team 

-Syrine-

[Jeanne Joly]

Posted on May 05, 2017 at 09:54

Hello,

Sorry for the late reply.

Here is the user manual on the crypto lib

http://www.st.com/content/ccc/resource/technical/document/user_manual/group0/f9/6e/f2/a2/b4/ec/49/c0/DM00215061/files/DM00215061.pdf/jcr:content/translations/en.DM00215061.pdf

that is very usefull and detailed and find hereafter the

http://www.st.com/en/embedded-software/x-cube-cryptolib.html

on ST website for the crypto lib.

Hope it will help you.

BR. Eric

[William Brosche]

Posted on July 24, 2017 at 16:54

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?

[Elkin Granados]

Posted on August 08, 2017 at 21:52

Hi!

You can check this, hope to be useful:

https://community.st.com/0D50X00009nNBvtSAG

 

[anotherandrew]

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*:

1. How does one install X-CUBE-CRYPTOLIB?
2. 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

[mkrk]

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.

[Marcos3]

In this date with STM32CubeIDE v2.0.0, STM32CubeMX v6.16.0, it's hard to find any info on how to install Software Expansions. Software Expansions come with CMSIS, HAL drivers and sometimes Middleware that can roll back STM32CubeH5 V1.5.1 drivers (in my case).

Simply copy the entire Software Expansion package over STM32CubeH5 (in my case) may overwrite existent data like drivers and examples. It seems to be not a good idea. This makes sense only when you patch with an update.

Under STM32CubeIDE point of view we can download Software Expansios, try them without "installing" in the STM32CubeH5 (in my case) and test it. When you have to use in a new project you have to "copy" inexistent files from these Software Expansions packs (like Middlewares), incorporate in the code and test for inconsistencies or mismatch dependencies. I don't think that is a good practice because Middleware may have dependency on some old driver...

Under STM32CubeMX point of view we don't have any choice. When you generate a code it will ends up erasing all manually added files in the previous generates.