tighten up the hard-coded locations for the trng test

these locations look good for a while, now that i see the
structure of data allocation (it's split between top and bottom)
This commit is contained in:
bunnie 2021-10-31 02:58:43 +08:00
parent 5f327126ab
commit 6360d1c902
2 changed files with 4 additions and 4 deletions

View file

@ -582,7 +582,7 @@ impl Tester {
pub fn new(server_csr: *mut u32) -> Tester {
use utralib::generated::*;
let buff_a = xous::syscall::map_memory(
xous::MemoryAddress::new(0x40B0_0000), // fix this at a known physical address
xous::MemoryAddress::new(0x4080_0000), // fix this at a known physical address
None,
crate::TRNG_BUFF_LEN,
xous::MemoryFlags::R | xous::MemoryFlags::W,
@ -590,7 +590,7 @@ impl Tester {
.expect("couldn't map TRNG comms buffer A");
let buff_b = xous::syscall::map_memory(
xous::MemoryAddress::new(0x40C0_0000), // fix this at a known physical address
xous::MemoryAddress::new(0x4088_0000), // fix this at a known physical address
None,
crate::TRNG_BUFF_LEN,
xous::MemoryFlags::R | xous::MemoryFlags::W,

View file

@ -303,8 +303,8 @@ def main():
messible2_in = pc_usb.register('messible2_in')
messible_out = pc_usb.register('messible_out')
RAM_A = 0x40B0_0000
RAM_B = 0x40C0_0000
RAM_A = 0x4080_0000
RAM_B = 0x4088_0000
BURST_LEN = 512 * 1024
TIMEOUT = 30.0