NUCLEO STM32F767ZI: problems to enable USB OTG FS (Host)

Hello,

Tips: please refer to the example provided in STM32CubeF7 under : Projects\STM32F767ZI-Nucleo\Applications\USB_Host\MSC_Standalone

STM32

Hi,

thanks! - i was using another example as reference: FatFs_USBDisk (which works).

But both - FatFs_USBDisk and MSC_Standalone - don't use *.ioc file for the project.

Is there a reference project with *.ioc? I would like to use that device configuration tool.

regards,

Frank

Hello,

I think the simple way to generate USB_FS by using CubeMx with NUCLEO STM32F767ZI is to start your project from "Home" and select "Access to board selector" instead of MCU. Then let CubeMx initialize the board. You can add your code after ..

STM32

I think there is an error in the generated code here:

/**

 * @brief Drive VBUS.

 * @param state : VBUS state

 *         This parameter can be one of the these values:

 *          - 1 : VBUS Active

 *          - 0 : VBUS Inactive

 */

void MX_DriverVbusFS(uint8_t state)

{

 uint8_t data = state;

 /* USER CODE BEGIN PREPARE_GPIO_DATA_VBUS_FS */

 if(state == 0)

 {

   /* Drive high Charge pump */

   data = GPIO_PIN_SET;

 }

 else

 {

   /* Drive low Charge pump */

   data = GPIO_PIN_RESET;

 }

 /* USER CODE END PREPARE_GPIO_DATA_VBUS_FS */

 HAL_GPIO_WritePin(GPIOG,GPIO_PIN_6,(GPIO_PinState)data);

}

The state evaluation is inverse.

its wrong in the framework code:

plugins/com.st.stm32cube.common.mx_6.2.1.202103241236/db/templates/usbh_platform_c.ftl

Hello,

Could you please attach the .ioc file that generates the above code of "void MX_DriverVbusFS(uint8_t state)"?

STM32

Hello,

> Your .ioc file generation code does not contain MX_DriverVbusFS(uint8_t state) function. Same case with your user code.

In my implementation in usbh_conf.c there is some USBH_LL_DriverVBUS() which delegates to MX_DriverVbusFS(), and it is implemented in my usbh_platform.c.

But the image created by STM32CubeIDE was wrong - until i fixed that manually.

And it is also wrong in the base image in /opt/st/stm32cubeide_1.6.1/plugins/com.st.stm32cube.common.mx_6.2.1.202103241236/db/templates/usbh_platform_c.ftl

from the installation of st-stm32cubeide_1.6.1_9958_20210326_1446_amd64.deb_bundle.sh (https://www.st.com/en/development-tools/stm32cubeide.html)

But thanks for pointing at the

> Projects\STM32F769I_EVAL\Applications\USB_Host\MSC_RTOS : with RTOS

as a reference :thumbs_up:

However, this reference is for a different board: STM32F769

And it does not have a *.ioc file, in which i could try to change the setting to make it usable for STM32F767.

(Btw, if "Projects\STM32F769I_EVAL\Applications\USB_Host\MSC_RTOS" would have some *.ioc file: would STM32CubeIDE support changing the board type for that? And do the adjustments for my board STM32F767 via *.ioc file?)

Moreover, this reference "Projects\STM32F769I_EVAL\Applications\USB_Host\MSC_RTOS" has some different USBH_LL_DriverVBUS() implementation - in usbh_conf.c:

USBH_StatusTypeDef USBH_LL_DriverVBUS(USBH_HandleTypeDef *phost, uint8_t state)
{
#ifdef USE_USB_FS
 if(state == 0)
 {
 /* Configure Low Charge pump */
 BSP_IO_WritePin(OTG_FS1_POWER_SWITCH_PIN, BSP_IO_PIN_RESET);
 }
 else
 {
 /* Drive High Charge pump */
 BSP_IO_WritePin(OTG_FS1_POWER_SWITCH_PIN, BSP_IO_PIN_SET);
 }
 
#endif
 
#ifdef USE_USB_HS_IN_FS
 if(state == 0)
 {
 /* Configure Low Charge pump */
 BSP_IO_WritePin(OTG_FS2_POWER_SWITCH_PIN, BSP_IO_PIN_RESET);
 }
 else
 {
 /* Drive High Charge pump */
 BSP_IO_WritePin(OTG_FS2_POWER_SWITCH_PIN, BSP_IO_PIN_SET);
 } 
#endif 
 HAL_Delay(200);
 return USBH_OK; 
}

I.e. this one does not use (delegate to) some MX_DriverVbusFS() function.

Instead, it implements itself. And it does this correct (while the MX_DriverVbusFS() implementation is wrong).

Is it possible, to have a version of "Projects\STM32F769I_EVAL\Applications\USB_Host\MSC_RTOS", that used *.ioc file?

thanks in advance!

regards,

Frank

Hello @FBerg.1​,

Unfortunately there is no .ioc file for F4, F7, H7 families .. and the examples/demo provided are developed directly with HAL. May be .ioc files will be available in the Cubes of new coming products.

There is no difference between STM32F769 & STM32F767 devices except the DSI interface which is available on F769.

For the boards, the main difference I think is the clock configuration. So I think you have to configure the board with periph initialization and then follow the example which I pointed out just for reference for USB config, then put your user code..

For the generated erroneous code with CubeMx I will escalate the subject internally, if there is an issue it will be fixed.

STM32