public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <w3sg@SoftHome.net>
To: Alexey Shusharin <mrfinch@mail.ru>
Cc: eCos discuss list <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: diag_printf via serial port
Date: Fri, 01 Jun 2007 18:31:00 -0000	[thread overview]
Message-ID: <20070601183048.GA16975@ubuntu> (raw)
In-Reply-To: <46604ADB.70407@mail.ru>

On Fri, Jun 01, 2007 at 11:35:39PM +0700, Alexey Shusharin wrote:
> Sergei Gavrikov wrote:
> >Alexey, with a default eCos settings the eCos 'examples/twothreads'
> >works without any tricks. You have to agree that is a bit complex test
> >than your.
> 
> Hello Sergei,
> 
> Of course, I tryed to run twothreads example. Moreover, I simplifyed it 
>  and got my test. Twothreads does't work on my board (via serial). :-(
> 
> It's strange, that your board works via serial. Maybe in your 
> configuration interrupt driven serial driver is enabled. It overwrites 
> variant implementation. In that case, my board works too. But, it 
> doesn't matter now.

At least one time in a week I rsync the eCos anonymous cvs tree with my
worked copy of the ECOS_REPOSITORY. I've done that today too. I'd done
no changes in Olimex plf HAL since 2007/01/31. So, I would want be sure
that your RedBoot, eCos test and your eCos repository is a freshmeat.
AFAIK, default ecos.ecc (configuration) uses ROM monitor (ROM calling
interface). Therefore, any out dated RedBoot stuff can be a reason of
the difference. 

So, 1) do cvs checkout; 2) download the latest epk, add it to ecos db
(ecosadmin.tcl), apply that CS8900A patch; 3) rebuild/upgrade RedBoot;
4) build the 'examples/twothreads'.

Note: Be sure that you didn't mess any sources in $ECOS_REPOSITORY
before. As I did note, it's better to rsync cvs tree with your worked
tree.

Only in such a case, it will be possible to compare our lab's results. 

A moment ago, I did repeat that lab with 1 only difference. I began do
that with line a 'ecosconfig new olpce2294' instead of that 'ecosconfig
new olpch2294' :-) The results are same (as I got for LPC-H2294). The
'twothreads' worked as expected. I even didn't connect RJ-45 for the
lab :-)

Kind regards,

-- Sergei


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2007-06-01 18:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 12:01 cetoni GmbH - Uwe Kindler
2007-05-31 12:30 ` Alexey Shusharin
2007-05-31 13:25   ` cetoni GmbH - Uwe Kindler
2007-05-31 14:29   ` Sergei Gavrikov
2007-06-01 12:27     ` Alexey Shusharin
2007-06-01 13:42       ` Sergei Gavrikov
2007-06-01 16:35         ` Alexey Shusharin
2007-06-01 18:25           ` Sergei Gavrikov
2007-06-04  7:40             ` Alexey Shusharin
2007-06-04  8:35               ` Sergei Gavrikov
2007-06-04 17:44                 ` Sergei Gavrikov
2007-06-01 18:31           ` Sergei Gavrikov [this message]
2007-06-01 18:48           ` Mike Arthur
2007-06-01 20:15             ` Sergei Gavrikov
2007-06-01 16:00       ` Sergei Gavrikov
2007-06-01 14:04   ` Sergei Gavrikov
2007-06-01 18:47   ` Sergei Gavrikov

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=20070601183048.GA16975@ubuntu \
    --to=w3sg@softhome.net \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=mrfinch@mail.ru \
    /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).