[beagleboard] Errors installing the Debian Image 2015-10-04

[lachlan . s . peter]

I have just installed the new Debian 8.2 via the flasher image on a 
BeagleboneBlack Rev C with 4DCape. I have changed the uEnv.txt file to 
disable HDMI. I get the following errors on install: (Even when I dont 
change the uEnv.txt file from default)

  [ 1113.740804] systemd[1]: Job 
console-setup.service/start deleted to break ordering cycle starting with 
basic.target/start

[ SKIP ] Ordering cycle found, skipping LSB: Set console font and keymap

.

[ 1114.681515] systemd[1]: systemd-modules-load.service: main process 
exited, code=exited, status=1/FAILURE

[FAILED] Failed to start Load Kernel Modules.

See 'systemctl status systemd-modules-load.service' for details.

.

[FAILED] Failed to start Store Sound Card State.

See 'systemctl status alsa-store.service' for details.


Then when I boot the new image I get the error:


   [FAILED] Failed to start Load Kernel Modules.

   See 'systemctl status systemd-modules-load.service' 
for details.


Then I do apt-get update.


Then when I do apt-get upgrade I get the following errors:

WARNING: missing /lib/modules/4.2.2-armv7-x2

Ensure all necessary drivers are built into the linux image!

depmod: ERROR: could not open directory /lib/modules/4.2.2-armv7-x2: No 
such file or directory

depmod: FATAL: could not search modules: No such file or directory

depmod: WARNING: could not open 
/var/tmp/mkinitramfs_0Ayicd/lib/modules/4.2.2-armv7-x2/modules.order: No 
such file or directory

depmod: WARNING: could not open 
/var/tmp/mkinitramfs_0Ayicd/lib/modules/4.2.2-armv7-x2/modules.builtin: No 
such file or directory
   .
   Warning: Unit file of cloud9.socket changed on disk, 'systemctl 
daemon-reload' recommended.
   
   c9-core-installer:Installing nak
   npm WARN excluding symbolic link 
tests/filelist_fixtures/symlink-to-1.txt -> 1.txt
   npm WARN excluding symbolic link 
tests/filelist_fixtures/symlink-to-nowhere.txt -> nowhere.txt
   npm WARN excluding symbolic link 
tests/search_fixtures/symlink-to-file1.txt -> file1.txt
   npm WARN excluding symbolic link 
tests/filelist_fixtures/symlink-to-1.txt -> 1.txt
   npm WARN excluding symbolic link 
tests/filelist_fixtures/symlink-to-nowhere.txt -> nowhere.txt
   npm WARN excluding symbolic link 
tests/search_fixtures/symlink-to-file1.txt -> file1.txt

Any ideas why this is occuring and how the problem can be fixed ?
Lachlan

-- 
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] Errors loading new Debian image 2015-10-04

[lachlan . s . peter]

I have just installed the Debian 8.2 image via the eMMC 4GB flasher on the 
BeagleboneBlack RevC. As the system installs I get the following messages / 
Errors

[ 1113.740804] systemd[1]: Job console-setup.service/start deleted to break 
ordering cycle starting with basic.target/start

[ SKIP ] Ordering cycle found, skipping LSB: Set console font and keymap

.

[ 1114.681515] systemd[1]: systemd-modules-load.service: main process 
exited, code=exited, status=1/FAILURE

[FAILED] Failed to start Load Kernel Modules.

See 'systemctl status systemd-modules-load.service' for details.

.

[FAILED] Failed to start Store Sound Card State.

See 'systemctl status alsa-store.service' for details.

-- 
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] AIN7 readout on BB with 4.1.10-bone16

[William Hermans]

>
> *I thought this had no actual bearing on the configuration of things, but
> was just there to warn you if any other overlay also claimed those same
> strings (e.g. claiming "p9-31" is not the same as "p9.31").*


I'm not a device tree expert. But it does make sense to me that the PIN
connected to the AIN7 channel of the ADC module should be explicit.

Whatever the case, I noticed the same behavior as Nikos. When attempting to
use AIN7 through sysfs, the system complains loudly - Something to the
effect that the device is busy, or some such related error.

On Mon, Oct 12, 2015 at 4:50 PM, Rick Mann  wrote:

>
> > On Oct 12, 2015, at 16:28 , William Hermans  wrote:
> >
> > First: exclusive-use = "P9.31", "P9.40", "P9.37", "P9.38", "P9.33",
> "P9.36", "P9.35", "tscadc"; P9.32 seems to be missing. It is my assumption
> if you replace "tscadc" with "P9.32" that should fix one configuration
> piece for your purposes.
>
> I thought this had no actual bearing on the configuration of things, but
> was just there to warn you if any other overlay also claimed those same
> strings (e.g. claiming "p9-31" is not the same as "p9.31").
>
> --
> Rick Mann
> rm...@latencyzero.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] AIN7 readout on BB with 4.1.10-bone16

[Rick Mann]

> On Oct 12, 2015, at 16:28 , William Hermans  wrote:
> 
> First: exclusive-use = "P9.31", "P9.40", "P9.37", "P9.38", "P9.33", "P9.36", 
> "P9.35", "tscadc"; P9.32 seems to be missing. It is my assumption if you 
> replace "tscadc" with "P9.32" that should fix one configuration piece for 
> your purposes.

I thought this had no actual bearing on the configuration of things, but was 
just there to warn you if any other overlay also claimed those same strings 
(e.g. claiming "p9-31" is not the same as "p9.31").

-- 
Rick Mann
rm...@latencyzero.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] connecting the BBB with a 4D display

[mark . huber153]

Hi, 

I am very new to all this, I have a BBB and a 4D systems display (28PTU) 
and trying to connect them both together but I have no idea how. I couldnt 
find anything on the homepage and the forum is rather poor. 

So I plug the display via the USB port into the BBB which starts the 
splashscreen of the display but I don't know how to execute a program or 
test if it even works. 

In the workshop program where I programmed my program there it says it 
doesn't recognize the display while scanning through the comm ports. 

Any idea how I could do this?  

-- 
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 tos and why fors

[William Hermans]

google works wonders, and unfortunately since you do not have a specific
question that's about as good as I or anyone else can do.

DHCP requires a service installed, and running at boot. A non working
serial debug cable can fail for many a reason. Is it known working ? Is it
3v3 ttl ? is it connected properly ? Which Linux image are you running on
the BBB ? Which init daemon are you running - systemd or sysv ?

As for anything, knowing a good bit about something goes a long way for
troubleshooting. You sir, will need to become intimately familiar with
Linux - Otherwise this show stops here. Also, as you can see above, there
is no one solution fix for many, or even any problem on a system running
Linux. Which is why you need to become familiar with it.

In the end, if you're running a stock image on a Beaglebone black REVC. I
can probably help you fix the DHCP issue. Set a static IP for the usb
ethernet gadget on both host, and BBB. 192.168.7.1 for host, 192.168.7.2
for the Beaglebone. netmask 255.255.255.0 will suffice. With gateway
192.168.7.1 on the Beaglebone note this as an example:
https://wiki.debian.org/NetworkConfiguration#Configuring_the_interface_manually

As for the serial debug cable. I can only guess at what the problem is, and
you need to answer all of the above questions first before anyone can help
you well.

On Mon, Oct 12, 2015 at 4:12 PM, John Nichols  wrote:

> The subject is accurate of lacking. I'm looking for MORE information on
> how to get things up and running when they dont.
> I'm new to this platform and I cant get anything to function except the
> mini-USB cable. I dont even know where to start troubleshooting. Its
> frustrating to say the least and I dont want to be "that guy" that hijacks
> every topic that touches on something similar.
> The getting started guide is great if everything works but its a
> paperweight when it doesnt.
> Where do i find information about why DHCP isnt working? Why my FTDI
> serial cable isnt working? how to force setups? determine if the OS is
> functioning? etc. etc. etc.
> I dont mind reading, thats all ive been doing for the past 10 days (since
> buying this device), but darn if i can find any info.
> Anything is appreciated at this point.
> thanks
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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] AIN7 readout on BB with 4.1.10-bone16

[William Hermans]

One last thing of note. If you use an LCD screen that has to use AIN7 as a
touchscreen ADC channel, then you will have problems with that device tree
file as well. You will either have to set the PIN back to how it was, or
modify the touchscreen device tree file.

On Mon, Oct 12, 2015 at 4:28 PM, William Hermans  wrote:

> OK, so this is what I think the deal is, but you should double check
> yourself ( always ) before taking someone else's word. For anything
> important.
>
> *Important: read *everything**
>
> First: exclusive-use = "P9.31", "P9.40", "P9.37", "P9.38", "P9.33",
> "P9.36", "P9.35", "tscadc"; P9.32 seems to be missing. It is my assumption
> if you replace "tscadc" with "P9.32" that should fix one configuration
> piece for your purposes.
>
> Second:
> ti,adc-channels = <0x0 0x1 0x2 0x3 0x4 0x5 0x6>;
> I would assume should be
> ti,adc-channels = <0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7>;
>
> For all 8 pins to be configured as general purpose ADC pins With all of
> the above said. I have not done this myself. So you should double check
> everything. I do recall reading in the TRM where it was mentioned that they
> ADC module can be configured as all channels running in general purpose
> mode. I have not however checked the schematics to see if P.32 is in fact
> exposed to the P9 header, or if that PIN is in fact connected to channel 7
> of the ADC module. You need to check that for yourself.
>
> On Mon, Oct 12, 2015 at 4:11 PM, William Hermans 
> wrote:
>
>> This is because unless I'm mistaken AIN7 is configured as a touchscreen
>> PIN by default. Either way only AIN0-AIN6 are configured as general purpose
>> ADC's. Passed that, I', not sure of the ramifications of setting AIN7 as a
>> general purpose ADC either. Read the AM335x TRM before jumping in.
>> http://elinux.org/images/6/65/Spruh73c.pdf
>>
>> debian@beaglebone:~$ sudo cp /lib/firmware/BB-ADC-00A0.dtbo .
>> debian@beaglebone:~$ dtc -I dtb -O dts BB-ADC-00A0.dtbo > BB-ADC-00A0.dts
>> debian@beaglebone:~$ nano BB-ADC-00A0.dts
>> /dts-v1/;
>>
>> / {
>> compatible = "ti,beaglebone", "ti,beaglebone-black",
>> "ti,beaglebone-green";
>> part-number = "BB-ADC";
>> version = "00A0";
>> exclusive-use = "P9.31", "P9.40", "P9.37", "P9.38", "P9.33",
>> "P9.36", "P9.35", "tscadc";
>>
>> fragment@0 {
>> target = <0xdeadbeef>;
>>
>> __overlay__ {
>> status = "okay";
>>
>> adc {
>> ti,adc-channels = <0x0 0x1 0x2 0x3 0x4
>> 0x5 0x6>;
>> };
>> };
>> };
>>
>> __fixups__ {
>> tscadc = "/fragment@0:target:0";
>> };
>> };
>>
>>
>>
>>
>> On Mon, Oct 12, 2015 at 3:49 PM, Nikos 
>> wrote:
>>
>>> Hello, I have installed 4.1.10-bone16 from RCN's git on my custom board.
>>> All digital I/Os have been configured via device tree, but I cannot access
>>> AIN7 as I used to with pre-dtb kernels. All suggestions about going through
>>> */sys/devices/bone_capemgr.*/slots* seem to not apply, as there is no
>>> such path on my installation. Any ideas on what I might be missing?
>>>
>>> Thanks
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

-- 
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: CPU usage is ~100% on BBB most of the times: is it ok?

[Dig2Dig]

Hi,

i think this means the same like this post a few days 
ago: 
https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/mQk790K-6dg

The 100% usage appears when you force webgl or try to force the HW 
acceleration in an other way in a browser app. I saw this with Firefox too.
The mean questions is, how to connect the browser to the framebuffer. Is 
this possible and useable?

Usacase: the browser uses the framebuffer as DRI for HW accelerating.
Did this somebody in the past? Where can we find the discreption? 

THX!

-- 
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] AIN7 readout on BB with 4.1.10-bone16

[William Hermans]

OK, so this is what I think the deal is, but you should double check
yourself ( always ) before taking someone else's word. For anything
important.

*Important: read *everything**

First: exclusive-use = "P9.31", "P9.40", "P9.37", "P9.38", "P9.33",
"P9.36", "P9.35", "tscadc"; P9.32 seems to be missing. It is my assumption
if you replace "tscadc" with "P9.32" that should fix one configuration
piece for your purposes.

Second:
ti,adc-channels = <0x0 0x1 0x2 0x3 0x4 0x5 0x6>;
I would assume should be
ti,adc-channels = <0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7>;

For all 8 pins to be configured as general purpose ADC pins With all of the
above said. I have not done this myself. So you should double check
everything. I do recall reading in the TRM where it was mentioned that they
ADC module can be configured as all channels running in general purpose
mode. I have not however checked the schematics to see if P.32 is in fact
exposed to the P9 header, or if that PIN is in fact connected to channel 7
of the ADC module. You need to check that for yourself.

On Mon, Oct 12, 2015 at 4:11 PM, William Hermans  wrote:

> This is because unless I'm mistaken AIN7 is configured as a touchscreen
> PIN by default. Either way only AIN0-AIN6 are configured as general purpose
> ADC's. Passed that, I', not sure of the ramifications of setting AIN7 as a
> general purpose ADC either. Read the AM335x TRM before jumping in.
> http://elinux.org/images/6/65/Spruh73c.pdf
>
> debian@beaglebone:~$ sudo cp /lib/firmware/BB-ADC-00A0.dtbo .
> debian@beaglebone:~$ dtc -I dtb -O dts BB-ADC-00A0.dtbo > BB-ADC-00A0.dts
> debian@beaglebone:~$ nano BB-ADC-00A0.dts
> /dts-v1/;
>
> / {
> compatible = "ti,beaglebone", "ti,beaglebone-black",
> "ti,beaglebone-green";
> part-number = "BB-ADC";
> version = "00A0";
> exclusive-use = "P9.31", "P9.40", "P9.37", "P9.38", "P9.33",
> "P9.36", "P9.35", "tscadc";
>
> fragment@0 {
> target = <0xdeadbeef>;
>
> __overlay__ {
> status = "okay";
>
> adc {
> ti,adc-channels = <0x0 0x1 0x2 0x3 0x4 0x5
> 0x6>;
> };
> };
> };
>
> __fixups__ {
> tscadc = "/fragment@0:target:0";
> };
> };
>
>
>
>
> On Mon, Oct 12, 2015 at 3:49 PM, Nikos  wrote:
>
>> Hello, I have installed 4.1.10-bone16 from RCN's git on my custom board.
>> All digital I/Os have been configured via device tree, but I cannot access
>> AIN7 as I used to with pre-dtb kernels. All suggestions about going through
>> */sys/devices/bone_capemgr.*/slots* seem to not apply, as there is no
>> such path on my installation. Any ideas on what I might be missing?
>>
>> Thanks
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 tos and why fors

[John Nichols]

The subject is accurate of lacking. I'm looking for MORE information on how 
to get things up and running when they dont.
I'm new to this platform and I cant get anything to function except the 
mini-USB cable. I dont even know where to start troubleshooting. Its 
frustrating to say the least and I dont want to be "that guy" that hijacks 
every topic that touches on something similar.
The getting started guide is great if everything works but its a 
paperweight when it doesnt.
Where do i find information about why DHCP isnt working? Why my FTDI serial 
cable isnt working? how to force setups? determine if the OS is 
functioning? etc. etc. etc. 
I dont mind reading, thats all ive been doing for the past 10 days (since 
buying this device), but darn if i can find any info. 
Anything is appreciated at this point.
thanks 

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

Re: [beagleboard] AIN7 readout on BB with 4.1.10-bone16

[William Hermans]

This is because unless I'm mistaken AIN7 is configured as a touchscreen PIN
by default. Either way only AIN0-AIN6 are configured as general purpose
ADC's. Passed that, I', not sure of the ramifications of setting AIN7 as a
general purpose ADC either. Read the AM335x TRM before jumping in.
http://elinux.org/images/6/65/Spruh73c.pdf

debian@beaglebone:~$ sudo cp /lib/firmware/BB-ADC-00A0.dtbo .
debian@beaglebone:~$ dtc -I dtb -O dts BB-ADC-00A0.dtbo > BB-ADC-00A0.dts
debian@beaglebone:~$ nano BB-ADC-00A0.dts
/dts-v1/;

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black",
"ti,beaglebone-green";
part-number = "BB-ADC";
version = "00A0";
exclusive-use = "P9.31", "P9.40", "P9.37", "P9.38", "P9.33",
"P9.36", "P9.35", "tscadc";

fragment@0 {
target = <0xdeadbeef>;

__overlay__ {
status = "okay";

adc {
ti,adc-channels = <0x0 0x1 0x2 0x3 0x4 0x5
0x6>;
};
};
};

__fixups__ {
tscadc = "/fragment@0:target:0";
};
};




On Mon, Oct 12, 2015 at 3:49 PM, Nikos  wrote:

> Hello, I have installed 4.1.10-bone16 from RCN's git on my custom board.
> All digital I/Os have been configured via device tree, but I cannot access
> AIN7 as I used to with pre-dtb kernels. All suggestions about going through
> */sys/devices/bone_capemgr.*/slots* seem to not apply, as there is no
> such path on my installation. Any ideas on what I might be missing?
>
> Thanks
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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] TI sitara sdk

[William Hermans]

>
> *Hey guys!*
>
> *Does anyone know which benefits this sdk provides? I used to use building
> scripts from Robert Nelson, but this SDK seems to offer more flexible tool*
>
> *http://www.ti.com/lsds/ti/tools-software/processor_sw.page?DCMP=epd-sdo-pro-prosdk-wwe&HQS=epd-sdo-pro-prosdk-pr-lp-sdk-wwe
> *


What flexible tool is that ? The only real difference I can see up front is
the availability of TI-RTOS, which technically as per that link is open
source and free.

*Supported features:*

   - Long Term Stable (LTS) Mainline Linux
    kernel
   support
   - U-Boot community boot loader
   - Robust, commercial-grade Linaro® GNU compiler collection (GCC)
   toolchain
   - Yocto Project™ OE Core compatible file systems support enables
   tailored Linux application support

All this is available from the community, by the community. But If I had to
guess, TI could be offering pay / professional support into the mix as
well. I know they have a wiki page of third party consultants, etc already.
Linked to from that page as well.

Personally, I already had interest in TI-RTOS, but until now did not know
it was supported on the AM335x. Will definitely look into it now, and
thanks for the link :)


On Mon, Oct 12, 2015 at 3:19 PM, Maxim Podbereznyy 
wrote:

> Hey guys!
>
> Does anyone know which benefits this sdk provides? I used to use building
> scripts from Robert Nelson, but this SDK seems to offer more flexible tool
>
>
> http://www.ti.com/lsds/ti/tools-software/processor_sw.page?DCMP=epd-sdo-pro-prosdk-wwe&HQS=epd-sdo-pro-prosdk-pr-lp-sdk-wwe
>
> Отправлено с 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.
>

-- 
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] AIN7 readout on BB with 4.1.10-bone16

[Nikos]

Hello, I have installed 4.1.10-bone16 from RCN's git on my custom board. 
All digital I/Os have been configured via device tree, but I cannot access 
AIN7 as I used to with pre-dtb kernels. All suggestions about going through 
*/sys/devices/bone_capemgr.*/slots* seem to not apply, as there is no such 
path on my installation. Any ideas on what I might be missing?

Thanks

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

[beagleboard] TI sitara sdk

[Maxim Podbereznyy]

Hey guys!

Does anyone know which benefits this sdk provides? I used to use building 
scripts from Robert Nelson, but this SDK seems to offer more flexible tool

http://www.ti.com/lsds/ti/tools-software/processor_sw.page?DCMP=epd-sdo-pro-prosdk-wwe&HQS=epd-sdo-pro-prosdk-pr-lp-sdk-wwe

Отправлено с 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] How could I get the kernel with 3.8.13-bone47 version?

[Robert Nelson]

On Mon, Oct 12, 2015 at 4:54 PM, Mian Tang  wrote:
> Hi Robert,
>
> Thank you for your help.
>
> After I run "git checkout 3.8.13-bone47 -b tmp" command, I got some errors
> when executing ./patch.sh
>
> Could you please help me further about this problem?

Yeap, that's kinda expected... "everything" in that script is from 2
years ago when you checked out 3.8.13-bone47...

So even the scripts used to generate the final kernel image also have
2 years of bugs. ;)

IF you know what your doing, you can compare "scripts" with this repo...

https://github.com/RobertCNelson/stable-kernel

IF this is your first round of trying to build a kernel, just switch
too: 3.8.13-bone78

Regards,

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

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

Re: [beagleboard] How could I get the kernel with 3.8.13-bone47 version?

[Mian Tang]

Hi Robert,

Thank you for your help.
 
After I run "git checkout 3.8.13-bone47 -b tmp" command, I got some errors 
when executing ./patch.sh

Could you please help me further about this problem?

Thanks again.


Best Regards,
Mian





On Sunday, October 11, 2015 at 9:01:55 PM UTC-4, RobertCNelson wrote:
>
> On Sun, Oct 11, 2015 at 7:53 PM, Mian Tang  > wrote: 
> > Hi, 
> > 
> > I have linux running on my beaglebone board, and use "uname -r" to get 
> the 
> > current version which is 3.8.13-bone47. 
> > 
> > I hope to download the same version of kernel, but I cannot find it from 
> > github. 
> > 
> > Could you please tell me how to get the version of 3.8.13-bone47 ? 
>
> It's tagged in this repo: 
>
> https://github.com/RobertCNelson/bb-kernel/ 
>
> git checkout 3.8.13-bone47 -b tmp 
>
> But sorry, beyond that i'll be ignoring this thread.. as your 2 years 
> late for "bone47".. 
>
> Feel free to ask about: 3.8.13-bone78 and i'll reply... 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

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

[beagleboard] Re: Beaglebone Black won't power on, did I do something wrong? :(

[김진수]

Hey, I think I'm undergoing the symptom like what you'd have experienced... 
What can I do for recovery of BBB?? What does it mean that;
[I guess I expected the PWR led to be lit any time 5V was feeding the 
board, regardless of it's On/Off state.]
I was designing the program that can controls GPIO through SSH 
terminal, when it's power was downed. I wondered around the internet, and 
found this.

What can I do for this exactly?

2013년 4월 30일 화요일 오후 9시 19분 57초 UTC+9, Jason Stapels 님의 말:

> Hi all,
>
> Just wanted to share my experience with my dead BBB. It's my first 
> experience with the Beagle line so it's possible I did something wrong 
> somewhere so I thought it would be a good idea to share my experiences in 
> case other newb's read this. Feel free to skip to the bottom for the 
> symptoms.
>
> -- Begin Background Info --
>
> I was lucky enough to get my BBB almost right away from Digikey. I 
> immediately installed the drivers on my Mac and started playing around with 
> it the first night. Unfortunately, the second night I couldn't get my Mac 
> to allocate an IP address through the USB to talk to it so I thought maybe 
> I shouldn't have skipped that "update software" step. So next I downloaded 
> the latest "flash eMMC" image, wrote it to an SD card and then went through 
> the upgrade process.
>
> Here's where things went a little South. After the first attempt the USR 
> lights eventually went solid (presumably indicating the flashing process 
> was finished) but when I rebooted it without the SD card, the power light 
> would come on but it wouldn't boot. After a couple repower attempts I 
> decided to flash it again. This time, at some point during the flash 
> process, the board seemed to just lose power (all the LEDs were off). 
> Attempts to power the board resulted in the same as before, power light 
> comes on but no booting.
>
> So, my assumption was I messed up the SD card image. I downloaded/reimaged 
> the SD card again, went through the flash process and this time it seemed 
> to finish. Now when I powered on the board it appeared to boot up. However, 
> I still couldn't get it to pick up an IP address from the Mac (after 
> reinstalling both drivers and a couple reboots). I read somewhere that 
> someone had a similar issue and an update to Angstrom solved it.
>
> This time I plugged the board into my linux box and I was able to access 
> the running linux image (yay!). I immediately SSH'd in, and went through 
> the Angstrom upgrade (opkg update; opkg upgrade). The upgrade took awhile 
> and seemed to have a few issues with the new kernel modules 
> (/lib/modules/blah didn't exist). I figured it was just a warning and after 
> the upgrade finished I unplugged the board and plugged it back into my 
> Mac...
>
> -- End Background Info --
>
> The power light came on... the USR lights all went solid for a couple 
> seconds... and then the board died. I can no longer seem to power the board 
> up at all. I've tried multiple USB cables, multiple USB ports on multiple 
> machines, and even tried the DC jack with a 5v/2.2A supply. :( I submitted 
> an RMA (although my board doesn't seem to have a serial number) because I 
> don't think I did anything wrong, but I'm a very sad panda regardless.
>
> Any ideas? Anything I should check?
>
> ~ Jason
>

-- 
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] OpenGL SGX no support for hardware renderer

[Robert Nelson]

On Mon, Oct 12, 2015 at 1:48 PM, Matthias Laubnitz
 wrote:
> Hi Robert,
>
> it is not as if i did not search a lot of time. But there are so many
> differnt ways for differnt aims.
> Please answer me on question!
> Is there a possibility to get hardware support for the OpenGL Driver in
> Firefox with the Sitara AM3359 with Ubuntu 14.04, X-Server and Ti kernel
> 3.14?

nope...

OpenGL = "nope"...
X-server/Xorg = "nope"..

We have EGL and opengl es 1/2 support.. Framebuffer...

Regards,

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

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

Re: [beagleboard] OpenGL SGX no support for hardware renderer

[Matthias Laubnitz]

Hi Robert,

it is not as if i did not search a lot of time. But there are so many 
differnt ways for differnt aims.
Please answer me on question!
Is there a possibility to get hardware support for the OpenGL Driver in 
Firefox with the Sitara AM3359 with Ubuntu 14.04, X-Server and Ti kernel 
3.14?

Thank you very much!

Am Sonntag, 11. Oktober 2015 22:54:53 UTC+2 schrieb RobertCNelson:
>
> Please search this list, we've repeatedly documented the 
> do/don't/con/pro's of the "Current" SGX situation so many times, it 
> should be easy to find... 
>
> Regards, 
>
> On Sun, Oct 11, 2015 at 1:00 PM, Matthias Laubnitz 
> > wrote: 
> > Hi all, 
> > 
> > i want to have openGL support in firefox. I bulid and install the TI SGX 
> > -Modules: 
> > 
> > ubuntu@arm:~$ lsmod 
> > Module  Size  Used by 
> > omaplfb12027  0 
> > usb_f_ecm   7909  1 
> > g_ether 1802  0 
> > usb_f_rndis17719  2 g_ether 
> > u_ether 9460  3 usb_f_ecm,usb_f_rndis,g_ether 
> > libcomposite   38675  3 usb_f_ecm,usb_f_rndis,g_ether 
> > pvrsrvkm  184039  1 omaplfb 
> > pruss_remoteproc   12852  0 
> > c_can_platform  5971  0 
> > c_can   9400  1 c_can_platform 
> > can_dev 7494  1 c_can 
> > uio_pdrv_genirq 2848  0 
> > uio 7032  1 uio_pdrv_genirq 
> > ubuntu@arm:~$ 
> > 
> > The demos like Chameleonman runs perfect. 
> > 
> > But i have no hardware renderer! 
> > 
> > 
> > ubuntu@arm:~$ es2_info 
> > libEGL warning: DRI2: failed to authenticate 
> > EGL_VERSION: 1.4 (DRI2) 
> > EGL_VENDOR: Mesa Project 
> > EGL_EXTENSIONS: 
> > EGL_KHR_surfaceless_context 
> > EGL_CLIENT_APIS: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3 
> > GL_VERSION: OpenGL ES 2.0 Mesa 10.1.3 
> > GL_RENDERER: Software Rasterizer 
> > GL_EXTENSIONS: 
> > GL_EXT_blend_minmax, GL_EXT_multi_draw_arrays, 
> > GL_EXT_texture_filter_anisotropic, GL_EXT_texture_compression_dxt1, 
> > GL_EXT_texture_format_BGRA, GL_OES_depth24, 
> > GL_OES_element_index_uint, 
> > GL_OES_fbo_render_mipmap, GL_OES_mapbuffer, GL_OES_rgb8_rgba8, 
> > GL_OES_standard_derivatives, GL_OES_stencil8, GL_OES_texture_3D, 
> > GL_OES_texture_npot, GL_OES_depth_texture, 
> GL_OES_packed_depth_stencil, 
> > GL_EXT_texture_type_2_10_10_10_REV, GL_OES_get_program_binary, 
> > GL_APPLE_texture_max_level, GL_EXT_discard_framebuffer, 
> > GL_EXT_read_format_bgra, GL_NV_fbo_color_attachments, 
> > GL_OES_vertex_array_object, GL_ANGLE_texture_compression_dxt3, 
> > GL_ANGLE_texture_compression_dxt5, GL_EXT_texture_rg, 
> > GL_EXT_unpack_subimage, GL_NV_draw_buffers, GL_NV_read_buffer, 
> > GL_EXT_map_buffer_range, GL_OES_surfaceless_context 
> > ubuntu@arm:~$ 
> > 
> > What can i do? 
> > 
> > -- 
> > 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...@googlegroups.com . 
> > For more options, visit https://groups.google.com/d/optout. 
>
>
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

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

Re: [beagleboard] Hardware OpenGL ES acceleration on BeagleBone Black running Debian

[Robert Nelson]

On Mon, Oct 12, 2015 at 4:33 AM,   wrote:
> Hello,
>
> Below are the steps needed to get hardware OpenGL ES
> acceleration on BeagleBone Black running Debian. I wasn't able to
> find such instructions anywhere. Maybe someone could put this up
> on the wiki?

They are on the wiki.. ;)

http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black


> I wanted to test 3D acceleration because I have been researching
> the possibility to run Qt Quick 2 applications directly on the
> BBB. First I tried running them under X in 24bpp (software
> rendering) and it was impossibly slow. Then I tried running them
> under X in 16bpp (software rendering) and they didn't start
> (please shout if you know the reason for this error and how to
> fix it):
>  Cant find EGLConfig, returning null config
>  Unable to find an X11 visual which matches EGL config 0
>  Could not initialize OpenGL
> Then I tried running them using the EGLFS platform and it worked,
> but for this I had to install the drivers. Hence the instructions.
>
> --
> juodumas
>
> -
> 3 steps to get hardware OpenGL ES acceleration on BeagleBone
> Black running Debian (tested 2015-10 on wheezy, jessie and sid).
>
> Note that after following the steps you will be able to run a
> single fullscreen OpenGL ES application (e.g. Qt Quick 2 in EGLFS
> mode) and nothing else, meaning:
> * 3D acceleration in X server doesn't work on BBB and apparently
>   won't work anytime in the future
> * Wayland can run with accelerating compositing (window drawing
>   handled by the GPU chip), but starting OpenGL applications
>   won't work. For this to work the graphics driver must have
>   built-in Wayland support, exposing the EGL_EXT_platform_wayland
>   EGL extension. Robert Nelson mentioned on IRC that TI is
>   working on this and progress can be followed here:
>   http://git.ti.com/gitweb/?p=graphics/omap5-sgx-ddk-um-linux.git;a=summary
>
> 1. First pick a kernel version from this list of kernel modules
>for the GPU (the packages are from the
>http://repos.rcn-ee.com/debian/ repo):
>$ apt-cache search ti-sgx-es8-modules
>Then install the kernel together with the modules. For
>example, if you picked ti-sgx-es8-modules-3.14.54-ti-r77, run:
>$ apt-get install -y
> {ti-sgx-es8-modules,linux-image,linux-firmware-image}-3.14.54-ti-r77
> 2. On an x86 Linux computer run this (an x86 host is needed
>because an x86 binary installer from TI will be unpacked):
>$ git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
>$ cd ti-linux-kernel-dev
>$ ./sgx_create_package.sh
>$ scp deploy/GFX_*_es8.x.tar.gz :/tmp/
> 3. Now install the utilities on your BBB and reboot:
>$ cd /
>$ sudo tar zxf /tmp/GFX_*_es8.x.tar.gz
>$ sudo /opt/gfxinstall/sgx-install.sh
>
> Qt Quick 2 fullscreen programs can be launched from the terminal
> or within Wayland by exporting these variables:
> $ export QT_QPA_PLATFORM=eglfs
> $ export QT_QPA_EVDEV_KEYBOARD_PARAMETERS="grab=1"
> $ export QT_QPA_EVDEV_MOUSE_PARAMETERS="grab=1"
>
> Wayland with accelerated compositing (but without the possibility
> to launch windowed OpenGL programs) can be run like this:
> $ weston-launch -- --backend=fbdev-backend.so --use-gl

Regards,


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

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

[beagleboard] BagleBone doesn't show up as a USB device

[johnsemi]

Hello,
 I'm having trouble connecting to my beaglebone through ssh.  I've 
verified that other computers can see it and that it's booting properly but 
my computer doesn't even see it as a listed USB device when I plug it in.

I'm running 64 Bit windows 8.1 and have installed all the beaglebone 
drivers and still have no luck.  Anyone have any ideas?  We're using these 
for the intro to robotics class I'm teaching and several students are 
having similar problems.  Linux seems to have no issues, but most of my 
students are only running linux in virtual machines which would bring a 
whole host of different headaches.


-- 
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] Hardware OpenGL ES acceleration on BeagleBone Black running Debian

[juodumas]

Hello,

Below are the steps needed to get hardware OpenGL ES
acceleration on BeagleBone Black running Debian. I wasn't able to
find such instructions anywhere. Maybe someone could put this up
on the wiki?

I wanted to test 3D acceleration because I have been researching
the possibility to run Qt Quick 2 applications directly on the
BBB. First I tried running them under X in 24bpp (software
rendering) and it was impossibly slow. Then I tried running them
under X in 16bpp (software rendering) and they didn't start
(please shout if you know the reason for this error and how to
fix it):
 Cant find EGLConfig, returning null config
 Unable to find an X11 visual which matches EGL config 0
 Could not initialize OpenGL
Then I tried running them using the EGLFS platform and it worked,
but for this I had to install the drivers. Hence the instructions.

-- 
juodumas

-
3 steps to get hardware OpenGL ES acceleration on BeagleBone
Black running Debian (tested 2015-10 on wheezy, jessie and sid).

Note that after following the steps you will be able to run a
single fullscreen OpenGL ES application (e.g. Qt Quick 2 in EGLFS
mode) and nothing else, meaning:
* 3D acceleration in X server doesn't work on BBB and apparently
  won't work anytime in the future
* Wayland can run with accelerating compositing (window drawing
  handled by the GPU chip), but starting OpenGL applications
  won't work. For this to work the graphics driver must have
  built-in Wayland support, exposing the EGL_EXT_platform_wayland
  EGL extension. Robert Nelson mentioned on IRC that TI is
  working on this and progress can be followed here:
  http://git.ti.com/gitweb/?p=graphics/omap5-sgx-ddk-um-linux.git;a=summary

1. First pick a kernel version from this list of kernel modules
   for the GPU (the packages are from the
   http://repos.rcn-ee.com/debian/ repo):
   $ apt-cache search ti-sgx-es8-modules
   Then install the kernel together with the modules. For
   example, if you picked ti-sgx-es8-modules-3.14.54-ti-r77, run:
   $ apt-get install -y 
{ti-sgx-es8-modules,linux-image,linux-firmware-image}-3.14.54-ti-r77
2. On an x86 Linux computer run this (an x86 host is needed
   because an x86 binary installer from TI will be unpacked):
   $ git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
   $ cd ti-linux-kernel-dev
   $ ./sgx_create_package.sh
   $ scp deploy/GFX_*_es8.x.tar.gz :/tmp/
3. Now install the utilities on your BBB and reboot:
   $ cd /
   $ sudo tar zxf /tmp/GFX_*_es8.x.tar.gz
   $ sudo /opt/gfxinstall/sgx-install.sh

Qt Quick 2 fullscreen programs can be launched from the terminal
or within Wayland by exporting these variables:
$ export QT_QPA_PLATFORM=eglfs
$ export QT_QPA_EVDEV_KEYBOARD_PARAMETERS="grab=1"
$ export QT_QPA_EVDEV_MOUSE_PARAMETERS="grab=1"

Wayland with accelerated compositing (but without the possibility
to launch windowed OpenGL programs) can be run like this:
$ weston-launch -- --backend=fbdev-backend.so --use-gl

-- 
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] Signed BBB drivers for Windows 10

[Jason Kridner]

Just an update. Had to get a lawyer involved because the old letter had a
phone number that wasn't getting answer. Still waiting on Godaddy to call
me to verify.

On Thu, Oct 1, 2015 at 9:53 PM, William Hermans  wrote:

> *The drivers are signed for 10, but the certificate expired. I got
>> paperwork to GoDaddy 2 days ago to get it renewed. Waiting for them to call
>> to verify. They had been calling the wrong number for weeks. Might still
>> need to get them a note from a lawyer that will cost pointless money, but
>> we'll see. *
>>
>
> Yikes ! And my bad I had not realized. Too bad so many of us suckers feel
> compelled to use Windows in the first place. I've been using MS OSes since
> DOS 5, and now . . . I couldn't say what OS I'll be using passed Windows 8.
> For the desktop that is.
>
>>
> On Thu, Oct 1, 2015 at 6:32 PM, Jason Kridner  wrote:
>
>> The drivers are signed for 10, but the certificate expired. I got
>> paperwork to GoDaddy 2 days ago to get it renewed. Waiting for them to call
>> to verify. They had been calling the wrong number for weeks. Might still
>> need to get them a note from a lawyer that will cost pointless money, but
>> we'll see.
>>
>> On Oct 1, 2015, at 5:54 PM, William Hermans  wrote:
>>
>> I do not believe there are any signed drivers for Win10 yet. I also would
>> not expect any for a while either. Due to MS's dodgy EULA for Windows 10.
>>
>> You can disable driver signing though.
>>
>> On Thu, Oct 1, 2015 at 2:50 PM, Manish Shakya 
>> wrote:
>>
>>> Hi Everyone,
>>>
>>> Where can I find signed drivers for Windows 10?
>>>
>>> Thanks
>>>
>>> Manish
>>>
>>> --
>>> 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] hub port change event

[Robert Nelson]

On Mon, Oct 12, 2015 at 10:36 AM, Guido Paoluzi Cusani
 wrote:
> Hello All,
> does anyone know what the following dmesg output lines could mean:
> [ 5973.943655] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
> [ 5973.943962] hub 1-1:1.0: port 1, status 0101, change 0001, 12 Mb/s
> I suspect it is some error happening on the hub port #1 but could not find
> out anywhere what the
> status and change codes are.
> dmesg output is attached.
> My Beaglebone Black USB host is connected to a commercial hub having 2 FTDI
> USB-to-232 cables (port#1 and #2) downstream.

Looking at log, yeap 3.8 kernel + musb issues...  Most of those are
known issues..

Fell free, to please try: 4.1.10-ti-r21  as most of the musb issues
are fixed/workarounded/etc in mainline..

sudo apt-get update
sudo apt-get install linux-image-4.1.10-ti-r21
sudo reboot

Regards,

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

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

[beagleboard] hub port change event

[Guido Paoluzi Cusani]

Hello All,
does anyone know what the following dmesg output lines could mean:
[ 5973.943655] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
[ 5973.943962] hub 1-1:1.0: port 1, status 0101, change 0001, 12 Mb/s
I suspect it is some error happening on the hub port #1 but could not find 
out anywhere what the 
status and change codes are.
dmesg output is attached.
My Beaglebone Black USB host is connected to a commercial hub having 2 FTDI 
USB-to-232 cables (port#1 and #2) downstream.
Thank you

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[0.681725] bone-capemgr bone_capemgr.9: slot #6: 
'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN'
[0.681888] bone-capemgr bone_capemgr.9: Skipping loading of disabled cape 
with part# BB-BONELT-HDMI
[0.681902] bone-capemgr bone_capemgr.9: Skipping loading of disabled cape 
with part# BB-BONELT-HDMIN
[0.682043] bone-capemgr bone_capemgr.9: initialized OK.
[0.683534] OneNAND driver initializing
[0.684388] usbcore: registered new interface driver cdc_ether
[0.684438] usbcore: registered new interface driver rndis_host
[0.684546] usbcore: registered new interface driver cdc_ncm
[0.684876] bone-capemgr bone_capemgr.9: loader: before slot-4 
BB-BONE-EMMC-2G:00A0 (prio 1)
[0.684892] bone-capemgr bone_capemgr.9: loader: check slot-4 
BB-BONE-EMMC-2G:00A0 (prio 1)
[0.684906] bone-capemgr bone_capemgr.9: loader: after slot-4 
BB-BONE-EMMC-2G:00A0 (prio 1)
[0.684938] bone-capemgr bone_capemgr.9: slot #4: Requesting firmware 
'cape-bone-2g-emmc1.dtbo' for board-name 'Bone-LT-eMMC-2G', version '00A0'
[0.684956] bone-capemgr bone_capemgr.9: slot #4: dtbo 
'cape-bone-2g-emmc1.dtbo' loaded; converting to live tree
[0.685209] bone-capemgr bone_capemgr.9: slot #4: #2 overlays
[0.685790] bone-capemgr bone_capemgr.9: slot #4: Applied #2 overlays.
[0.685809] bone-capemgr bone_capemgr.9: loader: done slot-4 
BB-BONE-EMMC-2G:00A0 (prio 1)
[0.686067] usbcore: registered new interface driver cdc_acm
[0.686078] cdc_acm: USB Abstract Control Model driver for USB modems and 
ISDN adapters
[0.686085] Initializing USB Mass Storage driver...
[0.686151] usbcore: registered new interface driver usb-storage
[0.686158] USB Mass Storage support registered.
[0.686293] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[0.686533] musb-hdrc musb-hdrc.0.auto: pdev->id = 0
[0.686550] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:480 
dsps_musb_init: OK
[0.686577] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, 
bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[0.686588] musb-hdrc: MHDRC RTL version 2.0 
[0.686596] musb-hdrc: setup fifo_mode 4
[0.686611] musb-hdrc: 28/31 max ep, 16384/16384 memory
[0.686704] musb-hdrc musb-hdrc.0.auto: *** mode=3
[0.686715] musb-hdrc musb-hdrc.0.auto: *** power=250
[0.687292] musb-hdrc musb-hdrc.1.auto: pdev->id = 1
[0.687309] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:480 
dsps_musb_init: OK
[0.687332] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, 
bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[0.687342] musb-hdrc: MHDRC RTL version 2.0 
[0.687349] musb-hdrc: setup fifo_mode 4
[0.687360] musb-hdrc: 28/31 max ep, 16384/16384 memory
[0.687434] musb-hdrc musb-hdrc.1.auto: *** mode=1
[0.687445] musb-hdrc musb-hdrc.1.auto: *** power=250
[0.687456] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[0.687670] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus 
number 1
[0.687701] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup
[0.687769] usb usb1: default language 0x0409
[0.687801] usb usb1: udev 1, busnum 1, minor = 0
[0.687812] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[0.687823] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[0.687833] usb usb1: Product: MUSB HDRC host driver
[0.687842] usb usb1: Manufacturer: Linux 3.8.13-bone69 musb-hcd
[0.687851] usb usb1: SerialNumber: musb-hdrc.1.auto
[0.688251] usb usb1: usb_probe_device
[0.688267] usb usb1: configuration #1 chosen from 1 choice
[0.688306] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[0.688408] hub 1-0:1.0: usb_probe_interface
[0.688419] hub 1-0:1.0: usb_probe_interface - got id
[0.688435] hub 1-0:1.0: USB hub found
[0.688459] hub 1-0:1.0: 1 port detected
[0.688468] hub 1-0:1.0: standalone hub
[0.688477] hub 1-0:1.0: individual port power switching
[0.688487] hub 1-0:1.0: no over-current protection
[0.688495] hub 1-0:1.0: Single TT
[0.688504] hub 1-0:1.0: TT requires at most 8

[beagleboard] USB ethernet gadget networking problem

[bremenpl]

Hello there,
I have just installed the latest Debian kernel v 4.1.9 on BeagleBone Black. 
The ethernet gadget seems to work, as I can connect through ssh to the 
board. This is my configuration on BeagleBone Black:

usb0  Link encap:Ethernet  HWaddr 90:59:af:4e:f2:c0
  inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
  inet6 addr: fe80::9259:afff:fe4e:f2c0/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:717 errors:0 dropped:0 overruns:0 frame:0
  TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:58635 (57.2 KiB)  TX bytes:18668 (18.2 KiB)

# Ethernet/RNDIS gadget (g_ether)
# Used by: /opt/scripts/boot/autoconfigure_usb0.sh
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.252
network 192.168.7.0
gateway 192.168.7.1

On the windows host:



On windows host i can ping the board by 192.168.7.2 address and I am 
getting response.
The problem is I cannot ping my host from the BeagleBone Black... 

root@beaglebone:/etc/network# ping 192.168.7.1
PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.

and it hands like that, I am not responed. Everything seems correct, I dont 
know wither this is a network configuration issue. I would areally 
apreciate all help regarding this problem.

-- 
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] CPU usage is ~100% on BBB most of the times: is it ok?

[Upol Ryskulova]

Hello again,
I want to add some details to this problem. We have two BBB, two usb
wireless adaptor. First BBB is connected to two usb wireless adaptor( one
for connecting to internet and the other for connecting to second BBB
device remotely and read data from the it), supplied by 5v power supply,
and connected through hdmi cable to display screen. When we boot first BBB
and start running chrome on it by doing some typing on browser, display
screen starts to blink rapidly. When we stop typing on browser search field
blink stops. What may be causing this blink?
When we run our web app on the browser CPU usage rises to ~100%. And
display starts to blink.

Could this blink related to CPU usage or network connection?



On Mon, Oct 12, 2015 at 10:32 AM, Upol Ryskulova 
wrote:

> Hello there,
>
> We are running our web application on chrome browser and CPU usage is
> ~100%( == 96%) most of the times. Will it be a problem for bbb? Or is it
> ok? I know that high CPU usage causes heat and probably it will gradually
> deteriorate electronic components.
>
> I am curious maybe 100% cpu usage is ok for bbb :)?
>
> Regards,
> Upol
>
> --
> 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/7VnFWpGgPQw/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] Kernel 4.1.9 overlays not working

[Bremenpl]

I think I managed to do everything, thank you.
There is still one thing that differs from version 3.8 kernel- I dont 
see either hdmi/emmc was disabled or not by looking at the slots. How 
can I check that?


W dniu 2015-10-12 o 11:58, 'Andreas Müller' via BeagleBoard pisze:

On Mon, Oct 12, 2015 at 11:51 AM, Bremenpl  wrote:

I used dtc in version 1.4.0 i believe.


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

To make overlays build properly, you need a special version of dtc
found at [1] further details see [2]

[1] https://github.com/pantoniou/dtc
[2] https://github.com/beagleboard/bb.org-overlays

Andreas



--
Bremenpl

--
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] Kernel 4.1.9 overlays not working

[Bremenpl]

Im sorry but I cant find any source on how to install the dtc compiller 
after I have downloaed it from http://devicetree.org/Device_Tree_Compiler


W dniu 2015-10-12 o 11:58, 'Andreas Müller' via BeagleBoard pisze:

On Mon, Oct 12, 2015 at 11:51 AM, Bremenpl  wrote:

I used dtc in version 1.4.0 i believe.


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

To make overlays build properly, you need a special version of dtc
found at [1] further details see [2]

[1] https://github.com/pantoniou/dtc
[2] https://github.com/beagleboard/bb.org-overlays

Andreas



--
Bremenpl

--
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] Kernel 4.1.9 overlays not working

[Bremenpl]

I will try this out, thank you.

W dniu 2015-10-12 o 11:58, 'Andreas Müller' via BeagleBoard pisze:

On Mon, Oct 12, 2015 at 11:51 AM, Bremenpl  wrote:

I used dtc in version 1.4.0 i believe.


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

To make overlays build properly, you need a special version of dtc
found at [1] further details see [2]

[1] https://github.com/pantoniou/dtc
[2] https://github.com/beagleboard/bb.org-overlays

Andreas



--
Bremenpl

--
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] Kernel 4.1.9 overlays not working

['Andreas Müller' via BeagleBoard]

On Mon, Oct 12, 2015 at 11:51 AM, Bremenpl  wrote:
> I used dtc in version 1.4.0 i believe.
>
>
> --
> 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.
To make overlays build properly, you need a special version of dtc
found at [1] further details see [2]

[1] https://github.com/pantoniou/dtc
[2] https://github.com/beagleboard/bb.org-overlays

Andreas

-- 
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] Kernel 4.1.9 overlays not working

[Bremenpl]

I used dtc in version 1.4.0 i believe.

--
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] Kernel 4.1.9 overlays not working

['Andreas Müller' via BeagleBoard]

On Mon, Oct 12, 2015 at 11:01 AM, bremenpl  wrote:
> Hello there,
> I have installed latest console version of Debian from eLinux.org. Its uses
> kernel version 4.1.9:
> Linux beaglebone 4.1.9-ti-r20 #1 SMP PREEMPT Fri Oct 2 05:35:56 UTC 2015
> armv7l GNU/Linux
>
> I was trying to load BB-UART5 overlay but I failed. I also dont see any
> overlays loaded I thought I would, like eMMC:
> root@beaglebone:/sys/devices/platform/bone_capemgr# cat slots
>  0: PF  -1
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
>
> When I tried to load the tree i got:
> [ 3013.532495] bone_capemgr bone_capemgr: part_number 'BB-UART5', version
> 'N/A'
> [ 3013.532543] bone_capemgr bone_capemgr: slot #4: override
> [ 3013.532561] bone_capemgr bone_capemgr: Using override eeprom data at slot
> 4
> [ 3013.532579] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A0,Override Manuf,BB-UART5'
> [ 3013.533110] __of_adjust_tree_phandle_references: Could not find target
> property 'fixup' @/__local_fixups__
> [ 3013.548518] bone_capemgr bone_capemgr: slot #4: Failed to resolve tree
>
> And I have compiled the tds before and put the dtbo in /lib/firmware/
>
> Has anything changed in the new kernel regarding dts loading and general
> usage?
> I would apreciate all help regarding this topic!
>
> --
Am not sure: Did you compile dts with the patched version of dtc?

Andreas

-- 
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] Kernel 4.1.9 overlays not working

[bremenpl]

Hello there,
I have installed latest console version of Debian from eLinux.org. Its uses 
kernel version 4.1.9:
Linux beaglebone 4.1.9-ti-r20 #1 SMP PREEMPT Fri Oct 2 05:35:56 UTC 2015 
armv7l GNU/Linux

I was trying to load BB-UART5 overlay but I failed. I also dont see any 
overlays loaded I thought I would, like eMMC:
root@beaglebone:/sys/devices/platform/bone_capemgr# cat slots
 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 

When I tried to load the tree i got:
[ 3013.532495] bone_capemgr bone_capemgr: part_number 'BB-UART5', version 
'N/A'
[ 3013.532543] bone_capemgr bone_capemgr: slot #4: override
[ 3013.532561] bone_capemgr bone_capemgr: Using override eeprom data at 
slot 4
[ 3013.532579] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,BB-UART5'
[ 3013.533110] __of_adjust_tree_phandle_references: Could not find target 
property 'fixup' @/__local_fixups__
[ 3013.548518] bone_capemgr bone_capemgr: slot #4: Failed to resolve tree

And I have compiled the tds before and put the dtbo in /lib/firmware/

Has anything changed in the new kernel regarding dts loading and general 
usage?
I would apreciate all help regarding this topic!

-- 
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: USB and ethernet ports are not working - D14 led not powered

[Roger Quadros]

Hi,

On 11/10/15 23:57, Robert Nelson wrote:
> Hi John,
> 
> On Sun, Oct 11, 2015 at 8:21 AM,   wrote:
>> I don want to hijack this string, just commenting that my BeagleBone Black
>> is having what appears to be the exact same issue, or at least similar
>> enough to be put in the same category.
> 
> Nope sorry, completely different hardware, and a completely different
> usb "PHY" ip...

Actually, on bone black, ethernet is not over USB. It is directly over MII.

> 
>> I can access just fine using the mini USB port.
>> I cannot access via ethernet, it appears no IP address was set from DHCP
>> server because the port seems active (lights all blinky and stuff).
>> I connected an FTDI serial cable and the connection is spotty but when i do
>> (seem) to connect it doesnt recognize "root" use - all password attempts
>> fail.
> 
> The default images printout the user/password combination..  If it
> doesn't contact who you go the image from..
> 
>>
>> No LEDs lit except nearest power connection.
>>
>> No SD card mounted (at the moment).
>>
>> My MacBook Pro lives on my home wifi while the BBB is connected to a switch,
>> connected directly to the router. I know the IPs are same subnet because my
>> Drobo is also on that switch and I access that from my laptop continually.
>>
>> I'm reading through your previous entries and will look for obvious
>> similarities and address as suggested.
> 

cheers,
-roger

-- 
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] CPU usage is ~100% on BBB most of the times: is it ok?

[Upol Ryskulova]

Hello there,

We are running our web application on chrome browser and CPU usage is 
~100%( == 96%) most of the times. Will it be a problem for bbb? Or is it 
ok? I know that high CPU usage causes heat and probably it will gradually 
deteriorate electronic components. 

I am curious maybe 100% cpu usage is ok for bbb :)? 

Regards,
Upol

-- 
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] g_ether gadget usb0 not configured at boot

[bremenpl]

Hello there,
I am using BeagleBone Black with Debian console version (3.8.13-bone70 #1 
SMP Fri Jan 23 02:15:42 UTC 2015 armv7l GNU/Linux). I have enabled g_ether 
module for usb ethernet gadget. The problem is, the usb0 interface is not 
visible on boot. I have to manually login to BeagleBone Black and use 
ifconfig:

ifconfig usb0 192.168.7.2

Without that, I cannot connect using usb. I see the interface on the 
windows side but its down. In my interfaces file I have:

# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
# Note on some boards, usb0 is automaticly setup with an init script
auto usb0
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.0
network 192.168.7.0
gateway 192.168.7.1

I tried to work around this and added ifconfig usb0 192.168.7.2 rclocal 
file but that ahvent helped as well. 

I would really apreciate all help here- Why isnt usb0 configured at boot?

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