On Wednesday, January 22, 2014 11:23:25 AM UTC-5, pushu...@gmail.com wrote: > > BBB Board running Angstrom v2012.12 and Linux beaglebone 3.8.13 #1 SMP Tue > Jun 18 02:11:09 EDT 2013 armv7l GNU/Linux > > Trying to run command "echo <overlay> > $SLOTS" results in error "-su: > echo: write error: No such file or directory" >
What's in 'overlay' -- is this the overlay file itself or does it contain the name of the overlay? You should be echoing the overlay name into $SLOTS; take a look here: http://learn.adafruit.com/introduction-to-the-beaglebone-black-device-tree/exporting-and-unexporting-an-overlay Could also be a conflict, you might need to add the following to uEnv in the boot partition (you'll need to mount /dev/mmcblk0p1 into /mnt to access this): optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN I can "cat $SLOTS" (/sys/devices/bone_capemgr.8/slots) just fine. I am root > and root has rw on that file.. > > I'm trying to get my own overlay working for a very simple no-eeprom cape > which has a DS1307 (which works fine, btw) and which will have an HD47780 > LCD. I have a number of pre-built overlays in /lib/firmware and none of > them will load. > > An example from dmesg: > [ 330.631832] bone-capemgr bone_capemgr.8: failed to load firmware > 'cape-bone-adafru-00A0.dtbo' > [ 490.071059] bone-capemgr bone_capemgr.8: part_number > 'cape-bone-adafruit-lcd-00A0', version 'N/A' > [ 490.071138] bone-capemgr bone_capemgr.8: slot #11: generic override > [ 490.071157] bone-capemgr bone_capemgr.8: bone: Using override eeprom > data at slot 11 > [ 490.071175] bone-capemgr bone_capemgr.8: slot #11: 'Override Board > Name,00A0,Override Manuf,cape-bone-adafru' > [ 490.071277] bone-capemgr bone_capemgr.8: slot #11: Requesting part > number/version based 'cape-bone-adafru-00A0.dtbo > [ 490.071296] bone-capemgr bone_capemgr.8: slot #11: Requesting firmware > 'cape-bone-adafru-00A0.dtbo' for board-name 'Override Board Name', version > '00A0' > [ 490.080114] bone-capemgr bone_capemgr.8: failed to load firmware > 'cape-bone-adafru-00A0.dtbo' > > Is it failing due to lack of an eeprom? > No, the EEPROM just enables "auto detection" of your cape, you put the part#/revision and it'll try to load it. However, there are issues, if you don't compile the overlay into the kernel, then the boot stalls for 60 seconds because the eMMC overlay gets loaded *after* the EEPROM ones and of course, the rootfs isn't available until then. Check your filenames here, the part # seems to be cape-bone-adafruit-lcd, but it's looking for cape-bone-adafru. Also, take another look at dmesg, after the 60 second stall, the eMMC overlay is loaded and rootfs mounted, I think it tries again. You could also try explicitly adding it to uEnv.txt: optargs=capemgr.enable_partno=my-overlay > My LCD project is using code from here: > LCD library: > http://www.nunoalves.com/open_source/?p=152 > (git repo https://github.com/nunoalves/BeagleBone_IO_lib) > > It looks like in the code (which fails on asserting GPIO pins) tries to > set up the pins itself. Should an overlay even be needed? > Yes, you'll likely need an overlay unless the pins you are using are already configured by default (e.g. I2C2). Hope this helps, -W -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
