Andreas Konopik
2018-07-27 11:57:39 UTC
Hello,
i am running the latest gem5 and want to simulate an AArch32 Full system.
The standard gem5/configs/example/arm/starter_fs.py config file works
perfectly with AArch64, but as soon as i change the kernel from
vmlinux.vexpress_gem5_v1_64 to vmlinux.vexpress_gem5_v1 and the image
from linaro-minimal-aarch64.img to linux-aarch32-ael.img it aborts with
this kernel panic:
VFS: Cannot open root device "vda1" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available
partitions:
I tried fixing this error by renaming the root partition in the Linux
boot command flags: root=/dev/hda1 and root=/dev/sda1.
For both partition names it still gives the same error.
How can i start a functioning aarch32 in Full System mode?
regards,
Andreas
i am running the latest gem5 and want to simulate an AArch32 Full system.
The standard gem5/configs/example/arm/starter_fs.py config file works
perfectly with AArch64, but as soon as i change the kernel from
vmlinux.vexpress_gem5_v1_64 to vmlinux.vexpress_gem5_v1 and the image
from linaro-minimal-aarch64.img to linux-aarch32-ael.img it aborts with
this kernel panic:
VFS: Cannot open root device "vda1" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available
partitions:
I tried fixing this error by renaming the root partition in the Linux
boot command flags: root=/dev/hda1 and root=/dev/sda1.
For both partition names it still gives the same error.
How can i start a functioning aarch32 in Full System mode?
regards,
Andreas