[MinnowBoard] Echo to MinnowBoardMax GPIO export fails

Michael Jones mike at proclivis.com
Thu Jan 8 17:41:35 UTC 2015


John,

I can send me the outputs tonight. But, my kernel is 3.18.1, merged minnow board max txt file, and hand tweaked to support /dev/i2c. I did not merge or start with the ubuntu config file. So any affect from ubuntu is related to things outside the kernel, or outside the kernel causing the kernel to behave differently. When I used an ubuntu config to build 3.18.1, I had the same behavior as when not using it.

Mike


On Jan 8, 2015, at 10:37 AM, Darren Hart <dvhart at linux.intel.com> wrote:

> Thank you John,
> 
> So now we need to sort out if this is some configuration delta that I'm
> ignorant of, or if Ubuntu is being clever.
> 
> For those of you experiencing problems here, do you have anything else
> connected to the board? Any GPIO expanders or devices which might have
> GPIOs? I'm assuming not, but it's worth checking.
> 
> On an Ubuntu kernel, can someone send me the output of:
> 
> $ ls /sys/class/gpio/gpiochip*/
> 
> Or perhaps:
> 
> $ tree /sys/class/gpio
> 
> Thanks,
> 
> -- 
> Darren Hart
> Intel Open Source Technology Center
> 
> 
> 
> 
> On 1/7/15, 5:32 PM, "John Hawley" <john.hawley at intel.com> wrote:
> 
>> Ok I spent a little bit of time digging into this, it *LOOKS* like
>> Ubuntu is offset by +256 vs. stock and/or Fedora kernels.  Not 100% sure
>> why yet.
>> 
>> That being said I wrote up a quick script that should discover the right
>> values for everything and output it to a text console:
>> 
>> https://github.com/warthog9/minnow-max-extras/blob/master/lse/what_gpio_nu
>> m.sh
>> 
>> and I've got a merge request in with it (I'll let Darren have a look at
>> it and yell at me about it before it gets merged).
>> 
>> If you are having problems, can you run that script and let me know if
>> the output is right for you?  In the meantime I'll try and dig into why
>> the offset.
>> 
>> - John 'Warthog9' Hawley
>> 
>> On 01/07/2015 06:51 AM, Michael Jones wrote:
>>> Martin,
>>> 
>>> Very helpful, thanks. I had to think a bit to understand the base of 82
>>> and 154.
>>> 
>>> For others:
>>> 
>>> For 8x, Code GPIO# = 338 + Linux GPIO# (Chart) - 82
>>> For 2x, Code GPIO# = 410 + Linux GPIO# (Chart) - 154
>>> 
>>> So for the two examples:
>>> 
>>> 338 + 84 - 82 = 340
>>> 
>>> and
>>> 
>>> 410 + 208 - 154 = 464
>>> 
>>> I¹ll give this a try later this week.
>>> 
>>> Are there any proper ways to expose the /sys paths for user mode like
>>> one can do for /dev/ttyN? Or do people just run their code as root?
>>> 
>>> Mike
>>> 
>>> 
>>> On Jan 5, 2015, at 7:29 AM, Martin Oldfield
>>> <elinux-mbmx-2014-11 at mjoldfield.com> wrote:
>>> 
>>>> I've also found wildly different GPIO numbers on my Minnowboard Max.
>>>> 
>>>> You can read about it at
>>>> http://www.mjoldfield.com/atelier/2014/12/mbmx-gpio.html.
>>>> 
>>>> 
>>>> 
>>>> --
>>>> View this message in context:
>>>> http://minnowboard.57273.x6.nabble.com/MinnowBoard-Echo-to-MinnowBoardMa
>>>> x-GPIO-export-fails-tp903p907.html
>>>> Sent from the MinnowBoard mailing list archive at Nabble.com.
>>>> _______________________________________________
>>>> elinux-MinnowBoard mailing list
>>>> elinux-MinnowBoard at lists.elinux.org
>>>> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>>> 
>>> 
>>> _______________________________________________
>>> elinux-MinnowBoard mailing list
>>> elinux-MinnowBoard at lists.elinux.org
>>> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>>> 
> 
> 
> _______________________________________________
> elinux-MinnowBoard mailing list
> elinux-MinnowBoard at lists.elinux.org
> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard




More information about the elinux-MinnowBoard mailing list