Yes, this is our fault; there's a patch that's already been posted to
the mailing list. Let me know if you can't find it in the archive.
Steve
Adam Kaplan wrote:
While running an example configuration of full-system M5,
$ build/ALPHA_FS/m5.opt -d /path/to/output configs/example/fs.py
I received the following error:
Error creating object 'system.cpu':
parameter 'mem': not found
Program aborted at cycle 0
In the previous version of M5, I believe mem was assigned to point
to the system's memory controller. No such assignment seems to be taking
place in the currently distributed 2.0 scripts. Should this assignment be
performed in the same manner as version 1.1?
Thanks!
-Adam
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
