public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: "adon@walkersun" <adon@walkersun.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] cannot run test on PC
Date: Mon, 11 Sep 2000 11:04:00 -0000	[thread overview]
Message-ID: <39BD1EAB.F3BDF86C@redhat.com> (raw)
In-Reply-To: <001b01c01ba2$d32a71c0$24e7f1d2@walkersun>

> "adon@walkersun" wrote:
> 
>     I have build all the files which eCos wanted, and I use the eCos to
> build the stubs for PC target follows the starting guild.
>     So, for the gdb_module.bin, I could make it into floppy and boot a
> PC, and I could let it communicated with host PC(I used the win2000 for
> the host). and then I open the "run test" in eCos configure tools, but I
> cannot get any further response form my target PC(pentiun II, 266M, 128M
> RAM). the target always hangup or reboot after download the test program,
> and I do not know the program either been download finished. So, could
> anybody guide me how to solve this???

Did you change your template back to "default" from "stubs" and rebuild all
the tests, preferably in a new build tree?

> And I also found another problem, when I configure the serial port speed
> to 115200 as default, and I let the target PC boot, but I found the
> target PC serial port speed also 38400, where am I wrong???

Nothing - this is again one of the failings of the i386-pc port I'm afraid.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

      reply	other threads:[~2000-09-11 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-10 20:38 adon@walkersun
2000-09-11 11:04 ` Jonathan Larmour [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=39BD1EAB.F3BDF86C@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=adon@walkersun.com \
    --cc=ecos-discuss@sourceware.cygnus.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).