Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cdc_acm_composite sample doesn't catch DTR from second UART #23047

Closed
endian-benjamin opened this issue Feb 24, 2020 · 3 comments
Closed

cdc_acm_composite sample doesn't catch DTR from second UART #23047

endian-benjamin opened this issue Feb 24, 2020 · 3 comments
Assignees
@jfischer-no
Labels
area: USB Universal Serial Bus bug The issue is a bug, or the PR is fixing a bug

Comments

@endian-benjamin
Copy link
Contributor

Built samples/subsys/usb/cdc_acm_composite with -DBOARD=nrf52840_pca10056 and verified that ttyACM0 and ttyACM1 appeared. ttyACM0 contains debug logs. ttyACM1 is silent. Hooked up GDB and found that the main loop is stuck waiting for DTR from CDC_ACM_1, even though minicom is connected and even though it had caught the DTR from CDC_ACM_0.
@endian-benjamin endian-benjamin added the bug The issue is a bug, or the PR is fixing a bug label Feb 24, 2020
@endian-benjamin
Copy link
Contributor Author

(tried with both v2.0.0 and v2.1.0)

@endian-benjamin
Copy link
Contributor Author

@jfischer-phytec-iot @finikorg

@carlescufi carlescufi added the area: USB Universal Serial Bus label Feb 24, 2020
@endian-benjamin
Copy link
Contributor Author

It was just me misunderstanding the sample - I thought ttyACM0 and ttyACM1 were supposed to communicate, but since I had the console on a USB UART as well, it actually created three ttyACMs. Communication worked fine between ttyACM1 and ttyACM2...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jfischer-no jfischer-no

Labels
area: USB Universal Serial Bus bug The issue is a bug, or the PR is fixing a bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jfischer-no @carlescufi @endian-benjamin