From: Sriramkumar Raju <rsriramkumar@gmail.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Red Boot Command Line Interface
Date: Mon, 23 May 2005 10:19:00 -0000 [thread overview]
Message-ID: <7de07eff050523024419606121@mail.gmail.com> (raw)
In-Reply-To: <m3is1ab8dk.fsf@xl5.calivar.com>
Hi,
No i didn't connected to serial port. What i am seeing is in
the target's screen itself. ie i am typing from the target which is
having a key board. The caps lock is not on since some characters
comes in small case and some in upper case.
Regards,
Sriram.R
On 23 May 2005 10:26:47 +0100, Nick Garnett <nickg@ecoscentric.com> wrote:
> Sriramkumar Raju <rsriramkumar@gmail.com> writes:
>
> > Hi,
> > I had successfully built Red Boot for I386 platform. My
> > development machine is Windows XP and i had installed cygwin
> > "CYGWIN_NT-5.1" which i got from "http://www.cygwin.com" I used ecos
> > config tool 2.0 to build the red boot image. The red boot image is
> > booting.
> >
> > But he command line is behaving differently.
> >
> > some key when i press it is displayed in caps and when i press "." it
> > displays ">" which is equivalent to pressing shift + "."
> >
> > I want to know do i missed any patch. or does anyone know what might
> > be the problem.
>
> Assuming that this is not simply a matter of leaving the caps-lock on,
> it looks like a mismatch between the setup of target and host serial
> devices. Check that the host terminal emulator is set to 8N1 38400 baud.
>
>
> --
> Nick Garnett eCos Kernel Architect
> http://www.ecoscentric.com The eCos and RedBoot experts
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-05-23 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 9:51 Sriramkumar Raju
2005-05-23 10:15 ` Nick Garnett
2005-05-23 10:19 ` Sriramkumar Raju [this message]
2005-05-23 12:18 ` Nick Garnett
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=7de07eff050523024419606121@mail.gmail.com \
--to=rsriramkumar@gmail.com \
--cc=ecos-discuss@sources.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).