-
Notifications
You must be signed in to change notification settings - Fork 1k
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.
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
Enable UART on QSPI pins #2280
Comments
I think the example in raspberrypi/pico-examples#571 does what you need? It uses qspi_gpio_set_function() to switch the pins to UART and then uses them to communicate with the RP2350 that booted it. |
Wow, @burtyb thanks! :-) By the way, my code is here: https://codeberg.org/retsifp/rp2350_uart |
So can this issue be closed @retsifp , or is there still missing SDK functionality that you'd like to see added? |
For me it's fine, can be closed if you want. |
I'll close this as a duplicate of #1799 then 🙂 |
I'll leave this around, just because i thought (and maybe this isn't the case) that it might require changes to our UART code to make this friendly - if this is just a IO and FUNCSEL setup issue, then I guess we can indeed close - i just haven't looked at it in detail |
Me neither 😂 Pinging @will-v-pi as he wrote the previously-mentioned raspberrypi/pico-examples#571 |
Yeah, it was just an io/pads issue - although stdio_uart_init might need modifications too if we wanted to support that |
Hi,
I'm doing tests with the UART bootloader, which is described in the datasheet of RP2350 (Chapter 5.8).
The pins SD2 and SD3 of QSPI are used as TX and RX by the bootloader. It works very good, but it would make sense to use the same pins in 'user mode' for communication with another controller. However it looks like the SDK lacks any functions to switch UART to bank1 pins?
So at the moment it's not possible to use the same pins as the bootloader uses in 'user mode', disregarding the possibility to manually set the registers to do so (but for that I'm too far away ...).
Would be great if there could be a solution in the long term :)
BR Thomas.
The text was updated successfully, but these errors were encountered: