From bf5d755fd7947099375523c8cdf8a621931bdaa0 Mon Sep 17 00:00:00 2001 From: bunnie Date: Fri, 2 Jan 2026 04:18:20 +0800 Subject: [PATCH] Update README-baochip.md --- README-baochip.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README-baochip.md b/README-baochip.md index 61fb9d427..87ff35d63 100644 --- a/README-baochip.md +++ b/README-baochip.md @@ -5,7 +5,7 @@ Baochip-based boards use the `bao1x` SoC. There are two boards supported out-of- - `dabao` is a minimal SoM-style breakout board. Basically just the chip on a board. - `baosec` is a hardware security token. It features a camera, display, external memory, buttons, and a supplemental hardware TRNG. -The build idiom is `cargo xtask `, i.e. `cargo xtask dabao`. The build will generate a [`UF2`](https://makecode.com/blog/one-chip-to-flash-them-all) artifact, which can be found in `target/riscv32imac-unknown-[xous|none]-elf/release/`. +The build idiom is `cargo xtask `, i.e. `cargo xtask dabao`. The build will generate a [`UF2`](https://makecode.com/blog/one-chip-to-flash-them-all) artifact, which can be found in `target/riscv32imac-unknown-[xous|none]-elf/release/`. You will need to copy all three artifacts generated (loader.uf2, xous.uf2, and apps.uf2) initially to ensure that the loader, kernel, and applications are at the same revision. After that point if the loader and kernel are not updated, one can just update apps.uf2. Holding down the `PROG` button while plugging the device into USB will cause it to enter a bootloader that enumerates a mass storage device. The build artifacts can then be copied onto the device. Pressing `PROG` again will cause the device to run the program. Targets also enumerate a serial port over USB, which will activate a debug console.