search

STMicroelectronics / STM32CubeH7

STM32Cube MCU Full Package for the STM32H7 series - (HAL + LL Drivers, CMSIS Core, CMSIS Device, MW libraries plus a set of Projects running on all boards provided by ST (Nucleo, Evaluation and Discovery Kits))
https://www.st.com/en/embedded-software/stm32cubeh7.html
Other
499 stars 305 forks source link

STM32CubeMX 6.0.1 with STM32Cube MCU Package for STM32H7 Series version 1.8.0 adds bad value for Keil UVPROJX file #65

Closed rxa1031 closed 4 years ago

rxa1031 commented 4 years ago

Hello,

I am currently using STM32CubeMX version 6.0.1 with STM32Cube MCU Package for STM32H7 Series version 1.8.0. The generated code executes when using ULINKpro, but does not execute when Reset signal is given to microcontroller or Power to Microcontroller is recycled.

When I open a IOC project that was created with below STM32CubeMX version with STM32CubeMX latest version 6.0.1, it asks for migrating the project.

MxCube.Version=5.6.1
MxDb.Version=DB.5.0.60

Once I migrate the project I save and close it. Then open the IOC again and generate code.

Below issue is observed when Toolchain / IDE: MDK-ARM (minimum version 5.27) is selected and Source code is generated.

                        <uC99>1</uC99>
                        <uGnu>1</uGnu>

When the earlier STM32CubeMX (version 5.6.1 was in use along with STM32Cube MCU Package for STM32H7 Series version 1.7.0) the generated Keil UVPROJX file had below values:

                        <uC99>1</uC99>
                        <uGnu>0</uGnu>

Please fix the bug by ensuring that <uGnu>0</uGnu> is added to Keil UVPROJX file.

Regards, @rxa1031

RKOUSTM commented 4 years ago

Hi @rxa1031,

Glad to read from you again. Thank you for your contribution. However, this issue is related to a generation problem with Cube MX. In fact, aspects related to Cube MX tool are not handled at GitHub level. They are rather treated at ST Community level, precisely within the Cube MX dedicated section.

Thank you for your comprehension.

With regards,

rxa1031 commented 4 years ago

Hello @RKOUSTM ,

Thanks for the information. I will share my concern on St Community.

Thanks, @rxa1031

rxa1031 commented 4 years ago

Hello @RKOUSTM

I am not sure whether closing this issue was a right step from my side.

Is there a way that this issue gets internally reported to appropriate team?

You may take appropriate action for this issue.

Regards, @rxa1031

RKOUSTM commented 4 years ago

Hi @rxa1031,

Thank you for your contribution. Allow me to close this ticket as it is out of the scope of this GitHub organization.

With regards,