shuffle around package order

There's a hardware bug that makes concurrent camera and SPIM
traffic unreliable. The work-around is to place the camera
code inside the XIP area so we don't have to hit SPIM to swap
in code while the camera is running.

However, we do need to figure out a more reliable fix for this.
This commit is contained in:
bunnie 2024-11-07 16:13:08 +08:00
parent 12f0159fc0
commit fd6c2ad4ff

View file

@ -566,8 +566,9 @@ fn main() -> Result<(), Box<dyn std::error::Error>> {
// - bao-console is the serial debug console handler
// - [planned] pddb server
// - [planned] vault application
let bao_rram_pkgs = ["xous-ticktimer", "xous-log", "xous-names", "usb-cramium"].to_vec();
let bao_swap_pkgs = ["bao-video", "cram-hal-service", "bao-console"].to_vec();
let bao_rram_pkgs =
["xous-ticktimer", "xous-log", "xous-names", "usb-cramium", "bao-video"].to_vec();
let bao_swap_pkgs = ["cram-hal-service", "bao-console"].to_vec();
if !builder.is_swap_set() {
builder.set_swap(0, 8 * 1024 * 1024);
}
@ -577,6 +578,8 @@ fn main() -> Result<(), Box<dyn std::error::Error>> {
builder.add_loader_feature("debug-print");
builder.add_kernel_feature("debug-swap");
// builder.add_kernel_feature("debug-print");
// builder.add_kernel_feature("debug-swap-verbose");
builder.add_feature("quantum-timer");
builder.add_kernel_feature("v2p");
builder.add_loader_feature("sram-margin");