You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a H7B3 on a custom board. On this board I want to use USB with Azure USBx.
The USB configuration in CubeMX is:
USB host only
DMA enabled
internal PHY
Speed: FullSpeed
The USB devices I want to connect to my board are:
Prolific-Device
MassStorage-Device
I'm using CubeIDE 1.10.1 and X-CUBE-AZRTOS-H7 v2.1.0
Describe the bug (skip if none)
If I connect a prolific device for the first time, it gets detected correctly.
When I disconnect it and reconnect it after a few seconds, sometimes a communication is not possible any more, even it seems that it was detected.
How to reproduce the bug (skip if none)
Connect a prolific device to USB interface
Communicate -> working
Disconnect the prolific device
Wait some seconds
Connect the prolific device again
Communicate -> sometime not working
Additional context
I currently fixed it by reinitialize the HCD after a disconnection was detected. I placed the reinit into the USBx-EventCallback in the event UX_DEVICE_DISCONNECTION.
Describe the set-up
I'm using a H7B3 on a custom board. On this board I want to use USB with Azure USBx.
The USB configuration in CubeMX is:
The USB devices I want to connect to my board are:
I'm using CubeIDE 1.10.1 and X-CUBE-AZRTOS-H7 v2.1.0
Describe the bug (skip if none)
If I connect a prolific device for the first time, it gets detected correctly.
When I disconnect it and reconnect it after a few seconds, sometimes a communication is not possible any more, even it seems that it was detected.
How to reproduce the bug (skip if none)
Additional context
I currently fixed it by reinitialize the HCD after a disconnection was detected. I placed the reinit into the USBx-EventCallback in the event UX_DEVICE_DISCONNECTION.
Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: