Skip to main content
Associate
Nov 12, 2024 8:29 AM UTC
Solved

Compilation Error Due to stm32h5xx_util_i3c.h Missing USE_FULL_LL_DRIVER Flag Protection

In the STM32H5 HAL, the file stm32h5xx_util_i3c.h was not included in the compilation list because it does not contain protection with the #if defined (USE_FULL_LL_DRIVER) flag, even though it uses the LL driver. This absence of protection results in a compilation error when the USE_FULL_LL_DRIVER flag is not defined.

Steps to Reproduce:

  1. Attempt to compile a project that references stm32h5xx_util_i3c.h without defining USE_FULL_LL_DRIVER.
  2. Observe the compilation failure due to missing flag protection in the file.

Suggested Solution:
Add conditional compilation protection around the code in stm32h5xx_util_i3c.h using #if defined (USE_FULL_LL_DRIVER). This would prevent compilation issues when the full LL driver is not in use.

 

This topic has been closed for replies.
STTwo-32
STTwo-32Best answer
ST Technical Moderator
Nov 12, 2024 8:51 AM UTC

Hello @vaa2ovr and welcome to the ST Community.

I've been able to reproduce this behavior. As a temporary workaround, you can copy the stm32_util_i3c.h from "STM32Cube_FW_H5_V1.3.0\Drivers\STM32H5xx_HAL_Driver\Inc to the " to the "Drivers/STM32H5xx_HAL_Driver/Inc/" of your project. I will report this for correction on the future (under internal ticket number 196105). 

Update: this issue has been solved on the STM32CubeMX V6.13.0.

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

2 replies

STTwo-32
STTwo-32Best answer
ST Technical Moderator
Nov 12, 2024 8:51 AM UTC

Hello @vaa2ovr and welcome to the ST Community.

I've been able to reproduce this behavior. As a temporary workaround, you can copy the stm32_util_i3c.h from "STM32Cube_FW_H5_V1.3.0\Drivers\STM32H5xx_HAL_Driver\Inc to the " to the "Drivers/STM32H5xx_HAL_Driver/Inc/" of your project. I will report this for correction on the future (under internal ticket number 196105). 

Update: this issue has been solved on the STM32CubeMX V6.13.0.

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
vaa2ovrAuthor
Associate
Nov 12, 2024 9:01 AM UTC

Thanks, the workaround works for me!