From: Keith Seitz <keiths@redhat.com>
To: "Robert S. Grimes" <rsg@ll.mit.edu>
Cc: insight@sourceware.org
Subject: Re: Adding new target type
Date: Wed, 05 Sep 2007 22:15:00 -0000 [thread overview]
Message-ID: <46DF2A71.30905@redhat.com> (raw)
In-Reply-To: <46DF2397.5@ll.mit.edu>
Robert S. Grimes wrote:
>
> Not really following you exactly, but... it works! Here's what I put there:
I think you followed me exactly... :-)
> When I open the Target Selection dialog now, I see "RTEMS Remote/TCP",
> and when I select that, it gets pre-filled with 192.168.1.69, port 2159,
> just like I want it to! Of course, I'm not sure where those host:port
> values came from, but I'm guessing its some cache action on the part of
> gdb, as that's the last target I attempted to - is that right?
Hmm. I don't know where that would have come from. Insight's target
settings are pretty disjoint from gdb's... Nonetheless, Insight should
remember these numbers for you after you enter them the first time.
> Note from the above that I was also trying to get the serial setup to
> work, but that presented one oddity - when I selected the serial RTEMS
> target, the Baud value started out with "TCP" instead of 38400 - odd.
Yeah, that is odd. As long as you have the two database targets
"rtems-remote" and "rtems-remotetcp", you should be fine. Just
cut-n-paste the entries for Remote Serial/TCP.
> But don't worry, I don't want to use the serial port anyway, and even if
> I did, I could live with that.
Okay -- cool!
Happy hacking,
Keith
prev parent reply other threads:[~2007-09-05 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 19:32 Robert S. Grimes
2007-09-05 19:39 ` Keith Seitz
2007-09-05 20:33 ` Robert S. Grimes
2007-09-05 20:44 ` Keith Seitz
2007-09-05 20:56 ` Robert S. Grimes
2007-09-05 21:07 ` Keith Seitz
2007-09-05 21:46 ` Robert S. Grimes
2007-09-05 22:15 ` Keith Seitz [this message]
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=46DF2A71.30905@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=rsg@ll.mit.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).