2014-05-08 19:52 GMT+02:00 Robert Nelson <[email protected]>:
> On Thu, May 8, 2014 at 12:49 PM, José Luis Redrejo <[email protected]> wrote:
>> Hi, I've updated my Debian Wheezy BBB kernel to Robert Nelson
>> 3.13.10-bone9 kernel .
>>
>> Previously I had in my /etc/rc.local file this line:
>> echo BB-SPI0-01 > /sys/devices/bone_capemgr.9/slots
>>
>> to enable SPI0. Now the line is failing because
>> /sys/devices/bone_capemgr.* doesn't exist.
>>
>> I wouldn't care because /dev/spidev1.0 is appearing automagically, but
>> when I try to use Adafruit BBB Python library, it's failing with:
>> IOError: [Errno 2] No such file or directory: '/slots'
>>
>> So, is there any way to make this directory appear?, I've read in this
>> group somebody was working in a new cape manager, but I haven't found
>> how to use or get it.
>>
>> Before updating, with my 3.8 kernel it worked perfectly. But I'd like
>> to keep 3.13 because wifi is working much better now.
>
> So with v3.13/v3.14 we don't have capemgr. No one has successfully
> reported that from 3.8. We are hopeing when overlay's finally get
> mainlined, we may have a future capemgr.
>
> For right now, if you want spi, you need to edit the dtb file. For
> those that don't want to udpate, here is the default "pinmux" which
> includes SPI0 enabled.
>
> http://elinux.org/CircuitCo:Basic_Proto_Cape
>
>

Thanks for the information Robert, the funny thing is that SPI is
enabled and working, I've tested it. There is an available
/dev/spidev1.0, even if bone_capemgr.9 does not exist. I've switched
from Adafruit library (which needs the 'slots' directory) to another
python spi library ( https://github.com/doceme/py-spidev) and it works
perfectly.

Regards
José L.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to