This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Re: Problems with RedBoot on x86 generic pc...
- To: "'Mats Nordlund'" <Mats dot J dot Nordlund at telia dot se>,<ecos-discuss at sources dot redhat dot com>
- Subject: RE: [ECOS] Re: Problems with RedBoot on x86 generic pc...
- From: "Trenton D. Adams" <tadams at theone dot dnsalias dot com>
- Date: Thu, 30 Aug 2001 08:47:35 -0600
- Cc: <tadams at extremeeng dot com>
Yep, sounds like the same problem as mine. I find it weird that anyone
gets it going because every type of system I've tried it on I get the
same result. It's extremely odd. You would think that at the very
least the Screen/keyboard interface would be functional. Afterall,
those should be standard BIOS interrupt calls. Of course eCos probably
doesn't use the BIOS except to start.
Does the screen/keyboard interface work for you?
-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com] On Behalf Of Mats
Nordlund
Sent: Thursday, August 30, 2001 5:46 AM
To: ecos-discuss@sources.redhat.com
Cc: tadams@extremeeng.com
Subject: [ECOS] Re: Problems with RedBoot on x86 generic pc...
Hi,
I also have the same problem; the PC boots from floppy and
displays the startup screen on the serial interface. But I get no
response when trying to send keyboard strokes over the serial line.
Tried to switch serial ports. Tried to boot on 3-4 different machines
with the same result. Also tried two different machines as terminal (in
addition, with different terminal applications).
I also rebuilt i386-pc RedBoot using ct2 and the latest CVS without any
improvements (the same result as using the pre-built redboot.bin).
Seems like RedBoot doesn't read my serial line. It could be useful to
see which serial input RedBoot chooses.
Any suggestions?
br
/ Mats
>
> Anyway, my current problem is with RedBoot. I built the x86 version
and
> booted with the diskette. It seems to come up, and I see a RedBoot
> prompt on my screen. I'm assuming that even though I can see it on the
> local console, the local console isn't active, right? So, I have to
use
> a serial port or network, right?