Re: [beagleboard] Re: How to use USB headset with Beagle Board

[Zainab S.V]

How to use the switch/push buttton to record voice in beaglebone? Is it by
using gpio programming by setting the pin as input?

On Fri, Mar 13, 2015 at 11:07 AM, Harvey White 
wrote:

> On Fri, 13 Mar 2015 10:34:08 +0530, you wrote:
>
> >Does USB headset mic amplifies input speech signal?
>
> Probably, but you'd have to look at the specifications to be sure. The
> input is voice, the output is a digital data stream.  The microphone
> puts out millivolts, the USB data stream can be scaled to anything.
>
> Check the specifications, or borrow one and try it.
>
> Harvey
>
>
> >
> >On Thu, Mar 12, 2015 at 10:37 AM, Harvey White 
> >wrote:
> >
> >> On Wed, 11 Mar 2015 21:49:00 -0700 (PDT), you wrote:
> >>
> >> >Will USB headset with mic work for audio application that records sound
> >> and
> >> >playback on beaglebone with quality?Here is there is no need for
> separate
> >> >pre- amplifier or circuit that requires biasing mic voltage?
> >>
> >> The hardware can't tell the difference between being plugged into the
> >> BBB and a standard computer.  The microphone will be properly biased.
> >>
> >> You will have to have a driver to communicate with the USB interface
> >> in the headset.
> >>
> >> Harvey
> >>
> >> >
> >> >
> >> >On Monday, February 24, 2014 at 5:00:39 AM UTC+5:30, Kenji Nakasone
> wrote:
> >> >>
> >> >> Same problem here with beatblock bluetooth speaker. I pair the
> speaker
> >> but
> >> >> can listen to music on it.
> >> >>
> >> >> I tried creating .asoundrc and asound.conf
> >> >>
> >> >> I run:
> >> >> mplayer -ao alsa:device=btheadset  song.mp3
> >> >>
> >> >> but I get this:
> >> >>
> >> >> [AO_ALSA] alsa-lib: dlmisc.c:236:(snd1_dlobj_cache_get) Cannot open
> >> shared
> >> >> library /usr/lib/alsa-lib/libasound_module_pcm_bluetooth.so
> >> >> [AO_ALSA] Playback open error: No such device or address
> >> >> Failed to initialize audio driver 'alsa:device=btheadset'
> >> >> Could not open/initialize audio device -> no sound.
> >> >> Audio: no sound
> >> >> Video: no video
> >> >>
> >> >> any help?
> >> >>
> >> >> On Wednesday, February 25, 2009 3:43:45 AM UTC-2, vijay...@gmail.com
> >> >> wrote:
> >> >>>
> >> >>> Hi,
> >> >>>   I am trying to use USB headset with Beagle Board.I have
> >> >>> connected USB headset to beagle board through USB hub.I am not able
> to
> >> >>> listen audio through USB headset. But at the same time i can hear
> the
> >> >>> audio through normal headset (Through sterio audio output jack).I
> can
> >> >>> see USB headset is getting detected on Beagle Board.
> >> >>>   Please help me in this case. First thing is it possible to use
> >> >>> USB headset with Beagle Board? Do i need to modify any configuration
> >> >>> file Or Some Kernel Configuration? Or what other changes i need to
> do
> >> >>> for using the USB headset with Beagle Board.It will be great help if
> >> >>> you provide the solution.
> >> >>>
> >> >>> Thanks,
> >> >>> Vijay Swami
> >> >>>
> >> >>
> >>
> >> --
> >> For more options, visit http://beagleboard.org/discuss
> >> ---
> >> You received this message because you are subscribed to a topic in the
> >> Google Groups "BeagleBoard" group.
> >> To unsubscribe from this topic, visit
> >> https://groups.google.com/d/topic/beagleboard/f8k7_s5Tjqo/unsubscribe.
> >> To unsubscribe from this group and all its topics, send an email to
> >> beagleboard+unsubscr...@googlegroups.com.
> >> 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/f8k7_s5Tjqo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Soldering JTAG connector with Element14(Embest) version BBB failed

[Claud Xiao]

Hi Harvery, 

700 dgree can melt lead-free solder *directly* very well -- that's how I 
adhere a layer of solder to connector pins. Then I put connector on top of 
P2 on the board and heat the pins for making the solder melt and connect 
joint just like the video. But the solder between pins and P2 won't melt 
and none of it will adhere to the P2 even I heated 4-6 seconds in 700 
degree. Note that I cleaned the solder iron with tip tinner and brass 
sponge before this step. 

Another way is just like you said (hope my understanding is correct) to 
heat some solder and let it flow to the pin and wet the joint. I tried. But 
the solder flow won't adhere to the P2 but just accumulated on the pin till 
bridge with adjacent pin. 

Do you have any comment on this situation? 

Thank you so much!

On Monday, March 23, 2015 at 8:37:46 PM UTC-7, Harvey White wrote:
>
> On Mon, 23 Mar 2015 19:46:19 -0700 (PDT), you wrote: 
>
> >Thank you Tom and Harvey! I'll try again with higher temperature (800 or 
> >even more higher till it melts) as well as adopt Harvey's suggestions. 
> >Result will be reported in this thread. 
>
> Ah, no, more temperature is not always what's needed.   
>
> Too cold and it never melts.  Too hot and it damages the board and 
> what you're soldering.  For leaded solder, 600 degrees is fine for 
> small sensitive parts, 700 degrees for standard parts, and you almost 
> never need 800 degrees. 
>
> Try a few joints with the solder and just solder a few pieces of wire 
> together, say 22 gauge or so.  That gives you the practice you may 
> need for lead free solder (behaves differently). 
>
>
> > 
> >I used lead-free .022 in 700 degree. Temperature is one of a few factors 
> I 
> >haven't adjusted in those attempts for not damaging the board. 
> > 
> 800 degrees is a bit too hot.  There's a bit of a touch to it, as to 
> how to solder and how not to.  You want the solder to "flow" and to 
> "wet" the joint as if it were water. 
>
> I'd see what the melting point of your particular lead free solder is, 
> and then see what the recommended iron temperature is as well. 
>
> Harvey 
>
> >Also I've found CircuitCo version in Jameco Electronics. 
> > 
> >On Monday, March 23, 2015 at 5:25:56 PM UTC-7, Harvey White wrote: 
> >> 
> >> On Mon, 23 Mar 2015 16:56:58 -0700 (PDT), you wrote: 
> >> 
> >> > 
> >> >> 
> >> >> 
> >> >>   
> >> >> 
> >> > 
> >> >I just checked my settings. I have my iron set to 430C / 806 F and 
> >> haven't 
> >> >touched it since soldering that JTAG connector last week.  Yeah.  So 
> very 
> >> >hot. Don't leave it sit on the board at that temp. I figured a fast 
> dab 
> >> at 
> >> >high temp is better than letting it sit at lower temp though.  Maybe 
> I'm 
> >> >wrong. Like I said, I'm not a pro with the soldering, but it worked 
> for 
> >> me 
> >> >on the first try. Before I got my nice soldering iron I had problems 
> >> >getting connectors soldered onto another board because my iron wasn't 
> >> >getting hot enough. I don't have that problem anymore. :-) 
> >> > 
> >> >My solder is Kester 44 Rosin Core Solder 60/40 .031. 
> >> 
> >> OK, several things here: 
> >> 
> >> 1) 63/37 is eutectic for solder, and has the lowest melting point.  It 
> >> goes from liquid to solid and does not have a plastic phase (good). 
> >> 
> >> 2) 700 degrees is normal, and 600 is used for sensitive devices. 
> >> 
> >> 3) the amount of power that your tip can deliver (not necessarily the 
> >> temperature) determines the size of the joint you can heat and 
> >> successfully solder 
> >> 
> >> 4) clean is the key, a freshly tinned tip (clean and can transfer heat 
> >> well)  is much better than an oxidized tip. 
> >> 
> >> 5) better to use a brass sponge than a wet one.  Less thermal shock to 
> >> the tip. 
> >> 
> >> Harvey 
> >> 
> >> > 
> >> >Tom Olenik 
> >> 
> >> 
>
>

-- 
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/d/optout.

[beagleboard] RE: Reading from ADC hangs

[Matti Laakso]

Hi,

I simply added

&tscadc {
status = "okay";
};

&am335x_adc {
ti,adc-channels = <0 1 2 3 4 5 6 7>;
};

to the end of am335x-boneblack.dts.

Date: Mon, 23 Mar 2015 15:07:04 -0700
From: matthew.mcne...@gmail.com
To: beagleboard@googlegroups.com
CC: dajiang...@gmail.com; malaa...@elisanet.fi
Subject: Re: Reading from ADC hangs

Hi Matti,
Would you please provide details on which dts entries (or maybe a link to the 
entire dts file!) you're specifying in order to get ADC working with 3.18?
Thanks!

On Monday, March 2, 2015 at 1:04:39 PM UTC-5, mala...@elisanet.fi wrote:

On Thursday, February 26, 2015 at 5:18:51 PM UTC+2, dajia...@gmail.com wrote:Hi,
How come in my system, there is no /sys/bus/iio/devices/iio:device0?Under 
/sys/bus/iio/devices/, there is only one file iio_sysfs_trigger, which is a 
symbolic link to some other directory.Is there any configuration I need to do?I 
am using the latest BB black Rev C by Element14. It is OS is 3.8.13-bone47.
Thx.

Hi,
You need to enable the ADC either by enabling the correct "cape" with capemgr 
(only in kernel 3.8.*, see e.g. 
http://hipstercircuits.com/reading-analog-adc-values-on-beaglebone-black/), or 
by enabling it in the .dts-file (later kernels, such as the 3.18.4 which I'm 
using).
Matti 
On Wednesday, February 25, 2015 at 8:36:18 PM UTC+8, mala...@elisanet.fi 
wrote:Thanks for the suggestion. I'll keep that in mind if I need higher 
sampling rates. However, I did find a way to read ADC through IIO so that it 
doesn't hang.

First set up the channels and the buffer through sysfs:

echo 1 > /sys/bus/iio/devices/iio\:device0/scan_elements/in_voltage0_en
echo 256 > /sys/bus/iio/devices/iio\:device0/buffer/length
echo 1 >  /sys/bus/iio/devices/iio\:device0/buffer/enable

and then read from /dev/iio:device0. This way I can achieve about 8 kHz 
sampling rate with a single channel, 4 kHz with two channels and down to ~300 
Hz with all eight channels.
  

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

dmesg | grep cape showed a lot:

[0.560695] bone-capemgr bone_capemgr.9: Baseboard:
'A335BNLT,00C0,3214BBBK8615'
[0.560722] bone-capemgr bone_capemgr.9:
compatible-baseboard=ti,beaglebone-black
[0.584814] bone-capemgr bone_capemgr.9: slot #0: 'BeagleBone AUDIO
CAPE,00A1,Beagleboardtoys,BB-BONE-AUDI-01'
[0.614598] bone-capemgr bone_capemgr.9: slot #1: No cape found
[0.651706] bone-capemgr bone_capemgr.9: slot #2: No cape found
[0.688814] bone-capemgr bone_capemgr.9: slot #3: No cape found
[0.695030] bone-capemgr bone_capemgr.9: slot #4: specific override
[0.695052] bone-capemgr bone_capemgr.9: bone: Using override eeprom
data at slot 4
[0.695067] bone-capemgr bone_capemgr.9: slot #4:
'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'
[0.695147] bone-capemgr bone_capemgr.9: slot #5: specific override
[0.695166] bone-capemgr bone_capemgr.9: bone: Using override eeprom
data at slot 5
[0.695180] bone-capemgr bone_capemgr.9: slot #5:
'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'
[0.695251] bone-capemgr bone_capemgr.9: slot #6: specific override
[0.695268] bone-capemgr bone_capemgr.9: bone: Using override eeprom
data at slot 6
[0.695282] bone-capemgr bone_capemgr.9: slot #6:
'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN'
[0.695602] bone-capemgr bone_capemgr.9: loader: before slot-0
BB-BONE-AUDI-01:00A1 (prio 0)
[0.695619] bone-capemgr bone_capemgr.9: loader: check slot-0
BB-BONE-AUDI-01:00A1 (prio 0)
[0.695694] bone-capemgr bone_capemgr.9: loader: before slot-4
BB-BONE-EMMC-2G:00A0 (prio 1)
[0.695707] bone-capemgr bone_capemgr.9: loader: check slot-4
BB-BONE-EMMC-2G:00A0 (prio 1)
[0.695777] bone-capemgr bone_capemgr.9: loader: before slot-5
BB-BONELT-HDMI:00A0 (prio 1)
[0.695789] bone-capemgr bone_capemgr.9: loader: check slot-5
BB-BONELT-HDMI:00A0 (prio 1)
[0.695822] bone-capemgr bone_capemgr.9: initialized OK.
[0.696283] bone-capemgr bone_capemgr.9: loader: after slot-0
BB-BONE-AUDI-01:00A1 (prio 0)
[0.696302] bone-capemgr bone_capemgr.9: slot #0: Requesting part
number/version based 'BB-BONE-AUDI-01-00A1.dtbo
[0.696318] bone-capemgr bone_capemgr.9: slot #0: Requesting firmware
'BB-BONE-AUDI-01-00A1.dtbo' for board-name 'BeagleBone AUDIO CAPE', version
'00A1'
[0.696708] bone-capemgr bone_capemgr.9: loader: check slot-4
BB-BONE-EMMC-2G:00A0 (prio 1)
[0.698667] bone-capemgr bone_capemgr.9: loader: check slot-5
BB-BONELT-HDMI:00A0 (prio 1)
[0.700292] bone-capemgr bone_capemgr.9: loader: before slot-6
BB-BONELT-HDMIN:00A0 (prio 2)
[0.700307] bone-capemgr bone_capemgr.9: loader: check slot-6
BB-BONELT-HDMIN:00A0 (prio 2)
[0.700321] bone-capemgr bone_capemgr.9: loader: check slot-6
BB-BONELT-HDMIN:00A0 (prio 2)
[1.070829] bone-capemgr bone_capemgr.9: failed to load firmware
'BB-BONE-AUDI-01-00A1.dtbo'
[1.079721] bone-capemgr bone_capemgr.9: loader: failed to load slot-0
BB-BONE-AUDI-01:00A1 (prio 0)
[1.089331] bone-capemgr bone_capemgr.9: loader: check slot-6
BB-BONELT-HDMIN:00A0 (prio 2)
[1.089357] bone-capemgr bone_capemgr.9: loader: check slot-5
BB-BONELT-HDMI:00A0 (prio 1)
[1.089371] bone-capemgr bone_capemgr.9: loader: after slot-5
BB-BONELT-HDMI:00A0 (prio 1)
[1.089395] bone-capemgr bone_capemgr.9: slot #5: Requesting firmware
'cape-boneblack-hdmi-00A0.dtbo' for board-name 'Bone-Black-HDMI', version
'00A0'
[1.089424] bone-capemgr bone_capemgr.9: slot #5: dtbo
'cape-boneblack-hdmi-00A0.dtbo' loaded; converting to live tree
[1.089771] bone-capemgr bone_capemgr.9: slot #5: #4 overlays
[1.090823] bone-capemgr bone_capemgr.9: loader: check slot-4
BB-BONE-EMMC-2G:00A0 (prio 1)
[1.090845] bone-capemgr bone_capemgr.9: loader: after slot-4
BB-BONE-EMMC-2G:00A0 (prio 1)
[1.090864] bone-capemgr bone_capemgr.9: slot #4: Requesting firmware
'cape-bone-2g-emmc1.dtbo' for board-name 'Bone-LT-eMMC-2G', version '00A0'
[1.090879] bone-capemgr bone_capemgr.9: slot #4: dtbo
'cape-bone-2g-emmc1.dtbo' loaded; converting to live tree
[1.091426] bone-capemgr bone_capemgr.9: slot #4: #2 overlays
[1.120725] bone-capemgr bone_capemgr.9: slot #4: Applied #2 overlays.
[1.120750] bone-capemgr bone_capemgr.9: loader: done slot-4
BB-BONE-EMMC-2G:00A0 (prio 1)
[1.120959] bone-capemgr bone_capemgr.9: loader: check slot-6
BB-BONELT-HDMIN:00A0 (prio 2)
[1.253451] bone-capemgr bone_capemgr.9: slot #5: Applied #4 overlays.
[1.253473] bone-capemgr bone_capemgr.9: loader: done slot-5
BB-BONELT-HDMI:00A0 (prio 1)
[1.253506] bone-capemgr bone_capemgr.9: loader: check slot-6
BB-BONELT-HDMIN:00A0 (prio 2)
[1.253522] bone-capemgr bone_capemgr.9: loader: after slot-6
BB-BONELT-HDMIN:00A0 (prio 2)
[1.253549] bone-capemgr bone_capemgr.9: slot #6: Requesting firmware
'cape-boneblack-hdmin-00A0.dtbo' for board-name 'Bone-Black-HDMIN', version
'00A0'
[1.253581] bone-capemgr bone_capemgr.9: slot #6: dtbo
'cape-boneblack-hdmin-00A0.dtb

[beagleboard] Re: Having to manually start Wifi

[Nathaniel Johnson]

UPDATE: Fredrik Olofsson's solution worked for me.  I left in my auto 
statement as well.

On Thursday, March 19, 2015 at 11:06:22 AM UTC-5, Nathaniel Johnson wrote:
>
>
> I have been trying to get wifi to work on the latest debian image.  It 
> does work but requires me to manually start it after logging in. If I log 
> in and type 'ifup wlan0' It works fine.  Even putting 'ifup wlan0' in 
> /etc/rc.local does not work.
>
> Here is a link to my etc/network/interfaces http://pastebin.com/37AjV6tG
>
> I also noticed this repeating over and over in /var/log/wicd/
>
> 2015/03/01 22:03:16 :: Autoconnecting...
> 2015/03/01 22:03:16 :: No wired connection present, attempting to 
> autoconnect to wireless network
> 2015/03/01 22:03:18 :: Unable to autoconnect, you'll have to manually 
> connect
>
>
> The full file http://pastebin.com/8sznu2bB
>
> Any help would be appreciated.
>

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Bill Traynor]

On Tue, Mar 24, 2015 at 5:29 AM, Marty  wrote:
> dmesg | grep cape showed a lot:
>
> [0.560695] bone-capemgr bone_capemgr.9: Baseboard:
> 'A335BNLT,00C0,3214BBBK8615'
> [0.560722] bone-capemgr bone_capemgr.9:
> compatible-baseboard=ti,beaglebone-black
> [0.584814] bone-capemgr bone_capemgr.9: slot #0: 'BeagleBone AUDIO
> CAPE,00A1,Beagleboardtoys,BB-BONE-AUDI-01'
> [0.614598] bone-capemgr bone_capemgr.9: slot #1: No cape found
> [0.651706] bone-capemgr bone_capemgr.9: slot #2: No cape found
> [0.688814] bone-capemgr bone_capemgr.9: slot #3: No cape found
> [0.695030] bone-capemgr bone_capemgr.9: slot #4: specific override
> [0.695052] bone-capemgr bone_capemgr.9: bone: Using override eeprom data
> at slot 4
> [0.695067] bone-capemgr bone_capemgr.9: slot #4:
> 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'
> [0.695147] bone-capemgr bone_capemgr.9: slot #5: specific override
> [0.695166] bone-capemgr bone_capemgr.9: bone: Using override eeprom data
> at slot 5
> [0.695180] bone-capemgr bone_capemgr.9: slot #5:
> 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'
> [0.695251] bone-capemgr bone_capemgr.9: slot #6: specific override
> [0.695268] bone-capemgr bone_capemgr.9: bone: Using override eeprom data
> at slot 6
> [0.695282] bone-capemgr bone_capemgr.9: slot #6:
> 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN'
> [0.695602] bone-capemgr bone_capemgr.9: loader: before slot-0
> BB-BONE-AUDI-01:00A1 (prio 0)
> [0.695619] bone-capemgr bone_capemgr.9: loader: check slot-0
> BB-BONE-AUDI-01:00A1 (prio 0)
> [0.695694] bone-capemgr bone_capemgr.9: loader: before slot-4
> BB-BONE-EMMC-2G:00A0 (prio 1)
> [0.695707] bone-capemgr bone_capemgr.9: loader: check slot-4
> BB-BONE-EMMC-2G:00A0 (prio 1)
> [0.695777] bone-capemgr bone_capemgr.9: loader: before slot-5
> BB-BONELT-HDMI:00A0 (prio 1)
> [0.695789] bone-capemgr bone_capemgr.9: loader: check slot-5
> BB-BONELT-HDMI:00A0 (prio 1)
> [0.695822] bone-capemgr bone_capemgr.9: initialized OK.
> [0.696283] bone-capemgr bone_capemgr.9: loader: after slot-0
> BB-BONE-AUDI-01:00A1 (prio 0)
> [0.696302] bone-capemgr bone_capemgr.9: slot #0: Requesting part
> number/version based 'BB-BONE-AUDI-01-00A1.dtbo
> [0.696318] bone-capemgr bone_capemgr.9: slot #0: Requesting firmware
> 'BB-BONE-AUDI-01-00A1.dtbo' for board-name 'BeagleBone AUDIO CAPE', version
> '00A1'
> [0.696708] bone-capemgr bone_capemgr.9: loader: check slot-4
> BB-BONE-EMMC-2G:00A0 (prio 1)
> [0.698667] bone-capemgr bone_capemgr.9: loader: check slot-5
> BB-BONELT-HDMI:00A0 (prio 1)
> [0.700292] bone-capemgr bone_capemgr.9: loader: before slot-6
> BB-BONELT-HDMIN:00A0 (prio 2)
> [0.700307] bone-capemgr bone_capemgr.9: loader: check slot-6
> BB-BONELT-HDMIN:00A0 (prio 2)
> [0.700321] bone-capemgr bone_capemgr.9: loader: check slot-6
> BB-BONELT-HDMIN:00A0 (prio 2)
> [1.070829] bone-capemgr bone_capemgr.9: failed to load firmware
> 'BB-BONE-AUDI-01-00A1.dtbo'
> [1.079721] bone-capemgr bone_capemgr.9: loader: failed to load slot-0
> BB-BONE-AUDI-01:00A1 (prio 0)
> [1.089331] bone-capemgr bone_capemgr.9: loader: check slot-6
> BB-BONELT-HDMIN:00A0 (prio 2)
> [1.089357] bone-capemgr bone_capemgr.9: loader: check slot-5
> BB-BONELT-HDMI:00A0 (prio 1)
> [1.089371] bone-capemgr bone_capemgr.9: loader: after slot-5
> BB-BONELT-HDMI:00A0 (prio 1)
> [1.089395] bone-capemgr bone_capemgr.9: slot #5: Requesting firmware
> 'cape-boneblack-hdmi-00A0.dtbo' for board-name 'Bone-Black-HDMI', version
> '00A0'
> [1.089424] bone-capemgr bone_capemgr.9: slot #5: dtbo
> 'cape-boneblack-hdmi-00A0.dtbo' loaded; converting to live tree
> [1.089771] bone-capemgr bone_capemgr.9: slot #5: #4 overlays
> [1.090823] bone-capemgr bone_capemgr.9: loader: check slot-4
> BB-BONE-EMMC-2G:00A0 (prio 1)
> [1.090845] bone-capemgr bone_capemgr.9: loader: after slot-4
> BB-BONE-EMMC-2G:00A0 (prio 1)
> [1.090864] bone-capemgr bone_capemgr.9: slot #4: Requesting firmware
> 'cape-bone-2g-emmc1.dtbo' for board-name 'Bone-LT-eMMC-2G', version '00A0'
> [1.090879] bone-capemgr bone_capemgr.9: slot #4: dtbo
> 'cape-bone-2g-emmc1.dtbo' loaded; converting to live tree
> [1.091426] bone-capemgr bone_capemgr.9: slot #4: #2 overlays
> [1.120725] bone-capemgr bone_capemgr.9: slot #4: Applied #2 overlays.
> [1.120750] bone-capemgr bone_capemgr.9: loader: done slot-4
> BB-BONE-EMMC-2G:00A0 (prio 1)
> [1.120959] bone-capemgr bone_capemgr.9: loader: check slot-6
> BB-BONELT-HDMIN:00A0 (prio 2)
> [1.253451] bone-capemgr bone_capemgr.9: slot #5: Applied #4 overlays.
> [1.253473] bone-capemgr bone_capemgr.9: loader: done slot-5
> BB-BONELT-HDMI:00A0 (prio 1)
> [1.253506] bone-capemgr bone_capemgr.9: loader: check slot-6
> BB-BONELT-HDMIN:00A0 (prio 2)
> [1.253522] bone-capemgr bone_capemgr.9: loader: after slot-6
> BB-BONELT-HDMIN:00A0 (prio 2)
> [1.253

[beagleboard] installing os

[Praveen chowdary]

hi i have got a old bb xm board from scrap and there was no sd card in that 
,can any one says me how to install os into that. is there android os for xm

-- 
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/d/optout.

[beagleboard] Location of .dtb files in 2015-03-01

[ohararp]

Per RobertC's help I have 2015-03-01 up and running.  I have been using our 
LEDscape repo to modify the .dtb file locations to handle the control of 
the prus to enable 48 parallel outputs for the control of leds.  Normally, 
I would follow one of the procedures below, but for this new image it seems 
the .dtb file locations have changed.  Can anybody point me to any 
documentation about whree they might reside and any chnages made in regard 
to the .dtb functionality?

Angstrom - RevB
> ```
> git clone git://github.com/Yona-Appletree/LEDscape
> cd LEDscape
> cp /boot/am335x-boneblack.dtb{,.preledscape_bk}
> cp am335x-boneblack.dtb /boot/
> modprobe uio_pruss
> reboot
> ```
> Debian - RevC
> ```
> git clone git://github.com/Yona-Appletree/LEDscape
> cd LEDscape
> cp /boot/uboot/dtbs/am335x-boneblack.dtb{,.preledscape_bk}
> cp am335x-boneblack.dtb /boot/uboot/dtbs/
> modprobe uio_pruss

```

-- 
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/d/optout.

Re: [beagleboard] Location of .dtb files in 2015-03-01

[Robert Nelson]

/boot/dtbs/`uname -r/
On Mar 24, 2015 6:16 AM, "ohararp"  wrote:

> Per RobertC's help I have 2015-03-01 up and running.  I have been using
> our LEDscape repo to modify the .dtb file locations to handle the control
> of the prus to enable 48 parallel outputs for the control of leds.
> Normally, I would follow one of the procedures below, but for this new
> image it seems the .dtb file locations have changed.  Can anybody point me
> to any documentation about whree they might reside and any chnages made in
> regard to the .dtb functionality?
>
> Angstrom - RevB
>> ```
>> git clone git://github.com/Yona-Appletree/LEDscape
>> cd LEDscape
>> cp /boot/am335x-boneblack.dtb{,.preledscape_bk}
>> cp am335x-boneblack.dtb /boot/
>> modprobe uio_pruss
>> reboot
>> ```
>> Debian - RevC
>> ```
>> git clone git://github.com/Yona-Appletree/LEDscape
>> cd LEDscape
>> cp /boot/uboot/dtbs/am335x-boneblack.dtb{,.preledscape_bk}
>> cp am335x-boneblack.dtb /boot/uboot/dtbs/
>> modprobe uio_pruss
>
> ```
>
> --
> 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/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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Location of .dtb files in 2015-03-01

[ohararp]

3.8.13-bone70

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

I copied and pasted that into /boot/uboot/uEnv.txt but created that file
with nano since it didn't exist.  What should the permissions be on this
file?

><>Sent From Marty's S3<><
On Mar 24, 2015 8:44 AM, "Bill Traynor"  wrote:

> On Tue, Mar 24, 2015 at 5:29 AM, Marty  wrote:
> > dmesg | grep cape showed a lot:
> >
> > [0.560695] bone-capemgr bone_capemgr.9: Baseboard:
> > 'A335BNLT,00C0,3214BBBK8615'
> > [0.560722] bone-capemgr bone_capemgr.9:
> > compatible-baseboard=ti,beaglebone-black
> > [0.584814] bone-capemgr bone_capemgr.9: slot #0: 'BeagleBone AUDIO
> > CAPE,00A1,Beagleboardtoys,BB-BONE-AUDI-01'
> > [0.614598] bone-capemgr bone_capemgr.9: slot #1: No cape found
> > [0.651706] bone-capemgr bone_capemgr.9: slot #2: No cape found
> > [0.688814] bone-capemgr bone_capemgr.9: slot #3: No cape found
> > [0.695030] bone-capemgr bone_capemgr.9: slot #4: specific override
> > [0.695052] bone-capemgr bone_capemgr.9: bone: Using override eeprom
> data
> > at slot 4
> > [0.695067] bone-capemgr bone_capemgr.9: slot #4:
> > 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'
> > [0.695147] bone-capemgr bone_capemgr.9: slot #5: specific override
> > [0.695166] bone-capemgr bone_capemgr.9: bone: Using override eeprom
> data
> > at slot 5
> > [0.695180] bone-capemgr bone_capemgr.9: slot #5:
> > 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'
> > [0.695251] bone-capemgr bone_capemgr.9: slot #6: specific override
> > [0.695268] bone-capemgr bone_capemgr.9: bone: Using override eeprom
> data
> > at slot 6
> > [0.695282] bone-capemgr bone_capemgr.9: slot #6:
> > 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN'
> > [0.695602] bone-capemgr bone_capemgr.9: loader: before slot-0
> > BB-BONE-AUDI-01:00A1 (prio 0)
> > [0.695619] bone-capemgr bone_capemgr.9: loader: check slot-0
> > BB-BONE-AUDI-01:00A1 (prio 0)
> > [0.695694] bone-capemgr bone_capemgr.9: loader: before slot-4
> > BB-BONE-EMMC-2G:00A0 (prio 1)
> > [0.695707] bone-capemgr bone_capemgr.9: loader: check slot-4
> > BB-BONE-EMMC-2G:00A0 (prio 1)
> > [0.695777] bone-capemgr bone_capemgr.9: loader: before slot-5
> > BB-BONELT-HDMI:00A0 (prio 1)
> > [0.695789] bone-capemgr bone_capemgr.9: loader: check slot-5
> > BB-BONELT-HDMI:00A0 (prio 1)
> > [0.695822] bone-capemgr bone_capemgr.9: initialized OK.
> > [0.696283] bone-capemgr bone_capemgr.9: loader: after slot-0
> > BB-BONE-AUDI-01:00A1 (prio 0)
> > [0.696302] bone-capemgr bone_capemgr.9: slot #0: Requesting part
> > number/version based 'BB-BONE-AUDI-01-00A1.dtbo
> > [0.696318] bone-capemgr bone_capemgr.9: slot #0: Requesting firmware
> > 'BB-BONE-AUDI-01-00A1.dtbo' for board-name 'BeagleBone AUDIO CAPE',
> version
> > '00A1'
> > [0.696708] bone-capemgr bone_capemgr.9: loader: check slot-4
> > BB-BONE-EMMC-2G:00A0 (prio 1)
> > [0.698667] bone-capemgr bone_capemgr.9: loader: check slot-5
> > BB-BONELT-HDMI:00A0 (prio 1)
> > [0.700292] bone-capemgr bone_capemgr.9: loader: before slot-6
> > BB-BONELT-HDMIN:00A0 (prio 2)
> > [0.700307] bone-capemgr bone_capemgr.9: loader: check slot-6
> > BB-BONELT-HDMIN:00A0 (prio 2)
> > [0.700321] bone-capemgr bone_capemgr.9: loader: check slot-6
> > BB-BONELT-HDMIN:00A0 (prio 2)
> > [1.070829] bone-capemgr bone_capemgr.9: failed to load firmware
> > 'BB-BONE-AUDI-01-00A1.dtbo'
> > [1.079721] bone-capemgr bone_capemgr.9: loader: failed to load slot-0
> > BB-BONE-AUDI-01:00A1 (prio 0)
> > [1.089331] bone-capemgr bone_capemgr.9: loader: check slot-6
> > BB-BONELT-HDMIN:00A0 (prio 2)
> > [1.089357] bone-capemgr bone_capemgr.9: loader: check slot-5
> > BB-BONELT-HDMI:00A0 (prio 1)
> > [1.089371] bone-capemgr bone_capemgr.9: loader: after slot-5
> > BB-BONELT-HDMI:00A0 (prio 1)
> > [1.089395] bone-capemgr bone_capemgr.9: slot #5: Requesting firmware
> > 'cape-boneblack-hdmi-00A0.dtbo' for board-name 'Bone-Black-HDMI', version
> > '00A0'
> > [1.089424] bone-capemgr bone_capemgr.9: slot #5: dtbo
> > 'cape-boneblack-hdmi-00A0.dtbo' loaded; converting to live tree
> > [1.089771] bone-capemgr bone_capemgr.9: slot #5: #4 overlays
> > [1.090823] bone-capemgr bone_capemgr.9: loader: check slot-4
> > BB-BONE-EMMC-2G:00A0 (prio 1)
> > [1.090845] bone-capemgr bone_capemgr.9: loader: after slot-4
> > BB-BONE-EMMC-2G:00A0 (prio 1)
> > [1.090864] bone-capemgr bone_capemgr.9: slot #4: Requesting firmware
> > 'cape-bone-2g-emmc1.dtbo' for board-name 'Bone-LT-eMMC-2G', version
> '00A0'
> > [1.090879] bone-capemgr bone_capemgr.9: slot #4: dtbo
> > 'cape-bone-2g-emmc1.dtbo' loaded; converting to live tree
> > [1.091426] bone-capemgr bone_capemgr.9: slot #4: #2 overlays
> > [1.120725] bone-capemgr bone_capemgr.9: slot #4: Applied #2 overlays.
> > [1.120750] bone-capemgr bone_capemgr.9: loader: done slot-4
> > BB-BONE-EMMC-2G:00A0 (prio 1)
> > [1.120959] bone-capemgr bone_capemgr.9: loader: check slot-6
> > 

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

Actually, how would I know if this file is being read ok?

><>Sent From Marty's S3<><
On Mar 24, 2015 9:36 AM, "Marty"  wrote:

> I copied and pasted that into /boot/uboot/uEnv.txt but created that file
> with nano since it didn't exist.  What should the permissions be on this
> file?
>
> ><>Sent From Marty's S3<><
> On Mar 24, 2015 8:44 AM, "Bill Traynor"  wrote:
>
>> On Tue, Mar 24, 2015 at 5:29 AM, Marty  wrote:
>> > dmesg | grep cape showed a lot:
>> >
>> > [0.560695] bone-capemgr bone_capemgr.9: Baseboard:
>> > 'A335BNLT,00C0,3214BBBK8615'
>> > [0.560722] bone-capemgr bone_capemgr.9:
>> > compatible-baseboard=ti,beaglebone-black
>> > [0.584814] bone-capemgr bone_capemgr.9: slot #0: 'BeagleBone AUDIO
>> > CAPE,00A1,Beagleboardtoys,BB-BONE-AUDI-01'
>> > [0.614598] bone-capemgr bone_capemgr.9: slot #1: No cape found
>> > [0.651706] bone-capemgr bone_capemgr.9: slot #2: No cape found
>> > [0.688814] bone-capemgr bone_capemgr.9: slot #3: No cape found
>> > [0.695030] bone-capemgr bone_capemgr.9: slot #4: specific override
>> > [0.695052] bone-capemgr bone_capemgr.9: bone: Using override eeprom
>> data
>> > at slot 4
>> > [0.695067] bone-capemgr bone_capemgr.9: slot #4:
>> > 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'
>> > [0.695147] bone-capemgr bone_capemgr.9: slot #5: specific override
>> > [0.695166] bone-capemgr bone_capemgr.9: bone: Using override eeprom
>> data
>> > at slot 5
>> > [0.695180] bone-capemgr bone_capemgr.9: slot #5:
>> > 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'
>> > [0.695251] bone-capemgr bone_capemgr.9: slot #6: specific override
>> > [0.695268] bone-capemgr bone_capemgr.9: bone: Using override eeprom
>> data
>> > at slot 6
>> > [0.695282] bone-capemgr bone_capemgr.9: slot #6:
>> > 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN'
>> > [0.695602] bone-capemgr bone_capemgr.9: loader: before slot-0
>> > BB-BONE-AUDI-01:00A1 (prio 0)
>> > [0.695619] bone-capemgr bone_capemgr.9: loader: check slot-0
>> > BB-BONE-AUDI-01:00A1 (prio 0)
>> > [0.695694] bone-capemgr bone_capemgr.9: loader: before slot-4
>> > BB-BONE-EMMC-2G:00A0 (prio 1)
>> > [0.695707] bone-capemgr bone_capemgr.9: loader: check slot-4
>> > BB-BONE-EMMC-2G:00A0 (prio 1)
>> > [0.695777] bone-capemgr bone_capemgr.9: loader: before slot-5
>> > BB-BONELT-HDMI:00A0 (prio 1)
>> > [0.695789] bone-capemgr bone_capemgr.9: loader: check slot-5
>> > BB-BONELT-HDMI:00A0 (prio 1)
>> > [0.695822] bone-capemgr bone_capemgr.9: initialized OK.
>> > [0.696283] bone-capemgr bone_capemgr.9: loader: after slot-0
>> > BB-BONE-AUDI-01:00A1 (prio 0)
>> > [0.696302] bone-capemgr bone_capemgr.9: slot #0: Requesting part
>> > number/version based 'BB-BONE-AUDI-01-00A1.dtbo
>> > [0.696318] bone-capemgr bone_capemgr.9: slot #0: Requesting firmware
>> > 'BB-BONE-AUDI-01-00A1.dtbo' for board-name 'BeagleBone AUDIO CAPE',
>> version
>> > '00A1'
>> > [0.696708] bone-capemgr bone_capemgr.9: loader: check slot-4
>> > BB-BONE-EMMC-2G:00A0 (prio 1)
>> > [0.698667] bone-capemgr bone_capemgr.9: loader: check slot-5
>> > BB-BONELT-HDMI:00A0 (prio 1)
>> > [0.700292] bone-capemgr bone_capemgr.9: loader: before slot-6
>> > BB-BONELT-HDMIN:00A0 (prio 2)
>> > [0.700307] bone-capemgr bone_capemgr.9: loader: check slot-6
>> > BB-BONELT-HDMIN:00A0 (prio 2)
>> > [0.700321] bone-capemgr bone_capemgr.9: loader: check slot-6
>> > BB-BONELT-HDMIN:00A0 (prio 2)
>> > [1.070829] bone-capemgr bone_capemgr.9: failed to load firmware
>> > 'BB-BONE-AUDI-01-00A1.dtbo'
>> > [1.079721] bone-capemgr bone_capemgr.9: loader: failed to load
>> slot-0
>> > BB-BONE-AUDI-01:00A1 (prio 0)
>> > [1.089331] bone-capemgr bone_capemgr.9: loader: check slot-6
>> > BB-BONELT-HDMIN:00A0 (prio 2)
>> > [1.089357] bone-capemgr bone_capemgr.9: loader: check slot-5
>> > BB-BONELT-HDMI:00A0 (prio 1)
>> > [1.089371] bone-capemgr bone_capemgr.9: loader: after slot-5
>> > BB-BONELT-HDMI:00A0 (prio 1)
>> > [1.089395] bone-capemgr bone_capemgr.9: slot #5: Requesting firmware
>> > 'cape-boneblack-hdmi-00A0.dtbo' for board-name 'Bone-Black-HDMI',
>> version
>> > '00A0'
>> > [1.089424] bone-capemgr bone_capemgr.9: slot #5: dtbo
>> > 'cape-boneblack-hdmi-00A0.dtbo' loaded; converting to live tree
>> > [1.089771] bone-capemgr bone_capemgr.9: slot #5: #4 overlays
>> > [1.090823] bone-capemgr bone_capemgr.9: loader: check slot-4
>> > BB-BONE-EMMC-2G:00A0 (prio 1)
>> > [1.090845] bone-capemgr bone_capemgr.9: loader: after slot-4
>> > BB-BONE-EMMC-2G:00A0 (prio 1)
>> > [1.090864] bone-capemgr bone_capemgr.9: slot #4: Requesting firmware
>> > 'cape-bone-2g-emmc1.dtbo' for board-name 'Bone-LT-eMMC-2G', version
>> '00A0'
>> > [1.090879] bone-capemgr bone_capemgr.9: slot #4: dtbo
>> > 'cape-bone-2g-emmc1.dtbo' loaded; converting to live tree
>> > [1.091426] bone-capemgr bone_capemgr.9: slot #4: #2 overlays
>> > [1.120725] 

Re: [beagleboard] Location of .dtb files in 2015-03-01

[ohararp]

Got it - ./boot/dtbs/3.8.13-bone70/am335x-boneblack.dtb !  Thanks!

-- 
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/d/optout.

[beagleboard] Re: Reading from ADC hangs

[matthew . mcneely]

Hi Matti,

Would you please provide details on which dts entries (or maybe a link to 
the entire dts file!) you're specifying in order to get ADC working with 
3.18?

Thanks!

On Monday, March 2, 2015 at 1:04:39 PM UTC-5, mala...@elisanet.fi wrote:
>
>
>
> On Thursday, February 26, 2015 at 5:18:51 PM UTC+2, dajia...@gmail.com 
> wrote:
>>
>> Hi,
>>
>> How come in my system, there is no /sys/bus/iio/devices/iio:device0?
>> Under /sys/bus/iio/devices/, there is only one file iio_sysfs_trigger, 
>> which is a symbolic link to some other directory.
>> Is there any configuration I need to do?
>> I am using the latest BB black Rev C by Element14. It is OS is 
>> 3.8.13-bone47.
>>
>> Thx.
>>
>
> Hi,
>
> You need to enable the ADC either by enabling the correct "cape" with 
> capemgr (only in kernel 3.8.*, see e.g. 
> http://hipstercircuits.com/reading-analog-adc-values-on-beaglebone-black/), 
> or by enabling it in the .dts-file (later kernels, such as the 3.18.4 which 
> I'm using).
>
> Matti
>  
>
>>
>> On Wednesday, February 25, 2015 at 8:36:18 PM UTC+8, mala...@elisanet.fi 
>> wrote:
>>>
>>> Thanks for the suggestion. I'll keep that in mind if I need higher 
>>> sampling rates. However, I did find a way to read ADC through IIO so that 
>>> it doesn't hang.
>>>
>>> First set up the channels and the buffer through sysfs:
>>>
>>> echo 1 > /sys/bus/iio/devices/iio\:device0/scan_elements/in_voltage0_en
>>> echo 256 > /sys/bus/iio/devices/iio\:device0/buffer/length
>>> echo 1 > /sys/bus/iio/devices/iio\:device0/buffer/enable
>>>
>>> and then read from /dev/iio:device0. This way I can achieve about 8 kHz 
>>> sampling rate with a single channel, 4 kHz with two channels and down to 
>>> ~300 Hz with all eight channels.
>>>
>>

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Robert Nelson]

The march image its located at /boot/uEnv.txt

On Mar 24, 2015 6:41 AM, "Marty"  wrote:
>
> I copied and pasted that into /boot/uboot/uEnv.txt but created that file
with nano since it didn't exist.  What should the permissions be on this
file?
>
> ><>Sent From Marty's S3<><
>
> On Mar 24, 2015 8:44 AM, "Bill Traynor"  wrote:
>>
>> On Tue, Mar 24, 2015 at 5:29 AM, Marty  wrote:
>> > dmesg | grep cape showed a lot:
>> >
>> > [0.560695] bone-capemgr bone_capemgr.9: Baseboard:
>> > 'A335BNLT,00C0,3214BBBK8615'
>> > [0.560722] bone-capemgr bone_capemgr.9:
>> > compatible-baseboard=ti,beaglebone-black
>> > [0.584814] bone-capemgr bone_capemgr.9: slot #0: 'BeagleBone AUDIO
>> > CAPE,00A1,Beagleboardtoys,BB-BONE-AUDI-01'
>> > [0.614598] bone-capemgr bone_capemgr.9: slot #1: No cape found
>> > [0.651706] bone-capemgr bone_capemgr.9: slot #2: No cape found
>> > [0.688814] bone-capemgr bone_capemgr.9: slot #3: No cape found
>> > [0.695030] bone-capemgr bone_capemgr.9: slot #4: specific override
>> > [0.695052] bone-capemgr bone_capemgr.9: bone: Using override
eeprom data
>> > at slot 4
>> > [0.695067] bone-capemgr bone_capemgr.9: slot #4:
>> > 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'
>> > [0.695147] bone-capemgr bone_capemgr.9: slot #5: specific override
>> > [0.695166] bone-capemgr bone_capemgr.9: bone: Using override
eeprom data
>> > at slot 5
>> > [0.695180] bone-capemgr bone_capemgr.9: slot #5:
>> > 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'
>> > [0.695251] bone-capemgr bone_capemgr.9: slot #6: specific override
>> > [0.695268] bone-capemgr bone_capemgr.9: bone: Using override
eeprom data
>> > at slot 6
>> > [0.695282] bone-capemgr bone_capemgr.9: slot #6:
>> > 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN'
>> > [0.695602] bone-capemgr bone_capemgr.9: loader: before slot-0
>> > BB-BONE-AUDI-01:00A1 (prio 0)
>> > [0.695619] bone-capemgr bone_capemgr.9: loader: check slot-0
>> > BB-BONE-AUDI-01:00A1 (prio 0)
>> > [0.695694] bone-capemgr bone_capemgr.9: loader: before slot-4
>> > BB-BONE-EMMC-2G:00A0 (prio 1)
>> > [0.695707] bone-capemgr bone_capemgr.9: loader: check slot-4
>> > BB-BONE-EMMC-2G:00A0 (prio 1)
>> > [0.695777] bone-capemgr bone_capemgr.9: loader: before slot-5
>> > BB-BONELT-HDMI:00A0 (prio 1)
>> > [0.695789] bone-capemgr bone_capemgr.9: loader: check slot-5
>> > BB-BONELT-HDMI:00A0 (prio 1)
>> > [0.695822] bone-capemgr bone_capemgr.9: initialized OK.
>> > [0.696283] bone-capemgr bone_capemgr.9: loader: after slot-0
>> > BB-BONE-AUDI-01:00A1 (prio 0)
>> > [0.696302] bone-capemgr bone_capemgr.9: slot #0: Requesting part
>> > number/version based 'BB-BONE-AUDI-01-00A1.dtbo
>> > [0.696318] bone-capemgr bone_capemgr.9: slot #0: Requesting
firmware
>> > 'BB-BONE-AUDI-01-00A1.dtbo' for board-name 'BeagleBone AUDIO CAPE',
version
>> > '00A1'
>> > [0.696708] bone-capemgr bone_capemgr.9: loader: check slot-4
>> > BB-BONE-EMMC-2G:00A0 (prio 1)
>> > [0.698667] bone-capemgr bone_capemgr.9: loader: check slot-5
>> > BB-BONELT-HDMI:00A0 (prio 1)
>> > [0.700292] bone-capemgr bone_capemgr.9: loader: before slot-6
>> > BB-BONELT-HDMIN:00A0 (prio 2)
>> > [0.700307] bone-capemgr bone_capemgr.9: loader: check slot-6
>> > BB-BONELT-HDMIN:00A0 (prio 2)
>> > [0.700321] bone-capemgr bone_capemgr.9: loader: check slot-6
>> > BB-BONELT-HDMIN:00A0 (prio 2)
>> > [1.070829] bone-capemgr bone_capemgr.9: failed to load firmware
>> > 'BB-BONE-AUDI-01-00A1.dtbo'
>> > [1.079721] bone-capemgr bone_capemgr.9: loader: failed to load
slot-0
>> > BB-BONE-AUDI-01:00A1 (prio 0)
>> > [1.089331] bone-capemgr bone_capemgr.9: loader: check slot-6
>> > BB-BONELT-HDMIN:00A0 (prio 2)
>> > [1.089357] bone-capemgr bone_capemgr.9: loader: check slot-5
>> > BB-BONELT-HDMI:00A0 (prio 1)
>> > [1.089371] bone-capemgr bone_capemgr.9: loader: after slot-5
>> > BB-BONELT-HDMI:00A0 (prio 1)
>> > [1.089395] bone-capemgr bone_capemgr.9: slot #5: Requesting
firmware
>> > 'cape-boneblack-hdmi-00A0.dtbo' for board-name 'Bone-Black-HDMI',
version
>> > '00A0'
>> > [1.089424] bone-capemgr bone_capemgr.9: slot #5: dtbo
>> > 'cape-boneblack-hdmi-00A0.dtbo' loaded; converting to live tree
>> > [1.089771] bone-capemgr bone_capemgr.9: slot #5: #4 overlays
>> > [1.090823] bone-capemgr bone_capemgr.9: loader: check slot-4
>> > BB-BONE-EMMC-2G:00A0 (prio 1)
>> > [1.090845] bone-capemgr bone_capemgr.9: loader: after slot-4
>> > BB-BONE-EMMC-2G:00A0 (prio 1)
>> > [1.090864] bone-capemgr bone_capemgr.9: slot #4: Requesting
firmware
>> > 'cape-bone-2g-emmc1.dtbo' for board-name 'Bone-LT-eMMC-2G', version
'00A0'
>> > [1.090879] bone-capemgr bone_capemgr.9: slot #4: dtbo
>> > 'cape-bone-2g-emmc1.dtbo' loaded; converting to live tree
>> > [1.091426] bone-capemgr bone_capemgr.9: slot #4: #2 overlays
>> > [1.120725] bone-capemgr bone_capemgr.9: slot #4: Applied #2
overlays.
>

Re: [beagleboard] Re: Soldering JTAG connector with Element14(Embest) version BBB failed

[Harvey White]

On Tue, 24 Mar 2015 00:03:54 -0700 (PDT), you wrote:

>Hi Harvery, 
>
>700 dgree can melt lead-free solder *directly* very well -- that's how I 
>adhere a layer of solder to connector pins. Then I put connector on top of 
>P2 on the board and heat the pins for making the solder melt and connect 
>joint just like the video. 

This is called (or was) "sweat soldering"  it does work, but may not
be the best at times.  No problem though.

>But the solder between pins and P2 won't melt 

What may be happening is that the solder on P2 is protected by a layer
of something, either oxide, or solder mask, or the like.  I'd take a
small xacto knife or equivalent, and gently scratch one of the pads to
clean the surface.  You want to stay in the plating area (assuming
that this is solder plated.  Did you use flux?  Liquid flux is
generally very useful in this kind of situation.  You should be able
to melt the solder and let it flow onto the board land (the contact
area), without a pin there.  If the solder just beads up, then you're
not getting any heat transfer to the pad, or the pad is protected.  

I've had badly oxidized pads not take solder, and some plating on
boards will not accept solder (nickel, if I remember it).  In that
case, some very gentle abrasion of the plating may expose the copper.
This is a crude solution, though.  You could also try cleaning the
pads with a pencil eraser.  It's quite abrasive and should not be used
for edge contacts (it will remove gold plating very easily).

>and none of it will adhere to the P2 even I heated 4-6 seconds in 700 
>degree. Note that I cleaned the solder iron with tip tinner and brass 
>sponge before this step. 

Generally, what you do is avoid the tip tinner unless you're losing
the tinning on the tip (solder won't adhere to the tip itself).  I
normally don't use it or need it.  Then you add solder, just a bit, to
the tip, use the sponge to clean it (and any oxides) off, then solder.
You can add a tiny bit of solder to the tip, which forms a tiny drop
there, and when put to a joint, will help heat transfer.

The steps are generally 1) clean the tip, 2) do the joint, 3) put the
iron back (it doesn't need to be cleaned at this point, the excess
solder actually tends to protect the tip).

>
>Another way is just like you said (hope my understanding is correct) to 
>heat some solder and let it flow to the pin and wet the joint. I tried. But 
>the solder flow won't adhere to the P2 but just accumulated on the pin till 
>bridge with adjacent pin. 

Then there's something there that the solder won't wet.  There might
be a coating over the connector.
>
>Do you have any comment on this situation? 
>
Just did, it's an odd situation, since most of the boards are
manufactured to enable you to solder to selected areas, and the pads
for such a connector site would be ready to solder to.

Mine's a circuitco board, so I can't help with trying.  

If you have some leaded solder, I'd try that.  I'd also get a tube of
flux, you want the Kester RMA flux, which would be available at places
like Mouser or Digikey or Avnet (not sure about Jameco).  This flux is
quite helpful for doing surface mount soldering (I do that a lot...).

Harvey

>Thank you so much!
>
>On Monday, March 23, 2015 at 8:37:46 PM UTC-7, Harvey White wrote:
>>
>> On Mon, 23 Mar 2015 19:46:19 -0700 (PDT), you wrote: 
>>
>> >Thank you Tom and Harvey! I'll try again with higher temperature (800 or 
>> >even more higher till it melts) as well as adopt Harvey's suggestions. 
>> >Result will be reported in this thread. 
>>
>> Ah, no, more temperature is not always what's needed.   
>>
>> Too cold and it never melts.  Too hot and it damages the board and 
>> what you're soldering.  For leaded solder, 600 degrees is fine for 
>> small sensitive parts, 700 degrees for standard parts, and you almost 
>> never need 800 degrees. 
>>
>> Try a few joints with the solder and just solder a few pieces of wire 
>> together, say 22 gauge or so.  That gives you the practice you may 
>> need for lead free solder (behaves differently). 
>>
>>
>> > 
>> >I used lead-free .022 in 700 degree. Temperature is one of a few factors 
>> I 
>> >haven't adjusted in those attempts for not damaging the board. 
>> > 
>> 800 degrees is a bit too hot.  There's a bit of a touch to it, as to 
>> how to solder and how not to.  You want the solder to "flow" and to 
>> "wet" the joint as if it were water. 
>>
>> I'd see what the melting point of your particular lead free solder is, 
>> and then see what the recommended iron temperature is as well. 
>>
>> Harvey 
>>
>> >Also I've found CircuitCo version in Jameco Electronics. 
>> > 
>> >On Monday, March 23, 2015 at 5:25:56 PM UTC-7, Harvey White wrote: 
>> >> 
>> >> On Mon, 23 Mar 2015 16:56:58 -0700 (PDT), you wrote: 
>> >> 
>> >> > 
>> >> >> 
>> >> >> 
>> >> >>   
>> >> >> 
>> >> > 
>> >> >I just checked my settings. I have my iron set to 430C / 806 F and 
>> >> haven't 
>> >> >touched it since soldering that J

Re: [beagleboard] Re: Soldering JTAG connector with Element14(Embest) version BBB failed

[Gerald Coley]

Lead free. High temp neede to melt it.

Gerald

On Tue, Mar 24, 2015 at 9:23 AM, Harvey White 
wrote:

> On Tue, 24 Mar 2015 00:03:54 -0700 (PDT), you wrote:
>
> >Hi Harvery,
> >
> >700 dgree can melt lead-free solder *directly* very well -- that's how I
> >adhere a layer of solder to connector pins. Then I put connector on top of
> >P2 on the board and heat the pins for making the solder melt and connect
> >joint just like the video.
>
> This is called (or was) "sweat soldering"  it does work, but may not
> be the best at times.  No problem though.
>
> >But the solder between pins and P2 won't melt
>
> What may be happening is that the solder on P2 is protected by a layer
> of something, either oxide, or solder mask, or the like.  I'd take a
> small xacto knife or equivalent, and gently scratch one of the pads to
> clean the surface.  You want to stay in the plating area (assuming
> that this is solder plated.  Did you use flux?  Liquid flux is
> generally very useful in this kind of situation.  You should be able
> to melt the solder and let it flow onto the board land (the contact
> area), without a pin there.  If the solder just beads up, then you're
> not getting any heat transfer to the pad, or the pad is protected.
>
> I've had badly oxidized pads not take solder, and some plating on
> boards will not accept solder (nickel, if I remember it).  In that
> case, some very gentle abrasion of the plating may expose the copper.
> This is a crude solution, though.  You could also try cleaning the
> pads with a pencil eraser.  It's quite abrasive and should not be used
> for edge contacts (it will remove gold plating very easily).
>
> >and none of it will adhere to the P2 even I heated 4-6 seconds in 700
> >degree. Note that I cleaned the solder iron with tip tinner and brass
> >sponge before this step.
>
> Generally, what you do is avoid the tip tinner unless you're losing
> the tinning on the tip (solder won't adhere to the tip itself).  I
> normally don't use it or need it.  Then you add solder, just a bit, to
> the tip, use the sponge to clean it (and any oxides) off, then solder.
> You can add a tiny bit of solder to the tip, which forms a tiny drop
> there, and when put to a joint, will help heat transfer.
>
> The steps are generally 1) clean the tip, 2) do the joint, 3) put the
> iron back (it doesn't need to be cleaned at this point, the excess
> solder actually tends to protect the tip).
>
> >
> >Another way is just like you said (hope my understanding is correct) to
> >heat some solder and let it flow to the pin and wet the joint. I tried.
> But
> >the solder flow won't adhere to the P2 but just accumulated on the pin
> till
> >bridge with adjacent pin.
>
> Then there's something there that the solder won't wet.  There might
> be a coating over the connector.
> >
> >Do you have any comment on this situation?
> >
> Just did, it's an odd situation, since most of the boards are
> manufactured to enable you to solder to selected areas, and the pads
> for such a connector site would be ready to solder to.
>
> Mine's a circuitco board, so I can't help with trying.
>
> If you have some leaded solder, I'd try that.  I'd also get a tube of
> flux, you want the Kester RMA flux, which would be available at places
> like Mouser or Digikey or Avnet (not sure about Jameco).  This flux is
> quite helpful for doing surface mount soldering (I do that a lot...).
>
> Harvey
>
> >Thank you so much!
> >
> >On Monday, March 23, 2015 at 8:37:46 PM UTC-7, Harvey White wrote:
> >>
> >> On Mon, 23 Mar 2015 19:46:19 -0700 (PDT), you wrote:
> >>
> >> >Thank you Tom and Harvey! I'll try again with higher temperature (800
> or
> >> >even more higher till it melts) as well as adopt Harvey's suggestions.
> >> >Result will be reported in this thread.
> >>
> >> Ah, no, more temperature is not always what's needed.
> >>
> >> Too cold and it never melts.  Too hot and it damages the board and
> >> what you're soldering.  For leaded solder, 600 degrees is fine for
> >> small sensitive parts, 700 degrees for standard parts, and you almost
> >> never need 800 degrees.
> >>
> >> Try a few joints with the solder and just solder a few pieces of wire
> >> together, say 22 gauge or so.  That gives you the practice you may
> >> need for lead free solder (behaves differently).
> >>
> >>
> >> >
> >> >I used lead-free .022 in 700 degree. Temperature is one of a few
> factors
> >> I
> >> >haven't adjusted in those attempts for not damaging the board.
> >> >
> >> 800 degrees is a bit too hot.  There's a bit of a touch to it, as to
> >> how to solder and how not to.  You want the solder to "flow" and to
> >> "wet" the joint as if it were water.
> >>
> >> I'd see what the melting point of your particular lead free solder is,
> >> and then see what the recommended iron temperature is as well.
> >>
> >> Harvey
> >>
> >> >Also I've found CircuitCo version in Jameco Electronics.
> >> >
> >> >On Monday, March 23, 2015 at 5:25:56 PM UTC-7, Harvey White wr

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

Oh, so the file should already exist? What do u mean by the march
image...the image I flashed?

><>Sent From Marty's S3<><
On Mar 24, 2015 10:24 AM, "Robert Nelson"  wrote:

> The march image its located at /boot/uEnv.txt
>
> On Mar 24, 2015 6:41 AM, "Marty"  wrote:
> >
> > I copied and pasted that into /boot/uboot/uEnv.txt but created that file
> with nano since it didn't exist.  What should the permissions be on this
> file?
> >
> > ><>Sent From Marty's S3<><
> >
> > On Mar 24, 2015 8:44 AM, "Bill Traynor"  wrote:
> >>
> >> On Tue, Mar 24, 2015 at 5:29 AM, Marty  wrote:
> >> > dmesg | grep cape showed a lot:
> >> >
> >> > [0.560695] bone-capemgr bone_capemgr.9: Baseboard:
> >> > 'A335BNLT,00C0,3214BBBK8615'
> >> > [0.560722] bone-capemgr bone_capemgr.9:
> >> > compatible-baseboard=ti,beaglebone-black
> >> > [0.584814] bone-capemgr bone_capemgr.9: slot #0: 'BeagleBone AUDIO
> >> > CAPE,00A1,Beagleboardtoys,BB-BONE-AUDI-01'
> >> > [0.614598] bone-capemgr bone_capemgr.9: slot #1: No cape found
> >> > [0.651706] bone-capemgr bone_capemgr.9: slot #2: No cape found
> >> > [0.688814] bone-capemgr bone_capemgr.9: slot #3: No cape found
> >> > [0.695030] bone-capemgr bone_capemgr.9: slot #4: specific override
> >> > [0.695052] bone-capemgr bone_capemgr.9: bone: Using override
> eeprom data
> >> > at slot 4
> >> > [0.695067] bone-capemgr bone_capemgr.9: slot #4:
> >> > 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'
> >> > [0.695147] bone-capemgr bone_capemgr.9: slot #5: specific override
> >> > [0.695166] bone-capemgr bone_capemgr.9: bone: Using override
> eeprom data
> >> > at slot 5
> >> > [0.695180] bone-capemgr bone_capemgr.9: slot #5:
> >> > 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'
> >> > [0.695251] bone-capemgr bone_capemgr.9: slot #6: specific override
> >> > [0.695268] bone-capemgr bone_capemgr.9: bone: Using override
> eeprom data
> >> > at slot 6
> >> > [0.695282] bone-capemgr bone_capemgr.9: slot #6:
> >> > 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN'
> >> > [0.695602] bone-capemgr bone_capemgr.9: loader: before slot-0
> >> > BB-BONE-AUDI-01:00A1 (prio 0)
> >> > [0.695619] bone-capemgr bone_capemgr.9: loader: check slot-0
> >> > BB-BONE-AUDI-01:00A1 (prio 0)
> >> > [0.695694] bone-capemgr bone_capemgr.9: loader: before slot-4
> >> > BB-BONE-EMMC-2G:00A0 (prio 1)
> >> > [0.695707] bone-capemgr bone_capemgr.9: loader: check slot-4
> >> > BB-BONE-EMMC-2G:00A0 (prio 1)
> >> > [0.695777] bone-capemgr bone_capemgr.9: loader: before slot-5
> >> > BB-BONELT-HDMI:00A0 (prio 1)
> >> > [0.695789] bone-capemgr bone_capemgr.9: loader: check slot-5
> >> > BB-BONELT-HDMI:00A0 (prio 1)
> >> > [0.695822] bone-capemgr bone_capemgr.9: initialized OK.
> >> > [0.696283] bone-capemgr bone_capemgr.9: loader: after slot-0
> >> > BB-BONE-AUDI-01:00A1 (prio 0)
> >> > [0.696302] bone-capemgr bone_capemgr.9: slot #0: Requesting part
> >> > number/version based 'BB-BONE-AUDI-01-00A1.dtbo
> >> > [0.696318] bone-capemgr bone_capemgr.9: slot #0: Requesting
> firmware
> >> > 'BB-BONE-AUDI-01-00A1.dtbo' for board-name 'BeagleBone AUDIO CAPE',
> version
> >> > '00A1'
> >> > [0.696708] bone-capemgr bone_capemgr.9: loader: check slot-4
> >> > BB-BONE-EMMC-2G:00A0 (prio 1)
> >> > [0.698667] bone-capemgr bone_capemgr.9: loader: check slot-5
> >> > BB-BONELT-HDMI:00A0 (prio 1)
> >> > [0.700292] bone-capemgr bone_capemgr.9: loader: before slot-6
> >> > BB-BONELT-HDMIN:00A0 (prio 2)
> >> > [0.700307] bone-capemgr bone_capemgr.9: loader: check slot-6
> >> > BB-BONELT-HDMIN:00A0 (prio 2)
> >> > [0.700321] bone-capemgr bone_capemgr.9: loader: check slot-6
> >> > BB-BONELT-HDMIN:00A0 (prio 2)
> >> > [1.070829] bone-capemgr bone_capemgr.9: failed to load firmware
> >> > 'BB-BONE-AUDI-01-00A1.dtbo'
> >> > [1.079721] bone-capemgr bone_capemgr.9: loader: failed to load
> slot-0
> >> > BB-BONE-AUDI-01:00A1 (prio 0)
> >> > [1.089331] bone-capemgr bone_capemgr.9: loader: check slot-6
> >> > BB-BONELT-HDMIN:00A0 (prio 2)
> >> > [1.089357] bone-capemgr bone_capemgr.9: loader: check slot-5
> >> > BB-BONELT-HDMI:00A0 (prio 1)
> >> > [1.089371] bone-capemgr bone_capemgr.9: loader: after slot-5
> >> > BB-BONELT-HDMI:00A0 (prio 1)
> >> > [1.089395] bone-capemgr bone_capemgr.9: slot #5: Requesting
> firmware
> >> > 'cape-boneblack-hdmi-00A0.dtbo' for board-name 'Bone-Black-HDMI',
> version
> >> > '00A0'
> >> > [1.089424] bone-capemgr bone_capemgr.9: slot #5: dtbo
> >> > 'cape-boneblack-hdmi-00A0.dtbo' loaded; converting to live tree
> >> > [1.089771] bone-capemgr bone_capemgr.9: slot #5: #4 overlays
> >> > [1.090823] bone-capemgr bone_capemgr.9: loader: check slot-4
> >> > BB-BONE-EMMC-2G:00A0 (prio 1)
> >> > [1.090845] bone-capemgr bone_capemgr.9: loader: after slot-4
> >> > BB-BONE-EMMC-2G:00A0 (prio 1)
> >> > [1.090864] bone-capemgr bone_capemgr.9: slot #4: Request

Re: [beagleboard] Re: How to use USB headset with Beagle Board

[Harvey White]

On Tue, 24 Mar 2015 12:33:49 +0530, you wrote:

>How to use the switch/push buttton to record voice in beaglebone? Is it by
>using gpio programming by setting the pin as input?

You'd use GPIO programming and set the pin as an input.  Pressing it
can start whatever part of your program you want.  

It seems as if you need to look a bit more deeply into basic
microprocessor functions if you're asking this kind of question.  The
program to record could be initiated by almost anything, a remote
command, a pushbutton, or even a sound.

Harvey

>
>On Fri, Mar 13, 2015 at 11:07 AM, Harvey White 
>wrote:
>
>> On Fri, 13 Mar 2015 10:34:08 +0530, you wrote:
>>
>> >Does USB headset mic amplifies input speech signal?
>>
>> Probably, but you'd have to look at the specifications to be sure. The
>> input is voice, the output is a digital data stream.  The microphone
>> puts out millivolts, the USB data stream can be scaled to anything.
>>
>> Check the specifications, or borrow one and try it.
>>
>> Harvey
>>
>>
>> >
>> >On Thu, Mar 12, 2015 at 10:37 AM, Harvey White 
>> >wrote:
>> >
>> >> On Wed, 11 Mar 2015 21:49:00 -0700 (PDT), you wrote:
>> >>
>> >> >Will USB headset with mic work for audio application that records sound
>> >> and
>> >> >playback on beaglebone with quality?Here is there is no need for
>> separate
>> >> >pre- amplifier or circuit that requires biasing mic voltage?
>> >>
>> >> The hardware can't tell the difference between being plugged into the
>> >> BBB and a standard computer.  The microphone will be properly biased.
>> >>
>> >> You will have to have a driver to communicate with the USB interface
>> >> in the headset.
>> >>
>> >> Harvey
>> >>
>> >> >
>> >> >
>> >> >On Monday, February 24, 2014 at 5:00:39 AM UTC+5:30, Kenji Nakasone
>> wrote:
>> >> >>
>> >> >> Same problem here with beatblock bluetooth speaker. I pair the
>> speaker
>> >> but
>> >> >> can listen to music on it.
>> >> >>
>> >> >> I tried creating .asoundrc and asound.conf
>> >> >>
>> >> >> I run:
>> >> >> mplayer -ao alsa:device=btheadset  song.mp3
>> >> >>
>> >> >> but I get this:
>> >> >>
>> >> >> [AO_ALSA] alsa-lib: dlmisc.c:236:(snd1_dlobj_cache_get) Cannot open
>> >> shared
>> >> >> library /usr/lib/alsa-lib/libasound_module_pcm_bluetooth.so
>> >> >> [AO_ALSA] Playback open error: No such device or address
>> >> >> Failed to initialize audio driver 'alsa:device=btheadset'
>> >> >> Could not open/initialize audio device -> no sound.
>> >> >> Audio: no sound
>> >> >> Video: no video
>> >> >>
>> >> >> any help?
>> >> >>
>> >> >> On Wednesday, February 25, 2009 3:43:45 AM UTC-2, vijay...@gmail.com
>> >> >> wrote:
>> >> >>>
>> >> >>> Hi,
>> >> >>>   I am trying to use USB headset with Beagle Board.I have
>> >> >>> connected USB headset to beagle board through USB hub.I am not able
>> to
>> >> >>> listen audio through USB headset. But at the same time i can hear
>> the
>> >> >>> audio through normal headset (Through sterio audio output jack).I
>> can
>> >> >>> see USB headset is getting detected on Beagle Board.
>> >> >>>   Please help me in this case. First thing is it possible to use
>> >> >>> USB headset with Beagle Board? Do i need to modify any configuration
>> >> >>> file Or Some Kernel Configuration? Or what other changes i need to
>> do
>> >> >>> for using the USB headset with Beagle Board.It will be great help if
>> >> >>> you provide the solution.
>> >> >>>
>> >> >>> Thanks,
>> >> >>> Vijay Swami
>> >> >>>
>> >> >>
>> >>
>> >> --
>> >> For more options, visit http://beagleboard.org/discuss
>> >> ---
>> >> You received this message because you are subscribed to a topic in the
>> >> Google Groups "BeagleBoard" group.
>> >> To unsubscribe from this topic, visit
>> >> https://groups.google.com/d/topic/beagleboard/f8k7_s5Tjqo/unsubscribe.
>> >> To unsubscribe from this group and all its topics, send an email to
>> >> beagleboard+unsubscr...@googlegroups.com.
>> >> 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 a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/f8k7_s5Tjqo/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB not booting if connected to Motor Controller MD10C

[Khalil Estell]

Hello All,

I have become stumped by this issue. I am trying to boot up a BBB when 
connected to the inputs of six MD10C motor controllers 
. For 
the most part, it works fine if the BBB has been boot up before *connecting* 
the 
direction and pwm pins to the beagle bone black. If I attempt to power the 
BBB with them connected, the power light indicator will come on, but the 
status lights will not. The configuration of the circuit is this: I have a 
custom shield that I made that breaks out the pwm pins and gpio pins I need 
for the controller. The controllers are powered by an 24V battery power 
supply rated at 15A output. The BBB is powered by 5V regulator rated at 6A.

Here is what I have attempted thus far:


   1. Turn on battery, which is powers the 5V regulator and the motor 
   controllers, which turns everything on at the "same" time. BBB does not 
   boot up.
   2. Remove cape (with all the connections still on), turn on battery, BBB 
   boots, once the light indicators are no longer all a solid blue, I replace 
   the cape, and everything works, BBB continues to boot up.
   3. If I remove all but one input to one controller and power up the 
   battery, BBB sometimes boots.
   4. I have attempted to add 1k and 10k resistors between the connections 
   which allowed the BBB sometimes to boot with two motors inputs connected.
   5. *Wierd one:* I decided to remove the power from two controller 
   (except for ground), and connect them to the BBB. Still it did not boot. 
   The motor controllers did not get powered at all!
   6. *Wierder one: I removed all of the power wires from from both 
   controllers and still the BBB will not boot up if connected to the motor 
   controller inputs.*

Does anyone have idea what is happening here? One of my solutions was to 
use a relay to turn on the power to the motor controllers after the BBB has 
fully booted up or add a second switch that turns on the motor controllers 
after the BBB has fully booted, but that plan can not work if merely 
pluggin in the inputs causes this problem.

I do know about this issue: DO NOT APPLY VOLTAGE TO ANY I/O PIN WHEN POWER 
IS NOT SUPPLIED TO THE BOARD. IT WILL DAMAGE THE PROCESSOR AND VOID THE 
WARRANTY. NO PINS ARE TO BE DRIVEN UNTIL AFTER THE SYS_RESET LINE GOES 
HIGH. But in this case, there is no power coming from the input pins.

*Last note: I measured the resistance from the dir pin and the pwm pin to 
ground and they come up 16k and 20k respectively.  * 

I appreciate any suggestions or help on this matter.

-- 
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/d/optout.

[beagleboard] Re: BBB not booting if connected to Motor Controller MD10C

[Graham]

The Sitara uses a field of pull-up and pull-down resistors to tell it how 
to boot.
If you put any LOAD on these pins, and your I/O does NOT have to be 
powered, (which would make 
things even worse), you will give it the wrong boot commands, and the BBB 
won't boot.

Go read the section in the System Reference Manual on Boot Configuration, 
and
the section on Pin Usage Considerations.


--- Graham

==

On Tuesday, March 24, 2015 at 9:42:12 AM UTC-5, Khalil Estell wrote:
>
> Hello All,
>
> I have become stumped by this issue. I am trying to boot up a BBB when 
> connected to the inputs of six MD10C motor controllers 
> . For 
> the most part, it works fine if the BBB has been boot up before 
> *connecting* the direction and pwm pins to the beagle bone black. If I 
> attempt to power the BBB with them connected, the power light indicator 
> will come on, but the status lights will not. The configuration of the 
> circuit is this: I have a custom shield that I made that breaks out the pwm 
> pins and gpio pins I need for the controller. The controllers are powered 
> by an 24V battery power supply rated at 15A output. The BBB is powered by 
> 5V regulator rated at 6A.
>
> Here is what I have attempted thus far:
>
>
>1. Turn on battery, which is powers the 5V regulator and the motor 
>controllers, which turns everything on at the "same" time. BBB does not 
>boot up.
>2. Remove cape (with all the connections still on), turn on battery, 
>BBB boots, once the light indicators are no longer all a solid blue, I 
>replace the cape, and everything works, BBB continues to boot up.
>3. If I remove all but one input to one controller and power up the 
>battery, BBB sometimes boots.
>4. I have attempted to add 1k and 10k resistors between the 
>connections which allowed the BBB sometimes to boot with two motors inputs 
>connected.
>5. *Wierd one:* I decided to remove the power from two controller 
>(except for ground), and connect them to the BBB. Still it did not boot. 
>The motor controllers did not get powered at all!
>6. *Wierder one: I removed all of the power wires from from both 
>controllers and still the BBB will not boot up if connected to the motor 
>controller inputs.*
>
> Does anyone have idea what is happening here? One of my solutions was to 
> use a relay to turn on the power to the motor controllers after the BBB has 
> fully booted up or add a second switch that turns on the motor controllers 
> after the BBB has fully booted, but that plan can not work if merely 
> pluggin in the inputs causes this problem.
>
> I do know about this issue: DO NOT APPLY VOLTAGE TO ANY I/O PIN WHEN POWER 
> IS NOT SUPPLIED TO THE BOARD. IT WILL DAMAGE THE PROCESSOR AND VOID THE 
> WARRANTY. NO PINS ARE TO BE DRIVEN UNTIL AFTER THE SYS_RESET LINE GOES 
> HIGH. But in this case, there is no power coming from the input pins.
>
> *Last note: I measured the resistance from the dir pin and the pwm pin to 
> ground and they come up 16k and 20k respectively.  * 
>
> I appreciate any suggestions or help on this matter.
>

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Robert Nelson]

On Tue, Mar 24, 2015 at 9:27 AM, Marty  wrote:
> Oh, so the file should already exist? What do u mean by the march
> image...the image I flashed?

With the March "2015-03-01" image, the file you need to modify to stop
loading the pins is located at "/boot/uEnv.txt"

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

I don't have that file.  Do I need to reflash?

><>Sent From Marty's S3<><
On Mar 24, 2015 11:10 AM, "Robert Nelson"  wrote:

> On Tue, Mar 24, 2015 at 9:27 AM, Marty  wrote:
> > Oh, so the file should already exist? What do u mean by the march
> > image...the image I flashed?
>
> With the March "2015-03-01" image, the file you need to modify to stop
> loading the pins is located at "/boot/uEnv.txt"
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

That file was in /boot.  I'll move it to /boot/uboot and then add that
line.  Hopefully it works then.

><>Sent From Marty's S3<><
On Mar 24, 2015 11:10 AM, "Robert Nelson"  wrote:

> On Tue, Mar 24, 2015 at 9:27 AM, Marty  wrote:
> > Oh, so the file should already exist? What do u mean by the march
> > image...the image I flashed?
>
> With the March "2015-03-01" image, the file you need to modify to stop
> loading the pins is located at "/boot/uEnv.txt"
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Robert Nelson]

On Tue, Mar 24, 2015 at 10:19 AM, Marty  wrote:
> That file was in /boot.  I'll move it to /boot/uboot and then add that line.
> Hopefully it works then.

Stop! Don't do that... It's suppost to be in "/boot/uEnv.txt"...

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

Yeah... That didn't work.  No harm done since I just copied the file.  So
how do I get the file that should be in /boot/uboot?

><>Sent From Marty's S3<><
On Mar 24, 2015 11:24 AM, "Robert Nelson"  wrote:

> On Tue, Mar 24, 2015 at 10:19 AM, Marty  wrote:
> > That file was in /boot.  I'll move it to /boot/uboot and then add that
> line.
> > Hopefully it works then.
>
> Stop! Don't do that... It's suppost to be in "/boot/uEnv.txt"...
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBB MIDI .wav trigger

[Steve French]

Aaron,
Not sure about "special steps", but in general, as long as your Midi device 
is present when you do "lsusb", then PureData should be able to recognize 
it and use it in the PD setup and for the uSD card, just make sure to 
expand your root file system to use the full space on the uSD card...then 
copy the WAV files onto your uSD card.
-frenchy



On Monday, March 23, 2015 at 10:19:18 AM UTC-4, aaron...@gmail.com wrote:
>
> Steve,
>
> Were there any special steps on the BBB to get MIDI or audio storage on 
> the SD Card working with your setup?  
>
> Thanks, 
> Aaron
>
>
> On Monday, February 16, 2015 at 11:56:16 AM UTC-5, Steve French wrote:
>>
>> Aaron,
>> 1) yes, the sounds are on uSD card.  I stopped using the built-in 2GB of 
>> eMMC because the Debian image causes it to be 100% full so you cant even do 
>> an *apt-get update* and you especially cant save WAV files!  If you have 
>> the 4GB eMMC version, you could run everything from the eMMC including the 
>> sounds.
>> 2) I do boot with all of the USB devices connected because hot-plugging 
>> USB is questionable on embedded linux sometimes.  I did not take the time 
>> yet to figure out how to launch the PD application during bootso I have 
>> been manually launching it from another computer via SSH command line.
>>
>> Good Luck!
>> -frenchy
>> www.voltvision.com
>>
>> --
>> Respectfully,
>> Steve French
>> 800.664.7256.office
>> 814.730.0003.cell
>>
>> President, Volt Vision
>> www.voltvision.com
>>
>>
>> On Sat, Feb 14, 2015 at 9:30 AM,  wrote:
>>
>>> Thanks Steve! That sounds very promising.  I am starting to read through 
>>> the tutorial now and thinking about what changes to make to suit my needs.
>>>
>>> Can you tell me some about how you use your setup? I wondered if your 
>>> sounds are stored on microSD.  Also, are you able to boot your BBB with the 
>>> pedal and sound card connected and simply start jamming?
>>>
>>> Best,
>>> Aaron
>>>
>>> On Monday, February 9, 2015 at 6:51:34 PM UTC-5, aaron...@gmail.com 
>>> wrote:

 Hello All,

 I am new to BBB and wondered if anyone might be able to point me in the 
 right direction for a school project I am working on.
 I would like to have a single serial input to the BBB which triggers 
 audio files to play.  The incoming serial line will be MIDI information
 from a MIDI drum controller  (edrum kit) I have built.  The BBB will 
 have to mix a maybe 6 files together.  

 I have the BBB rev C with Debian pre-installed.  Where on earth do I 
 start?  I know I will be dealing with ALSA and JACK.  
 I have found software called SDDM which is a open source Linux drum 
 machine, however I believe this software may not be 
 compatible with eLinux? Not sure about this.  

 I own a behringer uca-222 which I have heard can be used with the BBB 
 through its USB port.  I would like to use the uca-222 for 
 audio playback and the headphone jack as well if I can get it working.

 Please, any help is greatly appreciated
 Aaron

>>>  -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "BeagleBoard" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/beagleboard/5wOxaWYjpMA/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> beagleboard...@googlegroups.com.
>>> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Robert Nelson]

On Mar 24, 2015 8:28 AM, "Marty"  wrote:
>
> Yeah... That didn't work.  No harm done since I just copied the file.  So
how do I get the file that should be in /boot/uboot?

You don't.. Everything is in /boot/uEnv.txt now, just open it and uncomment
the line to disable HDMI audio.

>
> ><>Sent From Marty's S3<><
>
> On Mar 24, 2015 11:24 AM, "Robert Nelson"  wrote:
>>
>> On Tue, Mar 24, 2015 at 10:19 AM, Marty  wrote:
>> > That file was in /boot.  I'll move it to /boot/uboot and then add that
line.
>> > Hopefully it works then.
>>
>> Stop! Don't do that... It's suppost to be in "/boot/uEnv.txt"...
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
beagleboard+unsubscr...@googlegroups.com.
>> 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 beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] chown on mounted microsd

[Ray Madigan]

I have mounted my microsd card to use as a database storage, however I 
can't seem to figure out how to change the settings in /etc/fstab to allow 
me to chown directories on the card so I can write to it.

After rereading the mount man page I thought the suid option would allow 
change group and change owner to take effect, so maybe I have conflicting 
options.

I have set   auto,rw,suid,async,user,nofail 0 0


what am I missing?  Thanks you

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

That file isn't on my install in that location.  I'll redownload the flash
file tonight and flash again.  Where should I download from?  This is where
I got it before:


https://rcn-ee.com/rootfs/bb.org/release/2015-03-01/lxde-4gb/BBB-eMMC-flasher-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz


I checked the md5sum code and it checked out.


><>Sent From Marty's S3<><
On Mar 24, 2015 11:47 AM, "Robert Nelson"  wrote:

>
> On Mar 24, 2015 8:28 AM, "Marty"  wrote:
> >
> > Yeah... That didn't work.  No harm done since I just copied the file.
> So how do I get the file that should be in /boot/uboot?
>
> You don't.. Everything is in /boot/uEnv.txt now, just open it and
> uncomment the line to disable HDMI audio.
>
> >
> > ><>Sent From Marty's S3<><
> >
> > On Mar 24, 2015 11:24 AM, "Robert Nelson" 
> wrote:
> >>
> >> On Tue, Mar 24, 2015 at 10:19 AM, Marty  wrote:
> >> > That file was in /boot.  I'll move it to /boot/uboot and then add
> that line.
> >> > Hopefully it works then.
> >>
> >> Stop! Don't do that... It's suppost to be in "/boot/uEnv.txt"...
> >>
> >> Regards,
> >>
> >> --
> >> Robert Nelson
> >> https://rcn-ee.com/
> >>
> >> --
> >> For more options, visit http://beagleboard.org/discuss
> >> ---
> >> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> >> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
> >> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> >> 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 beagleboard+unsubscr...@googlegroups.com.
> > 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

The flashing did only take 8 minutes on my rev C and I read it should take
25045 minutes.  Maybe that's a bad image?

><> Marty <><



On Tue, Mar 24, 2015 at 12:05 PM, Marty  wrote:

> That file isn't on my install in that location.  I'll redownload the flash
> file tonight and flash again.  Where should I download from?  This is where
> I got it before:
>
>
>
> https://rcn-ee.com/rootfs/bb.org/release/2015-03-01/lxde-4gb/BBB-eMMC-flasher-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz
>
>
> I checked the md5sum code and it checked out.
>
>
> ><>Sent From Marty's S3<><
> On Mar 24, 2015 11:47 AM, "Robert Nelson"  wrote:
>
>>
>> On Mar 24, 2015 8:28 AM, "Marty"  wrote:
>> >
>> > Yeah... That didn't work.  No harm done since I just copied the file.
>> So how do I get the file that should be in /boot/uboot?
>>
>> You don't.. Everything is in /boot/uEnv.txt now, just open it and
>> uncomment the line to disable HDMI audio.
>>
>> >
>> > ><>Sent From Marty's S3<><
>> >
>> > On Mar 24, 2015 11:24 AM, "Robert Nelson" 
>> wrote:
>> >>
>> >> On Tue, Mar 24, 2015 at 10:19 AM, Marty  wrote:
>> >> > That file was in /boot.  I'll move it to /boot/uboot and then add
>> that line.
>> >> > Hopefully it works then.
>> >>
>> >> Stop! Don't do that... It's suppost to be in "/boot/uEnv.txt"...
>> >>
>> >> Regards,
>> >>
>> >> --
>> >> Robert Nelson
>> >> https://rcn-ee.com/
>> >>
>> >> --
>> >> For more options, visit http://beagleboard.org/discuss
>> >> ---
>> >> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> >> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
>> >> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> >> 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 beagleboard+unsubscr...@googlegroups.com.
>> > 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 a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

that should be 25-45 minutes.

><> Marty <><



On Tue, Mar 24, 2015 at 12:12 PM, Marty  wrote:

> The flashing did only take 8 minutes on my rev C and I read it should take
> 25045 minutes.  Maybe that's a bad image?
>
> ><> Marty <><
>
>
>
> On Tue, Mar 24, 2015 at 12:05 PM, Marty  wrote:
>
>> That file isn't on my install in that location.  I'll redownload the
>> flash file tonight and flash again.  Where should I download from?  This is
>> where I got it before:
>>
>>
>>
>> https://rcn-ee.com/rootfs/bb.org/release/2015-03-01/lxde-4gb/BBB-eMMC-flasher-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz
>>
>>
>> I checked the md5sum code and it checked out.
>>
>>
>> ><>Sent From Marty's S3<><
>> On Mar 24, 2015 11:47 AM, "Robert Nelson" 
>> wrote:
>>
>>>
>>> On Mar 24, 2015 8:28 AM, "Marty"  wrote:
>>> >
>>> > Yeah... That didn't work.  No harm done since I just copied the file.
>>> So how do I get the file that should be in /boot/uboot?
>>>
>>> You don't.. Everything is in /boot/uEnv.txt now, just open it and
>>> uncomment the line to disable HDMI audio.
>>>
>>> >
>>> > ><>Sent From Marty's S3<><
>>> >
>>> > On Mar 24, 2015 11:24 AM, "Robert Nelson" 
>>> wrote:
>>> >>
>>> >> On Tue, Mar 24, 2015 at 10:19 AM, Marty  wrote:
>>> >> > That file was in /boot.  I'll move it to /boot/uboot and then add
>>> that line.
>>> >> > Hopefully it works then.
>>> >>
>>> >> Stop! Don't do that... It's suppost to be in "/boot/uEnv.txt"...
>>> >>
>>> >> Regards,
>>> >>
>>> >> --
>>> >> Robert Nelson
>>> >> https://rcn-ee.com/
>>> >>
>>> >> --
>>> >> For more options, visit http://beagleboard.org/discuss
>>> >> ---
>>> >> You received this message because you are subscribed to a topic in
>>> the Google Groups "BeagleBoard" group.
>>> >> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
>>> >> To unsubscribe from this group and all its topics, send an email to
>>> beagleboard+unsubscr...@googlegroups.com.
>>> >> 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 beagleboard+unsubscr...@googlegroups.com.
>>> > 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 a topic in the
>>> Google Groups "BeagleBoard" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> beagleboard+unsubscr...@googlegroups.com.
>>> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB not booting if connected to Motor Controller MD10C

[Khalil Estell]

Thank you Graham. That clears a lot of stuff up for me. It just so happens 
that I am using 8 of the LCD data pins for my shield without knowing about 
how loading those pins down can result in a disturbance in the booting 
process. Since I was not using an LCD, I thought no harm would come from 
using those pins.

On Tuesday, March 24, 2015 at 8:05:22 AM UTC-7, Graham wrote:
>
> The Sitara uses a field of pull-up and pull-down resistors to tell it how 
> to boot.
> If you put any LOAD on these pins, and your I/O does NOT have to be 
> powered, (which would make 
> things even worse), you will give it the wrong boot commands, and the BBB 
> won't boot.
>
> Go read the section in the System Reference Manual on Boot Configuration, 
> and
> the section on Pin Usage Considerations.
>
>
> --- Graham
>
> ==
>
> On Tuesday, March 24, 2015 at 9:42:12 AM UTC-5, Khalil Estell wrote:
>>
>> Hello All,
>>
>> I have become stumped by this issue. I am trying to boot up a BBB when 
>> connected to the inputs of six MD10C motor controllers 
>> . For 
>> the most part, it works fine if the BBB has been boot up before 
>> *connecting* the direction and pwm pins to the beagle bone black. If I 
>> attempt to power the BBB with them connected, the power light indicator 
>> will come on, but the status lights will not. The configuration of the 
>> circuit is this: I have a custom shield that I made that breaks out the pwm 
>> pins and gpio pins I need for the controller. The controllers are powered 
>> by an 24V battery power supply rated at 15A output. The BBB is powered by 
>> 5V regulator rated at 6A.
>>
>> Here is what I have attempted thus far:
>>
>>
>>1. Turn on battery, which is powers the 5V regulator and the motor 
>>controllers, which turns everything on at the "same" time. BBB does not 
>>boot up.
>>2. Remove cape (with all the connections still on), turn on battery, 
>>BBB boots, once the light indicators are no longer all a solid blue, I 
>>replace the cape, and everything works, BBB continues to boot up.
>>3. If I remove all but one input to one controller and power up the 
>>battery, BBB sometimes boots.
>>4. I have attempted to add 1k and 10k resistors between the 
>>connections which allowed the BBB sometimes to boot with two motors 
>> inputs 
>>connected.
>>5. *Wierd one:* I decided to remove the power from two controller 
>>(except for ground), and connect them to the BBB. Still it did not boot. 
>>The motor controllers did not get powered at all!
>>6. *Wierder one: I removed all of the power wires from from both 
>>controllers and still the BBB will not boot up if connected to the motor 
>>controller inputs.*
>>
>> Does anyone have idea what is happening here? One of my solutions was to 
>> use a relay to turn on the power to the motor controllers after the BBB has 
>> fully booted up or add a second switch that turns on the motor controllers 
>> after the BBB has fully booted, but that plan can not work if merely 
>> pluggin in the inputs causes this problem.
>>
>> I do know about this issue: DO NOT APPLY VOLTAGE TO ANY I/O PIN WHEN 
>> POWER IS NOT SUPPLIED TO THE BOARD. IT WILL DAMAGE THE PROCESSOR AND VOID 
>> THE WARRANTY. NO PINS ARE TO BE DRIVEN UNTIL AFTER THE SYS_RESET LINE GOES 
>> HIGH. But in this case, there is no power coming from the input pins.
>>
>> *Last note: I measured the resistance from the dir pin and the pwm pin to 
>> ground and they come up 16k and 20k respectively.  * 
>>
>> I appreciate any suggestions or help on this matter.
>>
>

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Robert Nelson]

On Tue, Mar 24, 2015 at 11:13 AM, Marty  wrote:
> that should be 25-45 minutes.

Things average 5-6 minutes a GB...

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

Good... Then 8 minutes is ok on the rev c.  I was thinking those numbers
musta been good for the rev b.  Think that's an OK download
place...BeagleBoard.org took me there?

><>Sent From Marty's S3<><
On Mar 24, 2015 12:43 PM, "Robert Nelson"  wrote:

> On Tue, Mar 24, 2015 at 11:13 AM, Marty  wrote:
> > that should be 25-45 minutes.
>
> Things average 5-6 minutes a GB...
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBB not booting if connected to Motor Controller MD10C

[Gerald Coley]

My advice is to read the System Reference Manual. It will save you a lot of
heartache.

Gerald


On Tue, Mar 24, 2015 at 11:14 AM, Khalil Estell 
wrote:

> Thank you Graham. That clears a lot of stuff up for me. It just so happens
> that I am using 8 of the LCD data pins for my shield without knowing about
> how loading those pins down can result in a disturbance in the booting
> process. Since I was not using an LCD, I thought no harm would come from
> using those pins.
>
>
> On Tuesday, March 24, 2015 at 8:05:22 AM UTC-7, Graham wrote:
>>
>> The Sitara uses a field of pull-up and pull-down resistors to tell it how
>> to boot.
>> If you put any LOAD on these pins, and your I/O does NOT have to be
>> powered, (which would make
>> things even worse), you will give it the wrong boot commands, and the BBB
>> won't boot.
>>
>> Go read the section in the System Reference Manual on Boot Configuration,
>> and
>> the section on Pin Usage Considerations.
>>
>>
>> --- Graham
>>
>> ==
>>
>> On Tuesday, March 24, 2015 at 9:42:12 AM UTC-5, Khalil Estell wrote:
>>>
>>> Hello All,
>>>
>>> I have become stumped by this issue. I am trying to boot up a BBB when
>>> connected to the inputs of six MD10C motor controllers
>>> .
>>> For the most part, it works fine if the BBB has been boot up before
>>> *connecting* the direction and pwm pins to the beagle bone black. If I
>>> attempt to power the BBB with them connected, the power light indicator
>>> will come on, but the status lights will not. The configuration of the
>>> circuit is this: I have a custom shield that I made that breaks out the pwm
>>> pins and gpio pins I need for the controller. The controllers are powered
>>> by an 24V battery power supply rated at 15A output. The BBB is powered by
>>> 5V regulator rated at 6A.
>>>
>>> Here is what I have attempted thus far:
>>>
>>>
>>>1. Turn on battery, which is powers the 5V regulator and the motor
>>>controllers, which turns everything on at the "same" time. BBB does not
>>>boot up.
>>>2. Remove cape (with all the connections still on), turn on battery,
>>>BBB boots, once the light indicators are no longer all a solid blue, I
>>>replace the cape, and everything works, BBB continues to boot up.
>>>3. If I remove all but one input to one controller and power up the
>>>battery, BBB sometimes boots.
>>>4. I have attempted to add 1k and 10k resistors between the
>>>connections which allowed the BBB sometimes to boot with two motors 
>>> inputs
>>>connected.
>>>5. *Wierd one:* I decided to remove the power from two controller
>>>(except for ground), and connect them to the BBB. Still it did not boot.
>>>The motor controllers did not get powered at all!
>>>6. *Wierder one: I removed all of the power wires from from both
>>>controllers and still the BBB will not boot up if connected to the motor
>>>controller inputs.*
>>>
>>> Does anyone have idea what is happening here? One of my solutions was to
>>> use a relay to turn on the power to the motor controllers after the BBB has
>>> fully booted up or add a second switch that turns on the motor controllers
>>> after the BBB has fully booted, but that plan can not work if merely
>>> pluggin in the inputs causes this problem.
>>>
>>> I do know about this issue: DO NOT APPLY VOLTAGE TO ANY I/O PIN WHEN
>>> POWER IS NOT SUPPLIED TO THE BOARD. IT WILL DAMAGE THE PROCESSOR AND VOID
>>> THE WARRANTY. NO PINS ARE TO BE DRIVEN UNTIL AFTER THE SYS_RESET LINE GOES
>>> HIGH. But in this case, there is no power coming from the input pins.
>>>
>>> *Last note: I measured the resistance from the dir pin and the pwm pin
>>> to ground and they come up 16k and 20k respectively.  *
>>>
>>> I appreciate any suggestions or help on this matter.
>>>
>>  --
> 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/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
http://circuitco.com/support/

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

ok, I think I got it by NOT following that tutorial and following advice
here.  Now I got this:

root@beaglebone:/home/debian# 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
 7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02


What I did as root was edit /boot/uEnv.txt and uncomment the audio cape
lines so that it looks like this:

#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:
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

uuid=c92d7bef-e149-4c25-83f4-fffb66c655cb

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

mplayer isn't happy now.  It ends with this:

Failed to initialize audio driver 'sdl:aalib'
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video


Exiting... (End of file)


><> Marty <><



On Tue, Mar 24, 2015 at 2:40 PM, Marty  wrote:

> ok, I think I got it by NOT following that tutorial and following advice
> here.  Now I got this:
>
> root@beaglebone:/home/debian# 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
>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02
>
>
> What I did as root was edit /boot/uEnv.txt and uncomment the audio cape
> lines so that it looks like this:
>
> #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:
> #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
>
> uuid=c92d7bef-e149-4c25-83f4-fffb66c655cb
>
>

-- 
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/d/optout.

Re: [beagleboard] Date/Time syncronization (Ubunutu 13.04)

[Craig Markwardt]

Updating every minute risks wearing out your emmc flash storage, especially 
if you do a 'sync' afterwards.  I used 6 hours, and of course I updated the 
timestamp at shutdown.  

Craig


On Monday, March 16, 2015 at 10:18:01 AM UTC-4, s.p.e...@gmail.com wrote:
>
> So, troubled by the same situation and not finding any alternatives, I 
> tried this technique. However, it doesn't seem to work -- at least on my BB 
> Black with the 2015-03-01 build.
>
> In fact, I had a hint that it would not work even before I tried it.
>
> My original /etc/timestamp file had a March 1 date matching the build 
> date, but my /var/log/syslog timestamps on reboot began with March 5 while 
> today's date is March 15.
>
> I don't know why the system decided to startup using March 5 as its date.
>
> And after following the suggestion of updating /etc/timestamp using a cron 
> job -- I chose once per minute since the /etc/timestamp file captured only 
> hours/minutes (why??) -- and confirming that the file was being updated 
> appropriately, after a reboot, I'm back to March 5 until after networking 
> is up and NTP can connect to a server.
>
> So, how DOES the system decide to choose a starting time on reboot???
>

-- 
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/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Bill Traynor]

Which part of the tutorial did you not do?  Note that it is a wiki, so
when things change, you can always update the tutorial.

On Tue, Mar 24, 2015 at 2:40 PM, Marty  wrote:
> ok, I think I got it by NOT following that tutorial and following advice
> here.  Now I got this:
>
> root@beaglebone:/home/debian# 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
>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02
>
>
> What I did as root was edit /boot/uEnv.txt and uncomment the audio cape
> lines so that it looks like this:
>
> #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:
> #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
>
> uuid=c92d7bef-e149-4c25-83f4-fffb66c655cb
>
> --
> 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/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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

I unconsumed both lines under audio cape but now mplayer doesn't work so
I'm not thinking this wiki needs to be revised by me yet.  The wiki is for
the rev b and not my c, though.

><>Sent From Marty's S3<><
On Mar 24, 2015 3:46 PM, "Bill Traynor"  wrote:

> Which part of the tutorial did you not do?  Note that it is a wiki, so
> when things change, you can always update the tutorial.
>
> On Tue, Mar 24, 2015 at 2:40 PM, Marty  wrote:
> > ok, I think I got it by NOT following that tutorial and following advice
> > here.  Now I got this:
> >
> > root@beaglebone:/home/debian# 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
> >  7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02
> >
> >
> > What I did as root was edit /boot/uEnv.txt and uncomment the audio cape
> > lines so that it looks like this:
> >
> > #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:
> > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
> >
> > uuid=c92d7bef-e149-4c25-83f4-fffb66c655cb
> >
> > --
> > 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/d/optout.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Bill Traynor]

Feel free to add Rev C notes ;)

On Tue, Mar 24, 2015 at 3:51 PM, Marty  wrote:
> I unconsumed both lines under audio cape but now mplayer doesn't work so I'm
> not thinking this wiki needs to be revised by me yet.  The wiki is for the
> rev b and not my c, though.
>
>><>Sent From Marty's S3<><
>
> On Mar 24, 2015 3:46 PM, "Bill Traynor"  wrote:
>>
>> Which part of the tutorial did you not do?  Note that it is a wiki, so
>> when things change, you can always update the tutorial.
>>
>> On Tue, Mar 24, 2015 at 2:40 PM, Marty  wrote:
>> > ok, I think I got it by NOT following that tutorial and following advice
>> > here.  Now I got this:
>> >
>> > root@beaglebone:/home/debian# 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
>> >  7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02
>> >
>> >
>> > What I did as root was edit /boot/uEnv.txt and uncomment the audio cape
>> > lines so that it looks like this:
>> >
>> > #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:
>> > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
>> >
>> > uuid=c92d7bef-e149-4c25-83f4-fffb66c655cb
>> >
>> > --
>> > 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/d/optout.
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> 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 beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Robert Nelson]

On Mar 24, 2015 12:51 PM, "Marty"  wrote:
>
> I unconsumed both lines under audio cape but now mplayer doesn't work so
I'm not thinking this wiki needs to be revised by me yet.  The wiki is for
the rev b and not my c, though.

The wiki was written for the old may 2014 release, the march 2015 is now
the official release, it will take time for 'all' wiki's will be updated.
Please update it for us. ;)

>
> ><>Sent From Marty's S3<><
>
> On Mar 24, 2015 3:46 PM, "Bill Traynor"  wrote:
>>
>> Which part of the tutorial did you not do?  Note that it is a wiki, so
>> when things change, you can always update the tutorial.
>>
>> On Tue, Mar 24, 2015 at 2:40 PM, Marty  wrote:
>> > ok, I think I got it by NOT following that tutorial and following
advice
>> > here.  Now I got this:
>> >
>> > root@beaglebone:/home/debian# 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
>> >  7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02
>> >
>> >
>> > What I did as root was edit /boot/uEnv.txt and uncomment the audio cape
>> > lines so that it looks like this:
>> >
>> > #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:
>> > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
>> >
>> > uuid=c92d7bef-e149-4c25-83f4-fffb66c655cb
>> >
>> > --
>> > 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/d/optout.
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
beagleboard+unsubscr...@googlegroups.com.
>>
>> 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 beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

Wow, this is a new rev c!

><>Sent From Marty's S3<><
On Mar 24, 2015 4:22 PM, "Robert Nelson"  wrote:

>
> On Mar 24, 2015 12:51 PM, "Marty"  wrote:
> >
> > I unconsumed both lines under audio cape but now mplayer doesn't work so
> I'm not thinking this wiki needs to be revised by me yet.  The wiki is for
> the rev b and not my c, though.
>
> The wiki was written for the old may 2014 release, the march 2015 is now
> the official release, it will take time for 'all' wiki's will be updated.
> Please update it for us. ;)
>
> >
> > ><>Sent From Marty's S3<><
> >
> > On Mar 24, 2015 3:46 PM, "Bill Traynor"  wrote:
> >>
> >> Which part of the tutorial did you not do?  Note that it is a wiki, so
> >> when things change, you can always update the tutorial.
> >>
> >> On Tue, Mar 24, 2015 at 2:40 PM, Marty  wrote:
> >> > ok, I think I got it by NOT following that tutorial and following
> advice
> >> > here.  Now I got this:
> >> >
> >> > root@beaglebone:/home/debian# 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
> >> >  7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02
> >> >
> >> >
> >> > What I did as root was edit /boot/uEnv.txt and uncomment the audio
> cape
> >> > lines so that it looks like this:
> >> >
> >> > #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:
> >> > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
> >> >
> >> > uuid=c92d7bef-e149-4c25-83f4-fffb66c655cb
> >> >
> >> > --
> >> > 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/d/optout.
> >>
> >> --
> >> For more options, visit http://beagleboard.org/discuss
> >> ---
> >> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> >> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
> >> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> >>
> >> 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 beagleboard+unsubscr...@googlegroups.com.
> > 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Bill Traynor]

Don't overwrite old content though.  Be sure to note that for your
board, things are different.

On Tue, Mar 24, 2015 at 4:25 PM, Marty  wrote:
> Wow, this is a new rev c!
>
>><>Sent From Marty's S3<><
>
> On Mar 24, 2015 4:22 PM, "Robert Nelson"  wrote:
>>
>>
>> On Mar 24, 2015 12:51 PM, "Marty"  wrote:
>> >
>> > I unconsumed both lines under audio cape but now mplayer doesn't work so
>> > I'm not thinking this wiki needs to be revised by me yet.  The wiki is for
>> > the rev b and not my c, though.
>>
>> The wiki was written for the old may 2014 release, the march 2015 is now
>> the official release, it will take time for 'all' wiki's will be updated.
>> Please update it for us. ;)
>>
>> >
>> > ><>Sent From Marty's S3<><
>> >
>> > On Mar 24, 2015 3:46 PM, "Bill Traynor"  wrote:
>> >>
>> >> Which part of the tutorial did you not do?  Note that it is a wiki, so
>> >> when things change, you can always update the tutorial.
>> >>
>> >> On Tue, Mar 24, 2015 at 2:40 PM, Marty  wrote:
>> >> > ok, I think I got it by NOT following that tutorial and following
>> >> > advice
>> >> > here.  Now I got this:
>> >> >
>> >> > root@beaglebone:/home/debian# 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
>> >> >  7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02
>> >> >
>> >> >
>> >> > What I did as root was edit /boot/uEnv.txt and uncomment the audio
>> >> > cape
>> >> > lines so that it looks like this:
>> >> >
>> >> > #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:
>> >> > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
>> >> >
>> >> > uuid=c92d7bef-e149-4c25-83f4-fffb66c655cb
>> >> >
>> >> > --
>> >> > 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/d/optout.
>> >>
>> >> --
>> >> For more options, visit http://beagleboard.org/discuss
>> >> ---
>> >> You received this message because you are subscribed to a topic in the
>> >> Google Groups "BeagleBoard" group.
>> >> To unsubscribe from this topic, visit
>> >> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
>> >> To unsubscribe from this group and all its topics, send an email to
>> >> beagleboard+unsubscr...@googlegroups.com.
>> >>
>> >> 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 beagleboard+unsubscr...@googlegroups.com.
>> > 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 a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> 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 beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you a

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

Yeah I'm not sure what I did is the correct way of doing things.  Since I
don't have sound yet I'm thinking not but maybe somebody will build on that
and set me straight :)

><>Sent From Marty's S3<><
On Mar 24, 2015 4:32 PM, "Bill Traynor"  wrote:

> Don't overwrite old content though.  Be sure to note that for your
> board, things are different.
>
> On Tue, Mar 24, 2015 at 4:25 PM, Marty  wrote:
> > Wow, this is a new rev c!
> >
> >><>Sent From Marty's S3<><
> >
> > On Mar 24, 2015 4:22 PM, "Robert Nelson" 
> wrote:
> >>
> >>
> >> On Mar 24, 2015 12:51 PM, "Marty"  wrote:
> >> >
> >> > I unconsumed both lines under audio cape but now mplayer doesn't work
> so
> >> > I'm not thinking this wiki needs to be revised by me yet.  The wiki
> is for
> >> > the rev b and not my c, though.
> >>
> >> The wiki was written for the old may 2014 release, the march 2015 is now
> >> the official release, it will take time for 'all' wiki's will be
> updated.
> >> Please update it for us. ;)
> >>
> >> >
> >> > ><>Sent From Marty's S3<><
> >> >
> >> > On Mar 24, 2015 3:46 PM, "Bill Traynor"  wrote:
> >> >>
> >> >> Which part of the tutorial did you not do?  Note that it is a wiki,
> so
> >> >> when things change, you can always update the tutorial.
> >> >>
> >> >> On Tue, Mar 24, 2015 at 2:40 PM, Marty  wrote:
> >> >> > ok, I think I got it by NOT following that tutorial and following
> >> >> > advice
> >> >> > here.  Now I got this:
> >> >> >
> >> >> > root@beaglebone:/home/debian# 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
> >> >> >  7: ff:P-O-L Override Board Name,00A0,Override
> Manuf,BB-BONE-AUDI-02
> >> >> >
> >> >> >
> >> >> > What I did as root was edit /boot/uEnv.txt and uncomment the audio
> >> >> > cape
> >> >> > lines so that it looks like this:
> >> >> >
> >> >> > #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:
> >> >> > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
> >> >> >
> >> >> > uuid=c92d7bef-e149-4c25-83f4-fffb66c655cb
> >> >> >
> >> >> > --
> >> >> > 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/d/optout.
> >> >>
> >> >> --
> >> >> For more options, visit http://beagleboard.org/discuss
> >> >> ---
> >> >> You received this message because you are subscribed to a topic in
> the
> >> >> Google Groups "BeagleBoard" group.
> >> >> To unsubscribe from this topic, visit
> >> >>
> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
> >> >> To unsubscribe from this group and all its topics, send an email to
> >> >> beagleboard+unsubscr...@googlegroups.com.
> >> >>
> >> >> 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 beagleboard+unsubscr...@googlegroups.com.
> >> > 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 a topic in the
> >> Google Groups "BeagleBoard" group.
> >> To unsubscribe from this topic, visit
> >> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
> >> To unsubscribe from this group and all its topics, send an email to
> >> beagleboard+unsubscr...@googlegroups.com.
> >> For more opti

Re: [beagleboard] Audio Cape on BBB rev C

[Robert Nelson]

On Mar 24, 2015 1:35 PM, "Marty"  wrote:
>
> Yeah I'm not sure what I did is the correct way of doing things.  Since I
don't have sound yet I'm thinking not but maybe somebody will build on that
and set me straight :)

The easiest thing to do is add the value of `cat /etc/dogtag` as that tells
everyone what version they have and how it's setup.

>
> ><>Sent From Marty's S3<><
>
> On Mar 24, 2015 4:32 PM, "Bill Traynor"  wrote:
>>
>> Don't overwrite old content though.  Be sure to note that for your
>> board, things are different.
>>
>> On Tue, Mar 24, 2015 at 4:25 PM, Marty  wrote:
>> > Wow, this is a new rev c!
>> >
>> >><>Sent From Marty's S3<><
>> >
>> > On Mar 24, 2015 4:22 PM, "Robert Nelson" 
wrote:
>> >>
>> >>
>> >> On Mar 24, 2015 12:51 PM, "Marty"  wrote:
>> >> >
>> >> > I unconsumed both lines under audio cape but now mplayer doesn't
work so
>> >> > I'm not thinking this wiki needs to be revised by me yet.  The wiki
is for
>> >> > the rev b and not my c, though.
>> >>
>> >> The wiki was written for the old may 2014 release, the march 2015 is
now
>> >> the official release, it will take time for 'all' wiki's will be
updated.
>> >> Please update it for us. ;)
>> >>
>> >> >
>> >> > ><>Sent From Marty's S3<><
>> >> >
>> >> > On Mar 24, 2015 3:46 PM, "Bill Traynor"  wrote:
>> >> >>
>> >> >> Which part of the tutorial did you not do?  Note that it is a
wiki, so
>> >> >> when things change, you can always update the tutorial.
>> >> >>
>> >> >> On Tue, Mar 24, 2015 at 2:40 PM, Marty  wrote:
>> >> >> > ok, I think I got it by NOT following that tutorial and following
>> >> >> > advice
>> >> >> > here.  Now I got this:
>> >> >> >
>> >> >> > root@beaglebone:/home/debian# 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
>> >> >> >  7: ff:P-O-L Override Board Name,00A0,Override
Manuf,BB-BONE-AUDI-02
>> >> >> >
>> >> >> >
>> >> >> > What I did as root was edit /boot/uEnv.txt and uncomment the
audio
>> >> >> > cape
>> >> >> > lines so that it looks like this:
>> >> >> >
>> >> >> > #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:
>> >> >> > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
>> >> >> >
>> >> >> > uuid=c92d7bef-e149-4c25-83f4-fffb66c655cb
>> >> >> >
>> >> >> > --
>> >> >> > 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/d/optout.
>> >> >>
>> >> >> --
>> >> >> For more options, visit http://beagleboard.org/discuss
>> >> >> ---
>> >> >> You received this message because you are subscribed to a topic in
the
>> >> >> Google Groups "BeagleBoard" group.
>> >> >> To unsubscribe from this topic, visit
>> >> >>
https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
>> >> >> To unsubscribe from this group and all its topics, send an email to
>> >> >> beagleboard+unsubscr...@googlegroups.com.
>> >> >>
>> >> >> 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 beagleboard+unsubscr...@googlegroups.com.
>> >> > 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 a topic in the
>> >> Google Group

Re: [beagleboard] Audio Cape on BBB rev C

[Jesse Cobra]

Did you disable HDMI audio?

What does aplay -l (or is it -L) output.

Does speaker-test work?
On Mar 24, 2015 1:38 PM, "Robert Nelson"  wrote:

>
> On Mar 24, 2015 1:35 PM, "Marty"  wrote:
> >
> > Yeah I'm not sure what I did is the correct way of doing things.  Since
> I don't have sound yet I'm thinking not but maybe somebody will build on
> that and set me straight :)
>
> The easiest thing to do is add the value of `cat /etc/dogtag` as that
> tells everyone what version they have and how it's setup.
>
> >
> > ><>Sent From Marty's S3<><
> >
> > On Mar 24, 2015 4:32 PM, "Bill Traynor"  wrote:
> >>
> >> Don't overwrite old content though.  Be sure to note that for your
> >> board, things are different.
> >>
> >> On Tue, Mar 24, 2015 at 4:25 PM, Marty  wrote:
> >> > Wow, this is a new rev c!
> >> >
> >> >><>Sent From Marty's S3<><
> >> >
> >> > On Mar 24, 2015 4:22 PM, "Robert Nelson" 
> wrote:
> >> >>
> >> >>
> >> >> On Mar 24, 2015 12:51 PM, "Marty"  wrote:
> >> >> >
> >> >> > I unconsumed both lines under audio cape but now mplayer doesn't
> work so
> >> >> > I'm not thinking this wiki needs to be revised by me yet.  The
> wiki is for
> >> >> > the rev b and not my c, though.
> >> >>
> >> >> The wiki was written for the old may 2014 release, the march 2015 is
> now
> >> >> the official release, it will take time for 'all' wiki's will be
> updated.
> >> >> Please update it for us. ;)
> >> >>
> >> >> >
> >> >> > ><>Sent From Marty's S3<><
> >> >> >
> >> >> > On Mar 24, 2015 3:46 PM, "Bill Traynor" 
> wrote:
> >> >> >>
> >> >> >> Which part of the tutorial did you not do?  Note that it is a
> wiki, so
> >> >> >> when things change, you can always update the tutorial.
> >> >> >>
> >> >> >> On Tue, Mar 24, 2015 at 2:40 PM, Marty  wrote:
> >> >> >> > ok, I think I got it by NOT following that tutorial and
> following
> >> >> >> > advice
> >> >> >> > here.  Now I got this:
> >> >> >> >
> >> >> >> > root@beaglebone:/home/debian# 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
> >> >> >> >  7: ff:P-O-L Override Board Name,00A0,Override
> Manuf,BB-BONE-AUDI-02
> >> >> >> >
> >> >> >> >
> >> >> >> > What I did as root was edit /boot/uEnv.txt and uncomment the
> audio
> >> >> >> > cape
> >> >> >> > lines so that it looks like this:
> >> >> >> >
> >> >> >> > #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:
> >> >> >> > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
> >> >> >> >
> >> >> >> > uuid=c92d7bef-e149-4c25-83f4-fffb66c655cb
> >> >> >> >
> >> >> >> > --
> >> >> >> > 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/d/optout.
> >> >> >>
> >> >> >> --
> >> >> >> For more options, visit http://beagleboard.org/discuss
> >> >> >> ---
> >> >> >> You received this message because you are subscribed to a topic
> in the
> >> >> >> Google Groups "BeagleBoard" group.
> >> >> >> To unsubscribe from this topic, visit
> >> >> >>
> https://groups.google.com/d/topic/beagleboard/kT0DKgpHQOU/unsubscribe.
> >> >> >> To unsubscribe from this group and all its topics, send an email
> to
> >> >> >> beagleboard+unsubscr...@googlegroups.com.
> >> >> >>
> >> >> >> 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 Goog

Re: [beagleboard] Soldering JTAG connector with Element14(Embest) version BBB failed

['Mark Lazarewicz' via BeagleBoard]

thanks for verification this fix  is more troubles than its worth  I bought 
parts but decided buying a BBW was easier 

Sent from Yahoo Mail on Android

From:"Bill Mar" 
Date:Mon, Mar 23, 2015 at 9:48 PM
Subject:Re: [beagleboard] Soldering JTAG connector with Element14(Embest) 
version BBB failed

https://specialcomp.com/beaglebone/


On Sun, Mar 22, 2015 at 9:36 PM, Claud Xiao  wrote:

Hi,


I tried to solder ARM20cTI20 JTAG connectors with Element14’s BBB but failed, 
twice (hence two boards broken). After some investigations, I think it’s not my 
fault but is manufacturer’s problem. Element14’s version and CircuitCo’s 
version are really different in this issue. 


As you may know, BBB hasn’t JTAG interface on board unless you manually solder 
an extra ARM20cTI20 connector to its P2. There’re some tutorials on how to do 
that:

http://www.tincantools.com/wiki/Flyswatter2_BeagleBone_Black_How_To

https://www.youtube.com/watch?v=7JmHn7aN2FU


I have lot of experiences in soldering and never failed before. But this time 
is different. Although I strictly followed these tutorials, no matter how long 
I keep the soldering iron on the connector’s pins to heat adherent solder, the 
solder on the pin will never glue with the P2. I tried many times and some 
other methods (even with different kinds of solder irons) but stilled no 
success. I also tried to directly paste some solder to P2 but it’s pretty hard 
to adhere to. Some solder even became sphere other than adhere the bottom pins. 
Anyway, now two boards’ P2 were destroyed while two ARM20cTI20 connectors was 
consumed away. 


After carefully compare images/video in tutorials with the boards I have, I 
found the main difference is, there isn’t any solder covered P2 pins in my 
boards. 


Let’s take a look at Adafruit’s pictures on BBB:

CircuitCo’s version: http://www.adafruit.com/products/1876 (out of stock)

Element14’s version: http://www.adafruit.com/products/1996


And in SeeedStudio:

CircuitCo’s version: 
http://www.seeedstudio.com/depot/BeagleBone-Black-p-1505.html (not rev C)

Element14’s version: 
http://www.seeedstudio.com/depot/Embest-BeagleBone-Black-RevC-Singleboard-Computer-p-1860.html


Take a look at P2 on the back of the board. There’s a huge difference that 
CircuitCo’s P2 pins are covered by solder while Element14’s are not. Note that 
all tutorials used CircuitCo’s version. I also highly doubt Element14’s pins 
are covered by some solder mask which prevent the solder’s adherent. 


My question is,


1) Is there anyone who successfully soldered it on Element14’s BBB before? If 
you are, how do you achieve that? 


2) Is there any way to buy CircuitCo’s BBB rev C? At least Amazon, Adafruit, 
SeeedStudio, Sparkfun are not. MakerShed’s picture is CircuitCo’s but it hasn’t 
any manufacturer information. Consider that Sparkfun’s picture is also 
CircuitCo’s but their products are Element14’s, I don’t think picture is 
trustworthy.


Thanks your guys!

- Claud


-- 
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/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 beagleboard+unsubscr...@googlegroups.com.
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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Audio Cape on BBB rev C

[Marty]

HDMI audio appears to be disabled since BB-BONELT-HDMIN shows up with cat
/sys/devices/bone_capemgr*/slots.  That was a good idea, Jesse, about
checking with aplay -L.  I hadn't tried that for this (though that is how I
got sound to work through a cheap USB adapter) until now.  Unfortunately,
it does not list any of the devices that that capemgr lists and no sound
works except for a USB adapter (mplayer -ao alsa:device=default=Device
-playlist filename.pls is how u stream internet music with a USB soundcard).

><> Marty <><



On Tue, Mar 24, 2015 at 4:50 PM, Jesse Cobra  wrote:

> Did you disable HDMI audio?
>
> What does aplay -l (or is it -L) output.
>
> Does speaker-test work?
> On Mar 24, 2015 1:38 PM, "Robert Nelson"  wrote:
>
>>
>> On Mar 24, 2015 1:35 PM, "Marty"  wrote:
>> >
>> > Yeah I'm not sure what I did is the correct way of doing things.  Since
>> I don't have sound yet I'm thinking not but maybe somebody will build on
>> that and set me straight :)
>>
>> The easiest thing to do is add the value of `cat /etc/dogtag` as that
>> tells everyone what version they have and how it's setup.
>>
>> >
>> > ><>Sent From Marty's S3<><
>> >
>> > On Mar 24, 2015 4:32 PM, "Bill Traynor"  wrote:
>> >>
>> >> Don't overwrite old content though.  Be sure to note that for your
>> >> board, things are different.
>> >>
>> >> On Tue, Mar 24, 2015 at 4:25 PM, Marty  wrote:
>> >> > Wow, this is a new rev c!
>> >> >
>> >> >><>Sent From Marty's S3<><
>> >> >
>> >> > On Mar 24, 2015 4:22 PM, "Robert Nelson" 
>> wrote:
>> >> >>
>> >> >>
>> >> >> On Mar 24, 2015 12:51 PM, "Marty"  wrote:
>> >> >> >
>> >> >> > I unconsumed both lines under audio cape but now mplayer doesn't
>> work so
>> >> >> > I'm not thinking this wiki needs to be revised by me yet.  The
>> wiki is for
>> >> >> > the rev b and not my c, though.
>> >> >>
>> >> >> The wiki was written for the old may 2014 release, the march 2015
>> is now
>> >> >> the official release, it will take time for 'all' wiki's will be
>> updated.
>> >> >> Please update it for us. ;)
>> >> >>
>> >> >> >
>> >> >> > ><>Sent From Marty's S3<><
>> >> >> >
>> >> >> > On Mar 24, 2015 3:46 PM, "Bill Traynor" 
>> wrote:
>> >> >> >>
>> >> >> >> Which part of the tutorial did you not do?  Note that it is a
>> wiki, so
>> >> >> >> when things change, you can always update the tutorial.
>> >> >> >>
>> >> >> >> On Tue, Mar 24, 2015 at 2:40 PM, Marty 
>> wrote:
>> >> >> >> > ok, I think I got it by NOT following that tutorial and
>> following
>> >> >> >> > advice
>> >> >> >> > here.  Now I got this:
>> >> >> >> >
>> >> >> >> > root@beaglebone:/home/debian# 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
>> >> >> >> >  7: ff:P-O-L Override Board Name,00A0,Override
>> Manuf,BB-BONE-AUDI-02
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > What I did as root was edit /boot/uEnv.txt and uncomment the
>> audio
>> >> >> >> > cape
>> >> >> >> > lines so that it looks like this:
>> >> >> >> >
>> >> >> >> > #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:
>> >> >> >> > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
>> >> >> >> >
>> >> >> >> > uuid=c92d7bef-e149-4c25-83f4-fffb66c655cb
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > 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/d/optout.
>> >> >> >>
>> >> >> >> --
>> >> >> >

[beagleboard] Re: Folks at Embedded Linux Conf?

[Robert Nelson]

nerdboy, ds2 are around if you can find them. ;)

On Tue, Mar 24, 2015 at 5:59 PM, Drew Fustini  wrote:
> Anyone else here this in San Jose for Embedded Linux Conf?
>
> Nice plug for BeagleBone Black in Andrew Tridgell's keynote on Dronecode!
> Dronecode Project and Autopilot With Linux - Andrew Tridgell, Technical
> Steering Committee Chair of Dronecode Project
> http://elcabs2015.sched.org/mobile/#session:120a64c529ec466bfa916602c99316b3
>
> I believe Linux Foundation will be uploading video to YouTube after
> conference ends
>
> Cheers
> Drew
> 773-710-7131
> @pdp7



-- 
Robert Nelson
https://rcn-ee.com/

-- 
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/d/optout.

Re: [beagleboard] Re: Folks at Embedded Linux Conf?

[Bill Traynor]

Find the trolls.  Just ask ranostay

On Tue, Mar 24, 2015 at 7:10 PM, Robert Nelson  wrote:
> nerdboy, ds2 are around if you can find them. ;)
>
> On Tue, Mar 24, 2015 at 5:59 PM, Drew Fustini  wrote:
>> Anyone else here this in San Jose for Embedded Linux Conf?
>>
>> Nice plug for BeagleBone Black in Andrew Tridgell's keynote on Dronecode!
>> Dronecode Project and Autopilot With Linux - Andrew Tridgell, Technical
>> Steering Committee Chair of Dronecode Project
>> http://elcabs2015.sched.org/mobile/#session:120a64c529ec466bfa916602c99316b3
>>
>> I believe Linux Foundation will be uploading video to YouTube after
>> conference ends
>>
>> Cheers
>> Drew
>> 773-710-7131
>> @pdp7
>
>
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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/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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Folks at Embedded Linux Conf?

[Robert Nelson]

Yeah, Matt's presentation is at 5:25 (Blossom Hill), all the trolls
should be there..

On Tue, Mar 24, 2015 at 6:13 PM, Bill Traynor  wrote:
> Find the trolls.  Just ask ranostay
>
> On Tue, Mar 24, 2015 at 7:10 PM, Robert Nelson  
> wrote:
>> nerdboy, ds2 are around if you can find them. ;)
>>
>> On Tue, Mar 24, 2015 at 5:59 PM, Drew Fustini  wrote:
>>> Anyone else here this in San Jose for Embedded Linux Conf?
>>>
>>> Nice plug for BeagleBone Black in Andrew Tridgell's keynote on Dronecode!
>>> Dronecode Project and Autopilot With Linux - Andrew Tridgell, Technical
>>> Steering Committee Chair of Dronecode Project
>>> http://elcabs2015.sched.org/mobile/#session:120a64c529ec466bfa916602c99316b3
>>>
>>> I believe Linux Foundation will be uploading video to YouTube after
>>> conference ends
>>>
>>> Cheers
>>> Drew
>>> 773-710-7131
>>> @pdp7
>>
>>
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> 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/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 beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Robert Nelson
https://rcn-ee.com/

-- 
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/d/optout.

Re: [beagleboard] Re: Folks at Embedded Linux Conf?

[Bill Traynor]

Be sure to heckle!

On Tue, Mar 24, 2015 at 7:16 PM, Robert Nelson  wrote:
> Yeah, Matt's presentation is at 5:25 (Blossom Hill), all the trolls
> should be there..
>
> On Tue, Mar 24, 2015 at 6:13 PM, Bill Traynor  wrote:
>> Find the trolls.  Just ask ranostay
>>
>> On Tue, Mar 24, 2015 at 7:10 PM, Robert Nelson  
>> wrote:
>>> nerdboy, ds2 are around if you can find them. ;)
>>>
>>> On Tue, Mar 24, 2015 at 5:59 PM, Drew Fustini  wrote:
 Anyone else here this in San Jose for Embedded Linux Conf?

 Nice plug for BeagleBone Black in Andrew Tridgell's keynote on Dronecode!
 Dronecode Project and Autopilot With Linux - Andrew Tridgell, Technical
 Steering Committee Chair of Dronecode Project
 http://elcabs2015.sched.org/mobile/#session:120a64c529ec466bfa916602c99316b3

 I believe Linux Foundation will be uploading video to YouTube after
 conference ends

 Cheers
 Drew
 773-710-7131
 @pdp7
>>>
>>>
>>>
>>> --
>>> Robert Nelson
>>> https://rcn-ee.com/
>>>
>>> --
>>> 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/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 beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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/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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] So now that my serial port broke off...

[Peter Kurrasch]

So the solder keeping the DB9 serial port firmly connected to my 
BeagleBoard-xM finally failed and now I have a conundrum:

- BeagleBoard-X15 seems to be a couple months out still
- BeagleBoard-xM is no longer available through the regular channels 
(though one place said a new shipment was arriving in April 2018)
- I've never done surface-mount soldering before

It looks like my best chance is to find one on ebay or something, but does 
anyone have other ideas?  Perhaps the soldering isn't too bad?


Looking forward to the X15

-- 
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/d/optout.

Re: [beagleboard] Re: Folks at Embedded Linux Conf?

[William Hermans]

Just what we need. Yet another Intel presentation. Dont heckle though, just
wave a 6-pack at him from the audience . . .

On Tue, Mar 24, 2015 at 4:17 PM, Bill Traynor  wrote:

> Be sure to heckle!
>
> On Tue, Mar 24, 2015 at 7:16 PM, Robert Nelson 
> wrote:
> > Yeah, Matt's presentation is at 5:25 (Blossom Hill), all the trolls
> > should be there..
> >
> > On Tue, Mar 24, 2015 at 6:13 PM, Bill Traynor 
> wrote:
> >> Find the trolls.  Just ask ranostay
> >>
> >> On Tue, Mar 24, 2015 at 7:10 PM, Robert Nelson 
> wrote:
> >>> nerdboy, ds2 are around if you can find them. ;)
> >>>
> >>> On Tue, Mar 24, 2015 at 5:59 PM, Drew Fustini 
> wrote:
>  Anyone else here this in San Jose for Embedded Linux Conf?
> 
>  Nice plug for BeagleBone Black in Andrew Tridgell's keynote on
> Dronecode!
>  Dronecode Project and Autopilot With Linux - Andrew Tridgell,
> Technical
>  Steering Committee Chair of Dronecode Project
> 
> http://elcabs2015.sched.org/mobile/#session:120a64c529ec466bfa916602c99316b3
> 
>  I believe Linux Foundation will be uploading video to YouTube after
>  conference ends
> 
>  Cheers
>  Drew
>  773-710-7131
>  @pdp7
> >>>
> >>>
> >>>
> >>> --
> >>> Robert Nelson
> >>> https://rcn-ee.com/
> >>>
> >>> --
> >>> 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/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 beagleboard+unsubscr...@googlegroups.com.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> > --
> > Robert Nelson
> > https://rcn-ee.com/
> >
> > --
> > 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/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 beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BeableBone Black as 6LoWPAN Border Router

[janszymanski12345]

Hi,

 I am trying to setup BBB as Contiki-6LoWPAN Border Router following the 
instruction from here 
http://processors.wiki.ti.com/index.php/Contiki-6LOWPAN-BBB#IPv4_network 
As my network is IPv4 I need to install a number of packages according to 
instructions:
The problems I have:
1)

root@beaglebone:~/radvd/radvd-1.15# apt-get install libcheck-dev 
libdaemon-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libcheck-dev

2) after disabling Conman, I lost SSH
systemctl stop connman.service 
systemctl disable connman.service 

cat > /etc/network/interfaces < /etc/resolv.conf 

[beagleboard] Issue: Flashing latest image on to onboard eMMC

[Shyam D]

>
> Board: Beagle Bone Black RevC


i have downloaded the latest linux debain image and written the image to SD 
card via win32 image writer

now my problem is

when i press the boot button during powerup the booting happens from SD and 
further all leds lit at a time then they all go off and leds keep on 
glowing not following any pattern and i am able to login via ssh

i searched many guides in which they explain the same above process even to 
flash the on board eMMC, i was not able to see the current flashing status 
of write over eMMC (some said i can see it over UART(J2) but i dont have 
one now :( )

how to differentiate whether i am booted through SD / currently flashing 
> the eMMC (are both independent ? / or the OS done in background ?)


is there any special led pattern i can observe during the process of eMMC 
> flashing ?


i tried some different stuff also 

xz the_image_downloaded.img.xz  > /dev

-- 
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/d/optout.

[beagleboard] Unable to Flash the internal eMMC of BBB Rev C

[Shyam D]

>
> Board: Beagle Bone Black RevC


i have downloaded the latest linux debain image and written the image to SD 
card via win32 image writer

now my problem is

when i press the boot button during powerup the booting happens from SD and 
further all leds lit at a time then they all go off and leds keep on 
glowing not following any pattern and i am able to login via ssh

i searched many guides in which they explain the same above process even to 
flash the on board eMMC, i was not able to see the current flashing status 
of write over eMMC (some said i can see it over UART(J2) but i dont have 
one now :( )

how to differentiate whether i am booted through SD / currently flashing 
> the eMMC (are both independent ? / or the OS done in background ?)


is there any special led pattern i can observe during the process of eMMC 
> flashing ?


i tried some different stuff also, like after logging in via SSH i just 
brought the image.xz in to my /tmp folder of board and did the below

#dont know what is my eMMC block 0 or 1 :( , dont know will it damage or not
> $ xz the_image_downloaded.img.xz  > /dev/mmcblk0


-- 
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/d/optout.

Re: [beagleboard] Re: building a out-of-tree module on Beagle Bone Black

[Shyam D]

i simply decided to update my eMMC with latest flash will update after it, 
by the way i am facing some issues while flashing the on board eMMC ,* help 
me in the tread named:Unable to Flash the internal eMMC of BBB Rev C*

-- 
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/d/optout.

Re: [beagleboard] Unable to Flash the internal eMMC of BBB Rev C

[Robert Nelson]

On Tue, Mar 24, 2015 at 11:48 PM, Shyam D  wrote:
>> Board: Beagle Bone Black RevC
>
>
> i have downloaded the latest linux debain image and written the image to SD
> card via win32 image writer
>
> now my problem is
>
> when i press the boot button during powerup the booting happens from SD and
> further all leds lit at a time then they all go off and leds keep on glowing
> not following any pattern and i am able to login via ssh



and the name of the "file" you flashed to the eMMC was?

"unless" it specifically was called "eMMC-flasher" it's only going to
run standalone on the microSD. To change it to "flash" the eMMC read:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC

We had "5" different images released for "2015-03-01" each one is
identified by it's file name

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-03-01

Regards,
-- 
Robert Nelson
https://rcn-ee.com/

-- 
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/d/optout.

Re: [beagleboard] Unable to Flash the internal eMMC of BBB Rev C

[Shyam D]

bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz  was the image which i 
have put to SD 

 
On Wednesday, March 25, 2015 at 10:29:42 AM UTC+5:30, RobertCNelson wrote:
>
> On Tue, Mar 24, 2015 at 11:48 PM, Shyam D  > wrote: 
> >> Board: Beagle Bone Black RevC 
> > 
> > 
> > i have downloaded the latest linux debain image and written the image to 
> SD 
> > card via win32 image writer 
> > 
> > now my problem is 
> > 
> > when i press the boot button during powerup the booting happens from SD 
> and 
> > further all leds lit at a time then they all go off and leds keep on 
> glowing 
> > not following any pattern and i am able to login via ssh 
>
>  
>
> and the name of the "file" you flashed to the eMMC was? 
>
> "unless" it specifically was called "eMMC-flasher" it's only going to 
> run standalone on the microSD. To change it to "flash" the eMMC read: 
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC 
>
> We had "5" different images released for "2015-03-01" each one is 
> identified by it's file name 
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-03-01 
>
> Regards, 
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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/d/optout.

Re: [beagleboard] Unable to Flash the internal eMMC of BBB Rev C

[Robert Nelson]

On Wed, Mar 25, 2015 at 12:03 AM, Shyam D  wrote:
> bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz  was the image which i
> have put to SD

Then the image was working perfectly as it was required.

Issue closed, read the FAQ to convert to flasher... ;)

Regards,
-- 
Robert Nelson
https://rcn-ee.com/

-- 
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/d/optout.

Re: [beagleboard] Unable to Flash the internal eMMC of BBB Rev C

[Shyam D]

Flasher: (lxde)

Flasher: (console)
what is the difference between the both , by the way i have started to 
download the first

On Wednesday, March 25, 2015 at 10:33:46 AM UTC+5:30, Shyam D wrote:
>
> bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz  was the image which 
> i have put to SD 
>
>  
> On Wednesday, March 25, 2015 at 10:29:42 AM UTC+5:30, RobertCNelson wrote:
>>
>> On Tue, Mar 24, 2015 at 11:48 PM, Shyam D  wrote: 
>> >> Board: Beagle Bone Black RevC 
>> > 
>> > 
>> > i have downloaded the latest linux debain image and written the image 
>> to SD 
>> > card via win32 image writer 
>> > 
>> > now my problem is 
>> > 
>> > when i press the boot button during powerup the booting happens from SD 
>> and 
>> > further all leds lit at a time then they all go off and leds keep on 
>> glowing 
>> > not following any pattern and i am able to login via ssh 
>>
>>  
>>
>> and the name of the "file" you flashed to the eMMC was? 
>>
>> "unless" it specifically was called "eMMC-flasher" it's only going to 
>> run standalone on the microSD. To change it to "flash" the eMMC read: 
>>
>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC 
>>
>> We had "5" different images released for "2015-03-01" each one is 
>> identified by it's file name 
>>
>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-03-01 
>>
>> Regards, 
>> -- 
>> Robert Nelson 
>> https://rcn-ee.com/ 
>>
>

-- 
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/d/optout.

Re: [beagleboard] Unable to Flash the internal eMMC of BBB Rev C

[Shyam D]

Please don't close the issue, i did not understand your reply :) , please 
answer my questions 

On Wednesday, March 25, 2015 at 10:38:19 AM UTC+5:30, Shyam D wrote:
>
> Flasher: (lxde)
>
> Flasher: (console)
> what is the difference between the both , by the way i have started to 
> download the first
>
> On Wednesday, March 25, 2015 at 10:33:46 AM UTC+5:30, Shyam D wrote:
>>
>> bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz  was the image 
>> which i have put to SD 
>>
>>  
>> On Wednesday, March 25, 2015 at 10:29:42 AM UTC+5:30, RobertCNelson wrote:
>>>
>>> On Tue, Mar 24, 2015 at 11:48 PM, Shyam D  wrote: 
>>> >> Board: Beagle Bone Black RevC 
>>> > 
>>> > 
>>> > i have downloaded the latest linux debain image and written the image 
>>> to SD 
>>> > card via win32 image writer 
>>> > 
>>> > now my problem is 
>>> > 
>>> > when i press the boot button during powerup the booting happens from 
>>> SD and 
>>> > further all leds lit at a time then they all go off and leds keep on 
>>> glowing 
>>> > not following any pattern and i am able to login via ssh 
>>>
>>>  
>>>
>>> and the name of the "file" you flashed to the eMMC was? 
>>>
>>> "unless" it specifically was called "eMMC-flasher" it's only going to 
>>> run standalone on the microSD. To change it to "flash" the eMMC read: 
>>>
>>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC 
>>>
>>> We had "5" different images released for "2015-03-01" each one is 
>>> identified by it's file name 
>>>
>>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-03-01 
>>>
>>> Regards, 
>>> -- 
>>> Robert Nelson 
>>> https://rcn-ee.com/ 
>>>
>>

-- 
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/d/optout.