public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@cygnus.co.uk>
To: "Ling Su" <lingsu@palmmicro.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Re: Fw: [ECOS] diag serial port and debug serial port conflict?
Date: Wed, 30 Aug 2000 10:23:00 -0000	[thread overview]
Message-ID: <poya1eekbu.fsf@balti.cygnus.co.uk> (raw)
In-Reply-To: <008a01c012a4$88abf080$0201a8c0@raccoon>

"Ling Su" <lingsu@palmmicro.com> writes:

> I met the same problem as descriped in following message, and I tried what
> Nick siad, actually I doubled the ZDEL, the result is the same. Any
> suggestion? Thanks!
> 

I do not now recall what the final solution to this problem was, but I
know it was solved. If Charles is listening, maybe he can remember
what the solution was.




> -Ling
> 
> 
> > "Charles F." <charles@202.96.178.16> writes:
> >
> > > I am sure they are initialized to the same speed. Yesterday I tried to
> use
> > > non-optimization setting (delete the -O2 switch in general build
> settings)
> > > to compile ecos and it works! I guess there is something wrong with the
> > > optimized serial port intialization code. I have experience porting
> WinCE to
> > > 4373 board and once I met this kind of problem too. Am I right?
> >
> >
> > This raises one possibility:
> >
> > The HAL_DUART_WRITE_CR() macro contains a delay loop that is used to
> > keep the Z8530 happy. It looks like with -O2 this loop maybe being
> > eliminated or optimized so it is too short. However, exactly the same
> > code appears in the initialization for the stubs, and GCC shouldn't
> > eliminate such loops. So it is not at all clear what the difference
> > here is.
> >
> > I have just compiled this code with -O2 and it seems to keep the delay
> > loop intact. Maybe your board has a faster CPU? The code is currently
> > set up for a 133MHz part. Try changing the value of ZDEL in
> > plf_z8530.h to something greater (and compiling with -O2) and see if
> > that makes a difference.
> >
> > --
> > Nick Garnett, eCos Kernel Architect
> > Red Hat, Cambridge, UK
> >
> >
> 
> 
> 


-- 
Nick Garnett, eCos Kernel Architect
Red Hat, Cambridge, UK

  reply	other threads:[~2000-08-30 10:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-30 10:05 [ECOS] " Ling Su
2000-08-30 10:23 ` Nick Garnett [this message]
2000-08-30 10:33   ` [ECOS] " Ling Su
2000-08-30 19:26   ` Charles Feng
2000-08-30 21:22     ` Jonathan Larmour
2000-08-31 10:55       ` 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=poya1eekbu.fsf@balti.cygnus.co.uk \
    --to=nickg@cygnus.co.uk \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=lingsu@palmmicro.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).