From: alfred hitch <alfred.hitch@gmail.com>
To: Nickolay <nickolay@protei.ru>
Cc: ecos-discuss <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] GPIO blinking
Date: Mon, 28 Mar 2005 08:50:00 -0000 [thread overview]
Message-ID: <29f91651050327175616bcee9e@mail.gmail.com> (raw)
In-Reply-To: <42440242.5000904@protei.ru>
Hi,
I havent done led blinking ..
but I think it shouldnt be that tough .. u can call the GPIO_HIGH ,
etc macros which are there in the whole code .. that should take that
specific GPIO high and if ur LED is on that GPIO, it should blink ..
I am not too sure first of all how come default image u have made isnt
working on IXDP425, I am also using IXP425 based board .. and it works
fine for me with default compilation on IXDP425,
may be u can post something on that here and we can try and help u with that ..
Cheers,
Alfred
On Fri, 25 Mar 2005 15:21:22 +0300, Nickolay <nickolay@protei.ru> wrote:
> Hallo.
>
> I'll try load redboot on new hand worked IXDP425 board, but has some
> problem.
> The prefect way to debug where problem is, turn on/off some GPIO leds.
> Can anyone can tell me, how i can turn on/off GPIO?
> I discovery, that redboot start running from cyg_start() function, and
> then i wanna
> insert code for GPIO blinking after each instruction in that file.
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-03-28 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 22:24 Nickolay
2005-03-28 8:50 ` alfred hitch [this message]
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=29f91651050327175616bcee9e@mail.gmail.com \
--to=alfred.hitch@gmail.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=nickolay@protei.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).