Hi Eliot, MemCtrl() memory controller in gem5 can control a single DRAM interface or a single NVM interface at a time. I think one way to verify that things are set-up correctly is to confirm this from the "m5out/config.ini". If config.ini seems to be using 'MemCtrl' type for the memory controller and the memory interface connected to the controller is of the type 'NVMInterface', I think that should confirm that you are simulating an NVM device.
-Ayaz On Sat, Mar 18, 2023 at 2:52 PM Eliot Moss via gem5-users < gem5-users@gem5.org> wrote: > Dear gem5-ers - > > I wanted to set up to use NVM only, so I tried this on the command line: > > --nvm-type=NVM_2400_1x64 > > This had no effect. Digging into configs/common/MemConfig.py was not > directly > enlightening. However, it seems that Options.py sets mem-type to a > particular > DRAM by default. Doing --mem-type=None does not work, giving an error > message > that None is not a valid memory type. > > What *seems* to work is saying this: > > --mem-type=NVM_2400_1x64 > > If that is the "approved" way, then fine, but I wanted to make sure that I > am > not ending up with some strange mix of controller and device, part intended > for DRAM and part for NVM ... > > (Maybe mem-type should be set to that default only if neither mem-type nor > nvm-type are given? I also noticed that the default and flags for "colors" > are such that one cannot get colors printed any more. I did a local fix, > but maybe that was not intended?) > > Regards - Eliot Moss > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org >
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
