Skip to main content
Rajeev Arora
Rajeev Arora
Senior
October 1, 2020
Solved

STM32CubeMX 6.0.1 with STM32Cube MCU Package for STM32H7 Series version 1.8.0 unchecks the MicroLIB checkbox

  • October 1, 2020
  • 7 replies
  • 4320 views

Hello,

I have an IOC file, which was generated with help of STM32CubeMX

MxCube.Version=5.6.1

MxDb.Version=DB.5.0.60

When I open this project to update the Keil project (which has Keil Compiler version 6 selected), with STM32CubeMX version 6.0.1 (with STM32Cube MCU Package for STM32H7 series version 1.8.0), and generate code, the STM32CubeMX deselects the MicroLIB check box.

I am observing the code is not behaving as expected with MicroLIB disabled / unchecked.

As the issue is not observed when using the ULINKpro debugger (which I am using to find the reason for the issue) I am unable to find the reason for different behavior of the same code just based on whether the MicroLIB is in use or not in use.

Please help with resolving my concern.

Thanks,

Rajeev

This topic has been closed for replies.
Best answer by MChec.1

I find this answer to be not acceptable. If there is an issue with using Keil's MicroLib, then it should be described in the release notes. If there is no issue with linking in MicroLIb, then do not reconfigure the project file. It is quite annoying to have to recheck a project file setting every time I regenerate a configuration. What other project settings are you changing behind my back?

Second, manipulating a project file, just to hide some compile warning is not ever acceptable. Transparency is paramount here. Let the warnings be issued, at least the users will be able to deal with them. Better yet, fix the code before you release it.

7 replies

Rajeev Arora
Rajeev AroraAuthor
Senior
October 5, 2020

7 ZIP file with sample IOC and UVPROJX file available with issue https://community.st.com/s/feed/0D53W00000JhsNISAZ

Rajeev Arora
Rajeev AroraAuthor
Senior
October 5, 2020

Please help.

Khouloud ZEMMELI
Khouloud ZEMMELI
ST Employee
October 7, 2020

Hello @Rajeev Arora​ 

It will be internally checked.

Best Regards,

Khouloud

Khouloud ZEMMELI
Khouloud ZEMMELI
ST Employee
October 12, 2020

Hi @Rajeev Arora​ 

After checking, this is not a bug but a change made by our development team on H7 & MP1 to avoid some compilation errors, the user can activate the MicroLIB on Keil at the end if it is necessary for his project (once your MX setup is complete).

Best Regards,

Khouloud

Rajeev Arora
Rajeev AroraAuthor
Senior
October 12, 2020

Hello @Khouloud ZEMMELI​  ,

Thanks for sharing the update.

from your inputs I understand that every time I generate the code with help of IOC file, the MicroLIB setting (even if enabled) in the existing UVPROJX file will get updated to unchecked, and then I will have to manually add that setting with help of Keil IDE or by making change to the UVPROJX file (by opening it in a text editor).

Is my understanding correct?

Thanks,

Rajeev

Khouloud ZEMMELI
Khouloud ZEMMELI
ST Employee
October 12, 2020

Yes, because MX force the MicroLIB to be unchecked for H7 and MP1, so every time you re-generate code MicroLIB will take the MX configuration.

Thanks for your understanding and you're always welcome.

Regards,

Khouloud

MChec.1
MChec.1Best answer
Associate
March 30, 2021

I find this answer to be not acceptable. If there is an issue with using Keil's MicroLib, then it should be described in the release notes. If there is no issue with linking in MicroLIb, then do not reconfigure the project file. It is quite annoying to have to recheck a project file setting every time I regenerate a configuration. What other project settings are you changing behind my back?

Second, manipulating a project file, just to hide some compile warning is not ever acceptable. Transparency is paramount here. Let the warnings be issued, at least the users will be able to deal with them. Better yet, fix the code before you release it.

VnlaCola
VnlaCola
Visitor II
August 11, 2021

Yeah. It's hard to disagree.​

Rajeev Arora
Rajeev AroraAuthor
Senior
August 25, 2021

Hello @Khouloud ZEMMELI​ 

After a while I opened one of my project's IOC file with STM32CubeMX version 6.3.0 and regenerated the code, so as to incorporate the Device Driver fixes.

The generated project was not working as expected and would crash. I had to debug the code and still could not find the reason for the Hard Fault. I was not sure whether the updated FreeRTOS or the Driver codes were causing it. So I had to start merging pieces of the newly generated code to the old / existing code.

I now have reached to the conclusion that the STM32CubeMX removing the Use MicroLIB check is the reason for the issue. This setting is available in Keil IDE under Options For Target -> Target -> Code Generation (section)

I am using ARM Compiler version 6. I have removed the Middlewares\Third_Party\FreeRTOS\Source\portable\RVDS folder and instead using the Middlewares\Third_Party\FreeRTOS\Source\portable\GCC folder so as to use Keil Compiler version 6.

Please help with the fix. My team mates and the ST Community might face the same / similar issue because of STM32CubeMX making unwanted changes.

Thanks,

Rajeev

william.w.jr
william.w.jr
Associate
September 9, 2021

After upgrade to 6.3.0 almost every project uncheck "Use MicroLib" after regenerated project files.... What .......

Terms & ConditionsAccessibility statement