From: "Stefano Martini" <martini@sci.univr.it>
To: <cgd@broadcom.com>
Cc: "GDB" <gdb@sources.redhat.com>
Subject: Re: new board
Date: Wed, 28 Apr 2004 13:58:00 -0000 [thread overview]
Message-ID: <00ca01c42d24$fdfcc410$2af21b9d@toti> (raw)
In-Reply-To: <yov5zn8yzkpo.fsf@ldt-sj3-010.sj.broadcom.com>
Thanks for the help,
I have defined all the memory regions for my board in
the file interp.c:
sim_do_command(sd,"memory region ......")
When I start the run program (mipsel-elf-run --board .....) to execute
a example program I get the following error messages:
mips-core: 1 byte read to unmapped address 0x0 at 0x800ab230
mips-core: 4 byte read to unmapped address 0x0 at 0x0
mips-core: 4 byte read to unmapped address 0x0 at 0x0
mips-core: 4 byte read to unmapped address 0x0 at 0x0
mips-core: 4 byte read to unmapped address 0x0 at 0x0
mips-core: 4 byte read to unmapped address 0x0 at 0x0
I have no address in region 0x0. Is this a problem
related to virtual and physical addresses?
I think "physical address" is an address generated by the
processor to access a memory region.
What is a virtual address?
Thanks in advance.
Stefano
----- Original Message -----
From: cgd@broadcom.com
To: Stefano Martini
Cc: GDB
Sent: Monday, April 26, 2004 7:56 PM
Subject: Re: new board
Unfortunately, as you've discovered, there's not much documentation
related to the simulator(s)...
At Mon, 26 Apr 2004 09:57:12 +0200, Stefano Martini wrote:
> I have seen two interesting commands:
>
> sim_do_command(sd,"memory region .....")
>
> sim_do_commandf(sd,"memory alias....");
>
> Which are the differences between sim_do_command and
> sim_do_commandf ?
looking at the changelogs:
* sim-utils.c (sim_do_commandf): New function, printf version of
sim_do_command.
That difference seems borne out by their usage.
> And more, which are the differences between memory region
> and memory alias?
memory region creates a region of memory to be used by the simulator.
memory alias creates a region in the address space that aliases an
existing region of memory.
As you can see from some of the code already there, this is used to
mock-up kseg1. (This method is, IMO, not ideal.)
chris
next prev parent reply other threads:[~2004-04-28 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 16:03 Stefano Martini
[not found] ` <mailpost.1082724164.28332@news-sj1-1>
2004-04-23 17:23 ` cgd
2004-04-26 17:57 ` Stefano Martini
[not found] ` <001801c42b64$17649c10$2af21b9d@toti>
2004-04-26 18:12 ` cgd
2004-04-28 13:58 ` Stefano Martini [this message]
2004-04-29 0:32 ` cgd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00ca01c42d24$fdfcc410$2af21b9d@toti' \
--to=martini@sci.univr.it \
--cc=cgd@broadcom.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox