I took a look at the flags I used when running KitKat. It looks like I omitted the --machine-type flag, had --os-type=android-kitkat and used the vexpress.aarch32 dtb.
Are you seeing the various "warn: unimplemented instructions" scrolling by in your gem5 output during boot? From: gem5-users [mailto:gem5-users-boun...@gem5.org] On Behalf Of Sebastian Cai Sent: Wednesday, July 13, 2016 9:12 PM To: m5-us...@m5sim.org Subject: [gem5-users] Android KitKat stuck and not booting Hello All, I've built an Android KitKat image as per the instructions on http://gem5.org/Android_KitKat and compiled the kernel as well. The command line that I run is: build/ARM/gem5.opt configs/example/fs.py --kernel=/home/scai/full_system_images/binaries/vmlinux-android --frame-capture --machine-type=RealView_PBX --disk-image=/home/scai/full_system_images/disks/android-kitkat.img --os-type=android-kitkat --mem-size=200MB However, when I connect via telnet or m5term, I just get: ==== m5 slave terminal: Terminal 0 ==== with nothing running or booting, and I can't input anything. Does anyone know what could be the issue? Perhaps I didn't use the correct kernel or the image file wasnt created properly? Also there is a "warn: Kernel supports device tree, but no DTB file specified". I tried using all the different dtb files provided such as armv7_gem5_v1_1cpu.dtb and the vexpress ones. Which dtb file does android kitkat use? Thanks, Sebastian
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
