I'm also trying to get Ruby in ARM FS working, but I'm working off a pull
of gem5 from today. I'm running into the same issue I think, but you
didn't give the error I'm getting. Here it is:
gem5.opt: build/ARM/mem/ruby/system/DirectoryMemory.cc:164: AbstractEntry*
DirectoryMemory::lookup(PhysAddress): Assertion `idx < m_num_entries'
failed.
I turned on tracing off RubyCache, and also see an invalid access to
0x80000000.
Here are the lines leading up to the assertion:
0: system.dir_cntrl0.directory: Looking up address: [0x354700, line
0x354700]
0: system.dir_cntrl0.directory: Looking up address: [0x354700, line
0x354700]
0: system.dir_cntrl0.directory: Looking up address: [0x354700, line
0x354700]
0: system.dir_cntrl0.directory: Looking up address: [0x80000000, line
0x80000000]
Anyone know how to fix this problem? This is my first attempt at getting
Ruby to work with Arm.
Thanks,
Andrew
On Sun, Apr 1, 2012 at 6:20 PM, Tony <[email protected]> wrote:
> Tony Feng <tony.fengkai <at> gmail.com> writes:
>
> >
> >
> > Hi,
> >
> > In M5Port::recvFunctional of RubyPort.cc, if the isPhysMemAddress test
> fails,
> does it necessarily mean it is a packet sent to a pio port?
> >
> > I added some debugging info, found the packet has an invalid source id,
> and a
> destination address of 0x80000000, whereas I believe the system port range
> is 0
> - 0x7ffffff. Could anyone share thoughts on this?
> >
> >
> > Thanks,
> > Tony
> >
> >
> >
> > _______________________________________________
> > gem5-users mailing list
> > gem5-users <at> gem5.org
> > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
>
> I believe I've found where went wrong, but still don't know the solution.
>
> Since I was running ARM FS with Ruby, the bootloader needs to be setup:
> info: Using bootloader at address 0x80000000
>
> this msg was shown immediately after I caught a functional access for
> address
> 0x8000000.
>
> Maybe something is wrong with the bootloader setup. The way that I
> implemented
> it in FSConfig.py is:
> self.realview.nvmem = PhysicalMemory(range = AddrRange(Addr('2GB'), size =
> '64MB'), zero = True)
> self.boot_loader = binary('boot.arm')
> self.boot_loader_mem = self.realview.nvmem
> self.realview.nvmem.port = self.piobus.master
>
> where the piobus is directly connected to the memory:
> self.piobus.master = physmem.port
>
> Could anyone observe anything wrong here? Or could anyone explain why a
> request
> has the address of the bootloader?
>
> Thanks,
> Tony
>
> _______________________________________________
> gem5-users mailing list
> [email protected]
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
