> > > Hi > > Sorry for the delay in responding. I switched to gem5 development > instead of gem5 stable and this BUS problem went away. However, I have > new issues. I list them here : > > 1. When I boot ARM FS with the kernel,bootloader and file images > available here : http://www.m5sim.org/Download, it does boot ( I used > the smaller 512 MB disk image). > However m5term asks me for a login ( saying AEL login) and a password > after booting into the system. > root
> 2. When I boot ARM_FS with the kernel image and file system I created > from the instructions here : > http://www.linux-arm.org/LinuxKernel/LinuxAndroidPlatform I get the > error : unrecognized/unsupported machine ID (r1 = 0x0000065a) and it > does not boot at all. used the bootloader from the gem5 site. > Maybe I am not using the correct format of the kernel file. You > mention that I need a vmlinux image and not a bootable image. How does > one create that; the instructions on the ARM Android page create a > uBoot target ? Also, how do I create a specific Android bootloader or > will the same boot.arm that is available on the m5 downloads page for > ARM work for this as well ? > You need to make sure the board time is a realview PBX. > 3. When I boot ARM_FS with the kernel provided in the GEM5 download > page but my own custom Android file system it fails with the following > error message: > 2244951734500: system.cpu.break_event: break event panic triggered > Probably the kernel needs to be compiled to support Android ? This > maybe out of the scope of GEM5. The in the gem5 download only supports linux not android. > 4. I get the following warnings upon boot : > > warn: The clidr register always reports 0 caches. > warn: clidr LoUIS field of 0b001 to match current ARM implementations. > warn: The csselr register isn't implemented. > warn: The ccsidr register isn't implemented and always reads as 0. > warn: instruction 'mcr bpiallis' unimplemented > warn: instruction 'mcr icialluis' unimplemented > 227304500: system.terminal: attach terminal 0 > warn: instruction 'mcr dccimvac' unimplemented > warn: instruction 'mcr dccmvau' unimplemented > warn: instruction 'mcr icimvau' unimplemented > warn: LCD dual screen mode not supported > > Are they harmless ? These are all expected. > > 5. How do I configure ARM_FS to accept different names for my kernel, > boot and file system images ? It looks like these are hardcoded at > places. > --kernel= on the command line and export LINUX_IMAGE <path to image> Ali _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
