CapeManager dilemma ?

Moderators: adafruit_support_bill, adafruit

Please be positive and constructive with your questions and comments.
Locked
User avatar
borisw37
 
Posts: 4
Joined: Fri Oct 10, 2014 5:25 pm

CapeManager dilemma ?

Post by borisw37 »

I'm using BeagleBone Black RevC, trying to disable the HDMI, eMMC capes and enable the ADAFRUIT-SPI0 cape (the ADAFRUIT-SPI0-00A0.dtbo was already included in the lib/firmware directory with the Debian distribution)

I've followed the instruction to modify the uEnv.txt. In the Debian dist. the file is no longer single line? It actually had the disable and enable commands already included just commented out.
- After modifying the file, the HDMI and eMMC capes do get disabled on bootup, but the SPI cape doesn't load.
- I've tried manually loading the cape by "echo ADAFRUIT-SPI0 >/sys/devices/bone_capemgr*/slots" that does work.
- I've added another cape enable to the uEnv.txt just for sanity check "cape_enable=capemgr.enable_partno=BB-ADC,ADAFRUIT-SPI0", the ADC cape does get loaded at bootup but not the SPI cape...

What am I doing wrong? I've attached the uEnv.txt file.
Should I re-compile the SPI cape?
Attachments
uEnv.txt
uEnv.txt
(1.65 KiB) Downloaded 164 times

User avatar
borisw37
 
Posts: 4
Joined: Fri Oct 10, 2014 5:25 pm

Re: CapeManager dilemma ?

Post by borisw37 »

Apparently the all new and fancy CapeManager is not without its own bugs. There is a workaround to doing boot-time config:
Ex:
add "CAPE=BB-SPI1-01" to /etc/default/capemgr

http://elinux.org/Beagleboard:BeagleBon ... stom_capes

Locked
Please be positive and constructive with your questions and comments.

Return to “Beagle Bone & Adafruit Beagle Bone products”