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 <enricogiordano1...@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
