Hi,
After some years, now getting back to gem5 for a test!
I followed the instructions on how to run bbench, however got an error that
relates to a missing file

What is 'vmlinux.aarch32.ll_20131205.0-gem5'  and where can I obtain that?
seems that a step is missing in the manual.




mahmood@orca:gem5$ echo $M5_PATH
/home/mahmood/gem5/system/

mahmood@orca:gem5$ ls system/disks/
ARMv7a-ICS-Android.SMP.nolock.img

mahmood@orca:gem5$ ls system/binaries/
android.m5.pbx.smp.mouse.config  vmlinux.smp.mouse.arm

mahmood@orca:gem5$ build/ARM/gem5.fast configs/example/fs.py -b bbench-ics
--kernel=vmlinux.smp.mouse.arm --frame-capture
Couldn't import dot_parser, loading of dot files will not be possible.
gem5 Simulator System.  http://gem5.org
gem5 is copyrighted software; use the --copyright option for details.

gem5 compiled Dec 24 2015 17:10:34
gem5 started Dec 24 2015 18:39:19
gem5 executing on orca, pid 5626
command line: build/ARM/gem5.fast configs/example/fs.py -b bbench-ics
--kernel=vmlinux.smp.mouse.arm --frame-capture

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/mahmood/gem5/src/python/m5/main.py", line 389, in main
    exec filecode in scope
  File "configs/example/fs.py", line 339, in <module>
    test_sys = build_test_system(np)
  File "configs/example/fs.py", line 102, in build_test_system
    external_memory=options.external_memory_system)
  File "/home/mahmood/gem5/configs/common/FSConfig.py", line 294, in
makeArmSystem
    self.kernel = binary(default_kernels[machine_type])
  File "/home/mahmood/gem5/configs/common/SysPaths.py", line 49, in binary
    return searchpath(binary.path, filename)
  File "/home/mahmood/gem5/configs/common/SysPaths.py", line 41, in
searchpath
    raise IOError, "Can't find file '%s' on path." % filename
IOError: Can't find file 'vmlinux.aarch32.ll_20131205.0-gem5' on path.




Regards,
Mahmood
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to