Re: [beagleboard] Beaglebone blue, buildroot and wifi

[Thomas Chamelot]

Le lun. 24 févr. 2020 à 09:11, Hugo van den Brand  a
écrit :

>
>
> Op ma 24 feb. 2020 05:03 schreef :
>
>>
>> Hi,
>>
>> I recently purchased a beaglebone blue and tried it with pre-installed
>> image and the latest debian image from beagleboard.org. Everything is ok
>> and the wifi works perfectly.
>>
>> Now, I want to build my own custom image with buildroot. I have some
>> experience with buildroot and raspberry pi. I managed to have a bootable
>> image with linux console on uart. The problem is that when I try to
>> activate wlan0 (ip link set wlan0 up), the  board hangs. I cannot connect
>> to ssh anymore (USB connection), I cannot access it via the uart linux
>> console (no more log from kernel), the heartbeat LED stops blinking, the
>> only thing i can do is ping the board (through USB).
>>
>
> That sounds like a kernel panic.
> Is any logging of this event written to a file that you can look at after
> boot?
> Do you get any output the moment it happens?
>

I do not have any log after the moment it happens, but I do not believe it
is a kernel panic as I can still ping my board through the USB connection.
It means that icmp request are handled by the kernel. I think that what
happens is a kind of deadlock.
Actually, yesterday, I tried with a different kernel version. I forgot to
mention that I was using the branch 4.19-rt from
https://github.com/beagleboard/linux. When changing to the default 4.14
version/branch, I was able to use wifi normally. So I belive it is related
to the preempt-rt patch, but I have to investigate further.


> Do you have the kernel module for wlan compiled into the kernel? You might
> get a bit more logging if it is a module.
>

I tried both.


>
>
>> What I have tried so far,
>>
>> Use different firmware (/lib/firmware/ti-connectivity) from:
>> * Buildroot linux-firmware package
>> * Beaglebone Black wireless firmware (on github)
>> * Pre installed firmware from the official Debian image
>>
>> Use different device-tree
>> * am35x-boneblue.dts built with the linux kernel by buildroot
>> * the devicetree provided in the official Debian image
>>
>
> I trust you know that the device tree  can be specific for a kernel.
> For my beaglebone black, there are huge differences between the beaglebone
> kernel and the stable kernel from kernel.org.
>
> I would try it as well with the beaglebone kernel and matching device
> tree.
> https://github.com/beagleboard/linux
> If you see that working you could backtrack where the differences are.
>

As I told, I was using a kernel from https://github.com/beagleboard/linux.
I even looked for a diff between my working setup am335xx-boneblue.dts and
the 4.19-rt am335xx-boneblue.dts, but they are equivalent.


>
>
>
>> Use different libc
>> * µclibc
>> * glibc
>>
>
> I don't think that matters that much. Errors in those libraries are not
> that common and would probably cause more errors.
> Glibc is used more, so to be safe stick to that.
>

I found on google that µclibc do not implement some stuff related to ipv6,
so I gave it a try ^^.


>
>
>> At this point I end up every time with the symptoms described before.
>> Could anyone help to investigate further?
>>
>> Thank you,
>>
>> Thomas
>>
>> Anyway, it works now. Thank you for your quick response, it made me
investigate the device-tree further.

Thomas

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CA%2Bqo%3DvVB%2ByLWHLvu4pZ6pa%2BG1XbVo1FVqA8ODk2%3DYewFoUf_Vg%40mail.gmail.com.

Re: [beagleboard] Re: Need advice on how to reduce boot time

[Robert Nelson]

On Mon, Feb 24, 2020 at 6:35 PM  wrote:
>
> My r127 seems very different from your r113!  Would mounting the EXT4-fs set 
> the lower limit on what I can hope for?  I also have a major jump at 45s to 
> 95s.
>
> Mike
> ...
> [1.385532] ALSA device list:
> [1.385540]   No soundcards found.
> [1.392228] Freeing unused kernel memory: 1024K
> [1.847501] random: systemd-udevd: uninitialized urandom read (16 bytes 
> read)
> [1.848225] random: systemd-udevd: uninitialized urandom read (16 bytes 
> read)
> [1.848327] random: systemd-udevd: uninitialized urandom read (16 bytes 
> read)

> [   34.166674] random: crng init done
> [   34.166698] random: 7 urandom warning(s) missed due to ratelimiting

In /boot/uEnv.txt at the end of the "cmdline" add:

rng_core.default_quality=100

it was added by default around ~6 months ago, so your image is just old. ;)

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjcVu5cd6njZ%2BC0DMJGtoV9q%3DojY1gafxqoHpMvHYAtYA%40mail.gmail.com.

[beagleboard] Re: Need advice on how to reduce boot time

[mikerostosky]

My r127 seems very different from your r113!  Would mounting the EXT4-fs 
set the lower limit on what I can hope for?  I also have a major jump at 
45s to 95s.

Mike
...
[1.385532] ALSA device list:
[1.385540]   No soundcards found.
[1.392228] Freeing unused kernel memory: 1024K
[1.847501] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
[1.848225] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
[1.848327] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
[   30.019624] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data 
mode. Opts: (null)
[   30.463662] systemd[1]: System time before build time, advancing clock.
[   30.534304] ip_tables: (C) 2000-2006 Netfilter Core Team
[   30.568706] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT 
+GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[   30.569470] systemd[1]: Detected architecture arm.
[   30.575682] systemd[1]: Set hostname to .
[   31.174199] systemd[1]: Set up automount Arbitrary Executable File 
Formats File System Automount Point.
[   31.175075] systemd[1]: Listening on /dev/initctl Compatibility Named 
Pipe.
[   31.175446] systemd[1]: Listening on fsck to fsckd communication Socket.
[   31.175897] systemd[1]: Listening on Journal Socket (/dev/log).
[   31.176334] systemd[1]: Listening on udev Control Socket.
[   31.176550] systemd[1]: Reached target Remote File Systems.
[   31.176704] systemd[1]: Reached target Swap.
[   31.615583] EXT4-fs (mmcblk1p1): re-mounted. Opts: errors=remount-ro
[   32.714627] systemd-journald[873]: Received request to flush runtime 
journal from PID 1
[   34.166674] random: crng init done
[   34.166698] random: 7 urandom warning(s) missed due to ratelimiting
[   39.624602] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
[   41.169342] using random self ethernet address
[   41.169362] using random host ethernet address
[   41.238422] net eth0: initializing cpsw version 1.12 (0)
[   41.315227] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver 
[SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=POLL)
[   41.344681] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   42.089601] Mass Storage Function, version: 2009/09/11
[   42.089624] LUN: removable file: (no medium)
[   42.723517] using random self ethernet address
[   42.723537] using random host ethernet address
[   43.094457] usb0: HOST MAC 74:e1:82:62:fc:20
[   43.098695] usb0: MAC 74:e1:82:62:fc:21
[   43.117882] usb1: HOST MAC 74:e1:82:62:fc:23
[   43.118204] usb1: MAC 74:e1:82:62:fc:24
[   43.359164] cpsw 4a10.ethernet eth0: Link is Up - 100Mbps/Full - 
flow control rx/tx
[   43.359253] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   43.509508] configfs-gadget gadget: high-speed config #1: c
[   43.735440] 8021q: 802.1Q VLAN Support v1.8
[   43.736197] 8021q: adding VLAN 0 to HW filter on device eth0
[   44.594345] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
[   95.541078] pvrsrvkm: loading out-of-tree module taints kernel.
[   95.572136] pruss 4a30.pruss: creating PRU cores and other child 
platform devices
[   95.603724] remoteproc remoteproc1: 4a334000.pru is available
[   95.603854] pru-rproc 4a334000.pru: PRU rproc node 
/ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed successfully
[   95.617530] remoteproc remoteproc2: 4a338000.pru is available
[   95.617648] pru-rproc 4a338000.pru: PRU rproc node 
/ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfully
[   95.717866] [drm:drm_minor_register]
[   95.717885] [drm:drm_minor_register]
[   95.718403] [drm:drm_minor_register] new minor registered 128
[   95.718415] [drm:drm_minor_register]
[   95.724539] [drm:drm_minor_register] new minor registered 1
[   95.730470] [drm] Initialized pvr 1.14.3699939 20110701 for 5600.sgx 
on minor 1

On Monday, February 24, 2020 at 11:46:53 AM UTC-5, Dennis Bieber wrote:
>
> On Sun, 23 Feb 2020 14:07:27 -0800 (PST), in 
> gmane.comp.hardware.beagleboard.user 
> mikerostosky-pkbjnfxxiarbdgjk7y7...@public.gmane.org  wrote: 
>
> > 
> > 
> > 
> >My application uses a beaglebone black rev C. The application is written 
> in 
> >python and uses serial ports, Adafruit_BBIO.PWM and GPIO and is started 
> by 
> >systemctl as a service. There is no graphical interface, just an LCD 
> >controlled with GPIO. It takes 90 seconds after boot up before the 
> program 
> >sounds the 'greeting' with PWM. I need to reduce this to <10 seconds. I 
> had 
> >high hopes for an older 2Gb image, but I think it predated the universal 
> >cape and I was having trouble getting it to work. There is also an IOT 
> >image, but some gpio's didn't work. After update_kernal.sh the gpio's 
> >worked and I'm on 4.14.108. I'm not sure this is even the IOT image 
> >anymore. I've tried various tweaks I've found on the web without much 
> >success. Can I make a standard 

[beagleboard] Re: Need advice on how to reduce boot time

[Dennis Lee Bieber]

On Sun, 23 Feb 2020 14:07:27 -0800 (PST), in
gmane.comp.hardware.beagleboard.user
mikerostosky-pkbjnfxxiarbdgjk7y7...@public.gmane.org wrote:

>
>
>
>My application uses a beaglebone black rev C. The application is written in 
>python and uses serial ports, Adafruit_BBIO.PWM and GPIO and is started by 
>systemctl as a service. There is no graphical interface, just an LCD 
>controlled with GPIO. It takes 90 seconds after boot up before the program 
>sounds the 'greeting' with PWM. I need to reduce this to <10 seconds. I had 
>high hopes for an older 2Gb image, but I think it predated the universal 
>cape and I was having trouble getting it to work. There is also an IOT 
>image, but some gpio's didn't work. After update_kernal.sh the gpio's 
>worked and I'm on 4.14.108. I'm not sure this is even the IOT image 
>anymore. I've tried various tweaks I've found on the web without much 
>success. Can I make a standard image work and if so how? Must I create my 
>own image? Where do I start? Thank you, Mike.

While it won't catch pre-kernel activity, have you checked the dmesg
list for what may be taking a long time in the start up sequence.

debian@beaglebone:~$ dmesg
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.14.108-ti-r113
(root@x1-am57xx-beagle-x15-2gb) (gcc version 6.3.0 20170516 (Debian
6.3.0-18+deb9u1)) #1 SMP PREEMPT Wed Jul 31 00:01:10 UTC 2019
[0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7),
cr=10c5387d



[1.403928] of_cfs_init
[1.404112] of_cfs_init: OK
[1.405499] ALSA device list:
[1.405510]   No soundcards found.
[1.412495] Freeing unused kernel memory: 1024K
[   23.407696] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data
mode. Opts: (null)
[   24.075336] systemd[1]: System time before build time, advancing clock.



Some 20+ seconds seem to have been lost in mounting the uSD file system

[   24.172908] ip_tables: (C) 2000-2006 Netfilter Core Team



[   25.507732] pru-rproc 4a338000.pru: PRU rproc node
/ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfully
[   26.566698] systemd-journald[1665]: Received request to flush runtime
journal from PID 1
[   33.501536] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
[   33.810548] pvrsrvkm: loading out-of-tree module taints kernel.



Another 6+ seconds going from the flush to nf_conntrack


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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/m5v75f5dfojjq97f5t5hitisopcc4hrvpk%404ax.com.

[beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6

[rileyboy36]

Searching for text messages from 2014 to 2016 from 810-399-9069

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/321a4f68-557b-4052-80db-1460cf1a7eac%40googlegroups.com.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[andrexice]

Hi Andrew thanks for all your hard work can you assist me to add a new 
4dcape-70ct cbl 
works with 4dcape-70t but not with the new 4dcape-70ct cbl 

Regards
Andre
 
On Sunday, 28 September 2014 17:14:24 UTC+2, Andrew Henderson wrote:
>
> Hello all. I have released a new port of Android for the BBB.  This 
> version uses AOSP 4.4.4 (KitKat) and the 3.8 Linux kernel. I have made 
> build instructions and a pre-made image available at 
> http://www.bbbandroid.org.  I use a combination of AOSP repos and Rowboat 
> build scripts, and I have a few custom repos for the kernel, bootloader, 
> and additional "external" tools (such as i2c-tools).  You can view the repo 
> manifest XML file for the project here:
>
>
> https://github.com/hendersa/bbbandroid-manifest/blob/master/bbbandroid-aosp-4.4.4_r1-3.8.xml
>
> Because this Android image uses the 3.8 kernel, you should be able to just 
> plug in your capes and go without any hassle:
>
> Built-in HDMI cape:
> http://i.imgur.com/q4AZQ95.jpg
>
> 4D Systems LCD capes:
> 4DCAPE-43T: http://i.imgur.com/6qHmgqX.jpg
> 4DCAPE-70T: http://i.imgur.com/UZLG7Or.jpg
>
> CircuitCo LCD capes:
> LCD3: http://i.imgur.com/LC7SrBB.jpg 
> LCD4: http://i.imgur.com/1xBQ8R6.jpg
> LCD7: http://i.imgur.com/vxoqROE.jpg
>
> Andrew
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/56d25eeb-4852-436a-a544-a84c3fedb9f4%40googlegroups.com.

[beagleboard] Re: Need advice on how to reduce boot time

[TJF]

On

4.14.146-bone29

I've a system starting my custom application after 7 s. The entire boot 
process ends after 18 s, WiFi network connection included.

It's a standard image, but no cape-universal overlays ==> no Adafruit 
libraries, instead libpruio. 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9f273942-6b51-4131-8895-eb4707de931d%40googlegroups.com.

Re: [beagleboard] download SDKs and CCS IDE onto beaglebone

['Mark Lazarewicz' via BeagleBoard]

Last time I checked BB AI isn't supported.

The JTAG may be over FDTI or direct connection. check docs.It  is only used for 
debugging not installing.If it's not FTDI you may also need to buy the cheapest 
JTAG


It's been that way for for many years CCS has become free and RTOS are free to 
use but only on the official TI Dev board.
You think they spend money porting to every ameatuers board and sell no 
chips?螺 Maybe they port to your board too.
Verify that here in supported hardware of videos it may have changed.
http://www.ti.com/tool/PROCESSOR-SDK-AM57X
If I remember after watching videos you can run RTOS on both ARM and DSP cores.
Process installing isn't difficult you must be able to read and Google and 
somehow avoid bad  advise from responder's who debug using serial Port 
Good Luck 

Sent from Yahoo Mail on Android 
 
  On Mon, Feb 24, 2020 at 3:06 AM, Hugo van den Brand 
wrote:   

Op ma 24 feb. 2020 05:03 schreef Tejas Pidkalwar :

Hi,
I am trying to download linux and RTOS SDKs to Beaglebone AI from my host PC 
ubuntu 18.04.Could anyone help me with the process of downloading these to 
beaglebone AI? And will this process required ftdi cable connection?

I guess you need this link http://www.ti.com/tool/PROCESSOR-SDK-AM57XThere is 
plenty of documentation on that site. 
The bandwidth of the ftdi is not enough. The cable is only used for terminal 
access, which comes in handy to see what is happening on the system. 
Typically, you put an image on an SD card or you connect via Ethernet or Wlan 
to get an image on the device. 



-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a4fae780-6bf8-41d3-9d85-10463277cc5a%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHK0gJ0rQdqn5tGWMBJ6qOduJ9M4XZynJjCc1y7sSxKvbkpmsg%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/259194436.713277.1582540918834%40mail.yahoo.com.

Re: [beagleboard] download SDKs and CCS IDE onto beaglebone AI from host PC ubuntu 18.04

[Hugo van den Brand]

Op ma 24 feb. 2020 05:03 schreef Tejas Pidkalwar :

> Hi,
>
> I am trying to download linux and RTOS SDKs to Beaglebone AI from my host
> PC ubuntu 18.04.
> Could anyone help me with the process of downloading these to beaglebone
> AI? And will this process required ftdi cable connection?
>

I guess you need this link http://www.ti.com/tool/PROCESSOR-SDK-AM57X
There is plenty of documentation on that site.

The bandwidth of the ftdi is not enough. The cable is only used for
terminal access, which comes in handy to see what is happening on the
system.

Typically, you put an image on an SD card or you connect via Ethernet or
Wlan to get an image on the device.

-- 
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/a4fae780-6bf8-41d3-9d85-10463277cc5a%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHK0gJ0rQdqn5tGWMBJ6qOduJ9M4XZynJjCc1y7sSxKvbkpmsg%40mail.gmail.com.

Re: [beagleboard] Beaglebone blue, buildroot and wifi

[Hugo van den Brand]

Op ma 24 feb. 2020 05:03 schreef :

>
> Hi,
>
> I recently purchased a beaglebone blue and tried it with pre-installed
> image and the latest debian image from beagleboard.org. Everything is ok
> and the wifi works perfectly.
>
> Now, I want to build my own custom image with buildroot. I have some
> experience with buildroot and raspberry pi. I managed to have a bootable
> image with linux console on uart. The problem is that when I try to
> activate wlan0 (ip link set wlan0 up), the  board hangs. I cannot connect
> to ssh anymore (USB connection), I cannot access it via the uart linux
> console (no more log from kernel), the heartbeat LED stops blinking, the
> only thing i can do is ping the board (through USB).
>

That sounds like a kernel panic.
Is any logging of this event written to a file that you can look at after
boot?
Do you get any output the moment it happens?

Do you have the kernel module for wlan compiled into the kernel? You might
get a bit more logging if it is a module.


> What I have tried so far,
>
> Use different firmware (/lib/firmware/ti-connectivity) from:
> * Buildroot linux-firmware package
> * Beaglebone Black wireless firmware (on github)
> * Pre installed firmware from the official Debian image
>
> Use different device-tree
> * am35x-boneblue.dts built with the linux kernel by buildroot
> * the devicetree provided in the official Debian image
>

I trust you know that the device tree  can be specific for a kernel.
For my beaglebone black, there are huge differences between the beaglebone
kernel and the stable kernel from kernel.org.

I would try it as well with the beaglebone kernel and matching device tree.
https://github.com/beagleboard/linux
If you see that working you could backtrack where the differences are.



> Use different libc
> * µclibc
> * glibc
>

I don't think that matters that much. Errors in those libraries are not
that common and would probably cause more errors.
Glibc is used more, so to be safe stick to that.


> At this point I end up every time with the symptoms described before.
> Could anyone help to investigate further?
>
> Thank you,
>
> Thomas
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/d9993f35-7307-4452-9789-be3aa5507d6e%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHK0gJ3LcDYR1%2Brn_x4kcTR2NkPy7iuo%2BZAO%3DgpoMnmnytpKgQ%40mail.gmail.com.