I see. Yes, I tried the UniFlex-x86 and it works:). I ran a small program and I get some statistics. I will go on try the CMPFlex :)
As for my account, emm, I think it should be the correct mail account. I will double check it. Anyway, Thanks very much~~~ -----Original Message----- From: Thomas Wenisch [mailto:[email protected]] Sent: Monday, October 17, 2005 1:54 PM To: shan Cc: [email protected] Subject: Re: [simflex]run simics fail after make SimFlex Hi Shan, Sorry for the delay. For some reason, the message you attached below has not appeared on the mailing list yet, although it was sent yesterday at 10. I don't see any problem in the list setup on our end, but, to be safe, why don't you cc me directly on your messages to the list, in case something is screwed up with your list registration. It is possible the list software did not like the form of the From: header in your message. Did you send your message from a different computer/account? Anyway, -- On Mon, 17 Oct 2005, shan wrote: <snip> > > From: shan [mailto:[email protected]] > Sent: Sunday, October 16, 2005 10:36 PM > To: '[email protected]' > Subject: [Simflex] load-module warning & Problem running Simics after 'make > install' > > <snip> > > I have made try on another machine. > <snip> > > Initializing Flexus::Debugger...DEBUG WARNING: Debug configuration file > debug.cfg was not found. > > done > > Initializing Flexus::ConfigurationManager...done > > Initializing Flexus::ComponentManager...done > > Entered init_local > <snip> > > Hi Shan, The output above is correct. The DEBUG WARNING can be fixed by ensuring that the file debug.cfg (located in flexus_test_app/config) is in the current working directory when you load the flexus module. This file is used to indicate where Flexus should write debugging output. You will then see a whole lot more output when you load flexus and run the simulation. The other warning messages you see about "unexpectedly defined class" are expected behavior. Simics expects plug-in modules to have tags on them that indicate what extension classes they define - we don't bother doing this because it is a hassle, and doesn't affect anything. You should be able to start a simulation with "run", and get Flexus to do things, like print statistics (play with the commands that the flexus object provides in simics, e.g. hit flexus.[TAB] to see what choices you have). At the end of simulation that is terminated with Flexus magic breakpoints, you may see a "Simics getting shaky" message. This is also expected behavior, and will not affect your simulation outputs. The error that causes this message will be fixed in the next Flexus release. I suspect the problems on your first machine are caused by GLIBC compatability issues. We haven't figured out what to do about these - the root cause of the problem is that Virtutech builds Simics with an old version of gcc. Regards, -Tom Wenisch
