public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Fano Ramparany <Fano.Ramparany@rd.francetelecom.fr>
To: "Lewin A.R.W. Edwards" <larwe@larwe.com>
Cc: eCos Disuss <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] ROM startup on EP7212
Date: Thu, 22 Mar 2001 00:51:00 -0000	[thread overview]
Message-ID: <3AB9BBE0.28227C66@rd.francetelecom.fr> (raw)
In-Reply-To: <4.3.2.7.2.20010321123306.00aff0e0@mail.larwe.com>

"Lewin A.R.W. Edwards" wrote:

> Does the DIAG LED come on when you hit the wakeup button?

Hi Lewin,
Yes it does. However I've noticed that it does only if I switch off and switch
on the
board before doing the "ureset wakeup" (if the boards remains switched on and
I do several "ureset wakeup", then only the first and sometimes second ones
make the DIAG come on.

> If so, try to compilfde this little example (just paste it over hello.c).
> Connect a loudspeaker to position LS2 on the board. If you hear a beep out
> of it, then the code is running and getting to main() OK.

No this example doesn't make the buzzer work, although the diag led turns on.

What date your version of ecos is?

The reason I've tested back the rom startup of hello.c. Is that I have just
finished testing  a client/server application with the redboot monitor. This
worked
fine, but the application gets stuck once I moved it to rom startup mode. So I
just wanted
to add some tracing (simple printf calls) to check on the hyperterminal  how
far the application
on the board is going? but couldn't.

Thank you again for your help.

Fano

  reply	other threads:[~2001-03-22  0:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21  9:03 Fano Ramparany
2001-03-21  9:47 ` Lewin A.R.W. Edwards
2001-03-22  0:51   ` Fano Ramparany [this message]
2001-03-22  5:43     ` Lewin A.R.W. Edwards
2001-03-22  8:22       ` Fano Ramparany
     [not found] <CAEMICOOKMKAGHPNGNFNOEDECHAA.danc@iobjects.com>
2001-03-23  7:45 ` Fano Ramparany

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=3AB9BBE0.28227C66@rd.francetelecom.fr \
    --to=fano.ramparany@rd.francetelecom.fr \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=larwe@larwe.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).