public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Michael Jones <mjones@linear.com>
To: EnneGi <enricogiordano1992@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: How to create a GPIO driver
Date: Thu, 14 Mar 2013 15:32:00 -0000	[thread overview]
Message-ID: <B812ED20-3EE6-456A-90A9-655A37F2BD8F@linear.com> (raw)
In-Reply-To: <1363274631389-225418.post@n7.nabble.com>

EnneGi,

I don't know this part, but you may want to look at the configuration of the port. Most GPIO have a configuration register. It is possible the GPIO port is disabled or disconnected. You should be able to examine the configuration registers with your debugger. I find it much faster to just see what is in the registers than wade through code trying to reason my way to the registers value.

Mike



On Mar 14, 2013, at 9:23 AM, EnneGi <enricogiordano1992@gmail.com> wrote:

> thanks for reply. Now I describe my steps:
> 
> - found explicit address of gpio in the file lpc17xx.h at this url:
> http://www.keil.com/dd/docs/arm/nxp/lpc17xx/lpc17xx.h
> (search   "Peripheral memory map")
> 
> - copy the address in the "var_io.h" of the stm32 in the "#define" of gpio
> and copy the part of source that I modify in the "var_io.h" in "the
> var_io.h" of lpc1766stk
> 
> - compile ecos with 
>   ecosconfig new lpc1766stk
>   ecosconfig tree
>   make
> 
> - try an application of gpio
> 
> 
> <cyg/hal/var_io.h>
> 
> int main (void)
> {
>    hal_LPC17XX_gpio_set(/*here I put the address*/);
>    hal_LPC17XX_gpio_out(/*here I put the address*/, 0);
> 
> }
> 
> 
> I think that gpio (associated to led) send value 0 in the output.
> 
> 
> 
> --
> View this message in context: http://sourceware-org.1504.n7.nabble.com/How-to-create-a-GPIO-driver-tp224910p225418.html
> Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.
> 
> -- 
> 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

  parent reply	other threads:[~2013-03-14 15:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10 18:19 [ECOS] " EnneGi
2013-03-10 18:59 ` Andrew Lunn
2013-03-10 19:23 ` Ilija Kocho
2013-03-10 22:57   ` [ECOS] " EnneGi
2013-03-11 14:24     ` Morris, Richard
2013-03-11 16:52       ` EnneGi
2013-03-12 14:49         ` [ECOS] " Morris, Richard
2013-03-12 22:17           ` [ECOS] " EnneGi
2013-03-13 15:36             ` Morris, Richard
2013-03-14 14:41               ` EnneGi
2013-03-14 15:05                 ` Michael Jones
2013-03-14 15:24                   ` EnneGi
2013-03-14 15:26                     ` EnneGi
2013-03-14 15:32                     ` Michael Jones [this message]
2013-03-14 15:35                       ` EnneGi
2013-03-14 15:43                         ` [ECOS] " Michael Jones
2013-03-14 15:53                           ` [ECOS] " EnneGi
2013-03-14 15:58                             ` Michael Jones
2013-03-14 16:09                         ` [ECOS] " Morris, Richard
2013-03-14 17:08                           ` [ECOS] " EnneGi
2013-03-14 18:17                             ` [ECOS] " Morris, Richard
2013-03-14 18:27                               ` [ECOS] " EnneGi
2013-03-14 19:59                               ` EnneGi
2013-03-14 21:10                                 ` Morris, Richard
2013-03-15 19:09                                   ` EnneGi
2013-03-15 22:14                                     ` EnneGi
2013-03-14 15:06                 ` EnneGi
2013-03-14 15:21                   ` Michael Jones
2013-03-12 22:36           ` EnneGi
2013-03-11 14:11   ` [ECOS] " Morris, Richard

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=B812ED20-3EE6-456A-90A9-655A37F2BD8F@linear.com \
    --to=mjones@linear.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=enricogiordano1992@gmail.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).