public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@cygnus.co.uk>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] problem regarding porting of ecos to PC i386
Date: Wed, 05 Sep 2001 00:10:00 -0000	[thread overview]
Message-ID: <po4s7oqn02.fsf@balti.cygnus.co.uk> (raw)
Message-ID: <20010905001000.f4mFwNjTCcY9UlTMbs620CzVLI1rvcQSN8OKMA-V-aM@z> (raw)
In-Reply-To: <000801bfc550$d5cc3a10$5800000a@amit>

"Amit Agrawal" <amita@aftek.com> writes:

> I have configured the kernel according to my target architecture i.e =
> i386 PC.
> Built the library and also the tests.
> After this I prepared the gdb stub startup floppy using the file.
> Using this I booted my target PC it shows some characters and numbers.
> 
> I dont know how to proceed further.
> I have to show ecos running on the target PC to the senior foks in my =
> company so that they r assured of ecos as a good RTOS.
> 
> HOW do I conclude that ecos is ported to the target system.
> PLZ help me !
> 
> 

What you are getting on the screen is the GDB stub reporting what it
is sending out of COM1. This means that the monitor floppy is up and
running.

You now need to connect COM1 of your target machine to a serial port
on your host machine using a null modem. You should now be able to run
GDB on the host and connect it via the serial line to the GDB stubs in
the target.

If you have built a standard RAM configuration of ecos and all the test
programs you can now download any of the tests (I would use tm_basic
for a demo) and run them in the ususal way.

-- 
Nick Garnett
Cygnus Solutions, a Red Hat Company
Cambridge, UK

  reply	other threads:[~2001-09-05  0:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-24  0:18 Amit Agrawal
2000-05-24  3:30 ` Nick Garnett [this message]
2001-09-05  0:10   ` 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=po4s7oqn02.fsf@balti.cygnus.co.uk \
    --to=nickg@cygnus.co.uk \
    --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).