Thanks for your rapid response. I did originally suspect it may already be included but a system wide search through folders did not reveal bb-bone-audi-02.dtbo file so I figured it wasn't included - I guess it has a different file name.
Would suggested fix be creating by own cape based on original dts and giving it a different name? ~C On Sunday, March 22, 2015 at 10:38:14 PM UTC-5, RobertCNelson wrote: > > The issue is name collision.. That dtbo is already built into the kernel. > Also see > > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Loading_custom_capes > > And search this list as we gone over it multiple times. > On Mar 22, 2015 8:14 PM, "Colin Bester" <[email protected] <javascript:>> > wrote: > >> Adding to this; >> >> If I remove the compiled dtbo file from /lib/firmware directory and >> power-off/power-on the board running manual insert "echo BB-BONE-AUDI-02 > >> /sys/devices/bone_capemgr.9/slots" gives error write error: File Exists and >> dmesg shows BB-BONE-AUDI-02 conflict gpio1_19 (#3:BB-BONE-LCD4-01) where >> I expect it to throw error stating No such file or directory. I validated >> expected error by trying >> >> echo BB-BONE-AUDI-03 > /sys/devices/bone_capemgr.9/slots which does give >> expected error of "write error: No such file or directory" >> >> On Sunday, March 22, 2015 at 9:57:06 PM UTC-5, Colin Bester wrote: >>> >>> In adding Audio Cape (BB-BONE-AUDI-02-00A0) to beaglebone black which >>> also has LCD4 mounted I receive a GPIO 19 conflict error. >>> >>> Looking at the dts file I see it has specified exclusive use for >>> gpio1_18 and gpio1_19. In the past I circumvented this error by commenting >>> these two pins out of the exclusive list and all works fine (doesn't appear >>> that these pwm pins are used by audio cape) >>> >>> Now I upgraded debian to 3.8.13-bone70 and in performing upgrade and >>> setting up new board I forgot to exclude these two pins from dts file >>> before compiling, only to see the conflict error again. >>> >>> My problem is that no matter what I do, (edit out pins, compile and copy >>> new dtbo to /lib/firmware), I keep getting the same conflict error. If I >>> edit the dts file and change the part number to something else and load it >>> manually it works so I know the change and compile is valid. >>> >>> It appears that my original compiled dtbo file is somehow being >>> cached/persisted through power off/power on and my updated dtbo is not >>> being 'seen'. >>> >>> I'd appreciate any suggestions on next steps. >>> >>> Colin >>> >>> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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.
