public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Ling Su" <lingsu@palmmicro.com>
To: "Jonathan Larmour" <jlarmour@redhat.co.uk>
Cc: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] eCos PCI problem and NEC vrc4373 build option.
Date: Tue, 29 Aug 2000 17:18:00 -0000	[thread overview]
Message-ID: <000f01c01217$df482950$0201a8c0@raccoon> (raw)
In-Reply-To: <39AC12F4.9C2F7678@redhat.co.uk>

> Jonathan Larmour wrote:
> >
> > I will send you the executable by private mail to see if it works on
your
> > board.
>
> Attached, gzipped. I kept the debug info in case it's useful, although the
> path names will be wrong of course.
>

Your code works pretty fine on my board. I remember I have something might
be different in my configuration. I usually can not straight forward use the
code generated by "ecosconfig new vrc4373", I usually modify two things, one
is to delete the "-O2" option for compiler, another is to set both the
serial port drive baud rate to 38400b/s. If I don't delete the -O2 option,
the gdb usually hang there after I type "cont" after successfully download
the code. This problem has been reported by Charles on this list, his work
around solution is not to optimize the code, I follow the suggestion and it
works. I tried several NEC board, the result is the same, I must delete
the -O2 option every time. Jifl, do you apply this usually? or everything
just works fine for your board? I think this option might bring some
differences for our pci1.exe code. But anyway, yours code just works fine on
my board, probably my toolchain is not as good as yours. :) I use
binutils2.10 and egcs20000313 snapshot, insight 5.0. (I follow Charles
suggestion on this list actually.), I am not sure if his pci test program
works fine or not.

Any good suggestion? Please kindly let me know. I will be grateful!

Regards,
-Ling

  parent reply	other threads:[~2000-08-29 17:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-29 11:37 [ECOS] eCos tools binary installation under Cygwin Grant Edwards
2000-08-29 11:57 ` Jonathan Larmour
2000-08-29 12:28   ` Ling Su
2000-08-29 12:43     ` Jonathan Larmour
     [not found]       ` <39AC12F4.9C2F7678@redhat.co.uk>
2000-08-29 17:18         ` Ling Su [this message]
2000-08-30 15:25           ` [ECOS] Re: eCos PCI problem and NEC vrc4373 build option Jonathan Larmour
2000-08-30 15:51             ` Ling Su
2000-08-30 15:58               ` Jonathan Larmour
2000-08-30 16:38                 ` Alfredo Knecht
2000-08-30 17:20                   ` Jonathan Larmour
2000-08-30 18:10                     ` Alfredo Knecht
2000-08-30 18:22                       ` Jonathan Larmour
2000-08-30 17:42                   ` Ling Su
2000-08-30 18:02                     ` Jonathan Larmour
2000-08-30 18:28                       ` Ling Su
2000-08-30 18:57                         ` Jonathan Larmour
2000-08-31  3:34                           ` Nick Garnett
2000-08-31 10:57                           ` Ling Su

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='000f01c01217$df482950$0201a8c0@raccoon' \
    --to=lingsu@palmmicro.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.co.uk \
    /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).