humm actually /boot/uEnv.txt say the opposite of what I said. However I still believe that to be wrong. Unless the file names have been swapped . . .
On Sat, Jul 4, 2015 at 12:57 AM, William Hermans <[email protected]> wrote: > OK so from this page: > http://elinux.org/BBB_Audio_Cape_RevB_Getting_Started > > *Since this Audio Cape uses the same audio signal from the onboard HDMI >> interface, you need to disable the audio portion of the HDMI by edit the >> uEnv.txt at /boot/uboot. Add this line to the uEnv.txt file: * >> >> * optargs=capemgr.disable_partno=BB-BONELT-HDMI* >> >> *Reboot your BBB. Log in and check the capemgr: * >> >> * root@beaglebone:~# cat /sys/devices/bone_capemgr*/slots >> 0: 54:PF--- >> 1: 55:PF--- >> 2: 56:PF--- >> 3: 57:PF--- >> 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G >> 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI >> 6: ff:P-O-L Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN* >> >> > If memory serves HDMIN is the audio portion of the hdmi output. So the > wiki is wrong. And seems I'm correct. > > debian@beaglebone:~$ *cat /boot/uEnv.txt* > #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 > > uname_r=3.8.13-bone70 > #dtb= > cmdline=quiet init=/lib/systemd/systemd > > ##Example > #cape_disable=capemgr.disable_partno= > #cape_enable=capemgr.enable_partno= > > ##Disable HDMI/eMMC > > #cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G > > ##Disable HDMI > #cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN > > ##Disable eMMC > #cape_disable=capemgr.disable_partno=BB-BONE-EMMC-2G > > > > *##Audio Cape (needs HDMI Audio > disabled)#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI#cape_enable=capemgr.enable_partno=BB-BONE-AUDI-02* > > > ##enable BBB: eMMC Flasher: > ##make sure, these tools are installed: dosfstools rsync > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh > > > > On Sat, Jul 4, 2015 at 12:25 AM, <[email protected]> wrote: > >> >> >> On Friday, July 3, 2015 at 9:59:05 PM UTC-6, William Hermans wrote: >>> >>> There was a change between 3.8.13-bone68, and 3.8.13-bone69 related to >>> I2C as I recall. That caused his problem. >>> >> >> Thanks William. I read that thread (which has more to do with Audio >> Cape's conflicts with the LCD Cape) and tried on a whim just commenting out >> pins 18 and 19, plus renaming the dtbo to BB-BONE-AUDI-03 but nothing >> changed... P9_28 is still flat when playing sound. >> >> >> >> >> >>> >>> Full post is here, and was quite recent: >>> https://groups.google.com/forum/#!searchin/beagleboard/audio$20cape|sort:date/beagleboard/2dXgKp9T8_g/j6o9Q8Jy2-QJ >>> >>> On Fri, Jul 3, 2015 at 8:35 PM, <[email protected]> wrote: >>> >>>> >>>> >>>> On Friday, July 3, 2015 at 7:14:16 PM UTC-6, [email protected] >>>> wrote: >>>>> >>>>> What distro and version are you using? I know on Debian after a >>>>> certain build ( I don't know which ) that BB-BONE-AUDI-02 is installed as >>>>> part of the kernel - if this is your case then the dts you are looking at >>>>> may not be the same at kernel dtbo is using - just a thought.... >>>>> >>>>> I had this issue with 3.13.8-bone70 >>>>> >>>> >>>> I'm using >>>> >>>> Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 >>>> armv7l GNU/Linux >>>> >>>> I'm not sure what you're saying though. I know that >>>> /lib/firmware/BB-BONE-AUDI-02.dtbo is the right one because I compiled it >>>> myself from the dts. Are you saying that it may conflict with another one >>>> already hardcoded in the kernel? >>>> >>>> When you had this issue, how did you resolve it? >>>> >>>> I suppose I could unload the dtbo and see if P9_28 comes to life?! >>>> >>>> >>>> -- >>>> 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. >>>> >>> >>> -- >> 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. >> > > -- 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.
