Hi It seems like the VExpress_GEM5_Base.bootmem (first 64MB of memory) is overlapping with some other memory.
Have you made any modifications to starter_fs.py or to other configuration scripts? By default starter_fs.py should start allocating memory at 2GB, so my guess is that you are adding an overlapping memory somewhere. Quick and dirty solution is to remove bootmem from your memory map (from RealView.py) but the real solution I recommend is to figure out which is the other memory and to adjust its range accordingly Kind Regards Giacomo > -----Original Message----- > From: Sherif AbdelFadil via gem5-users <[email protected]> > Sent: 20 January 2021 11:54 > To: gem5 users mailing list <[email protected]> > Cc: Sherif AbdelFadil <[email protected]> > Subject: [gem5-users] SimpleMem error > > Hi, > on commit 0d703041fcd5d119012b62287695723a2955b408, running fs.py or > starter_fs.py with --mem-type=SimpleMemory causes the following error: > "fatal: fatal condition addrMap.insert(m->getAddrRange(), m) == addrMap.end() > occurred: Memory address range for system.realview.bootmem is overlapping" > > > This does not occur on commit 96fce476785a834f102ae69a895e661cf08e47cd. > I am not posting the exact other script optionsused because I tried many > combinations and configurations and the problem seems unrelated. Any idea > what the issue is here? IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ gem5-users mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
