Skip to content

Add simple UART bootloader example #571

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

Open
wants to merge 8 commits into
base: develop
Choose a base branch
from

Conversation

will-v-pi
Copy link
Contributor

Add a UART bootloader example, which reads a binary from the partition table on the main device, and uses the UART bootloader to boot that binary on a separate device. Requires a modified separate board to run, as you need access to the QSPI pins to use them as UARTs for the bootloader (see 5.8 in the datasheet) - the main board can be a normal RP2350 board.

This sample binary flashes the LED and prints "Hello, world" back over the UART interface, which demonstrates setting up QSPI GPIOs as UARTs.

@will-v-pi will-v-pi added this to the 2.0.1 milestone Nov 12, 2024
@lurch
Copy link
Contributor

lurch commented Nov 14, 2024

I wonder if things like the "splash string", the "knock sequence", the "uart-bootloader baudrate", etc. ought to be defined in a header-file somewhere in pico-sdk? (As I assume they'll always be the same for every RP2350 chip?)

EDIT: Ah, perhaps https://github.com/raspberrypi/pico-sdk/blob/develop/src/rp2_common/boot_bootrom_headers/include/boot/bootrom_constants.h would be a good place for those 🙂

@peterharperuk
Copy link
Contributor

This worked well for me once I'd figured out that the uart binary had to be loaded into the "master" device first. It would be more fun if the binary could be built into a header file to avoid that step

kilograham
kilograham previously approved these changes Mar 24, 2025
@kilograham kilograham self-requested a review March 24, 2025 23:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants