From: "Stefano Martini" <martini@sci.univr.it>
To: <cgd@broadcom.com>
Cc: "GDB" <gdb@sources.redhat.com>
Subject: Re: new board
Date: Mon, 26 Apr 2004 17:57:00 -0000 [thread overview]
Message-ID: <003501c42b64$654262f0$2af21b9d@toti> (raw)
In-Reply-To: <yov565bq7i96.fsf@ldt-sj3-010.sj.broadcom.com>
Thank you for your help.
I have found, in interp.c, the memory layout definition for
some boards.
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 ?
And more, which are the differences between memory region
and memory alias?
Thanks in advance
Stefano
----- Original Message -----
From: cgd@broadcom.com
To: martini@sci.univr.it
Cc: GDB
Sent: Friday, April 23, 2004 6:48 PM
Subject: Re: new board
At Fri, 23 Apr 2004 12:42:44 +0000 (UTC), "Stefano Martini" wrote:
> I'm writing programs for a specific mips board.
> I need to edit the gdb (sim) source files to add this
> board.
>
> Is there any document about this topic?
Not really.
> I think I have to specify the memory regions for the board.
> Which is the right way to do this?
See interp.c.
But, my personal favorite method -- not currently supported in
unmodified sources, I don't think 8-) -- is to have a "no board"
option, and specify all of the devices (hardware files, memory
regions, etc.) from the command line.
Given that there can be ... dozens of possible board configurations
that one might want to model, stuffing them into C code in the
simultor is not particularly desirable in my opinion.
cgd
next prev parent reply other threads:[~2004-04-26 7:59 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 [this message]
[not found] ` <001801c42b64$17649c10$2af21b9d@toti>
2004-04-26 18:12 ` cgd
2004-04-28 13:58 ` Stefano Martini
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='003501c42b64$654262f0$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