[beagleboard] Re: PRU Pin Mux

2014-05-20 Thread foreverska
Code never seems to work out of the box for me on these things.  Now that I 
have operational code looking at R31 I have issues putting the results int 
datamemory which is just absurd.  Here's the code:

#define CONST_PRUDRAM   C3
#define TOOTH_COUNTER   R5

lpe:
ADD TOOTH_COUNTER, TOOTH_COUNTER, 1
QBEQ lpe, r31, 0

SBCO TOOTH_COUNTER, CONST_PRUDRAM, 0, 4

I have also done this with SBBO pointed to 0x0 with no success.  In 
prudebugger R5 has a non zero value but the memory comes up as 0x0 in the 
debugger.  The C program I have agrees with the bugger's reported values on 
that value and surrounding values.  Is there a setup for the pru to access 
DM?  That feels absurd.  It is it's own local ram.

As an aside, a C program should be able to look down in dram and see 
registers at the 0x7000 offset right?  It looks empty to the bugger and my 
C program.  Or are those different registers than the R0-R31?

-- 
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] windows internet connection sharing - beagle connected to windows over usb

2014-05-20 Thread Eric Fort
could someone who has made this work actually describe how to do it?  My
windows laptop has an internet connection (over wireless).  that same
laptop (running windows 7) has a network connection over usb to the beagle
bone (part of what's auto configured when usb gets connected between the
bone and the windows box along with presenting the bone as an external
disk).  The bone shows up as 192.168.7.2/30 and the laptop as
192.168.7.1/30(adapter 2).  laptop adapter 5 is connected to the
internet via the house
router which issues it an address on network 192.168.1.0/24.

How can I setup Windows ICS such that the beagle connected via adapter 2
(network over usb) can  get to the internet connected via adapter 5 on the
windows box with windows routing between those networks and thus sharing
it's internet connection?  when I tried this using ICS I only succeeded in
really messing up the routing tables on the laptop which broke the laptop's
ability to get to the internet (it thought the beagle was now it's default
gateway) without letting the beagle access the internet.  (worst possible
outcome...)  So how can I configure ICS to give the beagle an internet
connection when it's usb is plugged in?

Thanks,

Eric

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Re: Here is the BeagleBone Debian (beta) image you want to test

2014-05-20 Thread Michael Duffy
Thanks, Robert.  Sorry for not searching in the "right" place.  Now I know.


On Tue, May 20, 2014 at 6:25 PM, Robert Nelson wrote:

> On Tue, May 20, 2014 at 8:01 PM, Robert Nelson 
> wrote:
> > On Tue, May 20, 2014 at 7:53 PM,   wrote:
> >> RobertCNelson:
> >>
> >> I am running 2014-05-14 debian (flasher), and I can reliably generate a
> >> kernel null pointer dereference using no more than
> >> /sys/devices/bone_capemgr.*/slots and
> /lib/firmware/BB-SPIDEV1-00A0.dtbo.
> >
> > Yes and No... You got a null pointer dereference when you "unloaded a
> > cape", which is a long time old known issue. The "only" way to
> > properly unload a cape is to reboot with the v3.8.x based kernel.
> >
> >> Any interest?  If so, please see:
> >> https://groups.google.com/forum/#!topic/beaglebone/RpozbQ0gGH0
> >
> > Ah, i see. So you guys are on the "other" forum, if you would have
> > searched the main one (this one) you would have seen this old issue
> > discussed a few times over the last year.
>
> to follow up:
>
> root@am335x-boneblack-512mb-0:/home/voodoo# uname -r
> 3.8.13-bone54
>
> root@am335x-boneblack-512mb-0:/home/voodoo# export
> SLOTS=/sys/devices/bone_capemgr.9/slots
> root@am335x-boneblack-512mb-0:/home/voodoo# cat $SLOTS
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-- 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-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>
> root@am335x-boneblack-512mb-0:/home/voodoo# echo BB-SPIDEV1 > $SLOTS
>
> [   96.506849] bone-capemgr bone_capemgr.9: part_number 'BB-SPIDEV1',
> version 'N/A'
> [   96.516565] bone-capemgr bone_capemgr.9: slot #7: generic override
> [   96.523225] bone-capemgr bone_capemgr.9: bone: Using override
> eeprom data at slot 7
> [   96.531389] bone-capemgr bone_capemgr.9: slot #7: 'Override Board
> Name,00A0,Override Manuf,BB-SPIDEV1'
> [   96.541719] bone-capemgr bone_capemgr.9: slot #7: Requesting part
> number/version based 'BB-SPIDEV1-00A0.dtbo
> [   96.552162] bone-capemgr bone_capemgr.9: slot #7: Requesting
> firmware 'BB-SPIDEV1-00A0.dtbo' for board-name 'Override Board Name',
> version '00A0'
> [   96.570136] bone-capemgr bone_capemgr.9: slot #7: dtbo
> 'BB-SPIDEV1-00A0.dtbo' loaded; converting to live tree
> [   96.581977] bone-capemgr bone_capemgr.9: slot #7: #2 overlays
> [   96.629134] edma-dma-engine edma-dma-engine.0: allocated channel for
> 0:45
> [   96.643245] edma-dma-engine edma-dma-engine.0: allocated channel for
> 0:44
> [   96.692195] edma-dma-engine edma-dma-engine.0: allocated channel for
> 0:43
> [   96.706484] edma-dma-engine edma-dma-engine.0: allocated channel for
> 0:42
> [   96.725354] bone-capemgr bone_capemgr.9: slot #7: Applied #2 overlays.
>
> root@am335x-boneblack-512mb-0:/home/voodoo# ls /dev/spidev1.*
> /dev/spidev1.0  /dev/spidev1.1
>
>
> works for me..
>
> Regards,
>
> --
> Robert Nelson
> http://www.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/VRqGZbXBK1Q/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: Here is the BeagleBone Debian (beta) image you want to test

2014-05-20 Thread Robert Nelson
On Tue, May 20, 2014 at 8:01 PM, Robert Nelson  wrote:
> On Tue, May 20, 2014 at 7:53 PM,   wrote:
>> RobertCNelson:
>>
>> I am running 2014-05-14 debian (flasher), and I can reliably generate a
>> kernel null pointer dereference using no more than
>> /sys/devices/bone_capemgr.*/slots and /lib/firmware/BB-SPIDEV1-00A0.dtbo.
>
> Yes and No... You got a null pointer dereference when you "unloaded a
> cape", which is a long time old known issue. The "only" way to
> properly unload a cape is to reboot with the v3.8.x based kernel.
>
>> Any interest?  If so, please see:
>> https://groups.google.com/forum/#!topic/beaglebone/RpozbQ0gGH0
>
> Ah, i see. So you guys are on the "other" forum, if you would have
> searched the main one (this one) you would have seen this old issue
> discussed a few times over the last year.

to follow up:

root@am335x-boneblack-512mb-0:/home/voodoo# uname -r
3.8.13-bone54

root@am335x-boneblack-512mb-0:/home/voodoo# export
SLOTS=/sys/devices/bone_capemgr.9/slots
root@am335x-boneblack-512mb-0:/home/voodoo# cat $SLOTS
 0: 54:PF---
 1: 55:PF---
 2: 56:PF---
 3: 57:PF---
 4: ff:P-O-- 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-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN

root@am335x-boneblack-512mb-0:/home/voodoo# echo BB-SPIDEV1 > $SLOTS

[   96.506849] bone-capemgr bone_capemgr.9: part_number 'BB-SPIDEV1',
version 'N/A'
[   96.516565] bone-capemgr bone_capemgr.9: slot #7: generic override
[   96.523225] bone-capemgr bone_capemgr.9: bone: Using override
eeprom data at slot 7
[   96.531389] bone-capemgr bone_capemgr.9: slot #7: 'Override Board
Name,00A0,Override Manuf,BB-SPIDEV1'
[   96.541719] bone-capemgr bone_capemgr.9: slot #7: Requesting part
number/version based 'BB-SPIDEV1-00A0.dtbo
[   96.552162] bone-capemgr bone_capemgr.9: slot #7: Requesting
firmware 'BB-SPIDEV1-00A0.dtbo' for board-name 'Override Board Name',
version '00A0'
[   96.570136] bone-capemgr bone_capemgr.9: slot #7: dtbo
'BB-SPIDEV1-00A0.dtbo' loaded; converting to live tree
[   96.581977] bone-capemgr bone_capemgr.9: slot #7: #2 overlays
[   96.629134] edma-dma-engine edma-dma-engine.0: allocated channel for 0:45
[   96.643245] edma-dma-engine edma-dma-engine.0: allocated channel for 0:44
[   96.692195] edma-dma-engine edma-dma-engine.0: allocated channel for 0:43
[   96.706484] edma-dma-engine edma-dma-engine.0: allocated channel for 0:42
[   96.725354] bone-capemgr bone_capemgr.9: slot #7: Applied #2 overlays.

root@am335x-boneblack-512mb-0:/home/voodoo# ls /dev/spidev1.*
/dev/spidev1.0  /dev/spidev1.1


works for me..

Regards,

-- 
Robert Nelson
http://www.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] PRU Pin Mux

2014-05-20 Thread foreverska
That did it.

Helpful as always Charles.

On Monday, May 19, 2014 11:58:55 PM UTC-5, Charles Steinkuehler wrote:
>
> On 5/19/2014 6:53 PM, foreverska wrote: 
> > debian@beaglebone:~/Desktop/riot/pru_test$ cat 
> > /sys/devices/bone_capemgr.9/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-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 
> > debian@beaglebone:~/Desktop/riot/pru_test$ config-pin overlay 
> cape-universal 
> > 
> > Loading cape-universal overlay 
> > bash: line 0: echo: write error: File exists 
> > Error loading device tree overlay file: cape-universal 
> > debian@beaglebone:~/Desktop/riot/pru_test$ 
>
> You have the full HDMI interface enabled, which includes the audio 
> signals.  You either need to load the cape-universaln overlay that 
> doesn't try to grab the audio lines, or disable HDMI (which allows the 
> HDMIN overlay without audio to load, leaving the audio pins free for 
> your use). 
>
> I need to make the code smarter so it looks to see if HDMI or HDMIN is 
> loaded and selects the proper overlay automatically. 
>
> > I am not concerned with HDMI at all so I am more than willing to turn 
> that 
> > off if need be but I'm not 100% on where to do that. 
>
> Edit /boot/uboot/uEnv.txt, and look for the optargs= line. 
>
> -- 
> Charles Steinkuehler 
> cha...@steinkuehler.net  
>

-- 
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: Here is the BeagleBone Debian (beta) image you want to test

2014-05-20 Thread Robert Nelson
On Tue, May 20, 2014 at 7:53 PM,   wrote:
> RobertCNelson:
>
> I am running 2014-05-14 debian (flasher), and I can reliably generate a
> kernel null pointer dereference using no more than
> /sys/devices/bone_capemgr.*/slots and /lib/firmware/BB-SPIDEV1-00A0.dtbo.

Yes and No... You got a null pointer dereference when you "unloaded a
cape", which is a long time old known issue. The "only" way to
properly unload a cape is to reboot with the v3.8.x based kernel.

> Any interest?  If so, please see:
> https://groups.google.com/forum/#!topic/beaglebone/RpozbQ0gGH0

Ah, i see. So you guys are on the "other" forum, if you would have
searched the main one (this one) you would have seen this old issue
discussed a few times over the last year.

Regards,

-- 
Robert Nelson
http://www.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.


[beagleboard] Re: Here is the BeagleBone Debian (beta) image you want to test

2014-05-20 Thread michael . duffy
*RobertCNelson*:

I am running 2014-05-14 debian (flasher), and I can reliably generate a 
kernel null pointer dereference using no more than 
/sys/devices/bone_capemgr.*/slots and /lib/firmware/BB-SPIDEV1-00A0.dtbo.

Any interest?  If so, please 
see: https://groups.google.com/forum/#!topic/beaglebone/RpozbQ0gGH0 

Thanks for any help.

-- 
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] Beaglebone Audio Cape Rev B audio Input

2014-05-20 Thread Raphael Philipe
Hey folks,

Thank you all for the support so far. I did it. Now it is working.

It's a shame to admit but It was the capture sound level that was too
low. I used alsamixer and entered in the capture tab (F4) and put all
the inputs in the highest level.

Regards,

On Tue, May 20, 2014 at 7:17 PM, John Syn  wrote:
>
> From: Eric Fort 
> Reply-To: 
> Date: Tuesday, May 20, 2014 at 2:13 PM
> To: beagleboard 
> Subject: Re: [beagleboard] Beaglebone Audio Cape Rev B audio Input
>
> in my use of audio and this card from the console I found alasmixer much
> easier to use.  I just went through and set all the levels to 100% and it
> works well.  Try using alsamixer it should get things fixed up in an easy
> and intuitive way.  F1 and the man page cover the controls.
>
> This is true, and if you run alsamixer in a SSH session, it looks much
> better than in a tty console like minicom.
>
> Regards,
> John
>
>
>
> Eric
>
>
> On Tue, May 20, 2014 at 3:40 AM, Raphael Philipe  wrote:
>>
>> It seems that I messed with the amixer parameters. Now I can not even
>> hear from the speaker test. Is there a way of reseting alsa
>> parameters, not only the general audio volume?
>>
>> I saw something like
>> alsactl restore -P
>> and removing '/var/lib/alsa/asound.state
>> but it didn't work for parameters specifically to the DA830 EVM.
>>
>> Why the audio cape is recognized as a DA830 EVM?
>>
>> I suspect that the audio input is not working due to one of that
>> parameters.
>>
>> Regards, Raphael.
>>
>> On Sun, May 18, 2014 at 8:22 PM, John Syn  wrote:
>> >
>> > From: Raphael Philipe 
>> > Reply-To: 
>> > Date: Sunday, May 18, 2014 at 3:30 PM
>> > To: 
>> > Subject: [beagleboard] Beaglebone Audio Cape Rev B audio Input
>> >
>> >
>> > Hi
>> >
>> > I've acquired an Audio Cape Rev B
>> > http://elinux.org/CircuitCo:Audio_Cape_RevB for my Beaglebone Black.
>> >
>> > Following the instructions I was able to make it work. The audio
>> > playback is
>> > working pretty well. However, I cannot test the audio input. I saw that
>> > it
>> > is a line level input (line in), so it cannot be connected to a regular
>> > microphone.
>> >
>> > I want to test it through an echo scheme. I will produce some sound
>> > through
>> > q source (connected to the line in input of the cape) and check the
>> > response
>> > in the audio output, through an earphone.
>> >
>> > I tried to connect the cape line in to the earphone output of an old
>> > cellphone through a male male jack cable (I saw in some forums that the
>> > line
>> > level is similar to the earphone output of some appliances, apart from
>> > the
>> > impedance difference.). Unfortunately, it didn't work.
>> >
>> > The interesting thing is that when the cable is connected to the cape
>> > audio
>> > input and the other connector is unplluged, I can hear the noise from
>> > static, similar to an unplugged to the amplifier electric guitar .
>> >
>> > Can someone suggest me a simple form to test the audio input?
>> >
>> > I don’t have the Audio Cape, but I do have a TLV320AIC3106EVM connected
>> > to
>> > my BBB and it works fine. You may want to try the following command:
>> >
>> > arecord -r 44100 -c 1 -f S16_LE -t wav -vv -d 25 example.wav
>> >
>> > This will show you a bar graph in the terminal so you can see the input
>> > levels. I would just connect the output from you phone to the line input
>> > of
>> > your audio cape. In another terminal, run amixer to adjust the input
>> > levels.
>> >
>> > Regards,
>> > John
>> >
>> >
>> > Regards.
>> >
>> > --
>> > 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.
>
>
> --
> 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 opti

Re: [beagleboard] Beaglebone Audio Cape Rev B audio Input

2014-05-20 Thread John Syn

From:  Eric Fort 
Reply-To:  
Date:  Tuesday, May 20, 2014 at 2:13 PM
To:  beagleboard 
Subject:  Re: [beagleboard] Beaglebone Audio Cape Rev B audio Input

> in my use of audio and this card from the console I found alasmixer much
> easier to use.  I just went through and set all the levels to 100% and it
> works well.  Try using alsamixer it should get things fixed up in an easy and
> intuitive way.  F1 and the man page cover the controls.
This is true, and if you run alsamixer in a SSH session, it looks much
better than in a tty console like minicom.

Regards,
John
> 
> 
> Eric
> 
> 
> On Tue, May 20, 2014 at 3:40 AM, Raphael Philipe  wrote:
>> It seems that I messed with the amixer parameters. Now I can not even
>> hear from the speaker test. Is there a way of reseting alsa
>> parameters, not only the general audio volume?
>> 
>> I saw something like
>> alsactl restore -P
>> and removing '/var/lib/alsa/asound.state
>> but it didn't work for parameters specifically to the DA830 EVM.
>> 
>> Why the audio cape is recognized as a DA830 EVM?
>> 
>> I suspect that the audio input is not working due to one of that parameters.
>> 
>> Regards, Raphael.
>> 
>> On Sun, May 18, 2014 at 8:22 PM, John Syn  wrote:
>>> >
>>> > From: Raphael Philipe 
>>> > Reply-To: 
>>> > Date: Sunday, May 18, 2014 at 3:30 PM
>>> > To: 
>>> > Subject: [beagleboard] Beaglebone Audio Cape Rev B audio Input
>>> >
>>> >
>>> > Hi
>>> >
>>> > I've acquired an Audio Cape Rev B
>>> > http://elinux.org/CircuitCo:Audio_Cape_RevB for my Beaglebone Black.
>>> >
>>> > Following the instructions I was able to make it work. The audio playback
>>> is
>>> > working pretty well. However, I cannot test the audio input. I saw that it
>>> > is a line level input (line in), so it cannot be connected to a regular
>>> > microphone.
>>> >
>>> > I want to test it through an echo scheme. I will produce some sound
>>> through
>>> > q source (connected to the line in input of the cape) and check the
>>> response
>>> > in the audio output, through an earphone.
>>> >
>>> > I tried to connect the cape line in to the earphone output of an old
>>> > cellphone through a male male jack cable (I saw in some forums that the
>>> line
>>> > level is similar to the earphone output of some appliances, apart from the
>>> > impedance difference.). Unfortunately, it didn't work.
>>> >
>>> > The interesting thing is that when the cable is connected to the cape
>>> audio
>>> > input and the other connector is unplluged, I can hear the noise from
>>> > static, similar to an unplugged to the amplifier electric guitar .
>>> >
>>> > Can someone suggest me a simple form to test the audio input?
>>> >
>>> > I don¹t have the Audio Cape, but I do have a TLV320AIC3106EVM connected to
>>> > my BBB and it works fine. You may want to try the following command:
>>> >
>>> > arecord -r 44100 -c 1 -f S16_LE -t wav -vv -d 25 example.wav
>>> >
>>> > This will show you a bar graph in the terminal so you can see the input
>>> > levels. I would just connect the output from you phone to the line input
>>> of
>>> > your audio cape. In another terminal, run amixer to adjust the input
>>> levels.
>>> >
>>> > Regards,
>>> > John
>>> >
>>> >
>>> > Regards.
>>> >
>>> > --
>>> > 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.
> 
> 
> -- 
> 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 me

[beagleboard] USB ports on RCN Debian 3.8

2014-05-20 Thread Ross Morrison

Hi all,

I'm looking for a little direction from someone who may have worked with 
the musb-hdrc drivers. I need to use RCN's 3.8 Debian kernel, but have 
build my custom board with my USB Host connected to USB1 pins on the 
Sitara (nothing connected to USB0). Unfortunately I've been told that 
the 3.8 kernel only supports one of the two ports on the Sitara, no 
problem, what changes to the driver or pin mux or whatever do I need to 
make to get it look at USB1 instead of USB0. Or, maybe this is 
impossible (I hope not).


dmesg from 3.15 RCN kernel
[2.406291] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver
[2.412764] musb-hdrc musb-hdrc.0.auto: new USB bus registered, 
assigned bus number 1

[2.421299] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[2.428463] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1

[2.436038] usb usb1: Product: MUSB HDRC host driver
[2.441256] usb usb1: Manufacturer: Linux 3.14.4-bone4 musb-hcd
[2.447473] usb usb1: SerialNumber: musb-hdrc.0.auto
[2.453384] hub 1-0:1.0: USB hub found
[2.457439] hub 1-0:1.0: 1 port detected
[2.465323] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[2.471771] musb-hdrc musb-hdrc.1.auto: new USB bus registered, 
assigned bus number 2

[2.480262] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[2.487410] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1

[2.494984] usb usb2: Product: MUSB HDRC host driver
[2.500203] usb usb2: Manufacturer: Linux 3.14.4-bone4 musb-hcd
[2.506409] usb usb2: SerialNumber: musb-hdrc.1.auto
[2.512326] hub 2-0:1.0: USB hub found
[2.516307] hub 2-0:1.0: 1 port detected
[2.520945] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[2.532874] Freeing unused kernel memory: 452K (c09cc000 - c0a3d000)
Loading, please wait...
[2.609684] udevd[88]: starting version 175
[2.916925] usb 2-1: new high-speed USB device number 2 using musb-hdrc
[3.080094] usb 2-1: device v0b95 p7720 is not supported
[3.085693] usb 2-1: New USB device found, idVendor=0b95, idProduct=7720
[3.092826] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[3.100344] usb 2-1: Product: AX88x72A
[3.104274] usb 2-1: Manufacturer: ASIX Elec. Corp.
[3.109409] usb 2-1: SerialNumber: 000341





(ignore the time stamps, this is something else I have a fix for allready)
dmesg from 3.8 RCN kernel
[   37.654699] USB Mass Storage support registered.
[   37.659747] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[   37.666361] musb-hdrc musb-hdrc.0.auto: pdev->id = 0
[   37.671593] musb-hdrc musb-hdrc.0.auto: 
drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK

[   37.680510] musb-hdrc musb-hdrc.0.auto: *** mode=3
[   37.685542] musb-hdrc musb-hdrc.0.auto: *** power=250
[   37.691380] musb-hdrc musb-hdrc.1.auto: pdev->id = 1
[   37.696612] musb-hdrc musb-hdrc.1.auto: 
drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK

[   37.705508] musb-hdrc musb-hdrc.1.auto: *** mode=1
[   37.710536] musb-hdrc musb-hdrc.1.auto: *** power=250
[   37.715829] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[   37.722099] musb-hdrc musb-hdrc.1.auto: new USB bus registered, 
assigned bus number 1

[   37.730460] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   37.737578] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1

[   37.745139] usb usb1: Product: MUSB HDRC host driver
[   37.750340] usb usb1: Manufacturer: Linux 3.8.13-bone53 musb-hcd
[   37.756627] usb usb1: SerialNumber: musb-hdrc.1.auto
[   37.762765] hub 1-0:1.0: USB hub found
[   37.766764] hub 1-0:1.0: 1 port detected

Thanks for any suggestions.

Ross


--
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] Beaglebone Audio Cape Rev B audio Input

2014-05-20 Thread Eric Fort
in my use of audio and this card from the console I found alasmixer much
easier to use.  I just went through and set all the levels to 100% and it
works well.  Try using alsamixer it should get things fixed up in an easy
and intuitive way.  F1 and the man page cover the controls.

Eric


On Tue, May 20, 2014 at 3:40 AM, Raphael Philipe  wrote:

> It seems that I messed with the amixer parameters. Now I can not even
> hear from the speaker test. Is there a way of reseting alsa
> parameters, not only the general audio volume?
>
> I saw something like
> alsactl restore -P
> and removing '/var/lib/alsa/asound.state
> but it didn't work for parameters specifically to the DA830 EVM.
>
> Why the audio cape is recognized as a DA830 EVM?
>
> I suspect that the audio input is not working due to one of that
> parameters.
>
> Regards, Raphael.
>
> On Sun, May 18, 2014 at 8:22 PM, John Syn  wrote:
> >
> > From: Raphael Philipe 
> > Reply-To: 
> > Date: Sunday, May 18, 2014 at 3:30 PM
> > To: 
> > Subject: [beagleboard] Beaglebone Audio Cape Rev B audio Input
> >
> >
> > Hi
> >
> > I've acquired an Audio Cape Rev B
> > http://elinux.org/CircuitCo:Audio_Cape_RevB for my Beaglebone Black.
> >
> > Following the instructions I was able to make it work. The audio
> playback is
> > working pretty well. However, I cannot test the audio input. I saw that
> it
> > is a line level input (line in), so it cannot be connected to a regular
> > microphone.
> >
> > I want to test it through an echo scheme. I will produce some sound
> through
> > q source (connected to the line in input of the cape) and check the
> response
> > in the audio output, through an earphone.
> >
> > I tried to connect the cape line in to the earphone output of an old
> > cellphone through a male male jack cable (I saw in some forums that the
> line
> > level is similar to the earphone output of some appliances, apart from
> the
> > impedance difference.). Unfortunately, it didn't work.
> >
> > The interesting thing is that when the cable is connected to the cape
> audio
> > input and the other connector is unplluged, I can hear the noise from
> > static, similar to an unplugged to the amplifier electric guitar .
> >
> > Can someone suggest me a simple form to test the audio input?
> >
> > I don't have the Audio Cape, but I do have a TLV320AIC3106EVM connected
> to
> > my BBB and it works fine. You may want to try the following command:
> >
> > arecord -r 44100 -c 1 -f S16_LE -t wav -vv -d 25 example.wav
> >
> > This will show you a bar graph in the terminal so you can see the input
> > levels. I would just connect the output from you phone to the line input
> of
> > your audio cape. In another terminal, run amixer to adjust the input
> levels.
> >
> > Regards,
> > John
> >
> >
> > Regards.
> >
> > --
> > 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.
>

-- 
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: USB Connection issue

2014-05-20 Thread Matt Saraceno
ok one more thing i am on a mac and have downloaded all of the drivers, and 
that i have been able to connect via the network, for some reason anything 
to do with the screen command doesnt work

On Tuesday, May 20, 2014 4:27:09 PM UTC-4, Matt Saraceno wrote:
>
> Ok, I am trying out my first BBB, and every video show when you type in 
> your ssh terminal /dev/tty.usb*B 115200 it runs the linux, for me that 
> doesn't happen it say no such file or directory called "/dev/tty.usb*A 
> 115200". I have not updated the disk image yet, is that a solution anything 
> will help.
>
>

-- 
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] How to enable SSH in Single-user-mode(runlevel 1) ?

2014-05-20 Thread Sid Boyce

ssh requires networking to be active which it isn't in runlevel 1.
Regards
Sid.

On 20/05/14 00:50, Yiwei Zhang wrote:


Environment: ubuntu-precise-12.04 on Beaglebone Black, no GUI

1.

System hang when I did "init 1" or "telinit 1". Commandline just
stuck there.

2.

How to enable ssh service in single user mode? Since I just stuck
on step 1, so I don't know the following steps are correct or not.
I just add a new script to /etc/rc1.d/ directory which runs all
the scripts inside in run level 1. The script is "start ssh" or
"service ssh start" or "/etc/init.d/ssh start".

3.

If the first two steps are done, how could I ssh into the system?
In single user mode, what's the user name for the system? In
default run level 2, the user name is: ubuntu, with password:
ubuntu. If I just type ssh ip address, it will use the user name
of my Macbook by default. And I don't think ssh ubuntu@ip_address
will work...

Sincerely

--
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.



--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

--
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] Beaglebone Audio Cape Rev B audio Input

2014-05-20 Thread John Syn

On 5/20/14, 3:40 AM, "Raphael Philipe"  wrote:

>It seems that I messed with the amixer parameters. Now I can not even
>hear from the speaker test. Is there a way of reseting alsa
>parameters, not only the general audio volume?
>
>I saw something like
>alsactl restore -P
>and removing '/var/lib/alsa/asound.state
To restart alsa-utils, do the following:

invoke-rc.d alsa-utils restart

Regards,
John
>but it didn't work for parameters specifically to the DA830 EVM.
>
>Why the audio cape is recognized as a DA830 EVM?
>
>I suspect that the audio input is not working due to one of that
>parameters.
>
>Regards, Raphael.
>
>On Sun, May 18, 2014 at 8:22 PM, John Syn  wrote:
>>
>> From: Raphael Philipe 
>> Reply-To: 
>> Date: Sunday, May 18, 2014 at 3:30 PM
>> To: 
>> Subject: [beagleboard] Beaglebone Audio Cape Rev B audio Input
>>
>>
>> Hi
>>
>> I've acquired an Audio Cape Rev B
>> http://elinux.org/CircuitCo:Audio_Cape_RevB for my Beaglebone Black.
>>
>> Following the instructions I was able to make it work. The audio
>>playback is
>> working pretty well. However, I cannot test the audio input. I saw that
>>it
>> is a line level input (line in), so it cannot be connected to a regular
>> microphone.
>>
>> I want to test it through an echo scheme. I will produce some sound
>>through
>> q source (connected to the line in input of the cape) and check the
>>response
>> in the audio output, through an earphone.
>>
>> I tried to connect the cape line in to the earphone output of an old
>> cellphone through a male male jack cable (I saw in some forums that the
>>line
>> level is similar to the earphone output of some appliances, apart from
>>the
>> impedance difference.). Unfortunately, it didn't work.
>>
>> The interesting thing is that when the cable is connected to the cape
>>audio
>> input and the other connector is unplluged, I can hear the noise from
>> static, similar to an unplugged to the amplifier electric guitar .
>>
>> Can someone suggest me a simple form to test the audio input?
>>
>> I don¹t have the Audio Cape, but I do have a TLV320AIC3106EVM connected
>>to
>> my BBB and it works fine. You may want to try the following command:
>>
>> arecord -r 44100 -c 1 -f S16_LE -t wav -vv -d 25 example.wav
>>
>> This will show you a bar graph in the terminal so you can see the input
>> levels. I would just connect the output from you phone to the line
>>input of
>> your audio cape. In another terminal, run amixer to adjust the input
>>levels.
>>
>> Regards,
>> John
>>
>>
>> Regards.
>>
>> --
>> 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.


-- 
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] USB Connection issue

2014-05-20 Thread Matt Saraceno
Ok, I am trying out my first BBB, and every video show when you type in 
your ssh terminal /dev/tty.usb*B 115200 it runs the linux, for me that 
doesn't happen it say no such file or directory called "/dev/tty.usb*A 
115200". I have not updated the disk image yet, is that a solution anything 
will help.

-- 
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] Beaglebone Audio Cape Rev B audio Input

2014-05-20 Thread John Syn

On 5/20/14, 3:40 AM, "Raphael Philipe"  wrote:

>It seems that I messed with the amixer parameters. Now I can not even
>hear from the speaker test. Is there a way of reseting alsa
>parameters, not only the general audio volume?
>
>I saw something like
>alsactl restore -P
>and removing '/var/lib/alsa/asound.state
After this, you need to restart alsa-utils. Also make sure you don¹t have
.asoundrc in your home folder.

>but it didn't work for parameters specifically to the DA830 EVM.
>
>Why the audio cape is recognized as a DA830 EVM?
The TLV320AIC3xxx codec is recognized as a DA830 EVM. If you look in the
audio cape DTS file, you will see ti,model = ³DA830 EVM².

Regards,
John
>
>I suspect that the audio input is not working due to one of that
>parameters.
>
>Regards, Raphael.
>
>On Sun, May 18, 2014 at 8:22 PM, John Syn  wrote:
>>
>> From: Raphael Philipe 
>> Reply-To: 
>> Date: Sunday, May 18, 2014 at 3:30 PM
>> To: 
>> Subject: [beagleboard] Beaglebone Audio Cape Rev B audio Input
>>
>>
>> Hi
>>
>> I've acquired an Audio Cape Rev B
>> http://elinux.org/CircuitCo:Audio_Cape_RevB for my Beaglebone Black.
>>
>> Following the instructions I was able to make it work. The audio
>>playback is
>> working pretty well. However, I cannot test the audio input. I saw that
>>it
>> is a line level input (line in), so it cannot be connected to a regular
>> microphone.
>>
>> I want to test it through an echo scheme. I will produce some sound
>>through
>> q source (connected to the line in input of the cape) and check the
>>response
>> in the audio output, through an earphone.
>>
>> I tried to connect the cape line in to the earphone output of an old
>> cellphone through a male male jack cable (I saw in some forums that the
>>line
>> level is similar to the earphone output of some appliances, apart from
>>the
>> impedance difference.). Unfortunately, it didn't work.
>>
>> The interesting thing is that when the cable is connected to the cape
>>audio
>> input and the other connector is unplluged, I can hear the noise from
>> static, similar to an unplugged to the amplifier electric guitar .
>>
>> Can someone suggest me a simple form to test the audio input?
>>
>> I don¹t have the Audio Cape, but I do have a TLV320AIC3106EVM connected
>>to
>> my BBB and it works fine. You may want to try the following command:
>>
>> arecord -r 44100 -c 1 -f S16_LE -t wav -vv -d 25 example.wav
>>
>> This will show you a bar graph in the terminal so you can see the input
>> levels. I would just connect the output from you phone to the line
>>input of
>> your audio cape. In another terminal, run amixer to adjust the input
>>levels.
>>
>> Regards,
>> John
>>
>>
>> Regards.
>>
>> --
>> 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.


-- 
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] help getting audio cape rev b1 working

2014-05-20 Thread Raphael Philipe
I had a similar issue with this. I had to change this commands a little.

export SLOTS=`ls /sys/devices/bone_capemgr.*/slots`
echo BB-BONE-AUDI-02 > $SLOTS

Regards,

On Tue, May 20, 2014 at 4:26 PM, John Syn  wrote:
>
> From: Eric Fort 
> Reply-To: 
> Date: Monday, May 19, 2014 at 11:21 PM
> To: beagleboard 
> Subject: Re: [beagleboard] help getting audio cape rev b1 working
>
> John,
>
> here's what happens when I use your .dts file:
>
> root@beaglebone:~# export SLOTS=/sys/devices/bone_capemgr.*/slots
> root@beaglebone:~# echo BB-BONE-AUDI-02 > $SLOTS
> -bash: echo: write error: Invalid argument
>
> That is very strange. How did you compile the audio cape DTS? I just place
> it in the firmware/cape folder and updated the makefile so that it is
> compiled when I build the kernel.
>
> Regards,
> John
>
>
>
> and when I use the one linked to in the instructions
> (http://elinux.org/images/1/10/BB-BONE-AUDI-02-00A0.zip) - yes I extracted
> the file from the zip archive first...):
>
> root@beaglebone:~# export SLOTS=/sys/devices/bone_capemgr.*/slots
> root@beaglebone:~# echo BB-BONE-AUDI-02 > $SLOTS
>
> (no errors)
>
> Thanks,
>
> Eric
>
>
>
>
> On Mon, May 19, 2014 at 7:09 PM, John Syn  wrote:
>>
>>
>> From: Eric Fort 
>> Reply-To: 
>> Date: Monday, May 19, 2014 at 6:56 PM
>> To: beagleboard 
>> Subject: [beagleboard] help getting audio cape rev b1 working
>>
>> I have followed the instructions found at
>> http://elinux.org/CircuitCo:Audio_Cape_RevB#Audio_Cape_Revision_B1 and I'm
>> just getting static when I try speaker-test -f 600 or aplay filename.wav.
>> the wav file plays fine on my windows laptop and aplay identifies it
>> properly but just static for audio.  what may I have missed?
>>
>> Try the attached DTO. I generated this myself before Circuitco published
>> theirs. When Circuitco published their DTO I described what I thought were
>> problems but no one responded.
>>
>> Regards,
>> John
>>
>>
>>
>> here's dmesg:
>>
>> root@beaglebone:~# dmesg|tail
>> [ 1088.018924] bone-capemgr bone_capemgr.8: slot #4: Requesting firmware
>> 'BB-BONE-AUDI-02-00A0.dtbo' for board-name 'Override Board Name', version
>> '00A0'
>> [ 1088.028213] bone-capemgr bone_capemgr.8: slot #4: dtbo
>> 'BB-BONE-AUDI-02-00A0.dtbo' loaded; converting to live tree
>> [ 1088.029031] bone-capemgr bone_capemgr.8: slot #4: #4 overlays
>> [ 1088.059524] of_get_named_gpio_flags: can't parse gpios property
>> [ 1088.071612] 1-0018 supply IOVDD not found, using dummy regulator
>> [ 1088.071867] 1-0018 supply DVDD not found, using dummy regulator
>> [ 1088.072049] 1-0018 supply AVDD not found, using dummy regulator
>> [ 1088.072277] 1-0018 supply DRVDD not found, using dummy regulator
>> [ 1088.098289] davinci_evm sound.10:  tlv320aic3x-hifi <-> 48038000.mcasp
>> mapping ok
>> [ 1088.134015] bone-capemgr bone_capemgr.8: slot #4: Applied #4 overlays.
>>
>> and a listing of slots showing the card:
>>
>> root@beaglebone:~# cat /sys/devices/bone_capemgr.*/slots
>>  0: 54:PF---
>>  1: 55:PF---
>>  2: 56:PF---
>>  3: 57:PF---
>>  4: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02
>>
>>
>> Thanks,
>>
>> Eric
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to 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.
>
> --
> 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] help getting audio cape rev b1 working

2014-05-20 Thread John Syn

From:  Eric Fort 
Reply-To:  
Date:  Monday, May 19, 2014 at 11:21 PM
To:  beagleboard 
Subject:  Re: [beagleboard] help getting audio cape rev b1 working

> John,
> 
> here's what happens when I use your .dts file:
> 
> root@beaglebone:~# export SLOTS=/sys/devices/bone_capemgr.*/slots
> root@beaglebone:~# echo BB-BONE-AUDI-02 > $SLOTS
> -bash: echo: write error: Invalid argument
That is very strange. How did you compile the audio cape DTS? I just place
it in the firmware/cape folder and updated the makefile so that it is
compiled when I build the kernel.

Regards, 
John
> 
> 
> and when I use the one linked to in the instructions
> (http://elinux.org/images/1/10/BB-BONE-AUDI-02-00A0.zip) - yes I extracted the
> file from the zip archive first...):
> 
> root@beaglebone:~# export SLOTS=/sys/devices/bone_capemgr.*/slots
> root@beaglebone:~# echo BB-BONE-AUDI-02 > $SLOTS
> 
> (no errors)
> 
> Thanks,
> 
> Eric
> 
> 
> 
> 
> On Mon, May 19, 2014 at 7:09 PM, John Syn  wrote:
>> 
>> From:  Eric Fort 
>> Reply-To:  
>> Date:  Monday, May 19, 2014 at 6:56 PM
>> To:  beagleboard 
>> Subject:  [beagleboard] help getting audio cape rev b1 working
>> 
>>> I have followed the instructions found at
>>> http://elinux.org/CircuitCo:Audio_Cape_RevB#Audio_Cape_Revision_B1 and I'm
>>> just getting static when I try speaker-test -f 600 or aplay filename.wav.
>>> the wav file plays fine on my windows laptop and aplay identifies it
>>> properly but just static for audio.  what may I have missed?
>> Try the attached DTO. I generated this myself before Circuitco published
>> theirs. When Circuitco published their DTO I described what I thought were
>> problems but no one responded.
>> 
>> Regards,
>> John
>>> 
>>> 
>>> here's dmesg:
>>> 
>>> root@beaglebone:~# dmesg|tail
>>> [ 1088.018924] bone-capemgr bone_capemgr.8: slot #4: Requesting firmware
>>> 'BB-BONE-AUDI-02-00A0.dtbo' for board-name 'Override Board Name', version
>>> '00A0'
>>> [ 1088.028213] bone-capemgr bone_capemgr.8: slot #4: dtbo
>>> 'BB-BONE-AUDI-02-00A0.dtbo' loaded; converting to live tree
>>> [ 1088.029031] bone-capemgr bone_capemgr.8: slot #4: #4 overlays
>>> [ 1088.059524] of_get_named_gpio_flags: can't parse gpios property
>>> [ 1088.071612] 1-0018 supply IOVDD not found, using dummy regulator
>>> [ 1088.071867] 1-0018 supply DVDD not found, using dummy regulator
>>> [ 1088.072049] 1-0018 supply AVDD not found, using dummy regulator
>>> [ 1088.072277] 1-0018 supply DRVDD not found, using dummy regulator
>>> [ 1088.098289] davinci_evm sound.10:  tlv320aic3x-hifi <-> 48038000.mcasp
>>> mapping ok
>>> [ 1088.134015] bone-capemgr bone_capemgr.8: slot #4: Applied #4 overlays.
>>> 
>>> and a listing of slots showing the card:
>>> 
>>> root@beaglebone:~# cat /sys/devices/bone_capemgr.*/slots
>>>  0: 54:PF---
>>>  1: 55:PF---
>>>  2: 56:PF---
>>>  3: 57:PF---
>>>  4: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02
>>> 
>>> 
>>> Thanks,
>>> 
>>> Eric
>>> 
>>> -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed to the Google Groups
>>> "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to 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.


-- 
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] Debian, GraphicsSDK and Qt 4.8.6 problems

2014-05-20 Thread Marcel von Kannen
Hi,
the last days were more or less successful. I've got Qt 5.1.1 on kernel 
v3.12 running. But there's no input device support and also no good cape 
support. So I'll take distance to Qt 5 and specialize to Qt 4.8.6 with 
kernel 3.8 (Robert Nelson, linux-dev).

In your link to the TI forums, on the second last site, there was somebody 
able to run Qt 4.8.5 with kernel v3.8. He provided 3 patches, which seems 
to me like they're implemented in Roberts repository. So I should have 
nothing to do there.
Next, I've downloaded the Graphics SDK 4.10.00.01 from 
http://downloads.ti.com/dsps/dsps_public_sw/gfxsdk/4_10_00_01/index_FDS.html 
(full package), installed it and adjusted the Rules to use the KERNEL 
directory and the same toolchain which was downloaded by Robert's kernel 
build script (linaro 3.8, hardfp). After the compilation was done without 
any errors, I've copied the created /etc and /opt folder to my BBB and ran 
the installation script. 
Unfortunately it doesn't load the omaplfb kernel module (can't remember the 
exactly error message, it was something meaningless like "error loading 
omaplfb").

I'm going to re-setup my Beaglebone Black now with the above mentioned 
settings, because actually there's kernel v3.12 running. Then I'm able to 
provide better error messages and details. But for all of that, maybe 
someone found an mistake in my procedure and can say what's wrong (so I 
don't recompile all the things now for the birds).


Many many thanks!

Regards,
Marcel

Am Montag, 19. Mai 2014 01:14:07 UTC+2 schrieb john3909:
>
>
> From: Marcel von Kannen >
> Reply-To: >
> Date: Sunday, May 18, 2014 at 1:54 PM
> To: >
> Subject: Re: [beagleboard] Debian, GraphicsSDK and Qt 4.8.6 problems
>
> Hi, thanks for your response!
>
> I've read that Qt 5 only supports one window at a time. That's why I want 
> to use Qt 4.8 with QWS. Or is my information wrong? If it's wrong, I could 
> of course switch to Qt 5. 
>
> I think what you need is xorg support which isn’t available for current 
> release of SGX running on V3.8 or V3.12.  
>
> http://e2e.ti.com/support/arm/sitara_arm/f/791/t/298596.aspx?pi301021=1
>
> I haven’t tried this myself, but perhaps you should try Wayland which is a 
> windows manager that works with QT. 
>
>
> I'm even not sure if kernel v3.12 is right for me - because I need to 
> activate the CAN bus with DTS, which isn't good supported in this kernel. 
> I'd prefer to use kernel v3.8, but there is no sgx support. (Nontheless, 
> currently I only want to run a Qt OpenGL application, no matter which 
> kernel)
>
> There is SGX support in V3.8.
>
>
> https://github.com/RobertCNelson/linux-dev/commit/c29ded356595c216ab534417f44528c27464
>
> Regards,
> John
>
>
> Cheers,
> Marcel
>
> Am Sonntag, 18. Mai 2014 22:23:58 UTC+2 schrieb john3909:
>
>> From: Marcel von Kannen 
>> Reply-To: 
>> Date: Sunday, May 18, 2014 at 3:37 AM
>> To: 
>> Subject: [beagleboard] Debian, GraphicsSDK and Qt 4.8.6 problems
>>
>> Hi,
>> I'm trying since some days to run a Qt OpenGL ES example application on 
>> my Beaglebone Black.
>>
>> I'm using the latest debian image from beagleboard.org with the 3.12 
>> kernel from Robert C Nelson's linux-dev repository. The Graphics SDK was 
>> downloaded and compiled by the sgx-build-modules.sh script (which is also 
>> provided in the git repository from Robert). I copied the sgx folders to 
>> /opt on the BBB and ran the sgx-install script, which setups and loads the 
>> pvrsrv and omaplfb modules. The sgx graphic examples (EvilSkull, 
>> ChameleonMan, etc.) run like a charm. (Before compilation I had to change 
>> this line 
>> https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.12/sgx_build_modules.sh#L272
>>  from 
>> "no" to "yes", otherwise there is a EGL error when I want to start a 
>> graphics sdk example)
>>
>> Now I want to compile Qt-4.8.6 applications with OpenGL ES support. I 
>> changed my qws mkspec to use OpenGL and use the same compiler which was 
>> used for compiling the kernel and the Graphics SDK 
>> (gcc-linaro-arm-linux-gnueabihf-4.8-2013.10_linux). Also I had to apply 
>> these two patches: 
>> https://github.com/prabindh/qt-configs/tree/master/qt4.8
>>
>> My configure directive is:
>>
>> ./configure -v -opensource -confirm-license -prefix /opt/qt -embedded arm 
>> -platform qws/linux-x86-g++ -xplatform qws/linux-TIarmv7-sgx-g++ -depths 
>> 16,24,32 -no-mmx -no-3dnow -no-sse -no-sse2 -no-ssse3 -no-glib -no-cups 
>> -no-largefile -no-accessibility -no-openssl -no-gtkstyle -qt-mouse-pc 
>> -qt-mouse-linuxtp -qt-mouse-linuxinput -plugin-mouse-linuxtp 
>> -plugin-mouse-pc -fast -little-endian -host-big-endian -no-pch 
>> -no-sql-ibase -no-sql-mysql -no-sql-odbc -no-sql-psql -no-sql-sqlite 
>> -no-sql-sqlite2 -no-webkit -no-qt3support -nomake demos -nomake docs 
>> -nomake translations -qt-mouse-tslib -opengl es2 -qt-gfx-linuxfb 
>> -plugin-gfx-powervr 
>> -D QT_NO_QWS_CURSOR -D QT_QWS_CLIENTBLIT 
>>
>>
>> After make install I'm copying the ex

Re: [beagleboard] help getting audio cape rev b1 working

2014-05-20 Thread John Syn

From:  Eric Fort 
Reply-To:  
Date:  Monday, May 19, 2014 at 9:01 PM
To:  beagleboard 
Subject:  Re: [beagleboard] help getting audio cape rev b1 working

> What LED's are you referring to?  the audio board has no LED's.
I don¹t know since I don¹t have an audio cape. The audio cape DTS refers to
two LEDs on the board.

Regards,
John
> 
> 
> Eric
> 
> 
> 
> On Mon, May 19, 2014 at 7:18 PM, John Syn  wrote:
>> 
>> From:  Eric Fort 
>> Reply-To:  
>> Date:  Monday, May 19, 2014 at 6:56 PM
>> To:  beagleboard 
>> Subject:  [beagleboard] help getting audio cape rev b1 working
>> 
>>> I have followed the instructions found at
>>> http://elinux.org/CircuitCo:Audio_Cape_RevB#Audio_Cape_Revision_B1 and I'm
>>> just getting static when I try speaker-test -f 600 or aplay filename.wav.
>>> the wav file plays fine on my windows laptop and aplay identifies it
>>> properly but just static for audio.  what may I have missed?
>> BTW, I don¹t have the LEDs defined in my DTO so you will have to add those
>> back in to my DTO if you want those to work.
>> 
>> Regards,
>> John
>>> 
>>> 
>>> here's dmesg:
>>> 
>>> root@beaglebone:~# dmesg|tail
>>> [ 1088.018924] bone-capemgr bone_capemgr.8: slot #4: Requesting firmware
>>> 'BB-BONE-AUDI-02-00A0.dtbo' for board-name 'Override Board Name', version
>>> '00A0'
>>> [ 1088.028213] bone-capemgr bone_capemgr.8: slot #4: dtbo
>>> 'BB-BONE-AUDI-02-00A0.dtbo' loaded; converting to live tree
>>> [ 1088.029031] bone-capemgr bone_capemgr.8: slot #4: #4 overlays
>>> [ 1088.059524] of_get_named_gpio_flags: can't parse gpios property
>>> [ 1088.071612] 1-0018 supply IOVDD not found, using dummy regulator
>>> [ 1088.071867] 1-0018 supply DVDD not found, using dummy regulator
>>> [ 1088.072049] 1-0018 supply AVDD not found, using dummy regulator
>>> [ 1088.072277] 1-0018 supply DRVDD not found, using dummy regulator
>>> [ 1088.098289] davinci_evm sound.10:  tlv320aic3x-hifi <-> 48038000.mcasp
>>> mapping ok
>>> [ 1088.134015] bone-capemgr bone_capemgr.8: slot #4: Applied #4 overlays.
>>> 
>>> and a listing of slots showing the card:
>>> 
>>> root@beaglebone:~# cat /sys/devices/bone_capemgr.*/slots
>>>  0: 54:PF---
>>>  1: 55:PF---
>>>  2: 56:PF---
>>>  3: 57:PF---
>>>  4: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02
>>> 
>>> 
>>> Thanks,
>>> 
>>> Eric
>>> 
>>> -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed to the Google Groups
>>> "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to 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.


-- 
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] help getting audio cape rev b1 working

2014-05-20 Thread John Syn


From:  Eric Fort 
Reply-To:  
Date:  Tuesday, May 20, 2014 at 12:27 AM
To:  beagleboard 
Subject:  Re: [beagleboard] help getting audio cape rev b1 working

> ok, 
> 
> seems the issue was one related to software and expectations and maybe a
> messed up debian install.  when I entered the command 'speaker-test -c2 -f600
> I expected a 600hz tone... I got white noise - but paying close attention to
> the text output, it said it was playing noise.  starting with a freshly imaged
> card and following the instructions from there seems to have it working with
> the files linked from the instructions.  Note to the designers of this cape -
> adding a stereo audio amp to drive headphones to a bit higher level would be
> extremely welcome.
Use amixer to increase the volume.

Regards,
John
> 
> 
> Eric
> 
> 
> On Mon, May 19, 2014 at 11:21 PM, Eric Fort  wrote:
>> John,
>> 
>> here's what happens when I use your .dts file:
>> 
>> root@beaglebone:~# export SLOTS=/sys/devices/bone_capemgr.*/slots
>> root@beaglebone:~# echo BB-BONE-AUDI-02 > $SLOTS
>> -bash: echo: write error: Invalid argument
>> 
>> and when I use the one linked to in the instructions
>> (http://elinux.org/images/1/10/BB-BONE-AUDI-02-00A0.zip) - yes I extracted
>> the file from the zip archive first...):
>> 
>> root@beaglebone:~# export SLOTS=/sys/devices/bone_capemgr.*/slots
>> root@beaglebone:~# echo BB-BONE-AUDI-02 > $SLOTS
>> 
>> (no errors)
>> 
>> Thanks,
>> 
>> Eric
>> 
>> 
>> 
>> 
>> On Mon, May 19, 2014 at 7:09 PM, John Syn  wrote:
>>> 
>>> From:  Eric Fort 
>>> Reply-To:  
>>> Date:  Monday, May 19, 2014 at 6:56 PM
>>> To:  beagleboard 
>>> Subject:  [beagleboard] help getting audio cape rev b1 working
>>> 
 I have followed the instructions found at
 http://elinux.org/CircuitCo:Audio_Cape_RevB#Audio_Cape_Revision_B1 and I'm
 just getting static when I try speaker-test -f 600 or aplay filename.wav.
 the wav file plays fine on my windows laptop and aplay identifies it
 properly but just static for audio.  what may I have missed?
>>> Try the attached DTO. I generated this myself before Circuitco published
>>> theirs. When Circuitco published their DTO I described what I thought were
>>> problems but no one responded.
>>> 
>>> Regards,
>>> John
 
 
 here's dmesg:
 
 root@beaglebone:~# dmesg|tail
 [ 1088.018924] bone-capemgr bone_capemgr.8: slot #4: Requesting firmware
 'BB-BONE-AUDI-02-00A0.dtbo' for board-name 'Override Board Name', version
 '00A0'
 [ 1088.028213] bone-capemgr bone_capemgr.8: slot #4: dtbo
 'BB-BONE-AUDI-02-00A0.dtbo' loaded; converting to live tree
 [ 1088.029031] bone-capemgr bone_capemgr.8: slot #4: #4 overlays
 [ 1088.059524] of_get_named_gpio_flags: can't parse gpios property
 [ 1088.071612] 1-0018 supply IOVDD not found, using dummy regulator
 [ 1088.071867] 1-0018 supply DVDD not found, using dummy regulator
 [ 1088.072049] 1-0018 supply AVDD not found, using dummy regulator
 [ 1088.072277] 1-0018 supply DRVDD not found, using dummy regulator
 [ 1088.098289] davinci_evm sound.10:  tlv320aic3x-hifi <-> 48038000.mcasp
 mapping ok
 [ 1088.134015] bone-capemgr bone_capemgr.8: slot #4: Applied #4 overlays.
 
 and a listing of slots showing the card:
 
 root@beaglebone:~# cat /sys/devices/bone_capemgr.*/slots
  0: 54:PF---
  1: 55:PF---
  2: 56:PF---
  3: 57:PF---
  4: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02
 
 
 Thanks,
 
 Eric
 
 -- 
 For more options, visit http://beagleboard.org/discuss
 --- 
 You received this message because you are subscribed to the Google Groups
 "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to 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.


-- 
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, 

[beagleboard] Re: USB cable provided by Beagle Bone Black

2014-05-20 Thread PLyttle
Some USB cables come with only 2 conductors and are only good for power 
supply.
Some USB cables have high resistance conductors. They are generally thin 
and very flexible. They can only be used for low power devices.
Most USB cables are sound low resistance conducors, sometimes even twisted 
pairs. . 

You can only use the first or the last kind. This does not mean that the 
second kind is bad, but they have limited use, generally the device they 
came with works fine with it. 


On Monday, May 19, 2014 6:34:16 AM UTC+2, Goodguy wrote:
>
> I found my BBB can be powered on by the provided USB cable, but cannot 
> with my own USB cable. I am sure my cable is in good condition. Now I get 
> this question, is the provided USB cable any special?
>
>

-- 
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: [Q] Can I serial connecting more than one BBB with together?

2014-05-20 Thread PLyttle
absolutely, the minute you hook it up as per instructions you are doing 
just that.

On Monday, May 19, 2014 7:19:57 PM UTC+2, Matrialism Dialectic wrote:
>
> Hello All!
> For example, can i serial connecting more than one BBB with together for 
> make Web-Server? how?
> Regards
>

-- 
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] LCD7 support in Debian 3.14.1 and Logibone support

2014-05-20 Thread macarr
Hi Robert,

I've been running Debian v3.8 for a while along with an LCD7 cape and 
decided to build/try 3.14.1-bone2. Everything is going well except for my 
LCD7 cape.

It isn't getting installed at boot/kernel start. I understand there is a 
patch for U-boot but I'm not sure about any USB side effects associated 
with the patch. I don't want to break something that is currently working.

Will the LCD7 be supported in 3.14?

I've also got Logibones on order and they mentioned that they have recently 
added software to the BBB repository and didn't mention any details. Do you 
happen to know if they are supported in Debian and if so what branch?

Regards,
Mike

-- 
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] Beaglebone Black USB modem

2014-05-20 Thread edwin . j . slv
I am using a Beaglebone black Version B with 3.8.13 Angstrom trying to 
connect to a Verizon 55L1 USB modem:

When I run the lsusb command, I am able to detect the Novatel wireless 
modem as shown below.  When I use the command ifconfig, I only can0, eth0, 
lo, and usb0.  How do I add an 'ifconfig' device and link it with my usb 
host device. 


root@beaglebone:# lsusb
Bus 001 Device 002: ID 1410:b001 Novatel Wireless
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

root@beaglebone:~# ifconfig
can0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
  UP NOARP  MTU:16  Metric:1
  RX packets:3 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:10
  RX bytes:24 (24.0 B)  TX bytes:0 (0.0 B)
  Interrupt:71

eth0  Link encap:Ethernet  HWaddr 1C:BA:8C:A2:81:A6
  inet addr:192.168.0.108  Bcast:192.168.0.255  Mask:255.255.255.0
  inet6 addr: fe80::1eba:8cff:fea2:81a6/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:37754 errors:0 dropped:0 overruns:0 frame:0
  TX packets:24564 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:53825036 (51.3 MiB)  TX bytes:1793322 (1.7 MiB)
  Interrupt:56

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:14 errors:0 dropped:0 overruns:0 frame:0
  TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:1068 (1.0 KiB)  TX bytes:1068 (1.0 KiB)

usb0  Link encap:Ethernet  HWaddr BE:2D:EB:0E:36:78
  inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:4990 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1892 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:393716 (384.4 KiB)  TX bytes:383178 (374.1 KiB)

-- 
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] Torrent Box

2014-05-20 Thread Hari Krishna Malladi
I didn't do that as this is limited to my hostel room. I have no TV or media 
players over here!—
Sent from Mailbox

On Tue, May 20, 2014 at 10:20 PM, Maxim Podbereznyy 
wrote:

> Nice job, man!
> did you enable upnp on it? I think sharing films to local TV or media
> players would be great!
> 2014-05-20 19:32 GMT+04:00 Hari Krishna Malladi <
> harikrishnamalladi.i...@gmail.com>:
>> Hey folks
>>
>> Out of necessity, I happened to make a Torrent Box with a Cubieboard. The
>> same thing can be done with a BBB or a BeagleBoard xM. I described the
>> process in detail here: http://tweakgeek.in/cubieboard-2-as-a-torrent-box/
>>
>> Should work unchanged on any Debian-based OS (such as Ubuntu). Unlike the
>> Cubieboard, a BBB will require a powered USB hub.
>>
>> Sent from my iPad
>>
>> --
>> 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.
>>
> -- 
> LinkedIn - http://www.linkedin.com/in/maximpodbereznyy
> Company - http://www.linkedin.com/company/mentorel
> Facebook - https://www.facebook.com/mentorel.company
> -- 
> 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] Torrent Box

2014-05-20 Thread Maxim Podbereznyy
Nice job, man!

did you enable upnp on it? I think sharing films to local TV or media
players would be great!


2014-05-20 19:32 GMT+04:00 Hari Krishna Malladi <
harikrishnamalladi.i...@gmail.com>:

> Hey folks
>
> Out of necessity, I happened to make a Torrent Box with a Cubieboard. The
> same thing can be done with a BBB or a BeagleBoard xM. I described the
> process in detail here: http://tweakgeek.in/cubieboard-2-as-a-torrent-box/
>
> Should work unchanged on any Debian-based OS (such as Ubuntu). Unlike the
> Cubieboard, a BBB will require a powered USB hub.
>
> Sent from my iPad
>
> --
> 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.
>



-- 
LinkedIn - http://www.linkedin.com/in/maximpodbereznyy
Company - http://www.linkedin.com/company/mentorel
Facebook - https://www.facebook.com/mentorel.company

-- 
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] Announce: Flasher Changes

2014-05-20 Thread Robert Nelson
On Tue, May 20, 2014 at 10:32 AM, Jason Kridner  wrote:
>
>
> On Sunday, May 18, 2014 4:19:54 PM UTC-4, RobertCNelson wrote:
>>
>>
>>
>>
>> On Fri, May 16, 2014 at 7:24 PM, Eric Fort  wrote:
>>>
>>> As an alternative or maybe in conjunction you could have the 4 LED's
>>> blink together in the following order:
>>> 000111010100011101110111000111010001 (DONE) with a bit duration
>>> somewhere between 250 & 62.5 milliseconds, 1 representing on, and 0
>>> representing off and the string repeating a number of times prior to off or
>>> infinitely.  come to think of this, have the script as it's final task
>>> compute an MD5 or similar checksum on what was just written to verify a
>>> proper write and on success start flashing the above sequence.  if somewhere
>>> along the process something went wrong causing it to exit, halt, or
>>> otherwise not obtain success it could blink
>>> 00010101110100010111000101000101110101 (FAIL) using the same timing as
>>> above.  Just a thought
>>
>>
>> It would be cooler if it did the cylon back n forth while flashing..
>
>
> Not as cool a doing a cylon, but it is at least a recognizable sweeping
> pattern (https://gist.github.com/jadonk/71a409ffaa151eb1f8e8):
>
> #!/bin/sh
> BASE=/sys/class/leds/beaglebone\:green\:usr
> echo timer > ${BASE}0/trigger
> echo 2000 > ${BASE}0/delay_off
> sleep 0.5
> echo timer > ${BASE}1/trigger
> echo 2000 > ${BASE}1/delay_off
> sleep 0.5
> echo timer > ${BASE}2/trigger
> echo 2000 > ${BASE}2/delay_off
> sleep 0.5
> echo timer > ${BASE}3/trigger
> echo 2000 > ${BASE}3/delay_off

Thanks Jason!

Added that:
https://github.com/RobertCNelson/boot-scripts/commit/d75480ef2d4f6b6e415ca5297e193c5e83f9aa3f

It'll get pulled in as we update things.

Regards,

-- 
Robert Nelson
http://www.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.


[beagleboard] Torrent Box

2014-05-20 Thread Hari Krishna Malladi
Hey folks

Out of necessity, I happened to make a Torrent Box with a Cubieboard. The same 
thing can be done with a BBB or a BeagleBoard xM. I described the process in 
detail here: http://tweakgeek.in/cubieboard-2-as-a-torrent-box/

Should work unchanged on any Debian-based OS (such as Ubuntu). Unlike the 
Cubieboard, a BBB will require a powered USB hub.

Sent from my iPad

-- 
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] Announce: Flasher Changes

2014-05-20 Thread Jason Kridner


On Sunday, May 18, 2014 4:19:54 PM UTC-4, RobertCNelson wrote:
>
>
>
>
> On Fri, May 16, 2014 at 7:24 PM, Eric Fort  wrote:
>
>> As an alternative or maybe in conjunction you could have the 4 LED's 
>> blink together in the following order: 
>> 000111010100011101110111000111010001 (DONE) with a bit duration 
>> somewhere between 250 & 62.5 milliseconds, 1 representing on, and 0 
>> representing off and the string repeating a number of times prior to off or 
>> infinitely.  come to think of this, have the script as it's final task 
>> compute an MD5 or similar checksum on what was just written to verify a 
>> proper write and on success start flashing the above sequence.  if 
>> somewhere along the process something went wrong causing it to exit, halt, 
>> or otherwise not obtain success it could blink 
>> 00010101110100010111000101000101110101 (FAIL) using the same timing as 
>> above.  Just a thought
>>
>
> It would be cooler if it did the cylon back n forth while flashing..
>

Not as cool a doing a cylon, but it is at least a recognizable sweeping 
pattern (https://gist.github.com/jadonk/71a409ffaa151eb1f8e8):

#!/bin/sh
BASE=/sys/class/leds/beaglebone\:green\:usr
echo timer > ${BASE}0/trigger
echo 2000 > ${BASE}0/delay_off
sleep 0.5
echo timer > ${BASE}1/trigger
echo 2000 > ${BASE}1/delay_off
sleep 0.5
echo timer > ${BASE}2/trigger
echo 2000 > ${BASE}2/delay_off
sleep 0.5
echo timer > ${BASE}3/trigger
echo 2000 > ${BASE}3/delay_off

 

>
> Regards,
>
> -- 
> Robert Nelson
> http://www.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] 3.15.0-rc5-bone1

2014-05-20 Thread Robert Nelson
On Tue, May 20, 2014 at 10:10 AM, Ross Morrison  wrote:
> Is it safe to move forward on 3.15 at this time? This is the only kernel
> that supports my Asix AX88x72A based USB Ethernet dongles correctly on our
> custom board. I'm using the Wheezy 7.5 root file system and would like to
> stay here and get everything working. My wants are to get multiple UARTs
> running and an LCD based on the LCD-3.

So far "v3.15-rc5" seems okay on my test farm, I'm getting close to
moving it over v3.14.x in the --beta-kernel channel for the bones..

> Since there is no capemgr for 3.14 and above (at this time), is there a
> simple way to get these cape type devices working?
>
> I saw in one of the postings to add cape=tty01 in uEnv.txt to enable tty01,
> are there other options to the like this to force configuration from
> uEnv.txt?

right now the options are:

cape=tty01
cape=tty02
cape=tty04

As these were something i need here in the lab for a new cape.

https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.15/patches/dts-bone-capes/0001-capes-ttyO1-ttyO2-ttyO4.patch

Looking at the above patch, it's pretty easy to add multiple serial
devices to a dts if you need it.

I just haven't really done much with the lcd's.

Regards,

-- 
Robert Nelson
http://www.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.


[beagleboard] 3.15.0-rc5-bone1

2014-05-20 Thread Ross Morrison
Is it safe to move forward on 3.15 at this time? This is the only kernel 
that supports my Asix AX88x72A based USB Ethernet dongles correctly on 
our custom board. I'm using the Wheezy 7.5 root file system and would 
like to stay here and get everything working. My wants are to get 
multiple UARTs running and an LCD based on the LCD-3.


Since there is no capemgr for 3.14 and above (at this time), is there a 
simple way to get these cape type devices working?


I saw in one of the postings to add cape=tty01 in uEnv.txt to enable 
tty01, are there other options to the like this to force configuration 
from uEnv.txt?


Thanks,
Ross

--
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] Error while porting the Android ICS 4.0.3 Kernel and File system on Beagle Board XM

2014-05-20 Thread amarnath dasari
I am working on the Beagleboard XM with Android ICS 4.0.3. When I ported 
the kernel and file system, it is giving the follwoing error.
 
EXT4-fs (mmcblk0p2): recovery complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:2.
Freeing init memory: 216K
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj 
instead.
init: cannot open '/initlogo.rle'
init: cannot find '/system/etc/install-recovery.sh', disabling 
'flash_recovery'
enabling adb
adb_open
root@android:/ # init: untracked pid 1007 exited
warning: `zygote' uses 32-bit capabilities (legacy support in use)
request_suspend_state: wakeup (3->0) at 16510101320 (2000-01-01 
00:00:12.812072754 UTC)

-- 
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] BBB UVC/DMA crash kernel 3.13.6-bone7.1

2014-05-20 Thread Robert Nelson
On Tue, May 20, 2014 at 8:32 AM, David Lambert  wrote:
> Unfortunately I seem to have spoken too soon. After multiple control
> commands, the UVC subsystem becomes unresponsive. Could I suggest making the
> default "PIO only" again?

Sure, I can do that. I Actually thought that was the default in my
v3.14.4 branch, I guess I've been spending too much time with
v3.15-rcX..

https://github.com/RobertCNelson/bb-kernel/commit/fbe2858bfe0f112511b45a6c1ecf9c111ef6f47f

Regards,

-- 
Robert Nelson
http://www.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] How to enable ssh in single user mode?

2014-05-20 Thread Robert Nelson
On Mon, May 19, 2014 at 6:43 PM,   wrote:
> Environment: ubuntu-precise-12.04 on Beaglebone Black, no GUI
>
> System hang when I did "init 1" or "telinit 1". Commandline just stuck
> there.
>
> How to enable ssh service in single user mode? Since I just stuck on step 1,
> so I don't know the following steps are correct or not. I just add a new
> script to /etc/rc1.d/ directory which runs all the scripts inside in run
> level 1. The script is "start ssh" or "service ssh start" or
> "/etc/init.d/ssh start".
>
> If the first two steps are done, how could I ssh into the system? In single
> user mode, what's the user name for the system? In default run level 2, the
> user name is: ubuntu, with password: ubuntu. If I just type ssh ip address,
> it will use the user name of my Macbook by default. And I don't think ssh
> ubuntu@ip_address will work...

These are very "ubuntu" specific questions, have you tried the ubuntu
forums or ubuntu irc channels?

Regards,

-- 
Robert Nelson
http://www.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.


[beagleboard] How to enable ssh in single user mode?

2014-05-20 Thread zzyiwei


Environment: ubuntu-precise-12.04 on Beaglebone Black, no GUI

   1. 
   
   System hang when I did "init 1" or "telinit 1". Commandline just stuck 
   there.
   2. 
   
   How to enable ssh service in single user mode? Since I just stuck on 
   step 1, so I don't know the following steps are correct or not. I just add 
   a new script to /etc/rc1.d/ directory which runs all the scripts inside in 
   run level 1. The script is "start ssh" or "service ssh start" or 
   "/etc/init.d/ssh start".
   3. 
   
   If the first two steps are done, how could I ssh into the system? In 
   single user mode, what's the user name for the system? In default run level 
   2, the user name is: ubuntu, with password: ubuntu. If I just type ssh ip 
   address, it will use the user name of my Macbook by default. And I don't 
   think ssh ubuntu@ip_address will work...
   
Sincerely

-- 
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: [beagle-alpha] help, I think the smoke escaped from my beagle stack (beagle white, battery cape, dvi cape, audio cape)

2014-05-20 Thread Gerald Coley
http://www.elinux.org/Beagleboard:BeagleBoneBlack#RMA_Support

You send the board back to the factory in the US.

Gerald



On Mon, May 19, 2014 at 7:49 PM, liyaoshi  wrote:

> Hello Gerald
>
> How to do RMA ? I am in Shanghai
>
>
> 2014-05-19 20:51 GMT+08:00 Gerald Coley :
>
>> Do the RMA.
>>
>> Gerald
>>
>>
>>
>> On Sun, May 18, 2014 at 9:13 PM, Eric Fort  wrote:
>>
>>> Help,
>>>
>>> I just got an audio cape today and wanting to get it working I added it
>>> to the top of the cape stack such that I had a beaglebone white, the
>>> battery cape, dvi cape, and finally the new rev b audio cape on top.  a
>>> couple days ago I used this setup without the audio cape running on
>>> batteries and it worked completely as expected.  I plugged it into the
>>> network and used the stack over ssh for over 3 hours as commented in a
>>> previous post.  Today, I was a bit short on batteries so after carefully
>>> looking over the battery cape SRM found here
>>> https://github.com/CircuitCo/BeagleBone-Battery/blob/master/BeagleBone-Battery-RevA-srm.pdf?raw=trueand
>>>  determining that it will accept from 1.8-5.5V across VBAT as
>>> doccumented on page 16 of the cape SRM I reviewed the schematic to find J8
>>> & J9 allow attachment to VBATT such that I may attach a power supply to J8
>>> or J9 for power.  I then placed 2 AA cells in the battery holders on the
>>> battery cape and measured the voltage across J8 & J9 to determine proper
>>> polarity after which I attached a black lead to the minus or negative
>>> terminal and a red lead to the positive terminal.  it blinked and flashed
>>> nicely as I would wxpect at this point as if trying to boot.  I then
>>> attached a 5V power supply to these terminals checking for proper polarity
>>> prior to turning on the supply which I measured at 5 volts.  I only took
>>> this option because after careful reading of the Battery cape SRM It stated
>>> that 5v is in spec.  well the board stack failed to come up or give any
>>> indication of life, not so much as a power LED on any of the boards!  then
>>> about 15 seconds elapsed and things started to smell.  I pulled power
>>> shortly thereafter.  now all that happens when I put batteries in the
>>> battery cape in the batteries get too hot to hold in just a couple seconds
>>> and the smell returns.  trying to power the beaglebone over USB with no
>>> other capes attached blinks the power LED but no other evidence of life is
>>> seen.  I am also suspect of the audio cape and dvi cape possibly being
>>> fried as well.  are there some additional things I can and should check or
>>> is this something for direct RMA?
>>>
>>> Thanks,
>>>
>>> Eric
>>>
>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Beagle Alpha" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagle-alpha+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.
>

-- 
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: requires to be root to ping!!

2014-05-20 Thread Gerald Coley
Yes, Agreed. But that is not out of the box.

Gerald



On Tue, May 20, 2014 at 8:49 AM, Robert Nelson wrote:

> On Tue, May 20, 2014 at 12:02 AM, neckTwi 
> wrote:
> >>  Next, usb is a complete hack on 3.8, so switch to v3.14.x if usb is
> >> important to you.  Note v3.14.x is lacking capemgr.
> >>
> > I need UART1 and USB. My application enables UART1 during startup; I
> found a
> > dtbo to enable UARTs on internet. In v3.14.x can I access /dev/ttyO1 out
> of
> > box?
>
> Yes, enabling ttyO1 is easy with v3.14.x
>
> In /boot/uboot/uEnv.txt
>
> Just un-comment this line:
>
> https://github.com/RobertCNelson/omap-image-builder/blob/master/target/boot/beagleboard.org.txt#L26
>
> Full steps:
>
> cd /opt/scripts/tools/
> git pull
> sudo ./update_kernel.sh --beta-kernel
>
> (reboot)
>
> edit: /boot/uboot/uEnv.txt
> add: cape=ttyO1
>
> (reboot)
>
> use newly enabled serial port.
>
> Regards,
>
> --
> Robert Nelson
> http://www.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: requires to be root to ping!!

2014-05-20 Thread Robert Nelson
On Tue, May 20, 2014 at 12:02 AM, neckTwi  wrote:
>>  Next, usb is a complete hack on 3.8, so switch to v3.14.x if usb is
>> important to you.  Note v3.14.x is lacking capemgr.
>>
> I need UART1 and USB. My application enables UART1 during startup; I found a
> dtbo to enable UARTs on internet. In v3.14.x can I access /dev/ttyO1 out of
> box?

Yes, enabling ttyO1 is easy with v3.14.x

In /boot/uboot/uEnv.txt

Just un-comment this line:
https://github.com/RobertCNelson/omap-image-builder/blob/master/target/boot/beagleboard.org.txt#L26

Full steps:

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh --beta-kernel

(reboot)

edit: /boot/uboot/uEnv.txt
add: cape=ttyO1

(reboot)

use newly enabled serial port.

Regards,

-- 
Robert Nelson
http://www.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: requires to be root to ping!!

2014-05-20 Thread Gerald Coley
No. We do not do special requests like this. Moving it to make you happy
will make a lot of other people that use the debug cable very unhappy.

Gerald




On Tue, May 20, 2014 at 12:02 AM, neckTwi  wrote:

>  Next, usb is a complete hack on 3.8, so switch to v3.14.x if usb is
>> important to you.  Note v3.14.x is lacking capemgr.
>>
>> I need UART1 and USB. My application enables UART1 during startup; I
> found a dtbo to enable UARTs on internet. In v3.14.x can I access
> /dev/ttyO1 out of box?
>
>  --
> 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] Re: Latest Angstrom demo/untested build hangs at "usbcore: registered new interface driver smsc95xx" ?

2014-05-20 Thread 蕭兆原

I find this is a old problem no body answered.

I also encountered this problem today, but the solution is wait for more 
minutes

So just wait.


Ed of the Mountain於 2012年12月20日星期四UTC+8上午3時03分13秒寫道:
>
>
> Is there a work-around for this?
>
> I am using a BeagleBoard-xM revC.  Thanks in advance,
> -Ed
>
> http://downloads.angstrom-distribution.org/demo/beagleboard/untested/
>
> -rw-r--r-- 1 z3 z3 100530739 2012-12-19 10:58 
> Angstrom-systemd-GNOME-image-eglibc-ipk-v2012.05-beagleboard.rootfs.tar.bz2
> -rw-r--r-- 1 z3 z3 42960 2012-12-19 10:56 MLO
> -rw-r--r-- 1 z3 z3  12833522 2012-12-19 10:57 
> modules-3.2.28-r122a-beagleboard.tgz
> -rw-r--r-- 1 z3 z3338172 2012-12-19 10:56 u-boot.img
> -rw-r--r-- 1 z3 z3   4388808 2012-12-19 10:57 
> uImage-3.2.28-r122a-beagleboard-20121009164219.bin
>
> Terminal:
> Started Load Kernel Modules[ 
>  OK  ]
> Started Debug File System  [ 
>  OK  ]
> Started Remount API VFS [   19.975006] udevd[58]: starting version 
> 182
>[  OK  ]
> Started udev Kernel Device Manager [ 
>  OK  ]
> Started Temporary Directory[ 
>  OK  ]
> Starting FUSE Control File System...   
> 
> Started Configuration File System  [ 
>  OK  ]
> Started FUSE Control File System   [ 
>  OK  ]
> Started File System Check on Root Device   [ 
>  OK  ]
> Starting Remount Root FS...   
>  
> [   20.226501] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
> Started Remount Root FS[ 
>  OK  ]
> Starting Recreate Volatile Files and Directories...   
>  
> Starting Load Random Seed...   
> 
> Started Machine ID first boot configure[ 
>  OK  ]
> Starting Run pending postinsts... 
>  
> Started udev Coldplug all Devices  [ 
>  OK  ]
> Started Recreate Volatile Files and Directories[ 
>  OK  ]
> Started Load Random Seed   [ 
>  OK  ]
> systemd-fsck[49]: Angstrom: clean, 28099/499712 files, 169199/1998084 
> blocks
> [   20.757873] input: gpio-keys as /devices/platform/gpio-keys/input/input4
> [   21.760070] rtc-ds1307: probe of 2-0068 failed with error -5
> [   22.175598] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
> [   22.643646] OMAP3 Beagle/Devkit8000 SoC init
> [   22.882202] asoc: twl4030-hifi <-> omap-mcbsp-dai.1 mapping ok
> [   23.256591] smsc95xx v1.0.4
> [   23.499877] smsc95xx 1-2.1:1.0: eth0: register 'smsc95xx' at 
> usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, 12:0a:a6:9b:d2:6c
> *[   23.512023] usbcore: registered new interface driver smsc95xx*
>
> Hangs at last line.
>

-- 
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] BBB UVC/DMA crash kernel 3.13.6-bone7.1

2014-05-20 Thread David Lambert
Unfortunately I seem to have spoken too soon. After multiple control 
commands, the UVC subsystem becomes unresponsive. Could I suggest making 
the default "PIO only" again?


Regards,

Dave.


On 05/19/2014 03:44 PM, David Lambert wrote:

Robert,
I just tried your 3.14.4-bone4 kernel. Thanks for including my 
Argus UPS cape patches:-) . It appears that the UVC DMA is getting 
better, but I am getting the following warning messages when I issue 
any UVC controls. The good news is that the system still continues to 
work fine apart from these messages. Close, but no cigar :-\
Please pass on words of encouragement to the developers responsible 
for this.


Regards,

Dave.



On 03/14/2014 11:20 AM, Robert Nelson wrote:
On Fri, Mar 14, 2014 at 11:14 AM, David Lambert  
wrote:
The USB DMA still appears to have problems when used with USB 
cameras. It
appears that whenever I attempt to issue controls via UVC to a 
camera that
is capturing, then I get the attached crash. PIO mode works fine. 
Could I
suggest that the default defconfig selects PIO mode until DMA mode 
works

reliably?

I hope this is the right place to post. If not, please excuse my 
intrusion,

and suggest another.
Done: 
https://github.com/RobertCNelson/linux-dev/commit/182589d51ae7ecc82c1ba9ef2b6440edf2d9


I don't see it getting completely fixed anytime soon either

Regards,


uname -a
Linux trax-jdal 3.14.4-bone4 #1 SMP Mon May 19 15:25:52 CDT 2014 
armv7l GNU/Linux

root@trax-jdal:~# [  238.501234] [ cut here ]
[  238.506128] WARNING: CPU: 0 PID: 498 at drivers/dma/cppi41.c:605 
cppi41_dma_control+0x2a0/0x2f0()
[  238.515429] Modules linked in: rtc_ds1307 snd_usb_audio 
snd_usbmidi_lib snd_hwdep snd_rawmidi uvcvideo snd_seq_device snd_pcm 
videobuf2_vmalloc snd_timer videobuf2_memops snd videobuf2_core 
soundcore ftdi_sio usbserial omap_aes omap_sham rtc_omap 
uio_pdrv_genirq uio loop
[  238.540705] CPU: 0 PID: 498 Comm: python Tainted: GW 
3.14.4-bone4 #1
[  238.548403] [] (unwind_backtrace) from [] 
(show_stack+0x10/0x14)
[  238.556539] [] (show_stack) from [] 
(dump_stack+0x80/0x90)
[  238.564121] [] (dump_stack) from [] 
(warn_slowpath_common+0x70/0x8c)
[  238.572607] [] (warn_slowpath_common) from [] 
(warn_slowpath_null+0x1c/0x24)
[  238.581822] [] (warn_slowpath_null) from [] 
(cppi41_dma_control+0x2a0/0x2f0)
[  238.591051] [] (cppi41_dma_control) from [] 
(cppi41_dma_channel_abort+0xc8/0x13c)
[  238.600723] [] (cppi41_dma_channel_abort) from 
[] (musb_cleanup_urb.isra.12+0x40/0x10c)
[  238.610942] [] (musb_cleanup_urb.isra.12) from 
[] (musb_urb_dequeue+0xe8/0x128)
[  238.620440] [] (musb_urb_dequeue) from [] 
(usb_hcd_unlink_urb+0x4c/0x84)
[  238.629292] [] (usb_hcd_unlink_urb) from [] 
(usb_kill_urb+0x50/0xcc)
[  238.637818] [] (usb_kill_urb) from [] 
(uvc_uninit_video+0x34/0x60 [uvcvideo])
[  238.647147] [] (uvc_uninit_video [uvcvideo]) from 
[] (uvc_video_enable+0x18/0x168 [uvcvideo])
[  238.657926] [] (uvc_video_enable [uvcvideo]) from 
[] (uvc_v4l2_do_ioctl+0x5b8/0x1180 [uvcvideo])
[  238.668979] [] (uvc_v4l2_do_ioctl [uvcvideo]) from 
[] (video_usercopy+0x194/0x53c)
[  238.678742] [] (video_usercopy) from [] 
(v4l2_ioctl+0x114/0x13c)
[  238.686872] [] (v4l2_ioctl) from [] 
(do_vfs_ioctl+0x400/0x5c4)
[  238.694813] [] (do_vfs_ioctl) from [] 
(SyS_ioctl+0x6c/0x7c)
[  238.702484] [] (SyS_ioctl) from [] 
(ret_fast_syscall+0x0/0x30)

[  238.710420] ---[ end trace 4b907c08f9a1b69e ]---
[  238.715257] [ cut here ]
[  238.720099] WARNING: CPU: 0 PID: 498 at drivers/dma/cppi41.c:629 
cppi41_dma_control+0x28c/0x2f0()
[  238.729397] Modules linked in: rtc_ds1307 snd_usb_audio 
snd_usbmidi_lib snd_hwdep snd_rawmidi uvcvideo snd_seq_device snd_pcm 
videobuf2_vmalloc snd_timer videobuf2_memops snd videobuf2_core 
soundcore ftdi_sio usbserial omap_aes omap_sham rtc_omap 
uio_pdrv_genirq uio loop
[  238.754654] CPU: 0 PID: 498 Comm: python Tainted: GW 
3.14.4-bone4 #1
[  238.762324] [] (unwind_backtrace) from [] 
(show_stack+0x10/0x14)
[  238.770448] [] (show_stack) from [] 
(dump_stack+0x80/0x90)
[  238.778024] [] (dump_stack) from [] 
(warn_slowpath_common+0x70/0x8c)
[  238.786509] [] (warn_slowpath_common) from [] 
(warn_slowpath_null+0x1c/0x24)
[  238.795722] [] (warn_slowpath_null) from [] 
(cppi41_dma_control+0x28c/0x2f0)
[  238.804939] [] (cppi41_dma_control) from [] 
(cppi41_dma_channel_abort+0xc8/0x13c)
[  238.814611] [] (cppi41_dma_channel_abort) from 
[] (musb_cleanup_urb.isra.12+0x40/0x10c)
[  238.824829] [] (musb_cleanup_urb.isra.12) from 
[] (musb_urb_dequeue+0xe8/0x128)
[  238.834317] [] (musb_urb_dequeue) from [] 
(usb_hcd_unlink_urb+0x4c/0x84)
[  238.843169] [] (usb_hcd_unlink_urb) from [] 
(usb_kill_urb+0x50/0xcc)
[  238.851664] [] (usb_kill_urb) from [] 
(uvc_uninit_video+0x34/0x60 [uvcvideo])
[  238.860986] [] (uvc_uninit_video [uvcvideo]) from 
[] (uvc_video_enable+0x18/0x168 [uvcvideo])
[  238.871765] [] (uvc_video_enable [uvcvideo]) from 
[] (uvc_v

[beagleboard] Is it possible to use arduino LCD library through BoneScript ?

2014-05-20 Thread henrique matias
Hello Guys,

I'm still trying to understand if would be possible to somehow use arduino
libraries on the beagleboard, for instance, i have a prototype running and
LCD using http://arduino.cc/en/Tutorial/LiquidCrystal library.

How could that translate to bonescript? Could i call methods of the LCD
library through bonescript?

thanks a lot

-- 
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] Beaglebone Audio Cape Rev B audio Input

2014-05-20 Thread Raphael Philipe
It seems that I messed with the amixer parameters. Now I can not even
hear from the speaker test. Is there a way of reseting alsa
parameters, not only the general audio volume?

I saw something like
alsactl restore -P
and removing '/var/lib/alsa/asound.state
but it didn't work for parameters specifically to the DA830 EVM.

Why the audio cape is recognized as a DA830 EVM?

I suspect that the audio input is not working due to one of that parameters.

Regards, Raphael.

On Sun, May 18, 2014 at 8:22 PM, John Syn  wrote:
>
> From: Raphael Philipe 
> Reply-To: 
> Date: Sunday, May 18, 2014 at 3:30 PM
> To: 
> Subject: [beagleboard] Beaglebone Audio Cape Rev B audio Input
>
>
> Hi
>
> I've acquired an Audio Cape Rev B
> http://elinux.org/CircuitCo:Audio_Cape_RevB for my Beaglebone Black.
>
> Following the instructions I was able to make it work. The audio playback is
> working pretty well. However, I cannot test the audio input. I saw that it
> is a line level input (line in), so it cannot be connected to a regular
> microphone.
>
> I want to test it through an echo scheme. I will produce some sound through
> q source (connected to the line in input of the cape) and check the response
> in the audio output, through an earphone.
>
> I tried to connect the cape line in to the earphone output of an old
> cellphone through a male male jack cable (I saw in some forums that the line
> level is similar to the earphone output of some appliances, apart from the
> impedance difference.). Unfortunately, it didn't work.
>
> The interesting thing is that when the cable is connected to the cape audio
> input and the other connector is unplluged, I can hear the noise from
> static, similar to an unplugged to the amplifier electric guitar .
>
> Can someone suggest me a simple form to test the audio input?
>
> I don’t have the Audio Cape, but I do have a TLV320AIC3106EVM connected to
> my BBB and it works fine. You may want to try the following command:
>
> arecord -r 44100 -c 1 -f S16_LE -t wav -vv -d 25 example.wav
>
> This will show you a bar graph in the terminal so you can see the input
> levels. I would just connect the output from you phone to the line input of
> your audio cape. In another terminal, run amixer to adjust the input levels.
>
> Regards,
> John
>
>
> Regards.
>
> --
> 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] Re: RepliCape Waiting Room - Or: Its all about capes, not the bones

2014-05-20 Thread rl . budde
Week 21 - any news?

-- 
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: Beaglebone connection failures

2014-05-20 Thread Thomas Laudan

i work with a beaglebone (white) and i am having the same problem with 
windows and ubuntu. sometimes i have to push the reset button on my 
beaglebone up to 10 times or even more to get it working, all the time 
observing system settings/network on ubuntu and wating to finally get a 
"connected" ... this is frustrating! so it doesn't seem to be a problem 
with windows.

-- 
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] help getting audio cape rev b1 working

2014-05-20 Thread Eric Fort
ok,

seems the issue was one related to software and expectations and maybe
a messed up debian install.  when I entered the command 'speaker-test -c2
-f600 I expected a 600hz tone... I got white noise - but paying close
attention to the text output, it said it was playing noise.  starting with
a freshly imaged card and following the instructions from there seems to
have it working with the files linked from the instructions.  Note to the
designers of this cape - adding a stereo audio amp to drive headphones to a
bit higher level would be extremely welcome.

Eric


On Mon, May 19, 2014 at 11:21 PM, Eric Fort  wrote:

> John,
>
> here's what happens when I use your .dts file:
>
> root@beaglebone:~# export SLOTS=/sys/devices/bone_capemgr.*/slots
> root@beaglebone:~# echo BB-BONE-AUDI-02 > $SLOTS
> -bash: echo: write error: Invalid argument
>
> and when I use the one linked to in the instructions (
> http://elinux.org/images/1/10/BB-BONE-AUDI-02-00A0.zip) - yes I extracted
> the file from the zip archive first...):
>
> root@beaglebone:~# export SLOTS=/sys/devices/bone_capemgr.*/slots
> root@beaglebone:~# echo BB-BONE-AUDI-02 > $SLOTS
>
> (no errors)
>
> Thanks,
>
> Eric
>
>
>
>
> On Mon, May 19, 2014 at 7:09 PM, John Syn  wrote:
>
>>
>>  From: Eric Fort 
>> Reply-To: 
>> Date: Monday, May 19, 2014 at 6:56 PM
>> To: beagleboard 
>> Subject: [beagleboard] help getting audio cape rev b1 working
>>
>> I have followed the instructions found at
>> http://elinux.org/CircuitCo:Audio_Cape_RevB#Audio_Cape_Revision_B1 and
>> I'm just getting static when I try speaker-test -f 600 or aplay
>> filename.wav.  the wav file plays fine on my windows laptop and aplay
>> identifies it properly but just static for audio.  what may I have missed?
>>
>> Try the attached DTO. I generated this myself before Circuitco published
>> theirs. When Circuitco published their DTO I described what I thought were
>> problems but no one responded.
>>
>> Regards,
>> John
>>
>>
>>
>> here's dmesg:
>>
>> root@beaglebone:~# dmesg|tail
>> [ 1088.018924] bone-capemgr bone_capemgr.8: slot #4: Requesting firmware
>> 'BB-BONE-AUDI-02-00A0.dtbo' for board-name 'Override Board Name', version
>> '00A0'
>> [ 1088.028213] bone-capemgr bone_capemgr.8: slot #4: dtbo
>> 'BB-BONE-AUDI-02-00A0.dtbo' loaded; converting to live tree
>> [ 1088.029031] bone-capemgr bone_capemgr.8: slot #4: #4 overlays
>> [ 1088.059524] of_get_named_gpio_flags: can't parse gpios property
>> [ 1088.071612] 1-0018 supply IOVDD not found, using dummy regulator
>> [ 1088.071867] 1-0018 supply DVDD not found, using dummy regulator
>> [ 1088.072049] 1-0018 supply AVDD not found, using dummy regulator
>> [ 1088.072277] 1-0018 supply DRVDD not found, using dummy regulator
>> [ 1088.098289] davinci_evm sound.10:  tlv320aic3x-hifi <-> 48038000.mcasp
>> mapping ok
>> [ 1088.134015] bone-capemgr bone_capemgr.8: slot #4: Applied #4 overlays.
>>
>> and a listing of slots showing the card:
>>
>> root@beaglebone:~# cat /sys/devices/bone_capemgr.*/slots
>>  0: 54:PF---
>>  1: 55:PF---
>>  2: 56:PF---
>>  3: 57:PF---
>>  4: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-AUDI-02
>>
>>
>> Thanks,
>>
>> Eric
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to 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.