USB stdio issue at lower sys clock #1697
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#1697
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?
USB stdio fails if SYS_CLK_KHZ overridden to 32MHz (PLL_SYS_VCO_FREQ_KHZ and PLL_SYS_POSTDIV1, 2 are also set to valid values).
/dev/ttyACM0 does not even appear
dmesg shows errors:
usb 1-7.2: new full-speed USB device number 71 using xhci_hcd
usb 1-7.2: Device not responding to setup address.
usb 1-7.2: device descriptor read/all, error -110
Meanwhile user code on the Pico runs ok.
At 64MHz everything seems fine (only SYS_CLK_KHZ and PLL_SYS_POSTDIV2 changed).
Is this expected, or is anything i can do to make it work?
Thx
They say in the datasheet, it NOPs when running higher clock than USB 48 MHz to wait for it, so maybe at lower clock it can not keep up. Maybe right, maybe wrong.
The hardware has been designed to work at a clk_sys of >= clk_usb. Perhaps we could assert about this when initializing USB? Would need to think about where to put it as you can have clk_sys as slow as you like if you are not using USB. Any thoughts @kilograham. Also worth noting this in the datasheet
I have added a note about this to the datasheet which will come out in the next release
We will add an assertion to check the clk_sys frequency is at least 48MHz when using USB. However, it's quite hard to defend against this post clocks initialization as we'd have to put an assert in every clock_configure function to check it thoroughly.