This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Middle ware and STCubemx incompatibilities and errors

I have a long standing project using a stm32f205 that I started on an earlier version 4.xx

Anyway rather than not be able to use the latest tools eg Keil updates and MXCube for the peripheral drivers I have started to look at converting the project to use the latest version.

In doing so I have come across the following issues

I use the USB FS port as host controller for MSD mem sticks
So in RTE_Device.h I have t selected but I have not ticked
1) VBUS Power ON/OFF
2) Overcurrent Detection Pin

But during compilation using 5.15 it throws up the warnings

<1>
C:\Keil_v5\ARM\PACK\Keil\STM32F2xx_DFP\2.2.0\CMSIS\Driver\OTG_FS_STM32F2xx.h(54): error: #35: #error directive: Configure VBUS Power On/Off pin for USB OTG Full-speed in RTE_Device.h! #error Configure VBUS Power On/Off pin for USB OTG Full-speed in RTE_Device.h!
C:\Keil_v5\ARM\PACK\Keil\STM32F2xx_DFP\2.2.0\CMSIS\Driver\OTG_FS_STM32F2xx.c: 0 warnings, 1 error

Also in stm32f2xx_hal_adc.c

while using the FULL assert option for the cube classic I get

compiling stm32f2xx_hal_adc.c...
C:\Keil_v5\ARM\PACK\Keil\STM32F2xx_DFP\2.2.0\Drivers\STM32F2xx_HAL_Driver\Src\stm32f2xx_hal_adc.c(491): error: #268: declaration may not appear after executable statement in block uint32_t timeout;

I am aware the ST peripheral drives are nothing to do with Keil but just building up a hardware platform using the management run-time environment shouldn't bring up faults