Hi Mike,
I tried the insecure setting and saw the exact same issue as you. The issue is
that the insecure setting would disable access to a region of RAM at 0x40000000
that should still be accessible. Re-enabling this device is a 1 line change
which I'll put up a PR for soon (see the patch below). Once I've made this
change the insecure version boots to login.
project projects/vm/
diff --git a/components/VM/src/modules/plat/tk1/init.c
b/components/VM/src/modules/plat/tk1/init.c
index dce7809..4bae973 100644
--- a/components/VM/src/modules/plat/tk1/init.c
+++ b/components/VM/src/modules/plat/tk1/init.c
@@ -38,7 +38,6 @@ static const struct device *linux_pt_devices[] = {
static const struct device *linux_ram_devices[] = {
#ifndef CONFIG_TK1_INSECURE
&dev_rtc_kbc_pmc,
- &dev_data_memory,
&dev_exception_vectors,
&dev_system_registers,
&dev_ictlr,
@@ -46,6 +45,7 @@ static const struct device *linux_ram_devices[] = {
&dev_fuse,
&dev_gpios,
#endif /* CONFIG_TK1_INSECURE */
+ &dev_data_memory,
};
extern reboot_hooks_list_t reboot_hooks_list;
_______________________________________________
Devel mailing list
Devel@sel4.systems
https://sel4.systems/lists/listinfo/devel
