[beagleboard] kernel boot failed after adding u-boot splash screen

2017-10-23 Thread laksono budi 




hi everyone any one can help? i have successed with adding splash screen in 
my u-boot, but after that when i load the kernel, i have some error like a 
picture...

-- 
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/e9aba5fc-3a28-44b1-9b98-6cb51390abfd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] kernel boot file after modify u-boot with splash screen

2017-10-23 Thread Robert Nelson 
On Oct 23, 2017 9:30 PM, "laksono budi"  wrote:



hi everyone any one can help? i have successed with adding splash screen in
my u-boot but after that when i load the kernel, i have some error like a
picture...


We it looks like the musb bus couldn't get the dma channel. But your
running 3.14.x sorry most users have moved if that kernel.

Regards,

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgi7xRjHHRFO-gPSr1cbhjS-5AaYM8cKtFpOii-5haivw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] kernel boot file after modify u-boot with splash screen

2017-10-23 Thread laksono budi 




hi everyone any one can help? i have successed with adding splash screen in 
my u-boot but after that when i load the kernel, i have some error like a 
picture...

-- 
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/11f36f9b-6617-4263-bbef-c662a0abb307%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BeagleBoard, G540, Linux CNC

2017-10-23 Thread mrarmyant 

Wanting to replace my dead CNC computer with a beagleboard.  I have a G540 
controller.  Everyone says to connect it to the beaglebone but I see no 
tutorial anywhere on pinning up a db25 connector to the board.  This seems 
so simple... lol.  Can anyone point me in the correct direction?

-- 
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/eb410c23-7fbf-47ff-9188-8391aa3b5f02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Powering the BeagleBone Blue?

2017-10-23 Thread ajsaenz 
Yes, only 2 Cell LiPo batteries are supported.  Note that the charge 
circuit is setup to charge at 1Amp, so make sure you use a battery that can 
that charge rate.  If you use at least a 1000mAh battery you should be fine.

-Longer lived batteries:  You can use larger capacity batteries (e.g. 
1500mAh, 2000mAh, 3000mAh, etc.) as long as they are *2 cell* Lipo.  

-More power draw (e.g. motors):  The on board motor drives can drive about 
1.2 Amp per motor which is really only enough for small motors, anything 
more and you'll burn the drive chip.  If you want to drive bigger motors 
you'll need external motor drivers that can handle the current.

-BBBlue via the barrel input:  The barrel input is really to charge the 
battery or run the board without a battery.  It is not intended as a way to 
provide more power to motors.  If you need more power for motors you need 
external motor drivers.




On Thursday, October 19, 2017 at 9:40:37 PM UTC-7, Unlisted Unlisted wrote:
>
> I see there's a connector labeled LIPO and In looking at the specs for the 
> Beagle Bone Blue it states that this is for
>
> "2 cell (2S) LiPo battery connector " 
>
> ( Short-Spec 
> 
>  
> and Schematic 
> 
>  
> ) 
>
> Does that mean that in that connector, only 2 Cell LiPo batteries are 
> supposed to be used? 
>
> What about wanting to have a battery operated robot with longer-lived 
> batteries and more power draw (e.g. motors)? Does that mean you need to 
> power the BBBlue via the barrel input and if so - then is it recommended 
> that you also have a 2 Cell LiPo battery connected to the LIPO connector?
>

-- 
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/89e15533-b530-49f5-898e-4d34bb74b8b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Windows 10 Bone_D64.exe Failing

2017-10-23 Thread leonardjowers 
Thank you!

On Wednesday, August 12, 2015 at 10:13:13 PM UTC-5, mscleavite wrote:
>
> I have just upgraded to Windows 10 on a machine that I have not previously 
> connected my BBB to.  I had success on other windows 8 machines as well as 
> SSHing using Putty.  I have spent SOME time searching forums and not 
> finding much at all on Windows 10.  During the install of the Bone_D64.exe, 
> the driver the status returned on all the drivers is "Install Failed".  Let 
> the flaming begin.  Or hopefully there is someone out there that has 
> encountered and concurred 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4a14e2d7-8913-4fd0-9c0c-f47a3857e149%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] beagle bone black is not booting from SD card

2017-10-23 Thread tlsmith3777 
Hi Madhu,

what did you change in your uEnv.txt to fix this issue? Thanks you

On Sunday, February 5, 2017 at 12:47:05 AM UTC-6, Madhu K wrote:
>
> Hi All,
>
> I could able to boot now from SD card, I fixed it uEnv.txt.
>
> Thank you
>
> On Sat, Feb 4, 2017 at 6:48 PM, Madhu K > 
> wrote:
>
>> Hi,
>>
>> while booting the beaglebone black board from SD card, boot process stuck 
>> with below errors. what could be the reason?
>>
>>
>> Terminal ready
>>
>> U-Boot SPL 2017.03-rc1-dirty (Feb 04 2017 - 17:38:05)
>> Trying to boot from MMC1
>> reading u-boot.img
>> reading u-boot.img
>>
>>
>> U-Boot 2017.03-rc1-dirty (Feb 04 2017 - 17:38:05 +0530)
>>
>> CPU  : AM335X-GP rev 2.1
>> I2C:   ready
>> DRAM:  512 MiB
>> Reset Source: Power-on reset has occurred.
>> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
>> Using default environment
>>
>>  not set. Validating first E-fuse MAC
>> BeagleBone Black:
>> BeagleBone: cape eeprom: i2c_probe: 0x54:
>> BeagleBone: cape eeprom: i2c_probe: 0x55:
>> BeagleBone: cape eeprom: i2c_probe: 0x56:
>> BeagleBone: cape eeprom: i2c_probe: 0x57:
>> Net:   eth0: MII MODE
>> cpsw
>> Press SPACE to abort autoboot in 2 seconds
>> board_name=[A335BNLT] ...
>> board_rev=[00C0] ...
>> switch to partitions #0, OK
>> mmc0 is current device
>> SD/MMC found on device 0
>> ** Bad device 0:2 0x8200 **
>> ** Bad device 0:2 0x8200 **
>> switch to partitions #0, OK
>> mmc0 is current device
>> Scanning mmc 0:1...
>> gpio: pin 56 (gpio 56) value is 0
>> gpio: pin 55 (gpio 55) value is 0
>> gpio: pin 54 (gpio 54) value is 0
>> gpio: pin 53 (gpio 53) value is 1
>> switch to partitions #0, OK
>> mmc0 is current device
>> gpio: pin 54 (gpio 54) value is 1
>> Checking for: /uEnv.txt ...
>> Checking for: /boot.scr ...
>> Checking for: /boot/boot.scr ...
>> Checking for: /boot/uEnv.txt ...
>> gpio: pin 55 (gpio 55) value is 1
>> 659 bytes read in 18 ms (35.2 KiB/s)
>> Loaded environment from /boot/uEnv.txt
>> Checking if uname_r is set in /boot/uEnv.txt...
>> ** Invalid partition 3 **
>> ** Invalid partition 4 **
>> ** Invalid partition 5 **
>> ** Invalid partition 6 **
>> ** Invalid partition 7 **
>> switch to partitions #0, OK
>> mmc1(part 0) is current device
>> Scanning mmc 1:1...
>> gpio: pin 56 (gpio 56) value is 0
>> gpio: pin 55 (gpio 55) value is 0
>> gpio: pin 54 (gpio 54) value is 0
>> gpio: pin 53 (gpio 53) value is 1
>> switch to partitions #0, OK
>> mmc1(part 0) is current device
>> gpio: pin 54 (gpio 54) value is 1
>> Checking for: /uEnv.txt ...
>> reading uEnv.txt
>> 26 bytes read in 4 ms (5.9 KiB/s)
>> gpio: pin 55 (gpio 55) value is 1
>> Loaded environment from /uEnv.txt
>> Importing environment from mmc ...
>> Checking if uenvcmd is set ...
>> gpio: pin 56 (gpio 56) value is 1
>> Running uenvcmd ...
>> syntax error
>> syntax error
>> ** Invalid partition 7 **
>> Checking if client_ip is set ...
>> Checking for: /boot.scr ...
>> Checking for: /boot/boot.scr ...
>> Checking for: /boot/uEnv.txt ...
>> gpio: pin 55 (gpio 55) value is 1
>> 33 bytes read in 37 ms (0 Bytes/s)
>> Loaded environment from /boot/uEnv.txt
>> Checking if uname_r is set in /boot/uEnv.txt...
>> ** Invalid partition 3 **
>> ** Invalid partition 4 **
>> ** Invalid partition 5 **
>> ** Invalid partition 6 **
>> ** Invalid partition 7 **
>> starting USB...
>> USB0:   Port not available.
>> cpsw Waiting for PHY auto negotiation to complete. TIMEOUT !
>> BOOTP broadcast 1
>> BOOTP broadcast 2
>> BOOTP broadcast 3
>> BOOTP broadcast 4
>> BOOTP broadcast 5
>> BOOTP broadcast 6
>> BOOTP broadcast 7
>> BOOTP broadcast 8
>> BOOTP broadcast 9
>> BOOTP broadcast 10
>> BOOTP broadcast 11
>> BOOTP broadcast 12
>> BOOTP broadcast 13
>> BOOTP broadcast 14
>> BOOTP broadcast 15
>> BOOTP broadcast 16
>> BOOTP broadcast 17
>> BOOTP broadcast 18
>> BOOTP broadcast 19
>> BOOTP broadcast 20
>> BOOTP broadcast 21
>> BOOTP broadcast 22
>> BOOTP broadcast 23
>> BOOTP broadcast 24
>> BOOTP broadcast 25
>> BOOTP broadcast 26
>> BOOTP broadcast 27
>> BOOTP broadcast 28
>> BOOTP broadcast 29
>>
>> Retry time exceeded; starting again
>> missing environment variable: pxeuuid
>> Retrieving file: pxelinux.cfg/01-d0-39-72-97-9f-4d
>> cpsw Waiting for PHY auto negotiation to complete. TIMEOUT !
>> *** ERROR: `serverip' not set
>> Retrieving file: pxelinux.cfg/
>> cpsw Waiting for PHY auto negotiation to complete. TIMEOUT !
>> *** ERROR: `serverip' not set
>> Retrieving file: pxelinux.cfg/000
>> cpsw Waiting for PHY auto negotiation to complete. TIMEOUT !
>> *** ERROR: `serverip' not set
>> Retrieving file: pxelinux.cfg/00
>> cpsw Waiting for PHY auto negotiation to complete. TIMEOUT !
>> *** ERROR: `serverip' not set
>> Retrieving file: pxelinux.cfg/0
>> cpsw Waiting for PHY auto negotiation to complete. TIMEOUT !
>> *** ERROR: `serverip' not set
>> Retrieving file: pxelinux.cfg/
>> cpsw Waiting for PHY auto negotiation to complete. TIMEOUT !
>> *** ERROR: `serverip' not set
>>

Re: [beagleboard] Beagleboard XM boot hangs on kernel 3.14.20

2017-10-23 Thread Robert Nelson 
On Mon, Oct 23, 2017 at 10:38 AM, 'Kai' via BeagleBoard
 wrote:
> Hi!
>
> I just kickstarted to build kernel 3.14.20 for xM. when it boots, it hangs
> on the following, but it worked on 3.2 when I built using gcc 4.7 before. I
> suspect it is related to gcc version, currently it is 7.2.1.  I tried to
> build 3.2 using gcc 7.2.1. it also hangs on boot.

So I'd use gcc 4.7...

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/CAOCHtYh27pVxD%2BT0V-AOxAvs34qtP1tf1MVWwFQn5AeR8wsnuw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beagleboard XM boot hangs on kernel 3.14.20

2017-10-23 Thread 'Kai' via BeagleBoard 
Hi! 

I just kickstarted to build kernel 3.14.20 for xM. when it boots, it hangs 
on the following, but it worked on 3.2 when I built using gcc 4.7 before. I 
suspect it is related to gcc version, currently it is 7.2.1.  I tried to 
build 3.2 using gcc 7.2.1. it also hangs on boot. 

[3.038848] kjournald starting.  Commit interval 5 seconds
[3.049865] EXT3-fs (mmcblk0p2): using internal journal
[3.055389] EXT3-fs (mmcblk0p2): mounted filesystem with ordered data 
mode
[3.062866] VFS: Mounted root (ext3 filesystem) on device 179:2.
[3.073974] devtmpfs: mounted
[3.078399] Freeing unused kernel memory: 380K (c0792000 - c07f1000)
[3.416015] systemd[1]: Failed to insert module 'autofs4': Function not 
implemented
[3.425140] systemd[1]: Failed to insert module 'ipv6': Function not 
implemented
[3.435424] systemd[1]: Failed to insert module 'ip_tables': Function 
not implemented
[3.469726] systemd[1]: Failed to mount tmpfs at /sys/fs/cgroup: No such 
file or directory
[3.489501] systemd[1]: Failed to mount cgroup at 
/sys/fs/cgroup/systemd: No such file or directory
[3.510314] random: systemd urandom read with 32 bits of entropy 
available
[3.522125] systemd[1]: [/etc/systemd/system.conf:10] Unknown section 
'Journal'. Ignoring.
[3.542297] systemd[1]: systemd 226 running in system mode. (+PAM -AUDIT 
-SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT 
+GNUTLS +ACL +XZ -LZ4 )
[3.562164] systemd[1]: Detected architecture arm.

Welcome to The �Ångstr�öm Distribution v2014.12!

[3.590820] systemd[1]: Set hostname to .
[3.607238] systemd[1]: Cannot determine cgroup we are running in: No 
such file or directory
[3.620605] systemd[1]: Failed to allocate manager object: No such file 
or directory
[!!] Failed to allocate manager object, freezing.

-- 
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/14b27500-4916-472f-a056-759a47966d82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone black SYS_5V giving 3V

2017-10-23 Thread scmanop 
Hey, i am not pretty sure about that, but i think that in order to get that 
5V through the aforementioned pin you have to get power from an external 
power supply (and specifically via the 5V DC barrel connector input) and 
not (only) from the usb cable.
Also, you have to keep in mind that the usage of the external 5VDC supply 
is necessary if the external circuit that you are going to use (if you are 
going to use any) or let's say a cape that you use, is "power hungry".

Hope that solves your problem and you don't have a damaged board!

On Sunday, October 22, 2017 at 4:08:54 PM UTC+3, Jonathan Prinsloo wrote:
>
>
> I have the beaglebone black connected to the PC via usb and I am trying to 
> power an Ultrasonic sensor via the SYS_5V but i am only getting 3.1V from 
> this.
> any possible reasons for 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ce881286-c325-4f01-b350-9b76b9d420e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to enable /dev/uio for PRU communication on Debian 9.2 kernel 4.9.54-ti-r68 ?

2017-10-23 Thread simo zz 
Hello Robert,

Thank you very much. It works now. :)

Regards,
Simon

On Mon, Oct 23, 2017 at 4:10 PM, Robert Nelson 
wrote:

> On Mon, Oct 23, 2017 at 3:59 AM, simo zz  wrote:
> > Hello,
> >
> > I am trying to communicate with the PRU unit on a Debian 9.2 and kernel
> > 4.9.54-ti-r68 by Robert Nelson, but the file
>
> 4.9.x-ti-ry is remoteproc pruss only..
>
> Use the 4.9.x-bone kernel
>
> cd /opt/scripts/tools/
> git pull
> sudo ./update_kernel.sh --bone-kernel --lts-4_9
>
> and make sure you set the uio overlay:
>
> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_PRU_Options
>
> 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/CAFvb%3Dpb4%2BcNTugfCHTdd8fF9VYFv9DFhzsKQAT8NdJ2A2XYSeA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to enable /dev/uio for PRU communication on Debian 9.2 kernel 4.9.54-ti-r68 ?

2017-10-23 Thread Robert Nelson 
On Mon, Oct 23, 2017 at 3:59 AM, simo zz  wrote:
> Hello,
>
> I am trying to communicate with the PRU unit on a Debian 9.2 and kernel
> 4.9.54-ti-r68 by Robert Nelson, but the file

4.9.x-ti-ry is remoteproc pruss only..

Use the 4.9.x-bone kernel

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh --bone-kernel --lts-4_9

and make sure you set the uio overlay:

https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_PRU_Options

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/CAOCHtYiQZqcL%3Dgdg_b1JfQ7sLOxP3BhVSpS0q3QeMS0DhYXcJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PocketBeagle SPI device nodes

2017-10-23 Thread Robert Nelson 
On Mon, Oct 23, 2017 at 5:48 AM,   wrote:
> My PocketBeagle, running a custom 4.9.57 kernel and standard device tree,
> creates the following SPI device nodes:
>
> usbgadget# ls -l /dev/spi*
> crw-rw1 root gpio  153,   0 Jan  1 00:00 /dev/spidev1.0
> crw-rw1 root gpio  153,   1 Jan  1 00:00 /dev/spidev1.1
> crw-rw1 root gpio  153,   2 Jan  1 00:00 /dev/spidev2.0
> crw-rw1 root gpio  153,   3 Jan  1 00:00 /dev/spidev2.1
>
> Why are there four device nodes?  Normally there should be a single device
> node for each slave select, and the
> PocketBeagle pinout only lists one slave select for each SPI bus controller.
>
> Which device nodes correspond to which slave selects?  (It appears to me
> that spidev1.x might correspond to McSPIO0
> and spidev2.x might correspond to McSPI1).

There are 4 listed, because i have not yet removed the two
chipselect's that are not available.

spi@4803 at chipselect 0
spi@481a at chipselect 1

patches welcome.

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/CAOCHtYg5qr73ujip9L4Tqz7norxr%2B7yYHctmunxHKVr38F%3DCXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB CAN cape - how to enable CAN interface

2017-10-23 Thread William 

Hello,

I want to use BBB with a CAN cape to parse some messages received on CAN 
bus.
For beginning, I want to see the CAN messages in a terminal with can-utils 
package.

I use the last image available at this time: Debian 9.2 2017-10-10 4GB SD 
IoT 


I need to configure device tree to be able to see CAN interface.
I want to use UART1 for CAN communication.
First step was to download and install bb.org-overlays. 

Since I could not find any useful information on internet for this Debian 
Stretch, can you please tell my how to start doing this configuration?

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e556950a-8570-4ff7-b090-7878b39f0c68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Coding

2017-10-23 Thread Rohit 
Hello, 

We are developing a gateway  application in pocket beagle bone .

Is it better to build the project in C or Python.



..

-- 
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/6af0e029-fdf2-4f5b-b8c6-2d1db82a199c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Pocket Beagle Bone For Mass Production

2017-10-23 Thread Rohit 
Hello, 

Can we use Pocket Beagle Bone for mass production in our product .

Will there be any restriction.

...
Regards
Rohith

-- 
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/c2817f24-ebe7-403a-a104-4091d1c4bfba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] PocketBeagle SPI device nodes

2017-10-23 Thread philip . munts 
My PocketBeagle, running a custom 4.9.57 kernel and standard device tree, 
creates the following SPI device nodes:

usbgadget# ls -l /dev/spi*
crw-rw1 root gpio  153,   0 Jan  1 00:00 /dev/spidev1.0
crw-rw1 root gpio  153,   1 Jan  1 00:00 /dev/spidev1.1
crw-rw1 root gpio  153,   2 Jan  1 00:00 /dev/spidev2.0
crw-rw1 root gpio  153,   3 Jan  1 00:00 /dev/spidev2.1

Why are there four device nodes?  Normally there should be a single device 
node for each slave select, and the
PocketBeagle pinout only lists one slave select for each SPI bus controller.

Which device nodes correspond to which slave selects?  (It appears to me 
that spidev1.x might correspond to McSPIO0
and spidev2.x might correspond to McSPI1).

Phil

-- 
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/bafe7c4e-797f-45fd-bad3-fd0820c58025%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to use PRU with Debian 9.2 and kernel 4.9.54-ti-r68 ?

2017-10-23 Thread simo zz 
Hello,

I need to use the PRU unit on my Beaglebone Black Wireless with *Debian 9.2* 
and kernel *4.9.54-ti-r68*, and I have a few doubts about how to use it.

Looking for *'*pru**' named files on my file-system I have 


































































































*/run/udev/data/+drivers:platform:pruss-soc-bus/run/udev/data/+module:pruss_soc_bus/run/udev/data/+platform:4a326000.pruss-soc-bus/run/udev/data/+mbox:mbox_pru1/run/udev/data/+mbox:mbox_pru0/lib/firmware/uio_pruss_enable-00A0.dtbo/lib/modules/4.9.54-ti-r68/kernel/drivers/remoteproc/pru_rproc.ko/lib/modules/4.9.54-ti-r68/kernel/drivers/remoteproc/pruss.ko/lib/modules/4.9.54-ti-r68/kernel/drivers/remoteproc/pruss_intc.ko/lib/modules/4.9.54-ti-r68/kernel/drivers/remoteproc/pruss_soc_bus.ko/lib/modules/4.9.54-ti-r68/kernel/drivers/rpmsg/rpmsg_pru.ko/var/lib/dpkg/info/libaprutil1-dbd-sqlite3:armhf.md5sums/var/lib/dpkg/info/libaprutil1:armhf.shlibs/var/lib/dpkg/info/libaprutil1:armhf.md5sums/var/lib/dpkg/info/libaprutil1:armhf.list/var/lib/dpkg/info/libaprutil1-ldap:armhf.list/var/lib/dpkg/info/libaprutil1:armhf.symbols/var/lib/dpkg/info/libaprutil1:armhf.triggers/var/lib/dpkg/info/libaprutil1-ldap:armhf.md5sums/var/lib/dpkg/info/libaprutil1-dbd-sqlite3:armhf.list/usr/lib/git-core/git-prune/usr/lib/git-core/git-prune-packed/usr/lib/arm-linux-gnueabihf/libaprutil-1.so.0.5.4/usr/lib/arm-linux-gnueabihf/libaprutil-1.so.0/usr/share/pastebin.d/sprunge.us.conf/usr/share/man/man1/git-prune-packed.1.gz/usr/share/man/man1/git-prune.1.gz/usr/share/doc/libaprutil1-ldap/usr/share/doc/libaprutil1/usr/share/doc/libaprutil1-dbd-sqlite3/usr/share/initramfs-tools/hooks/ti_pru_firmware/usr/share/lintian/overrides/libaprutil1/opt/scripts/device/x15/pru-rpmsg_client_sample/opt/scripts/device/x15/pru-rpmsg_client_sample/am57xx-pru2_1-fw/opt/scripts/device/x15/pru-rpmsg_client_sample/am57xx-pru2_0-fw/opt/scripts/device/x15/pru-rpmsg_client_sample/am57xx-pru1_1-fw/opt/scripts/device/x15/pru-rpmsg_client_sample/am57xx-pru1_0-fw/opt/scripts/device/bone/capes/BB-BEAGLELOGIC/beaglelogic-pru0/opt/scripts/device/bone/capes/BB-BEAGLELOGIC/beaglelogic-pru1/opt/scripts/device/bone/pru-rpmsg_client_sample/opt/scripts/device/bone/pru-rpmsg_client_sample/am335x-pru0-fw/opt/scripts/device/bone/pru-rpmsg_client_sample/am335x-pru1-fw/opt/source/dtb-4.4-ti/src/arm/am33xx-pruss-rproc.dtsi/opt/source/dtb-4.4-ti/src/arm/am33xx-pruss-uio.dtsi/opt/source/bb.org-overlays/src/arm/uio_pruss_enable-00A0.dts/sys/kernel/debug/clk/pruss_ocp_gclk/sys/devices/platform/ocp/4a30.pruss/sys/devices/platform/ocp/4a326000.pruss-soc-bus/sys/devices/platform/ocp/480c8000.mailbox/mbox/mbox_pru1/sys/devices/platform/ocp/480c8000.mailbox/mbox/mbox_pru0/sys/class/mbox/mbox_pru1/sys/class/mbox/mbox_pru0/sys/firmware/devicetree/base/__symbols__/mbox_pru1/sys/firmware/devicetree/base/__symbols__/pru1/sys/firmware/devicetree/base/__symbols__/pruss/sys/firmware/devicetree/base/__symbols__/pruss_soc_bus/sys/firmware/devicetree/base/__symbols__/mbox_pru0/sys/firmware/devicetree/base/__symbols__/pru0/sys/firmware/devicetree/base/__symbols__/pruss_ocp_gclk/sys/firmware/devicetree/base/__symbols__/pruss_mdio/sys/firmware/devicetree/base/__symbols__/pruss_intc/sys/firmware/devicetree/base/ocp/pruss_soc_bus@4a326000/sys/firmware/devicetree/base/ocp/pruss_soc_bus@4a326000/pruss@4a30/sys/firmware/devicetree/base/ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a338000/sys/firmware/devicetree/base/ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a334000/sys/firmware/devicetree/base/ocp/pruss@4a30/sys/firmware/devicetree/base/ocp/mailbox@480C8000/mbox_pru1/sys/firmware/devicetree/base/ocp/mailbox@480C8000/mbox_pru0/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_42_pru_ecap_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_91_pruout_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_27_pruin_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_41_pruin_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_91_pruin_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P8_15_pru_ecap_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P8_11_pruout_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_92_pruout_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P8_16_pruin_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_17_pru_uart_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_21_pru_uart_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_26_pru_uart_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P8_12_pruout_pin/sys/firmware/devicetree/bas

[beagleboard] How to enable /dev/uio for PRU communication on Debian 9.2 kernel 4.9.54-ti-r68 ?

2017-10-23 Thread simo zz 
Hello,

I am trying to communicate with the PRU unit on a *Debian 9.2* and kernel 
*4.9.54-ti-r68* by Robert Nelson, but the file

*/dev/uio*

is not loaded / enabled by default. Looking for **pru** on my file-system I 
have:









































































































*/run/udev/data/+drivers:platform:pruss-soc-bus/run/udev/data/+module:pruss_soc_bus/run/udev/data/+platform:4a326000.pruss-soc-bus/run/udev/data/+mbox:mbox_pru1/run/udev/data/+mbox:mbox_pru0/lib/firmware/uio_pruss_enable-00A0.dtbo/lib/modules/4.9.54-ti-r68/kernel/drivers/remoteproc/pru_rproc.ko/lib/modules/4.9.54-ti-r68/kernel/drivers/remoteproc/pruss.ko/lib/modules/4.9.54-ti-r68/kernel/drivers/remoteproc/pruss_intc.ko/lib/modules/4.9.54-ti-r68/kernel/drivers/remoteproc/pruss_soc_bus.ko/lib/modules/4.9.54-ti-r68/kernel/drivers/rpmsg/rpmsg_pru.ko/var/lib/dpkg/info/libaprutil1-dbd-sqlite3:armhf.md5sums/var/lib/dpkg/info/libaprutil1:armhf.shlibs/var/lib/dpkg/info/libaprutil1:armhf.md5sums/var/lib/dpkg/info/libaprutil1:armhf.list/var/lib/dpkg/info/libaprutil1-ldap:armhf.list/var/lib/dpkg/info/libaprutil1:armhf.symbols/var/lib/dpkg/info/libaprutil1:armhf.triggers/var/lib/dpkg/info/libaprutil1-ldap:armhf.md5sums/var/lib/dpkg/info/libaprutil1-dbd-sqlite3:armhf.list/usr/lib/git-core/git-prune/usr/lib/git-core/git-prune-packed/usr/lib/arm-linux-gnueabihf/libaprutil-1.so.0.5.4/usr/lib/arm-linux-gnueabihf/libaprutil-1.so.0/usr/lib/libprussdrv.so/usr/local/lib/libprussdrvd.a/usr/local/lib/libprussdrvd.so/usr/local/lib/libprussdrv.a/usr/local/lib/libprussdrv.so/usr/local/include/prussdrv.h/usr/local/include/pruss_intc_mapping.h/usr/share/pastebin.d/sprunge.us.conf/usr/share/man/man1/git-prune-packed.1.gz/usr/share/man/man1/git-prune.1.gz/usr/share/doc/libaprutil1-ldap/usr/share/doc/libaprutil1/usr/share/doc/libaprutil1-dbd-sqlite3/usr/share/initramfs-tools/hooks/ti_pru_firmware/usr/share/lintian/overrides/libaprutil1/opt/scripts/device/x15/pru-rpmsg_client_sample/opt/scripts/device/x15/pru-rpmsg_client_sample/am57xx-pru2_1-fw/opt/scripts/device/x15/pru-rpmsg_client_sample/am57xx-pru2_0-fw/opt/scripts/device/x15/pru-rpmsg_client_sample/am57xx-pru1_1-fw/opt/scripts/device/x15/pru-rpmsg_client_sample/am57xx-pru1_0-fw/opt/scripts/device/bone/capes/BB-BEAGLELOGIC/beaglelogic-pru0/opt/scripts/device/bone/capes/BB-BEAGLELOGIC/beaglelogic-pru1/opt/scripts/device/bone/pru-rpmsg_client_sample/opt/scripts/device/bone/pru-rpmsg_client_sample/am335x-pru0-fw/opt/scripts/device/bone/pru-rpmsg_client_sample/am335x-pru1-fw/opt/source/dtb-4.4-ti/src/arm/am33xx-pruss-rproc.dtsi/opt/source/dtb-4.4-ti/src/arm/am33xx-pruss-uio.dtsi/opt/source/bb.org-overlays/src/arm/uio_pruss_enable-00A0.dts/sys/kernel/debug/clk/pruss_ocp_gclk/sys/devices/platform/ocp/4a30.pruss/sys/devices/platform/ocp/4a326000.pruss-soc-bus/sys/devices/platform/ocp/480c8000.mailbox/mbox/mbox_pru1/sys/devices/platform/ocp/480c8000.mailbox/mbox/mbox_pru0/sys/class/mbox/mbox_pru1/sys/class/mbox/mbox_pru0/sys/firmware/devicetree/base/__symbols__/mbox_pru1/sys/firmware/devicetree/base/__symbols__/pru1/sys/firmware/devicetree/base/__symbols__/pruss/sys/firmware/devicetree/base/__symbols__/pruss_soc_bus/sys/firmware/devicetree/base/__symbols__/mbox_pru0/sys/firmware/devicetree/base/__symbols__/pru0/sys/firmware/devicetree/base/__symbols__/pruss_ocp_gclk/sys/firmware/devicetree/base/__symbols__/pruss_mdio/sys/firmware/devicetree/base/__symbols__/pruss_intc/sys/firmware/devicetree/base/ocp/pruss_soc_bus@4a326000/sys/firmware/devicetree/base/ocp/pruss_soc_bus@4a326000/pruss@4a30/sys/firmware/devicetree/base/ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a338000/sys/firmware/devicetree/base/ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a334000/sys/firmware/devicetree/base/ocp/pruss@4a30/sys/firmware/devicetree/base/ocp/mailbox@480C8000/mbox_pru1/sys/firmware/devicetree/base/ocp/mailbox@480C8000/mbox_pru0/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_42_pru_ecap_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_91_pruout_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_27_pruin_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_41_pruin_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_91_pruin_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P8_15_pru_ecap_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P8_11_pruout_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_92_pruout_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P8_16_pruin_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_17_pru_uart_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_21_pru_uart_pin/s

[beagleboard] How to enable /dev/uio for PRU communication on Debian 9.2 with kernel 4.9.54-ti-r68

2017-10-23 Thread simo zz 
Hello,

I am trying to communicate with the PRU unit on a *Debian 9.2* and kernel 
*4.9.54-ti-r68* by Robert Nelson, but the file

*/dev/uio*

is not loaded / enabled by default. Looking for **pru** on my file-system I 
have:









































































































*/run/udev/data/+drivers:platform:pruss-soc-bus/run/udev/data/+module:pruss_soc_bus/run/udev/data/+platform:4a326000.pruss-soc-bus/run/udev/data/+mbox:mbox_pru1/run/udev/data/+mbox:mbox_pru0/lib/firmware/uio_pruss_enable-00A0.dtbo/lib/modules/4.9.54-ti-r68/kernel/drivers/remoteproc/pru_rproc.ko/lib/modules/4.9.54-ti-r68/kernel/drivers/remoteproc/pruss.ko/lib/modules/4.9.54-ti-r68/kernel/drivers/remoteproc/pruss_intc.ko/lib/modules/4.9.54-ti-r68/kernel/drivers/remoteproc/pruss_soc_bus.ko/lib/modules/4.9.54-ti-r68/kernel/drivers/rpmsg/rpmsg_pru.ko/var/lib/dpkg/info/libaprutil1-dbd-sqlite3:armhf.md5sums/var/lib/dpkg/info/libaprutil1:armhf.shlibs/var/lib/dpkg/info/libaprutil1:armhf.md5sums/var/lib/dpkg/info/libaprutil1:armhf.list/var/lib/dpkg/info/libaprutil1-ldap:armhf.list/var/lib/dpkg/info/libaprutil1:armhf.symbols/var/lib/dpkg/info/libaprutil1:armhf.triggers/var/lib/dpkg/info/libaprutil1-ldap:armhf.md5sums/var/lib/dpkg/info/libaprutil1-dbd-sqlite3:armhf.list/usr/lib/git-core/git-prune/usr/lib/git-core/git-prune-packed/usr/lib/arm-linux-gnueabihf/libaprutil-1.so.0.5.4/usr/lib/arm-linux-gnueabihf/libaprutil-1.so.0/usr/lib/libprussdrv.so/usr/local/lib/libprussdrvd.a/usr/local/lib/libprussdrvd.so/usr/local/lib/libprussdrv.a/usr/local/lib/libprussdrv.so/usr/local/include/prussdrv.h/usr/local/include/pruss_intc_mapping.h/usr/share/pastebin.d/sprunge.us.conf/usr/share/man/man1/git-prune-packed.1.gz/usr/share/man/man1/git-prune.1.gz/usr/share/doc/libaprutil1-ldap/usr/share/doc/libaprutil1/usr/share/doc/libaprutil1-dbd-sqlite3/usr/share/initramfs-tools/hooks/ti_pru_firmware/usr/share/lintian/overrides/libaprutil1/opt/scripts/device/x15/pru-rpmsg_client_sample/opt/scripts/device/x15/pru-rpmsg_client_sample/am57xx-pru2_1-fw/opt/scripts/device/x15/pru-rpmsg_client_sample/am57xx-pru2_0-fw/opt/scripts/device/x15/pru-rpmsg_client_sample/am57xx-pru1_1-fw/opt/scripts/device/x15/pru-rpmsg_client_sample/am57xx-pru1_0-fw/opt/scripts/device/bone/capes/BB-BEAGLELOGIC/beaglelogic-pru0/opt/scripts/device/bone/capes/BB-BEAGLELOGIC/beaglelogic-pru1/opt/scripts/device/bone/pru-rpmsg_client_sample/opt/scripts/device/bone/pru-rpmsg_client_sample/am335x-pru0-fw/opt/scripts/device/bone/pru-rpmsg_client_sample/am335x-pru1-fw/opt/source/dtb-4.4-ti/src/arm/am33xx-pruss-rproc.dtsi/opt/source/dtb-4.4-ti/src/arm/am33xx-pruss-uio.dtsi/opt/source/bb.org-overlays/src/arm/uio_pruss_enable-00A0.dts/sys/kernel/debug/clk/pruss_ocp_gclk/sys/devices/platform/ocp/4a30.pruss/sys/devices/platform/ocp/4a326000.pruss-soc-bus/sys/devices/platform/ocp/480c8000.mailbox/mbox/mbox_pru1/sys/devices/platform/ocp/480c8000.mailbox/mbox/mbox_pru0/sys/class/mbox/mbox_pru1/sys/class/mbox/mbox_pru0/sys/firmware/devicetree/base/__symbols__/mbox_pru1/sys/firmware/devicetree/base/__symbols__/pru1/sys/firmware/devicetree/base/__symbols__/pruss/sys/firmware/devicetree/base/__symbols__/pruss_soc_bus/sys/firmware/devicetree/base/__symbols__/mbox_pru0/sys/firmware/devicetree/base/__symbols__/pru0/sys/firmware/devicetree/base/__symbols__/pruss_ocp_gclk/sys/firmware/devicetree/base/__symbols__/pruss_mdio/sys/firmware/devicetree/base/__symbols__/pruss_intc/sys/firmware/devicetree/base/ocp/pruss_soc_bus@4a326000/sys/firmware/devicetree/base/ocp/pruss_soc_bus@4a326000/pruss@4a30/sys/firmware/devicetree/base/ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a338000/sys/firmware/devicetree/base/ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a334000/sys/firmware/devicetree/base/ocp/pruss@4a30/sys/firmware/devicetree/base/ocp/mailbox@480C8000/mbox_pru1/sys/firmware/devicetree/base/ocp/mailbox@480C8000/mbox_pru0/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_42_pru_ecap_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_91_pruout_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_27_pruin_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_41_pruin_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_91_pruin_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P8_15_pru_ecap_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P8_11_pruout_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_92_pruout_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P8_16_pruin_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_17_pru_uart_pin/sys/firmware/devicetree/base/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_P9_21_pru_uart_pin/s

[beagleboard] Obtain ALL IO pins comlete guide.

2017-10-23 Thread Claudio La Rosa 
Ok, I'll fool.

Is there a *complete* and *clear* guide on how to get all the IO pins free ?

I installed Debian on SD, but the uEnv.txt file is not the same as that on 
eMMC.
I do not understand how to do it. Linux versions are all different.

This takes a long time and I can not devote myself to the real project.

Alternatively, is there a possibility to install Windows IoT s BeagleBone?

-- 
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/7253dec3-7b4a-4e44-8894-d036efebbb47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.