public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <w3sg@SoftHome.net>
To: Mike Arthur <arth2219@gmail.com>
Cc: eCos discuss list <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: diag_printf via serial port
Date: Fri, 01 Jun 2007 20:15:00 -0000	[thread overview]
Message-ID: <20070601201452.GA24139@ubuntu> (raw)
In-Reply-To: <2a3305fe0706011147v2f4711d9oddbdbbcd24f96315@mail.gmail.com>

On Fri, Jun 01, 2007 at 01:47:55PM -0500, Mike Arthur wrote:
> >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.
> 
> Could another difference be that Sergi is running through GDB and
> you're loading the ELF file directly?

I can load ELF and run it using RedBoot's 'go' as well for the target.
It seems, that the last way, it's to send him (UTFB): redboot.bin.gz,
twothreads.gz. Recently, he wrote about tweaking lpc variant HAL:
lpc2xxx/var/current/src/hal_diag.c as I could understand.

To clean _any_ mess in $ECOS_REPOSITORY at all, I preffer to fulfil
(well that does a script, but this just a way).

i. Checkout

    cd ~/cvs
    cvs -d ... login
    cvs -z3 -d ... checkout ecos ecos-host

ii. Move a worked tree anywhere, this is that case

    mv ~/ecos/ecos{,.bak}

iii. Rsync local 'cvs' and 'worked' tree

    rsync -a ~/cvs/ecos ~/ecos

iv. Add the stuff wasn't being here (in the repository)

    tclsh ecosadmin.tcl add <package-name.epk>

vi. build, test RedBoot/eCos

So, I did suggest Alexey to fulfil almost same things to leave behind
any doubts.


-- 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

  reply	other threads:[~2007-06-01 20:15 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
2007-06-01 18:48           ` Mike Arthur
2007-06-01 20:15             ` Sergei Gavrikov [this message]
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=20070601201452.GA24139@ubuntu \
    --to=w3sg@softhome.net \
    --cc=arth2219@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).