fix "mysterious" BIO errors

turns out...the memory test was subtly smashing stack. It made
sense during early bring up to do this quick test but I should
have retired it sooner.

Keeping it around for a little bit longer because chips aren't
fully brought-up and I could see this being a useful stub in
case we find an outlier that actually has memory access problems.
This commit is contained in:
bunnie 2025-08-14 02:04:39 +08:00
parent 6cd5a23893
commit 0cbdf1e9f1

View file

@ -159,6 +159,8 @@ pub fn early_init() {
let perclk = unsafe { init_clock_asic(SYSTEM_CLOCK_FREQUENCY) }; let perclk = unsafe { init_clock_asic(SYSTEM_CLOCK_FREQUENCY) };
// test memory // test memory
// NOTE: this smashes stack - need adjustment if this is going to be a "fixture"
/*
crate::println!("\ntest memory..."); crate::println!("\ntest memory...");
let base = 0x6108_5000; let base = 0x6108_5000;
let mem_range = unsafe { let mem_range = unsafe {
@ -182,6 +184,7 @@ pub fn early_init() {
} else { } else {
crate::println!("fast mem test passed"); crate::println!("fast mem test passed");
} }
*/
crate::println!("scratch page: {:x}, heap start: {:x}", SCRATCH_PAGE, HEAP_START); crate::println!("scratch page: {:x}, heap start: {:x}", SCRATCH_PAGE, HEAP_START);
// Define the .data region - bootstrap baremetal using these hard-coded parameters. // Define the .data region - bootstrap baremetal using these hard-coded parameters.