dc in AtomicSimpleCPU::tick
> (this=0x59649600) at build/ARM/cpu/simple/atomic.cc:685
> #20 0x5715ffcd in std::function::operator()() const
> (this=0x596499a0) at /usr/include/c++/7/bits/std_function.h:706
> #21 EventFunctionWrapper::process (this=0x59649968) at
>
tq.cc:223
#23 0x57181cd0 in doSimLoop (eventq=0x5900b200) at
build/ARM/sim/simulate.cc:216
#24 0x57182eda in simulate (num_cycles=) at
build/ARM/sim/simulate.cc:129
```
-jrb
From: Bohren, Jonathan via gem5-users
mailto:gem5-users@gem5.org>>
Sent: Friday, January 22, 202
/ARM/sim/eventq.cc:223
#23 0x57181cd0 in doSimLoop (eventq=0x5900b200) at
build/ARM/sim/simulate.cc:216
#24 0x57182eda in simulate (num_cycles=) at
build/ARM/sim/simulate.cc:129
```
-jrb
From: Bohren, Jonathan via gem5-users
Sent: Friday, January 22, 2021 10:07 AM
T
l Message-
> From: Bohren, Jonathan via gem5-users
> Sent: 22 January 2021 12:51
> To: gem5 users mailing list
> Cc: Gabe Black ; Bohren, Jonathan
>
> Subject: [gem5-users] Re: VExpress_GEM5_V1, Ethernet, and BARs
>
> Gabe,
>
>
>
> Yeah, this is a very recent
: [gem5-users] Re: VExpress_GEM5_V1, Ethernet, and BARs
Are you using up to date develop? There was a bug like this a while ago, but
it's been fixed on develop for a while as well.
Gabe
On Thu, Jan 21, 2021 at 6:35 PM Bohren, Jonathan via gem5-users
mailto:gem5-users@gem5.org>> wrote:
We'v
We've been using the `VExpress_GEM5_V1` platform but it was failing on both
`stable` and `develop` when adding an `IGbE_e1000` PCI device to the
`makeArmSystem()` function in `FSConfig.py`. We've worked around it, but
looking for the "right way" to add such a device.
For reference, the change
