From: "Trenton D. Adams" <tadams@theone.dnsalias.com>
To: "'Grant Edwards'" <grante@visi.com>,
"'Gary Thomas'" <gthomas@redhat.com>
Cc: "'Mark Salter'" <msalter@redhat.com>,
<ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] ethernet download
Date: Fri, 24 Aug 2001 09:03:00 -0000 [thread overview]
Message-ID: <002f01c12cb6$45d71c80$090110ac@TRENT> (raw)
In-Reply-To: <20010824110249.A3748@visi.com>
You're assuming I make bugs! ;)
-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[ mailto:ecos-discuss-owner@sources.redhat.com ] On Behalf Of Grant
Edwards
Sent: Friday, August 24, 2001 10:03 AM
To: Gary Thomas
Cc: Trenton D. Adams; Mark Salter; ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] ethernet download
On Fri, Aug 24, 2001 at 09:59:25AM -0600, Gary Thomas wrote:
>
> >> How about hardware with no serial port - only an ethernet
> >> connection? Yes, we have worked with such beasties... fun, in
> >> the purest sense :-)
> >
> > My version of RedBoot listens on a TCP port. You push the
> > reset button then you've got 10 seconds to telnet to RedBoot.
> > Once you've opened a telnet session, it just like you're
> > connected to a serial console.
>
> Actually, they all work that way :-) The real problem is when
> you're just bringing things up initially (or making major
> changes to the startup code). Trying to debug with only a
> network connection in this environment can be more than tricky.
That's when you use hardware-assisted debugging: either a
full-up in-circuit emulator or something like a JTAG interface.
Wasting several weeks of engineering time (and marketing
window) to save a few thousand dollars is false economy.
Or layout the board with a debugging serial port (something
with a nice big FIFO that will run at 115K baud or higher) and
then don't populate that portion of the board in production.
Or put a header of some sort on the board so that you can
attach a daughterboard with a UART. Something as simple as a
three pin SPI or I2C connector can be used to interface to a
UART while you're debugging.
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2001-08-24 9:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 14:41 Trenton D. Adams
2001-08-23 15:58 ` Gary Thomas
2001-08-24 7:38 ` Trenton D. Adams
2001-08-24 7:51 ` Gary Thomas
2001-08-24 7:59 ` Trenton D. Adams
2001-08-24 8:06 ` Gary Thomas
2001-08-24 8:22 ` Mark Salter
2001-08-24 8:24 ` Trenton D. Adams
2001-08-24 8:30 ` Gary Thomas
2001-08-24 8:32 ` Grant Edwards
2001-08-24 8:38 ` Trenton D. Adams
2001-08-24 8:41 ` Grant Edwards
2001-08-24 8:40 ` Gary Thomas
2001-08-24 8:42 ` Grant Edwards
2001-08-24 8:51 ` Gary Thomas
2001-08-24 9:00 ` Grant Edwards
2001-08-24 9:03 ` Trenton D. Adams [this message]
2001-08-24 9:05 ` Grant Edwards
2001-08-24 9:09 ` Trenton D. Adams
2001-08-24 9:03 ` Gary Thomas
2001-08-24 9:46 ` Grant Edwards
2001-08-24 8:34 ` Mark Salter
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='002f01c12cb6$45d71c80$090110ac@TRENT' \
--to=tadams@theone.dnsalias.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=grante@visi.com \
--cc=gthomas@redhat.com \
--cc=msalter@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).