This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: ethernet download
- To: Grant Edwards <grante at visi dot com>
- Subject: Re: [ECOS] ethernet download
- From: Gary Thomas <gthomas at redhat dot com>
- Date: Fri, 24 Aug 2001 09:59:25 -0600 (MDT)
- Cc: "Trenton D. Adams" <tadams at theone dot dnsalias dot com>,
- Cc: "Trenton D. Adams" <tadams at theone dot dnsalias dot com>,Mark Salter <msalter at redhat dot com>, ecos-discuss at sourceware dot cygnus dot com
- Organization: Red Hat, Inc.
On 24-Aug-2001 Grant Edwards wrote:
> On Fri, Aug 24, 2001 at 09:48:32AM -0600, Gary Thomas wrote:
>>
>> On 24-Aug-2001 Grant Edwards wrote:
>> > On Fri, Aug 24, 2001 at 09:24:30AM -0600, Trenton D. Adams wrote:
>> >
>> >> > Also, in the case of systems like linux, RedBoot is out of the
>> >> > picture completely once the app is started. The app is then
>> >> > free to reuse any RAM that was previously used by RedBoot.
>> >>
>> >> Well then how are you supposed to ever update your program? If
>> >> redboot doesn't watch on the network port, you can't update
>> >> your program anymore.
>> >
>> > You push the little red reset button on the corner of the
>> > board. That returns control to RedBoot.
>> >
>> > [There needs to be an international treaty forbidding the
>> > trafficing in hardware without reset buttons.]
>>
>> 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.