AnsweredAssumed Answered

Reinit of CDC Class driver in usb_v2 on TWRVF65GS10_A5

Question asked by Stefan Haase on Aug 24, 2015



Since MQX4.2 uses the usb_v2 for Vybrid we experience a problem in reactivating the USB CDC Class device driver on runtime.


The basic idea is to  activate CDC only when it is needed.

Therefore the app uses USB_Class_CDC_Init in the beginning of the connection session

and at the end USB_Class_CDC_Deinit to free and shutdown the USB device driver.


The problem is that this cycle only works at the first run. Any call of USB_Class_CDC_Init after USB_Class_CDC_Deinit

is activating the USB stack fine and the device is detected by the USB Host, but no data transfer is possible between

client and host. Even worse, the Vybrid gets unresponsive at all.


This situation can be reproduced using the example provided in the usb_v2 directory of MQX4.2.

I modified the example to call USB_Class_CDC_Deinit if a X is received from the host and rerun APP_init and APP_task.

It was build with DS5 and USB is established between the TWR and a Xubuntu PC

Here the output of the modified example can be found in the attachment.


Is USB_Class_CDC_Deinit used wrong?

Is there a bug in the stack?


I'm thankful for any advice to do to narrow the issue down.


Best Regards,


Original Attachment has been moved to:

Original Attachment has been moved to:

Original Attachment has been moved to: