This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: i386 RedBoot serial
- From: Pete Barrie <peter at cis dot strath dot ac dot uk>
- To: "McAtee, Kip" <Kip dot McAtee at SpirentCom dot COM>,"'ecos-discuss at sources dot redhat dot com'" <ecos-discuss at sources dot redhat dot com>
- Date: Thu, 07 Feb 2002 08:48:40 +0000
- Subject: Re: [ECOS] i386 RedBoot serial
At 17:03 06/02/2002 -1000, McAtee, Kip wrote:
>Greetings-
>
>I've successfully booted from the pre-built i386 RedBoot
>binary to the RedBoot> prompt, but the keyboard and the
>COM1 port don't accept input on several PCs.
>
>I'm using Hyperterm at 38400,8,N,1,none with a null
>modem cable. I see the boot messages (June 8, 2001 build)
>and the Redboot> prompt on both the video and the COM1
>port. Should I try a different terminal program?
This is interesting to me. I had redboot fail on several PC's
but then work on another (older Dell PII 180MHz) machine.
Failure always takes the same form on these non-working nodes:
1.Target PC boots:
2.Target PC delivers prompt via serial Port (seen on Hypertyerm on
my Win 2000 host)
Then...
Target PC does not respond to Hyperterm
Target PC local keyboard does not respond
Have others had this hit/miss experience with target PC's?
However, the latest advice on this group is to rebuild
redboot for i386 target PC's rather than use the prebuilt binary.
I've yet to get time to do this but will report back.
Maybe solves this issue?
Pete
See recent mail from:
Date: Wed, 6 Feb 2002 19:19:18 -0800 (PST)
From: michael shiloh <michael@magrittesystems.com>
To: "McAtee, Kip" <Kip.McAtee@SpirentCom.COM>
Pete
>My compliments and appreciation-
>Kip