Re: [Out-Of-Topic]How to Access Input GPIO of OMAP4460 without L4Re (direct access)

Matthias Lange <[email protected]>
Newsgroups gmane.comp.micro-kernel.l4.devel
Message-ID <[email protected]>
Hi,

On 01/27/2015 04:19 PM, Erry Pradana Darajati wrote:
> Hi L4 Hackers,
> My subject seems out of topic, but i don't know where i can ask this
> kind of thing, and i think there are many people have a knowledge about
> this subject.
> I have a problem. I want to directly access GPIO140 (in GPIO5 ball) as
> input.
> I have a function to print the value of GPIO5_DATAIN (0x4805 B138). But
> when i print that out, the value of it still not changed (zero value). I
> Conclude, the pin still not accepting the input. I have already done
> these things :
> 
> 1. Set GPIO5_OE to 0x1
> 2. See the value of MCSPI1_CS3 Pad Configuration (0x4A10 013C) and it
> give me value like this (0x011B 001B) which is for GPIO_140 ->
> MUX_MODE=gpio_140. PULLUDENABLE=0x1(enable). PULLTYPESELECT=0x1(enable).

This looks ok.

Do you have your input already connected to the pin? How does your input
works?

Maybe I can try your setup later today (no promise).

Matthias.

> Which is in my current knowledge, is a right setting for accepting
> input. But still, it's still not successful
> So where or what did i miss ? is it still any configuration / address to
> set ?
> 
> I appologize for the Out-of-Topic Subject .Thank you for any answer and
> suggestion and help.
> 
> -- 
> /Regards,/
> /Erry Pradana Darajati | *Student of Computer Engineering*/
> /*Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia*/
> 
> 
> _______________________________________________
> l4-hackers mailing list
> [email protected]
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
> 


-- 
Matthias Lange, [email protected], +49 - 351 - 41 88 86 14

Kernkonzept GmbH.  Sitz: Dresden.  Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-Ing. Michael Hohmuth
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.