Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gem5 ARM full-system error #40

Open
sudhanshu2 opened this issue Mar 24, 2024 · 4 comments
Open

Gem5 ARM full-system error #40

sudhanshu2 opened this issue Mar 24, 2024 · 4 comments

Comments

@sudhanshu2
Copy link

I replaced the memory config line of code in the starter full-system simulation for ARM with the code specified in the readme but get the following error:

src/mem/physical.cc:108: fatal: fatal condition addrMap.insert(m->getAddrRange(), m) == addrMap.end() occurred: Memory address range for system.realview.bootmem is overlapping

I was wondering if y'all knew why Gem5 is throwing this error with Ramulator 2 and/or have the Ramulator2 config and the Gem5 options that y'all used to verify that your code works?

Thanks :)

@lnghrdntcr
Copy link

I second this, I'm encountering the same error when I'm trying to run a configuration that has multiple gem5 memory channels. Did you manage to solve this?

@atrah22
Copy link

atrah22 commented Aug 12, 2024

Same here.
Could anyone manage to solve this?
There is no way to set the AddrRange in the Ramulator2() class. This is an issue due to to AddrRange which should start from 0x80000000 address for DDR as per the Express_GEM5_Base class in gem5/src/dev/arm/Realview.py.
If this is not resolved or shown in README file, its hard to compare ramulator with gem5 O3 ARM CPU

@sangjae4309
Copy link
Contributor

To set the AddrRange in the Ramulator2() class, We need to wrap the ramulator2 around AbstractMemorySystem which is conventional gem5's main memory source code.

Here is my code for how to set the addr range (line 67-82)

@sangjae4309
Copy link
Contributor

sangjae4309 commented Sep 19, 2024

Any way, I think the error is originated from using wrong version of kernel or bootloader (not form setting AddrRange).

Please refer to my script (line77-79) that ARM full system simulation works properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants