From 6360d1c9023f8b6c8fba190325cfc8fa70a8c162 Mon Sep 17 00:00:00 2001 From: bunnie Date: Sun, 31 Oct 2021 02:58:43 +0800 Subject: [PATCH] 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) --- services/trng/src/main.rs | 4 ++-- tools/trng_test.py | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/services/trng/src/main.rs b/services/trng/src/main.rs index 1c960368b..55e7a2bb0 100644 --- a/services/trng/src/main.rs +++ b/services/trng/src/main.rs @@ -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, diff --git a/tools/trng_test.py b/tools/trng_test.py index eec092d3d..dc1770eaa 100755 --- a/tools/trng_test.py +++ b/tools/trng_test.py @@ -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