Skip to main content
taraben
taraben
Associate III
March 5, 2019
Question

CubeMX 5 ErrorHandler in USB CDC is called too often

  • March 5, 2019
  • 2 replies
  • 876 views

Hello All,

I updated to CubeMX 5 and use STM32F4 USB CDC.

After update my programm crashes directly after init.

This is because the USB driver calles directly into ErrorHandler when USB is not connected.

The ErrorHandler does a while(1) forever loop.

Why did STM changed that behaviour?

As in the ErrorHandler itself I have no possibility to test where it comes from and react according to the problem. The ErrorHandler is generic and global and should only be called on severe problems.

But a not connected USB interface is not "severe" but is a generic use-case.

What I currently do is to modify the ErrorHandler to return immediately.

I think this behaviour now is not good solution.

There should be a parameter in the call to ErrorHandler, so that ErrorHandler can react properly to the problem.

My 2ct.

Adib.

This topic has been closed for replies.

2 replies

Vangelis Fortounas
Vangelis Fortounas
Associate II
March 5, 2019

I observe the same problem too.

After some investigation , i found that in stm32f4xx_hal_pcd.c module line 1294 and 1298 , the used enumerations for hpcd->Init.speed are wrong. (at least).

Theese enumerations cause the problem in a next piece of code that checks the speed.

A temporary workaround is to replace the USB_OTG_SPEED_HIGH with PCD_SPEED_HIGH and to replace USB_OTG_SPEED_FULL with PCD_SPEED_FULL

manat.r
manat.r
Visitor II
April 10, 2019

​I have faced the same problem with CubeMX 5 too.

The workaround is to change USB Core Speed define for USB_OTG_SPEED_FULL from 3U to 2U.

and USB_OTG_SPEED_LOW from 2U to 3U.

File: stm32f2xx_ll_usb.h

. . .

/** @defgroup USB_Core_Speed_  USB Core Speed

 * @{

 */ 

#define USB_OTG_SPEED_HIGH                    0U

#define USB_OTG_SPEED_HIGH_IN_FULL            1U

#define USB_OTG_SPEED_LOW                     3U 

#define USB_OTG_SPEED_FULL                    2U

/**

 * @}

Terms & ConditionsAccessibility statement