Skip to main content
B.Montanari
ST Technical Moderator
October 26, 2023

How to use STMicroelectronics classic USB device middleware with new STM32 families

  • October 26, 2023
  • 81 replies
  • 88647 views

Summary

This article presents a tutorial for importing and using the legacy STMicroelectronics USB middleware in the new lines of STM32 to implement a CDC class to open a virtual COM port. The STM32H5 series was selected for this tutorial, but the steps can be easily tailored to some other STM32 families, such as STM32U5.

For all the STM32 series released from 2021 onwards, the now classic, STMicroelectronics USB middleware is no longer offered as part of the STM32Cube native offer. But to maintain compatibility with legacy applications, this package is still available to be downloaded and manually included in your project via our GitHub page. You can download the package from the following links:

GitHub - STMicroelectronics - Middleware USB Device

GitHub - STMicroelectronics - Middleware USB Host

 

This tutorial was built using STM32CubeIDE 1.13.1, using the STM32CubeH5 HAL driver version 1.1.1 and using the NUCLEO-H503RB, which embeds an STM32H503RBT6 MCU. For further details about this board, refer to the device user manual.

 

BMontanari_49-1697562893677.jpeg

For a detailed explanation regarding the classic USB library, refer to to the USB wiki and the STM32 USB training:

ST Wiki - Introduction to USB with STM32

MOOC - STM32 USB Training

 

1. Development

Start by creating a project for the STM32H503RB in the STM32CubeIDE.

BMontanari_50-1697562893727.png

Once the project creation is done, enable the USB Peripheral in Device only mode and activate its interrupt in the NVIC Settings tab.

BMontanari_51-1697562893735.png

After that, increase the amount of heap and stack size of the project as indicated in the image below, this action can be done in the Project Manager tab: 

BMontanari_52-1697562893741.png

After doing that, generate the code by clicking on the highlighted icon, or just pressing the alt + K shortcut.

BMontanari_53-1697562893742.png

Once the code is generated, create a source folder in your project called USB.

 

BMontanari_54-1697562893746.png

Download the USB Device package from the GitHub (the same link presented in the introduction of this article). Open the software pack folder and import the Core folder into the created ‘USB’ folder.

BMontanari_55-1697562893754.png

Now, create another folder called ‘Class’ and import the desired classes to your project, in this case, the CDC is the only one selected.

BMontanari_56-1697562893764.png

Add the path to the include reference. Right click in the ‘Inc’ folder inside the USB/Class/CDC/.. path, then select `Add/remove include path…` option, and in the pop-up menu, press OK. Perform the same steps for the USB/Core/Inc as well.

BMontanari_57-1697562893767.png

Make sure to rename the USB/Core/Inc/usbd_conf_template.h and USB/Core/Src/usbd_conf_template.c files to usbd_conf.h/.c. After doing so, open the usbd_conf.h. In this file, we need to replace the HAL driver header file name according to the MCU Family we are using. In this case, the STM32H503 is being used, so the include is as follows:

/* Includes ------------------------------------------------------------------*/
#include "stm32h5xx.h" /* replace 'stm32xxx' with your HAL driver header filename, ex: stm32f4xx.h */
#include <stdio.h>
#include <stdlib.h>
#include <string.h>

In the next step, you should change the defines according to your application. In this example, we set the defines as follows (the other defines will not be used and can be deleted):

/** @defgroup USBD_CONF_Exported_Defines
 * @{
 */
#define USBD_MAX_NUM_INTERFACES 1U
#define USBD_MAX_NUM_CONFIGURATION 1U
#define USBD_MAX_STR_DESC_SIZ 0x100U
#define USBD_SELF_POWERED 1U
#define USBD_DEBUG_LEVEL 0U
/* #define USBD_USER_REGISTER_CALLBACK 1U */
/* ECM, RNDIS, DFU Class Config */
#define USBD_SUPPORT_USER_STRING_DESC 0U
/* BillBoard Class Config */
#define USBD_CLASS_USER_STRING_DESC 0U
#define USBD_CLASS_BOS_ENABLED 0U
#define USB_BB_MAX_NUM_ALT_MODE 0x2U
/* CDC Class Config */
#define USBD_CDC_INTERVAL 2000U

After that, the usbd_conf.h file can be saved and closed. Now, open the usbd_conf.c file. In this file, we need to link the HAL PCD drivers with the middleware. First, add the used class include header files:

/* Includes ------------------------------------------------------------------*/
#include "main.h"
#include "usbd_core.h"
#include "usbd_cdc.h" /* Include class header file */

The second step is to import the PCD_HandleTypeDef to this file:

/* Private variables ---------------------------------------------------------*/
extern PCD_HandleTypeDef hpcd_USB_DRD_FS;

The next one is to create a function prototype, which will be implemented later in this file:

/* Private function prototypes -----------------------------------------------*/
static USBD_StatusTypeDef USBD_Get_USB_Status(HAL_StatusTypeDef hal_status);

Then, we need to implement the PCD Callbacks and populate as follows:

/* Private functions ---------------------------------------------------------*/
void HAL_PCD_SetupStageCallback(PCD_HandleTypeDef *hpcd)
{
 USBD_LL_SetupStage((USBD_HandleTypeDef*)hpcd->pData, (uint8_t *)hpcd->Setup);
}

void HAL_PCD_DataOutStageCallback(PCD_HandleTypeDef *hpcd, uint8_t epnum)
{
 USBD_LL_DataOutStage((USBD_HandleTypeDef*)hpcd->pData, epnum, hpcd->OUT_ep[epnum].xfer_buff);
}

void HAL_PCD_DataInStageCallback(PCD_HandleTypeDef *hpcd, uint8_t epnum)
{
 USBD_LL_DataInStage((USBD_HandleTypeDef*)hpcd->pData, epnum, hpcd->IN_ep[epnum].xfer_buff);
}

void HAL_PCD_SOFCallback(PCD_HandleTypeDef *hpcd)
{
 USBD_LL_SOF((USBD_HandleTypeDef*)hpcd->pData);
}

void HAL_PCD_ResetCallback(PCD_HandleTypeDef *hpcd)
{
 USBD_SpeedTypeDef speed = USBD_SPEED_FULL;
 if ( hpcd->Init.speed != PCD_SPEED_FULL)
 {
 Error_Handler();
 }
 /* Set Speed. */
 USBD_LL_SetSpeed((USBD_HandleTypeDef*)hpcd->pData, speed);
 /* Reset Device. */
 USBD_LL_Reset((USBD_HandleTypeDef*)hpcd->pData);
}

void HAL_PCD_ConnectCallback(PCD_HandleTypeDef *hpcd)
{
 USBD_LL_DevConnected((USBD_HandleTypeDef*)hpcd->pData);
}

void HAL_PCD_DisconnectCallback(PCD_HandleTypeDef *hpcd)
{
 USBD_LL_DevDisconnected((USBD_HandleTypeDef*)hpcd->pData);
}

Finally, implement the code to perform the driver link for the STM32H503:

USBD_StatusTypeDef USBD_LL_Init(USBD_HandleTypeDef *pdev)
{
 pdev->pData = &hpcd_USB_DRD_FS;
 HAL_PCDEx_PMAConfig((PCD_HandleTypeDef*)pdev->pData , 0x00 , PCD_SNG_BUF, 0x40);
 HAL_PCDEx_PMAConfig((PCD_HandleTypeDef*)pdev->pData , 0x80 , PCD_SNG_BUF, 0x80);
 HAL_PCDEx_PMAConfig((PCD_HandleTypeDef*)pdev->pData , CDC_IN_EP , PCD_SNG_BUF, 0xC0);
 HAL_PCDEx_PMAConfig((PCD_HandleTypeDef*)pdev->pData , CDC_OUT_EP , PCD_SNG_BUF, 0x100);
 HAL_PCDEx_PMAConfig((PCD_HandleTypeDef*)pdev->pData , CDC_CMD_EP , PCD_SNG_BUF, 0x140);
 return USBD_OK;
}

USBD_StatusTypeDef USBD_LL_DeInit(USBD_HandleTypeDef *pdev)
{
 HAL_StatusTypeDef hal_status;
 hal_status = HAL_PCD_DeInit(pdev->pData);
 return USBD_Get_USB_Status(hal_status);
}

USBD_StatusTypeDef USBD_LL_Start(USBD_HandleTypeDef *pdev)
{
 HAL_StatusTypeDef hal_status;
 hal_status = HAL_PCD_Start(pdev->pData);
 return USBD_Get_USB_Status(hal_status);
}

USBD_StatusTypeDef USBD_LL_Stop(USBD_HandleTypeDef *pdev)
{
 HAL_StatusTypeDef hal_status;
 hal_status = HAL_PCD_Stop(pdev->pData);
 return USBD_Get_USB_Status(hal_status);
}

USBD_StatusTypeDef USBD_LL_OpenEP(USBD_HandleTypeDef *pdev, uint8_t ep_addr,
 uint8_t ep_type, uint16_t ep_mps)
{
 HAL_StatusTypeDef hal_status;
 hal_status = HAL_PCD_EP_Open(pdev->pData, ep_addr, ep_mps, ep_type);
 return USBD_Get_USB_Status(hal_status);
}

USBD_StatusTypeDef USBD_LL_CloseEP(USBD_HandleTypeDef *pdev, uint8_t ep_addr)
{
 HAL_StatusTypeDef hal_status;
 hal_status = HAL_PCD_EP_Close(pdev->pData, ep_addr);
 return USBD_Get_USB_Status(hal_status);
}

USBD_StatusTypeDef USBD_LL_FlushEP(USBD_HandleTypeDef *pdev, uint8_t ep_addr)
{
 HAL_StatusTypeDef hal_status;
 hal_status = HAL_PCD_EP_Flush(pdev->pData, ep_addr);
 return USBD_Get_USB_Status(hal_status);
}

USBD_StatusTypeDef USBD_LL_StallEP(USBD_HandleTypeDef *pdev, uint8_t ep_addr)
{
 HAL_StatusTypeDef hal_status;
 hal_status = HAL_PCD_EP_SetStall(pdev->pData, ep_addr);
 return USBD_Get_USB_Status(hal_status);
}

USBD_StatusTypeDef USBD_LL_ClearStallEP(USBD_HandleTypeDef *pdev,
 uint8_t ep_addr)
{
 HAL_StatusTypeDef hal_status;
 hal_status = HAL_PCD_EP_ClrStall(pdev->pData, ep_addr);
 return USBD_Get_USB_Status(hal_status);
}

uint8_t USBD_LL_IsStallEP(USBD_HandleTypeDef *pdev, uint8_t ep_addr)
{
 PCD_HandleTypeDef *hpcd = (PCD_HandleTypeDef*) pdev->pData;
 if((ep_addr & 0x80) == 0x80)
 {
 return hpcd->IN_ep[ep_addr & 0x7F].is_stall;
 }
 else
 {
 return hpcd->OUT_ep[ep_addr & 0x7F].is_stall;
 }
}

USBD_StatusTypeDef USBD_LL_SetUSBAddress(USBD_HandleTypeDef *pdev,
 uint8_t dev_addr)
{
 HAL_StatusTypeDef hal_status;
 hal_status = HAL_PCD_SetAddress(pdev->pData, dev_addr);
 return USBD_Get_USB_Status(hal_status);
}

USBD_StatusTypeDef USBD_LL_Transmit(USBD_HandleTypeDef *pdev, uint8_t ep_addr,
 uint8_t *pbuf, uint32_t size)
{
 HAL_StatusTypeDef hal_status;
 hal_status = HAL_PCD_EP_Transmit(pdev->pData, ep_addr, pbuf, size);
 return USBD_Get_USB_Status(hal_status);
}

USBD_StatusTypeDef USBD_LL_PrepareReceive(USBD_HandleTypeDef *pdev,
 uint8_t ep_addr, uint8_t *pbuf,
 uint32_t size)
{
 HAL_StatusTypeDef hal_status;
 hal_status = HAL_PCD_EP_Receive(pdev->pData, ep_addr, pbuf, size);
 return USBD_Get_USB_Status(hal_status);
}

uint32_t USBD_LL_GetRxDataSize(USBD_HandleTypeDef *pdev, uint8_t ep_addr)
{
 return HAL_PCD_EP_GetRxCount((PCD_HandleTypeDef*) pdev->pData, ep_addr);
}

void *USBD_static_malloc(uint32_t size)
{
 UNUSED(size);
 static uint32_t mem[(sizeof(USBD_CDC_HandleTypeDef) / 4) + 1]; /* On 32-bit boundary */
 return mem;
}

void USBD_static_free(void *p)
{
 UNUSED(p);
}

void USBD_LL_Delay(uint32_t Delay)
{
 HAL_Delay(Delay);
}

USBD_StatusTypeDef USBD_Get_USB_Status(HAL_StatusTypeDef hal_status)
{
 USBD_StatusTypeDef usb_status = USBD_OK;
 switch (hal_status)
 {
 case HAL_OK :
 usb_status = USBD_OK;
 break;
 case HAL_ERROR :
 usb_status = USBD_FAIL;
 break;
 case HAL_BUSY :
 usb_status = USBD_BUSY;
 break;
 case HAL_TIMEOUT :
 usb_status = USBD_FAIL;
 break;
 default :
 usb_status = USBD_FAIL;
 break;
 }
 return usb_status;
}

Doing that, all the needed changes in the usbd_conf files are done and we can move forward to the usbd_desc files. So, rename the USB/Core/Src/usbd_desc_template.c  and USB/Core/Inc/usbd_desc_template.h  to usbd_desc.h/.c. Then, let us start by opening the usbd_desc.c file. Here, we need to start changing some defines for the descriptor:

/* Private define ------------------------------------------------------------*/
#define USBD_VID 0x0483
#define USBD_PID 22336 /* Replace '0xaaaa' with your device product ID */
#define USBD_LANGID_STRING 1033 /* Replace '0xbbb' with your device language ID */
#define USBD_MANUFACTURER_STRING "STMicroelectronics" /* Add your manufacturer string */
#define USBD_PRODUCT_HS_STRING "STM32 Virtual ComPort" /* Add your product High Speed string */
#define USBD_PRODUCT_FS_STRING "STM32 Virtual ComPort" /* Add your product Full Speed string */
#define USBD_CONFIGURATION_HS_STRING "CDC Config" /* Add your configuration High Speed string */
#define USBD_INTERFACE_HS_STRING "CDC Interface" /* Add your Interface High Speed string */
#define USBD_CONFIGURATION_FS_STRING "CDC Config" /* Add your configuration Full Speed string */
#define USBD_INTERFACE_FS_STRING "CDC Interface" /* Add your Interface Full Speed string */

And change the descriptor settings, so the VCOM class can work properly (the lines 12 and 13 are the only ones that change from default):

__ALIGN_BEGIN uint8_t USBD_DeviceDesc[USB_LEN_DEV_DESC] __ALIGN_END =
{
 0x12, /* bLength */
 USB_DESC_TYPE_DEVICE, /* bDescriptorType */
#if ((USBD_LPM_ENABLED == 1) || (USBD_CLASS_BOS_ENABLED == 1))
 0x01, /*bcdUSB */ /* changed to USB version 2.01
 in order to support BOS Desc */
#else
 0x00, /* bcdUSB */
#endif /* (USBD_LPM_ENABLED == 1) || (USBD_CLASS_BOS_ENABLED == 1) */
 0x02,
 0x02, /* bDeviceClass */
 0x02, /* bDeviceSubClass */
 0x00, /* bDeviceProtocol */
 USB_MAX_EP0_SIZE, /* bMaxPacketSize */
 LOBYTE(USBD_VID), /* idVendor */
 HIBYTE(USBD_VID), /* idVendor */
 LOBYTE(USBD_PID), /* idVendor */
 HIBYTE(USBD_PID), /* idVendor */
 0x00, /* bcdDevice rel. 2.00 */
 0x02,
 USBD_IDX_MFC_STR, /* Index of manufacturer string */
 USBD_IDX_PRODUCT_STR, /* Index of product string */
 USBD_IDX_SERIAL_STR, /* Index of serial number string */
 USBD_MAX_NUM_CONFIGURATION /* bNumConfigurations */
}; /* USB_DeviceDescriptor */

You can change the template resource names to the most convenient name according to your implementation. For example, changing the function:

uint8_t *USBD_Class_DeviceDescriptor(USBD_SpeedTypeDef speed, uint16_t *length);

 to: 

uint8_t *USBD_CDC_DeviceDescriptor(USBD_SpeedTypeDef speed, uint16_t *length);

Make sure to update all the references related to these resources to avoid compiling warnings and errors.

Doing that, the editions in the usbd_desc.c are done, save this file and open the usbd_desc.h. In this file, edit the USBD_DescriptorsTypeDef exporting line to reflect the variable declared in the usbd_desc.c file. Since we did not change the resources name in this file, to make it easier to be followed, the standard name is used:

/* Exported functions ------------------------------------------------------- */
extern USBD_DescriptorsTypeDef Class_Desc; /* Replace 'XXX_Desc' with your active USB device class, ex: HID_Desc */

You can save and close both usbd_desc.h/.c files and move to the next one. In the following step, we need to rename the USB/Class/CDC/Inc/usbd_cdc_if_template.h and USB/Class/CDC/Src/usbd_cdc_if_template.c to usbd_cdc_if.h/.c. In the usbd_cdc_if.h file, add the following defines:

/* Exported constants --------------------------------------------------------*/
#define APP_RX_DATA_SIZE 512
#define APP_TX_DATA_SIZE 512

Add the exported function to transmit data through the VCP:

/* Exported functions ------------------------------------------------------- */
uint8_t TEMPLATE_Transmit(uint8_t* Buf, uint16_t Len);

Now, you can save and close this file to open the usbd_cdc_if.c. In this file, declare the buffer variables:

/* Create buffer for reception and transmission */
/* It's up to user to redefine and/or remove those define */
/** Received data over USB are stored in this buffer */
uint8_t UserRxBufferFS[APP_RX_DATA_SIZE];
/** Data to send over USB CDC are stored in this buffer */
uint8_t UserTxBufferFS[APP_TX_DATA_SIZE];
extern USBD_HandleTypeDef hUsbDeviceFS;

Then populate the following functions as shown below:

static int8_t TEMPLATE_Init(void)
{
 USBD_CDC_SetTxBuffer(&hUsbDeviceFS, UserTxBufferFS, 0);
 USBD_CDC_SetRxBuffer(&hUsbDeviceFS, UserRxBufferFS);
 return (0);
}

static int8_t TEMPLATE_Receive(uint8_t *Buf, uint32_t *Len)
{
 USBD_CDC_ReceivePacket(&hUsbDeviceFS);
 return (USBD_OK);
}

Finally, you can add the transmit function as:

uint8_t TEMPLATE_Transmit(uint8_t* Buf, uint16_t Len)
{
 uint8_t result = USBD_OK;
 USBD_CDC_HandleTypeDef *hcdc = (USBD_CDC_HandleTypeDef*)hUsbDeviceFS.pClassData;
 if (hcdc->TxState != 0){
 return
 USBD_BUSY;
 }
 USBD_CDC_SetTxBuffer(&hUsbDeviceFS, Buf, Len);
 result = USBD_CDC_TransmitPacket(&hUsbDeviceFS);
 return result;
}

There are no restrictions to change the function names and remove the TEMPLATE portion of it, but this action is up to the developer. You can save and close this file, and move to the main.c file. This article uses the comment section’s as guidance for the needed code to be added.

In this file, include the following headers:

/* Private includes ----------------------------------------------------------*/
/* USER CODE BEGIN Includes */
#include "usbd_core.h"
#include "usbd_cdc_if.h"
/* USER CODE END Includes */

Then, add these variables:

/* USER CODE BEGIN PV */
USBD_HandleTypeDef hUsbDeviceFS;
extern USBD_DescriptorsTypeDef Class_Desc;
/* USER CODE END PV */

And finally, add the following code into the MX_USB_PCD_Init function (note that each code has a user code section):

/* USER CODE BEGIN USB_Init 0 */
hpcd_USB_DRD_FS.pData = &hUsbDeviceFS;
/* USER CODE END USB_Init 0 */

/* USER CODE BEGIN USB_Init 2 */
if(USBD_Init(&hUsbDeviceFS, &Class_Desc, 0) != USBD_OK)
 Error_Handler();

if (USBD_RegisterClass(&hUsbDeviceFS, &USBD_CDC) != USBD_OK)
 Error_Handler();

if(USBD_CDC_RegisterInterface(&hUsbDeviceFS, &USBD_CDC_Template_fops) != USBD_OK)
 Error_Handler();

if(USBD_Start(&hUsbDeviceFS) != USBD_OK)
 Error_Handler();
/* USER CODE END USB_Init 2 */

Now, all the needed implementations are done. The next steps are just to create an example to check the middleware functionality.

To check the functionality, add the following code into the main.c file:

/* USER CODE BEGIN 1 */
uint8_t TxMessageBuffer[] = "MY USB IS WORKING! \r\n";
/* USER CODE END 1 */

/* USER CODE BEGIN 2 */
while(hUsbDeviceFS.pClassData == NULL);
/* USER CODE END 2 */

/* Infinite loop */
/* Infinite loop */
/* USER CODE BEGIN WHILE */

while (1)
{
 TEMPLATE_Transmit(TxMessageBuffer, sizeof(TxMessageBuffer));
 HAL_Delay(500);
 /* USER CODE END WHILE */

 /* USER CODE BEGIN 3 */
}
/* USER CODE END 3 */

In the USB/Class/CDC/Src/usbd_cdc_if.c file, add the following code:

static int8_t TEMPLATE_Receive(uint8_t *Buf, uint32_t *Len)
{
 if(Buf[0] == '1')
 HAL_GPIO_WritePin(GPIOA, GPIO_PIN_5, GPIO_PIN_SET);
 else if(Buf[0] == '0')
 HAL_GPIO_WritePin(GPIOA, GPIO_PIN_5, GPIO_PIN_RESET);
 USBD_CDC_ReceivePacket(&hUsbDeviceFS);
 return (USBD_OK);
}

Congratulations on reaching here! Now, you have all the necessary settings and demo code to test the example we have presented here. Now, let us see the results!

2. Results

The implemented code shows a basic transmit and receive data through the USB Virtual COM Port. At the beginning the TxMessageBuffer is created and filled with a message to be transmitted.

/* USER CODE BEGIN 1 */
uint8_t TxMessageBuffer[] = "MY USB IS WORKING! \r\n";
/* USER CODE END 1 */

After that, we wait for the USB to be connected and set, polling the pClassData into the hUsbDeviceFS.

/* USER CODE BEGIN 2 */
while(hUsbDeviceFS.pClassData == NULL);
/* USER CODE END 2 */

Once the USB is connected and set, we start to transmit the message on every 500 ms, as the code below:

/* Infinite loop */
/* USER CODE BEGIN WHILE */
while (1)
{
 TEMPLATE_Transmit(TxMessageBuffer, sizeof(TxMessageBuffer));
 HAL_Delay(500);
/* USER CODE END WHILE */

/* USER CODE BEGIN 3 */
}
/* USER CODE END 3 */

Finally, we use the received data to control the status of the User LED available in the Nucleo board, connected to the PA5, according to its User Manual.

static int8_t TEMPLATE_Receive(uint8_t *Buf, uint32_t *Len)
{
 if(Buf[0] == '1')
 HAL_GPIO_WritePin(GPIOA, GPIO_PIN_5, GPIO_PIN_SET);
 else if(Buf[0] == '0')
 HAL_GPIO_WritePin(GPIOA, GPIO_PIN_5, GPIO_PIN_RESET);

 USBD_CDC_ReceivePacket(&hUsbDeviceFS);
 return (USBD_OK);
}

Now that you know how the demo works, let us try it. So, build (you should get zero errors and zero warnings) then click on the Debug button and wait for the debug session to be opened. Your STLINK might request to be updated. You can do so and then issue to debug again once it is completed.

BMontanari_58-1697562893769.png

Wait until the code reaches the breakpoint in the first line of the main function:

BMontanari_59-1697562893773.png

Then click on Resume, or press F8 to let the application start to run:

BMontanari_60-1697562893774.png

Let us open a terminal in the STM32CubeIDE to see the application running. For that, click o New  Shell console:

BMontanari_61-1697562893775.png

In the opened menu, select Serial Port for the Connection Type, then click on New…

BMontanari_62-1697562893776.png

In the new menu, create a connection for your board. Make sure to select the proper Serial Port, then click Finish and finally OK:

BMontanari_63-1697562893777.png

Doing that, a console with a Virtual COM Port terminal opens and we can see our application running, printing the message on every 500 ms. If you type ‘1’ the User LED should be turned ON and ‘0’ will turn it OFF.

BMontanari_64-1697562893782.png

3. Conclusion

That concludes our article. Now you have the needed information to implement the STMicroelectronics classic USB device middleware. The steps for doing that in another MCU Family or for other classes are very similar. If you face any difficulties while developing, refer to our demonstration projects available in our GitHub or contact us through the Community or by the On-line Support channel.

We hope the this article was helpful!

4. Relevant links:

Here are some relevant links that can help you in your developments using our ST peripheral:

ST Wiki - Introduction to USB with STM32

MOOC - STM32 USB Training

GitHub - STMicroelectronics - Middleware USB Device

GitHub - STMicroelectronics - Middleware USB Host

STMicroelectronics · GitHub

NUCLEO-H503RB User Manual

STM32H503RB - High-performance, Arm Cortex-M33, MCU with 128-Kbyte Flash, 32-Kbyte RAM, 250 MHz CPU - STMicroelectronics

81 replies

gbm
Super User
February 20, 2024

I am not sure which delay you refer to. The one mentioned in errata is needed in low-level routines. Detecting the CDC VCP connection is a different story.

The delay loop fixing the rxcount problem is already present in ST PCD_GET_EP_RX_CNT inline function, defined in stm32h5xx_hal_pcd.h file (same for U5).

In my USB stack I solved the RX count problem in a different way, using the value of 1023 to initialize the rxcount field of buffer descriptor, then waiting for the value to be not equal to 1023. In theory at least, however, 1023 might be a valid data size for isochronous endpoint.

My USB stuff is here:

https://github.com/gbm-ii/gbmUSBdevice

You may also look at my method of detecting the VCP connection. It is still "work in progress" so some things need to be fixed but it works reliably for me.

My STM32 stuff on github - compact USB device stack and more: https://github.com/gbm-ii/gbmUSBdevice
Associate III
April 4, 2024

Hi @B.Montanari , 

 

I've tried exactly same what you explained, but the code gets stuck in below.

while(hUsbDeviceFS.pClassData == NULL);

 This issue is exactly same that @NikhilP, @JerryK mentioned. 

and Ican't try @JerryK 's codes about "enable VDDUS in HAL_PCD_MspInit()"

It is only for H563ZI model when I check the header file. Because my board is H503RB. 

I'd like to know there is solution for this issue. 

 

Thanks,

Luke.

 

 

 

D.Botelho
ST Employee
June 8, 2024

Hello @LukeJang522, @NikhilP, @ACand.3, @JerryK!!!

 

Let me explain the usage of the function below:
while(hUsbDeviceFS.pClassData == NULL);

 

 This is the simplest code that you can implement to wait the CDC Class to be initialized before doing any USB actions. To make the article as easy as possible to be understood and with a simple implementation, I've added a transmit code within the while(1) looping. But if the code reaches to this line before all the setup is done (enumeration phase) we will experience a Hard Fault as mentioned in some comments in this article. Since the CDC Class was not initialized before the pointer to the Class will be null, and access to it will fall into unknown addresses.

 

The implemented while looping will hold the code until the class is initialized. Of course it's not the better way to do that, but to present a simple example I thought it would work well.

 

Now, let me explain when this statement becomes false, allowing the code to continue.

 

When you connect the USB to your computer, it will start communicating to negotiate all the needed information to stablish the communication. During this phase, a Setup Stage will be issued to the Device side. At this time, the code will fall in the following callback:

DBotelho_0-1717886614987.png

 

Going through:

DBotelho_1-1717886720351.png

Again...:

DBotelho_3-1717886869964.png

...

DBotelho_2-1717886823187.png

And finally:

DBotelho_4-1717886970416.png

At this point, the USBD_CDC_Init(..) function will be called, fill the pClassData information and your application will be ready to go!

Given that, you know all the expected flow to get the communication working and pass through the strange while.

 

I.E.: This while should be stepped automatically after you connect your device to a host and the enumeration phase succeeds. If even you are connecting the USB to a host and the enumeration is not happening, there is another problem in your implementation, and probably is not related to this while.

 

Hope the information help guys!

Best Regards,

Dan

Associate II
June 14, 2024

@B.Montanari 

I hope this email finds you well. I am reaching out to discuss a technical challenge we are facing with the STM32L072CZY3TR microcontroller. Our goal is to implement Ethernet over USB functionality.

 

From my research, I understand that the CDC-RNDIS or CDC-ECM protocol can be used to carry Ethernet frames over USB, creating a virtual network connection.

so, for that I used the stack from STM32 GitHub repository. "GitHub - STMicroelectronics/stm32_mw_usb_device at 2022e75b01a499b17acd17d28691b1ed5bbef2dc"

but I landed with an issue where USB port is detecting network adaptor in device manger but disabled in network sharing options.

sai_sankar_rao_R_0-1718354492549.png

 

sai_sankar_rao_R_1-1718354492378.png

 

 

so please suggest some other approach to meet the ethernet over USB functionality or how to clear the issue.

R.sai sankar rao.

J.Christ
Associate II
June 14, 2024

<rant>

First of all, thank you to all the dedicated ST users that helped make this post semi-function, the dedicated ST employees that have contributed the original article and additional explanations and no thank you to ST for making this difficult.  I wish I could say I was disappointed in ST but at this point I would expect nothing less from ST than non-working code that is more difficult to use than an open source projects such as the AdafruitTinyUSB stack.  But since I didn't get to choose the processor on this project I have landed here due to the H503 Nucleo being choosing for me.  I prototyped and had working my portion of the project in about 8 hours on a PicoPi but now I'm porting to ST and have been working on this for over a week. 

</rant>

<issue>

After implementing the MX_ICACHE_Init() move and adding the 8ms delay the code seems to work pretty good.  

I have yet to implement the CRS (clock Recovery system) suggestions from @JerryK as I'm not sure what problem this solves since the MX_ICACHE_Init() move seemed to resolve any early issues I had with getting this code working.

 

However, a remaining issue I have is if I pull the USB cable then plug it back it the program hard faults (on reinsertion.

HardFault_Handler() at stm32h5xx_it.c:85 0x8000de4
<signal handler called>() at 0xffffffb0
Get_SerialNum() at usbd_desc.c:382 0x800b394
USBD_Class_SerialStrDescriptor() at usbd_desc.c:328 0x800b2fe
USBD_GetDescriptor() at usbd_ctlreq.c:526 0x800abec
USBD_StdDevReq() at usbd_ctlreq.c:119 0x800a5ec
USBD_LL_SetupStage() at usbd_core.c:559 0x800a032
HAL_PCD_SetupStageCallback() at usbd_conf.c:39 0x8009a54
PCD_EP_ISR_Handler() at stm32h5xx_hal_pcd.c:1,783 0x80024d4
HAL_PCD_IRQHandler() at stm32h5xx_hal_pcd.c:1,015 0x8001ddc
USB_DRD_FS_IRQHandler() at stm32h5xx_it.c:209 0x8000e46
<signal handler called>() at 0xffffffa8
HAL_Delay() at stm32h5xx_hal.c:424 0x8001280
main() at main.c:195 0x800062a

 

This is the same place the code was hard faulting for me before I moved the ICACHE init code and added the delay:

 

static void Get_SerialNum(void)
{
  uint32_t deviceserial0;
  uint32_t deviceserial1;
  uint32_t deviceserial2;

  deviceserial0 = *(uint32_t *)DEVICE_ID1; /// HARD FAULT IS ON THIS LINE OF CODE
  deviceserial1 = *(uint32_t *)DEVICE_ID2;
  deviceserial2 = *(uint32_t *)DEVICE_ID3;

  deviceserial0 += deviceserial2;

  if (deviceserial0 != 0U)
  {
    IntToUnicode(deviceserial0, &USBD_StringSerial[2], 8U);
    IntToUnicode(deviceserial1, &USBD_StringSerial[18], 4U);
  }
}

</issue>

<note>

A colleague of mine suggested that we just turn off the ICACHE for this project because we don't really need the speed. So I did and if I pulled and plug in the USB back in and no hard fault.  I would like to understand this issue better in the even that we change our minds.  I guess the first course of action to this end would be to read the errata and see what it suggests.

</note>

<retraction>

One test a good test suit it makes not.  I fooled myself, the problem didn't go away.

</retraction>

 

Associate
June 18, 2024

@J.Christ, hope this link can help you understand why:

https://community.st.com/t5/stm32-mcus/how-to-avoid-a-hard-fault-when-icache-is-enabled-on-the-stm32h5/ta-p/630085

 

In short, your reading deviceserial0 from a FLASH address after ICACHE enabled will cause a hardfault.

I met same condition before. My solution is to read it before ICACHE enabled and store it on a RAM variable,

In Get_SerialNum(void) I just get it from the RAM variable.

Best Regards, Andy

J.Christ
Associate II
June 18, 2024

Here is how I modified Get_SerialNum() to prevent hard fault based on additional information from @Andy Tsai 

static void Get_SerialNum(void)
{
  /*
  * Due to an issue with the STM32H503 the device ID cannot be read once the ICACHE is enabled.
  * so to prevent hard faults we read the data once and store it in static variables.
  */
  static uint8_t first_time = 1;
  static uint32_t deviceserial0;
  static uint32_t deviceserial1;
  static uint32_t deviceserial2;

  if( first_time )
  {
    deviceserial0 = *(uint32_t *)DEVICE_ID1;
    deviceserial1 = *(uint32_t *)DEVICE_ID2;
    deviceserial2 = *(uint32_t *)DEVICE_ID3;
    deviceserial0 += deviceserial2;
    first_time = 0;
  }

  if (deviceserial0 != 0U)
  {
    IntToUnicode(deviceserial0, &USBD_StringSerial[2], 8U);
    IntToUnicode(deviceserial1, &USBD_StringSerial[18], 4U);
  }
}

Robmar
Senior II
August 18, 2024

Hi, with a small investment ST could once and for all provide a neat USB solution that would satisfy most developers who don't want or need Microsoft RTOS just for USB!   Lets not forget that many ST customers are changing to other solutions, powerful but economic ESP or Raspberry industrial solutions, so why not support ST MCU product developers?


In our case, your driver didn't work with the ubiquitous Silicon Labs CP210X USB dual bridge, I made these changes so that it could identify the interface, but I still haven't got the getlinecoding working, as the CP2105 replies with a Stall:- (I did try to use code blocks <> but it didn't work!

In usbh_core.c:-  (HOST CDC on STM32)
 
   case HOST_CHECK_CLASS:
 
      if (phost->ClassNumber == 0U)
      {
        USBH_UsrLog("No Class has been registered.");
      }
      else
      {
        phost->pActiveClass = NULL;
 
        // Mod - added
        if (phost->device.DevDesc.idVendor == 0x10c4 && (phost->device.DevDesc.idProduct == 0xea60 || phost->device.DevDesc.idProduct == 0xea70))
        {
        // CP2102 dual-bridge (FT-891)
uint8_t intface = 0; // As some interfaces have dual port CDC bridges this needs to be selectable
        for (idx = 0U; idx < USBH_MAX_NUM_SUPPORTED_CLASS; idx++)
            {
              if (0xff == phost->device.CfgDesc.Itf_Desc[intface].bInterfaceClass) // CP2102 on FT-891 uses 0xff not 2 to specify CDC device!
              {
                phost->pActiveClass = phost->pClass[idx];
                break;
              }
            }
        }
        else
        {
for (idx = 0U; idx < USBH_MAX_NUM_SUPPORTED_CLASS; idx++)
{
  if (phost->pClass[idx]->ClassCode == phost->device.CfgDesc.Itf_Desc[idx].bInterfaceClass)
  {
phost->pActiveClass = phost->pClass[idx];
break;
  }
}
        }
 
        if (phost->pActiveClass != NULL)
        { ...

 

Associate III
October 24, 2024

Never mind, figured it out the USB_DRD_FS_IRQHandler() not called issue.

D.Botelho
ST Employee
October 24, 2024

Hello @Thatseasy !

 

It's good to hear that you found the problem of your application. I'd ask if you could share how you solved the problem. It may be useful to other people who face the same problem.

 

Thank you in advance,

Best Regards,

Dan