From: Alex Mathews <alexma@crosstor.com>
To: "D.S.Phani Kumar" <phani.kumar@wipro.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] i386 architecture
Date: Fri, 06 Oct 2000 07:38:00 -0000 [thread overview]
Message-ID: <39DDE334.880E8CA@crosstor.com> (raw)
In-Reply-To: <001301c02f5e$1cee8980$37eba8c0@wipro.com>
What you are seeing is correct. You are seeing data output to the
screen of the target system. Any printfs will be displayed in your GDB
session and not on the target screen. All output from the target goes
back over the serial line. So, play with the example programs, or the
test programs to see if things are working correctly.
-Alex
"D.S.Phani Kumar" wrote:
>
> Hello all,
> I am experimenting eCos with the PC (386 compatible). I have configured the
> eCos and finally got some .img and .bin files. Then I copied this into a
> floppy using the Unix DD command. I booted another system using this floppy.
> The system shows some funny characters. I have connected this system to
> another using serial cable. Now when I tried to run the tests on the another
> PC the PC which is booted with eCos shows some funny characters.
>
> Does anyone can tell me what I should do. Are there any links/material/URL's
> read about configuring the eCos for the 386 PC's
>
> with best regards,
> D.S.Phani Kumar
> *********************************************************
> Wipro Limited, Global R & D,
> Chamundi Complex,
> 26, Hosur Road, Bommanahalli,
> Bangalore - 560 068. India
>
> Ph : +91-80-5722293/96 Extn:5367
> Fax : +91-80-5722696 / 5722073
> mailto : phani.kumar@wipro.com
> *********************************************************
--
Alex Mathews
CrosStor Software, Inc.
908-226-0100 ext 148
alexma@crosstor.com
prev parent reply other threads:[~2000-10-06 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-05 23:20 D.S.Phani Kumar
2000-10-06 7:38 ` Alex Mathews [this message]
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=39DDE334.880E8CA@crosstor.com \
--to=alexma@crosstor.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=phani.kumar@wipro.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).