I modified my uEnv.txt optargs line from: optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
to: optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G capemgr.enable_partno=BB-BONE-AUDI-02 then rebooted and did the following: root@beaglebone:~# *aplay cats_in_cradle_harry_chapin.wav* ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver return ed error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned er ror: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned err or: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directo ry ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM default aplay: main:682: audio open error: No such file or directory root@beaglebone:~#* cat audioup* !# /bin/bash export SLOTS=/sys/devices/bone_capemgr.*/slots echo BB-BONE-AUDI-02 > $SLOTS root@beaglebone:~#* cat /sys/devices/bone_capemgr.8/slots* 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- root@beaglebone:~#* ./audioup* ./audioup: line 1: !#: command not found root@beaglebone:~# *cat /sys/devices/bone_capemgr.8/slots* 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 5: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02 root@beaglebone:~# aplay cats_in_cradle_harry_chapin.wav Playing WAVE 'cats_in_cradle_harry_chapin.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo root@beaglebone:~# uname -a Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l GNU/Linux root@beaglebone:~# as you can see it still needs done manually, even with the above change in uEnv.txt On Sat, May 24, 2014 at 10:20 PM, John Syn <[email protected]> wrote: > > From: Eric Fort <[email protected]> > Reply-To: <[email protected]> > Date: Saturday, May 24, 2014 at 9:52 PM > To: beagleboard <[email protected]> > Subject: Re: [beagleboard] Re: beagle audio cape (Rev B1) > > > > > On Sat, May 17, 2014 at 1:06 PM, John Syn <[email protected]> wrote: > >> >> >> From: Eric Fort <[email protected]> >> Reply-To: <[email protected]> >> Date: Saturday, May 17, 2014 at 10:57 AM >> To: beagleboard <[email protected]> >> Subject: [beagleboard] Re: beagle audio cape (Rev B1) >> >> ok, setup directions are here.... >> http://elinux.org/CircuitCo:Audio_Cape_RevB#Audio_Cape_Revision_B1 but >> I'm still trying to understand how all this works. are the cape eeproms >> and the info within them just not used? how is the cape Identified and >> setup automatically..... or must I edit one or more files to do this >> manually each and every time I add or remove the audio cape from the stack. >> >> Well, again it depends on your kernel version. If you are using V3.8, you >> add the audio cape in your uEnv.txt file and you enable the TLV320AIC3x >> driver in your kernel config. When your kernel boots, it runs the audio >> codec init which will eventually call the probe function and that will read >> in the audio cape device tree overlay and configure the audio codec. If you >> are using a kernel version later than V3.8, you have to manually add the >> audio cape device tree to your board device tree. >> >> Regards, >> John >> > > so since this is working manually how do I " add the audio cape in your > uEnv.txt file and you enable the TLV320AIC3x driver in your kernel config." > such that, " When your kernel boots, it runs the audio codec init which > will eventually call the probe function and that will read in the audio > cape device tree overlay and configure the audio codec." The instructions > are great for doing it manually but shouldn't end there. I'd like this to > happen on boot. > > Again, assuming Linux Kernel V3.8, add the following in uEnv.txt: > > add > > capemgr.enable_partno=BB-BONE-AUDI-02 > > to optargs > > So my optargs looks like this: > > optargs=capemgr.disable_partno=BB-BONELT-HDMI > capemgr.enable_partno=BB-BONE-AUDI-02 > > Regards, > John > > > > Thanks, > > Eric > >> >> Eric >> >> >> On Sat, May 17, 2014 at 10:30 AM, Eric Fort <[email protected]> wrote: >> >>> The beagle audio cape seems to not have a cape eeprom. How then is it >>> detected as being there with the present kernel? since it has no cape >>> eeprom does this mean that it does not count as to being one of the 4 cape >>> addresses thus giving a free pass with the ability to have this cape and 4 >>> others. I'm really looking forward to playing with this board. >>> >>> Eric >>> >> >> -- >> 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. > > -- > 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.
