public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mats Nordlund <Mats.J.Nordlund@telia.se>
To: "Trenton D. Adams" <tadams@theone.dnsalias.com>
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: Problems with RedBoot on x86 generic pc...
Date: Fri, 31 Aug 2001 00:15:00 -0000	[thread overview]
Message-ID: <3B8F3A1A.ACC9B7B8@telia.se> (raw)
In-Reply-To: <000401c13162$b4c7bef0$090110ac@TRENT>

Yes, the local keyboard/display input/output works fine. When a have a
serial terminal connected, I can see the startup screen (the RedBoot
prompt), but after that the serial terminal doesn't show the commands
given on the local keyboard. It seems like the serial output works until
the prompt, but not after. The serial input does not receive any
commands sent from the terminal application. After bootup, I have tried
to switch to the other serial output of the RedBoot machine, with no
success.

/ Mats

"Trenton D. Adams" wrote:
> 
> 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?

  reply	other threads:[~2001-08-31  0:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-30  4:44 Mats Nordlund
2001-08-30  7:47 ` Trenton D. Adams
2001-08-31  0:15   ` Mats Nordlund [this message]
2001-09-06 23:52     ` Jonathan Larmour
2001-09-07  0:18       ` Mats Nordlund
2001-09-07  0:26         ` Jonathan Larmour
2001-09-07  0:56           ` Mats Nordlund

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=3B8F3A1A.ACC9B7B8@telia.se \
    --to=mats.j.nordlund@telia.se \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=tadams@theone.dnsalias.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).