Re: [Gumstix-users] Changing overo.h pin muxing does not help

[Scott E. <sc...@ju...>]

Here's a simple kernel module will let you check the mux state on a
running system.

https://github.com/scottellis/omap3-mux

It might help with troubleshooting.

On Mon, 2011-09-26 at 12:52 +0000, Daniel wrote:
> Hi
> 
> I am failry new on the GUmstix platform, however I have designed an own carrier
> board to the Overo Earth. This carrier board does not have a display because I
> want to use the Omap DSS signal pins for GPIO instead. 
> 
> So I followed a tutorial on chaning the overo.h file. I changed the relevant pin
> muxing values in the .h file according to my needs, then apply the patch and
> then compile a new u-boot.bin. 
> 
> However, the u-boot change does not work propelry becuase I can see data signals
> on some DSS pins, and some relays on my GPIO interface is switching on/off
> rapidly. So DSS signals are still available. 
> 
> What am I doing wrong or what am I missing here? Is there a driver loaded
> somewhere during the boot-up that overrides my u-boot settings?
> 
> Happy for expert help! =)
> 
> BR
> Daniel
> 
> 
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users