stdio over USB needs DTR signal to be activated from terminal program #921
Labels
No labels
bazel
bluetooth
board settings
boot_stage2
bug
build
c++
can't reproduce
clang
clib-interface
cmsis
code cleanliness
code size
compiler version issues
cyw43_driver
debug
discussion
documentation
duplicate
dynamic_clock
elf2uf2
enhancement
errata
filesystem
flash layout
floating point
FreeRTOS
hardware_adc
hardware_claim
hardware_clocks
hardware_dma
hardware_exception
hardware_flash
hardware_gpio
hardware_i2c
hardware_irq
hardware_pio
hardware_pwm
hardware_rcp
hardware_rtc
hardware_spi
hardware_sync
hardware_uart
hardware_vreg
hardware_watchdog
hardware_xosc
help wanted
host
IAR
installation
invalid
linker scripts
lto
lwip
mbedtls
missing API
needs reporter detail
networking
newlib
newlib-multicore
non-c
non-cmake
non-gcc
openocd
orphan PR
OS integration
pico_async_context
pico_base
pico_binary_info
pico_flash
picolibc
pico_lwip
pico_malloc
pico_multicore
pico_printf
pico_runtime
pico_stdio
pico_stdio_usb
pico_sync
pico_time
pico_util
pioasm
port
question
review
review2
rtos interop
runtime init
static library
svd
test
tinyusb
vscode
wifi integration
wontfix
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-raspberrypi/pico-sdk#921
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I think, this is no bug but a feature ;-).
But at least, IMHO it would be worth a note in the documentation. (Chapter 4.4 in 'Getting started ...')
I wasted some time in debugging my Windows 11 - USB driver Stack and tried to understand your documented issues with the 'USB Enumeration workaround' .....
In the end, I found that using the HTerm terminal program is my issue! This terminal software does not set DTR signal on connect per default! Also my own code using NET Serial Port needed the line:
Port.DtrEnable = true;to be added in order to work. Using putty iso HTerm worked out of the box.
( But once you know the problem, there is a button fot DTR in HTerm 😄 ... )
This was also discussed recently in #906 - I've not been following it very closely, but it seems to be more of a tinyusb thing than a pico-sdk thing? https://github.com/hathach/tinyusb/issues/1548 🤷
Ok, Thx for pointing me there.
I am not sure, if "DTR" is considered part of 'Flow Control' but I also didn't expect the behaviour it currently shows....
Note (to others having problems to get this up and running):
I still need the
TUD_OPT_RP2040_USB_DEVICE_ENUMERATION_FIX=1to make the com port working on my Windows 11 Notebook. If I leave this to default or 0, then the COM port shows up in device manager but is 'not connectable' (Hterm hangs on connect).
Whether you need the USB_DEVICE_ENUMERATION_FIX or not depends which other USB devices you have connected at the same time. And it's also not needed if you're using a board using RP2040 B2, e.g. Raspberry Pi Pico W.
merged into develop