gh-raspberrypi/pico-sdk

Watch

issues related to which uart pico_stdio_uart is using. #3172

New issue

Open

opened 2026-09-03 16:50:08 -05:00 by kilograham · 0 comments

kilograham commented

2026-09-03 16:50:08 -05:00

(Migrated from github.com)

Related to #3171

One solution for that, is to add an accessor to pico_stdio_uart to get the uart_instance... beyond that we should have "glue" macro to convert a uart instance/number a la UART_DREQ_NUM() to find the correct CLK_DEST for the given UART.

Alternatively, maybe we should just enumerate the GPIOs and their funcsels?

note also, that in passing, i notice that pico_stdio_uart_deinit_ functions are a bit free and loose with what uart instance and pins they deinit, so will open another issue for that.

Related to #3171 One solution for that, is to add an accessor to pico_stdio_uart to get the uart_instance... beyond that we should have "glue" macro to convert a uart instance/number a la `UART_DREQ_NUM()` to find the correct CLK_DEST for the given UART. Alternatively, maybe we should just enumerate the GPIOs and their funcsels? note also, that in passing, i notice that `pico_stdio_uart_deinit_` functions are a bit free and loose with what uart instance and pins they deinit, so will open another issue for that.

Sign in to join this conversation.

No labels

can't reproduce

code cleanliness

compiler version issues

hardware_clocks

hardware_exception

hardware_watchdog

needs reporter detail

newlib-multicore

pico_async_context

pico_binary_info

wifi integration

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gh-raspberrypi/pico-sdk#3172

No description provided.