search

STMicroelectronics / STM32CubeG0

STM32Cube MCU Full Package for the STM32G0 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))
Other
165 stars 75 forks source link

Undefined RCC_CFGR_SWS_* symbols in migrated project #12

Closed bridadan closed 3 years ago

bridadan commented 3 years ago

Describe the set-up

Describe the bug After migrating a project from STM32CubeG0 1.3.1 (STM32Cube IDE was upgraded from 1.2.0) to 1.4.0, I attempted to build the project and received the same error as described here: https://community.st.com/s/question/0D53W00000OUZHcSAP/stm32cubefwg0v140-bug-

How To Reproduce

  1. Create a project using STM32CubeG0 1.3.1
  2. Migrate the project to STM32CubeG0 1.4.0
  3. Run a "Clean"
  4. Build (I built with the Debug profile)
ASELSTM commented 3 years ago

Hi @bridadan,

Thank you for your contribution.

For a better understanding of the source of the issue may i ask you if you have used STM32CubeMx to generate the project or not ?

Best regards,

bridadan commented 3 years ago

Hi @ASELSTM,

I have used the STM32Cube IDE project generator (File -> New -> STM32 Project), so I don't believe so. After upgrading the IDE and selecting the project's .ioc file, I was prompted to continue using the STM32Cube version the project was using (1.3.1), or to migrate to the latest version (1.4.0).

After checking the forum page I linked above, it looks like it may be as simple as deleting and regenerating system_stm32g0xx.c. I'll give that a try and report back here when I have time.

Thanks!

ASELSTM commented 3 years ago

Hi @bridadan,

Actually, this kind of project generation is associated to the STM32CubeMx. STM32Cube IDE project generator is based on STM32CubeMx tool which is in charge of the project generation.

This issue has been already tracked internally and STM32CubeMx team is working on it. It will be fixed and made available in a future STM32CubeMX release.

In general terms, we don't treat aspects related to CubeMX tool at GitHub level, they are rather treated at ST Community level. Now, as this issue is not directly related to software component published within this repository (CMSIS, HAL, BSP, etc.) but rather to ecosystem (CubeMX tool), please allow me to close it.

Thank you for your comprehension and thank you again for your contribution. We are looking forward to reading from you again.

With regards,

bridadan commented 3 years ago

Thanks for clarifying @ASELSTM!