Hey Ashkan, I looked over your config file briefly, and didn't find anything obviously wrong with it. I would also add this just before you switch -
print '\n\n Switching because %s' %(exit_event.getCause()) This would ensure that the exit cause is printed, and once you know the right exit cause, you can add a condition to ensure you are only switching for that cause. For instance, it can be something like= if exit_event.getCause() == "a thread reached the max instruction count": Try passing small instruction counts to both -F and -I (making sure fast_forward insts < max insts) to see if you are switching and stopping correctly. You are correct, after the switch, timing mode is enabled. Cheers, Swapnil Haria, Graduate Student, Dept of Computer Sciences, University of Wisconsin-Madison On Fri, Oct 28, 2016 at 9:15 AM, Swapnil Haria <[email protected]> wrote: > Hey Ashkan, > > 1) The gem5-stable repo will be decommissioned soon and you definitely > shouldn't be using that. You should definitely move to the latest release. > > 3) I don't think your dram changes are related to the error you are > seeing. Also, I don't see any code for fast forwarding in your config file. > Regarding the itb and the dtb connections, try comparing your script to the > learning_gem5 one - https://github.com/powerjg/learning_gem5/blob/master/_ > static/scripts/part3/system.py > Finally, for -F and -I, check how they are implemented in the example gem5 > scripts (mostly in configs/common/Simulation.py). You will need to do > something similar in your own config file. > > > Cheers, > Swapnil Haria, > Graduate Student, > Dept of Computer Sciences, > University of Wisconsin-Madison >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
