Getting using while using two CDC com ports #3362
siddhartha993549
started this conversation in
General
Replies: 2 comments 2 replies
-
|
Which MCU you are using ? On version 0.20 some code refactor was done for the CDC driver, please try if 0.19 works. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
After some iterations, one CDC port always shows fifo_space = 0, so even when the host sends IN tokens, the device keeps NAKing and cannot transmit. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I am trying to implement two CDC COM ports using TinyUSB. Receiving data from the host to the device works fine, and I can see the data in the buffer. However, when I loop the same data back to the same COM port, after a few iterations one of the COM ports stops working (it can be either one, randomly).
For that port, the API tud_cdc_n_write_available(itf) keeps returning 0. I checked the USB log as well: the host is sending IN tokens, but the device is responding with NAKs only. I am using tud_cdc_n_write() and tud_cdc_n_write_flush() for transmitting data.
Could anyone explain why tud_cdc_n_write_available() keeps returning 0 for one of the ports, and what might cause this behavior?
Beta Was this translation helpful? Give feedback.
All reactions