Azure USBX does not work properly on STM32F105

Question

I first refer to the x-cube-azrtos-h7 example on STM32 H7 to migrate ThreadX and USBX. CDC HID, including the combination of the two, have been tested, and they all work normally.
Then I ported ThreadX and USBX on STM32 F105RBT6. Currently, they can enumerate and work normally, but there are still some problems. The specific problems are as follows:

1：On F105RBT6, USBX has problems with the data processing (OUT) sent by the host. The specific manifestation is HAL_PCDEx_SetRxFiFo(&hpcd_USB_OTG_FS, 0x200) when the USB is initialized; the RX FIFO is 512 bytes. When the host sends more than 512 data to the STM32 through VCOM After the byte, VCOM will stop working. The same situation also occurs on HID devices. When the data received by app_usbx_device_thread_hid_callback() exceeds 512 bytes, it will also stop working. The same code will not have problems on H7.
2：My guess is that USBX did not correctly read data from the RX FIFO on the STM32 F105, which caused the RX FIFO to overflow and freeze, but I don’t know how to fix it. Can you provide some information?

Answer 1

Yes, I am the arilink on github

Answer 2

Thank you very much for your help. ThreadX and USBX are really good to use, but the corresponding technical support is relatively small, and problems are difficult to solve.