[beagleboard] Re: Welcome the Fall 2014 Beagle Class to the group

[Venkat Bommakanti]

Hi Mark,

Quite an interesting course...

Would like to know if it is available for self-paced remote-learning ?
While I have some C programming exp, I have no classic CS degree/background 
(Pre-reqs: No OS internals & H/W experience).
If not possible/eligible, pl. suggest books/courses to meet the 
prerequisites.

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] Re: trying to learn enough to get started

[William Hermans]

You're preaching to the choir John. Except that I do not feel that
JavaScript is the closest thing to a perfect anything. Again, there is no
one perfect "tool" to rule them all.

However, I do feel that because of google's V8 engine, and Nodejs, that
javascript finally is something worth using for high level Rapid
Application Development (RAD). Now, it is more like a Java, or dotNET done
right. Performance wise, it is also very fast, and performs very close to
native C.

In contrast, python and php are much slower. More so for Python which is
one of the slowest languages around. So, I will agree that it is not always
about what is faster, but n the case of an embedded device. Fast
performance means better efficiency. Which could mean the difference
between a battery lasting 2 hours, versus overnight.

*Shrug* Anyhow, I will not have anyone telling me what I can and cannot
use, so I will try to return the favor.


On Fri, Sep 5, 2014 at 3:18 PM, John Syn  wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com" 
> Date: Friday, September 5, 2014 at 2:43 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] Re: trying to learn enough to get started
>
> *Ours is all in python and php with darkhttpd as the webserver. I dispise
>> nodejs, it reminds me of the cluster that ruby gems are. *
>
> And this is why there is no easy guide. At least from a programing
> aspect.  No two people are going to agree on how it should be done, and
> what is used to get it done.
>
> Nodejs does however get a bad rap I think. The stigma of javascript comes
> with it. Which is its self often misunderstood. Nothing is perfect however
> . . .
>
> I agree with you William; however, php and darkhttpd don't scale very
> well, because it lacks asynchronous I/O capability. Also, the current
> spec’d Javascript is pretty close to the more perfect language compared to
> C, Java or Python. It also has the biggest user base of any language, by
> far and it is the only true language that works in all browsers and on the
> server. BTW, there are no bad parts, just bad programmers.
>
> Regards,
> John
>
>
>
>
>
> On Fri, Sep 5, 2014 at 1:06 PM, Don deJuan  wrote:
>
>>  On 09/05/2014 10:04 AM, William Hermans wrote:
>>
>>   *Why compile anything?  For the proposed project (Greenhouse control)*
>>> * speed is not any sort of priority so use an interpreted language, the*
>>> * obvious choice on BBB is Python.*
>>>
>>
>>  Well, the obvious choice to me is Nodejs, and am betting since this
>> person has 35 years experience in related fields, that C is a possibility
>> as well.
>>
>>  I've only been programming for 20 or so years . . . so what the hell do
>> i know ?
>>
>>
>> On Fri, Sep 5, 2014 at 1:51 AM,  wrote:
>>
>>> William Hermans  wrote:
>>> > [-- text/plain, encoding 7bit, charset: UTF-8, 51 lines --]
>>> >
>>> > You need to find and read sources about embedded Linux. Then, since
>>> your
>>> > project could be done using any number of languages, you need to figure
>>> > that out too. Past that, you're going to have to figure out what
>>> hardware
>>> > you're going to use. Which will indicate if you're using SPI. I2C,
>>> UART,
>>> > onboard ADC's or PWM's etc.
>>> >
>>> > In your shoes, I'd start off with and continue using these
>>> instructions:
>>> > https://eewiki.net/display/linuxonarm/BeagleBone+Black. You can use
>>> either
>>> > Debian or Ubuntu with these build instructions. I've been using these
>>> > instructions since last year ( around 14 or slightly more months ), and
>>> > they're very consistent.
>>> >
>>> > You could also start off with a premade Debian console image if you
>>> like.
>>> >
>>> > You can definitely compile natively on the board, but if you plan on
>>> cross
>>> > compiling, you're going to need to understand the gcc toolchain
>>> thoroughly.
>>> > For setup and use.
>>> >
>>> Why compile anything?  For the proposed project (Greenhouse control)
>>> speed is not any sort of priority so use an interpreted language, the
>>> obvious choice on BBB is Python.
>>>
>>> ... and I am also a long in the tooth software engineer with maybe 30
>>> years of experience writing C, but I'd still recommend going with
>>> Python on this sort of project.
>>>
>>> --
>>> Chris Green
>>>  ·
>>>
>>> --
>>> 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 ht

Re: [beagleboard] How do I find out what image my brand new Beaglebone Black is running?

[Robert Nelson]

On Fri, Sep 5, 2014 at 6:41 PM, jgold  wrote:
> That's the latest one I found on the images site
> (http://beagleboard.org/latest-images).  I'm not sure I want to use a test
> image.  Are they stable? Do they have a good reputation?

Other then an issue with "bone101" the "testing" release are just a
snapshot. If you need bone101 use http://beagleboard.org/latest-images

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

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

Re: [beagleboard] How do I find out what image my brand new Beaglebone Black is running?

[jgold]

That's the latest one I found on the images site 
(http://beagleboard.org/latest-images).  I'm not sure I want to use a test 
image.  Are they stable? Do they have a good reputation?

On Friday, September 5, 2014 12:17:11 AM UTC-7, William Hermans wrote:
>
> You're sure the latest image is from may ?
>
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots
>
>
> On Thu, Sep 4, 2014 at 10:48 PM, jgold  > wrote:
>
>> I just got a Beaglebone Black from Adafruit.  It came with debian 
>> pre-installed. In going though the getting started guide, one of the first 
>> things it recommends to do is update the image. That's probably a good idea 
>> but the lastest image is from May so I probably already have it.  I'd like 
>> to check before going to all the work of flashing a new image but I can't 
>> seem to determine the version I'm currently running.  It seems like 
>> something everyone would want to know before they do an update.  Anyone 
>> know how to find it?
>>
>> 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...@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] How do I find out what image my brand new Beaglebone Black is running?

[jgold]

Hi William,

I had tried uname but it just gave me the linux kernel number and I 
couldn't find anything that would tie that to a beaglebone image. Thanks 
though.


On Friday, September 5, 2014 1:52:13 AM UTC-7, William Pretty Security 
wrote:
>
> “ uname –a “   ;-)
>
>  
>
> "No one could make a greater mistake than he who did nothing because he 
> could do only a little."
>
> "All that is necessary for the triumph of evil is that good men do 
> nothing" Edmond Burke *(1729 - 1797)*
>
>
> http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book
>
>  
>
> *From:* beagl...@googlegroups.com  [mailto:
> beagl...@googlegroups.com ] *On Behalf Of *jgold
> *Sent:* Friday, September 05, 2014 1:49 AM
> *To:* beagl...@googlegroups.com 
> *Subject:* [beagleboard] How do I find out what image my brand new 
> Beaglebone Black is running?
>
>  
>
> I just got a Beaglebone Black from Adafruit.  It came with debian 
> pre-installed. In going though the getting started guide, one of the first 
> things it recommends to do is update the image. That's probably a good idea 
> but the lastest image is from May so I probably already have it.  I'd like 
> to check before going to all the work of flashing a new image but I can't 
> seem to determine the version I'm currently running.  It seems like 
> something everyone would want to know before they do an update.  Anyone 
> know how to find it?
>
> 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...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4765 / Virus Database: 4015/8155 - Release Date: 09/04/14
>

-- 
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: How do I find out what image my brand new Beaglebone Black is running?

[jgold]

That's what I was missing.  Thanks! My image is dated from April so I guess 
I need to update it.

On Friday, September 5, 2014 7:44:22 AM UTC-7, Mark A. Yoder wrote:
>
> jgold:
>  Try: *cat /etc/dogtag *
>
> I think the May image is the latest released image, that is the image that 
> ships on the Bone.  There was a new test image pushed yesterday 
> (4-Sep-2014).
>
> --Mark
>
>
> On Friday, September 5, 2014 1:48:36 AM UTC-4, jgold wrote:
>>
>> I just got a Beaglebone Black from Adafruit.  It came with debian 
>> pre-installed. In going though the getting started guide, one of the first 
>> things it recommends to do is update the image. That's probably a good idea 
>> but the lastest image is from May so I probably already have it.  I'd like 
>> to check before going to all the work of flashing a new image but I can't 
>> seem to determine the version I'm currently running.  It seems like 
>> something everyone would want to know before they do an update.  Anyone 
>> know how to find it?
>>
>> 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] Re: trying to learn enough to get started

[John Syn]

From:  William Hermans 
Reply-To:  "beagleboard@googlegroups.com" 
Date:  Friday, September 5, 2014 at 2:43 PM
To:  "beagleboard@googlegroups.com" 
Subject:  Re: [beagleboard] Re: trying to learn enough to get started

>> Ours is all in python and php with darkhttpd as the webserver. I dispise
>> nodejs, it reminds me of the cluster that ruby gems are.
> And this is why there is no easy guide. At least from a programing aspect.  No
> two people are going to agree on how it should be done, and what is used to
> get it done.
> 
> Nodejs does however get a bad rap I think. The stigma of javascript comes with
> it. Which is its self often misunderstood. Nothing is perfect however . . .
I agree with you William; however, php and darkhttpd don't scale very well,
because it lacks asynchronous I/O capability. Also, the current spec¹d
Javascript is pretty close to the more perfect language compared to C, Java
or Python. It also has the biggest user base of any language, by far and it
is the only true language that works in all browsers and on the server. BTW,
there are no bad parts, just bad programmers.

Regards,
John
> 
> 
> 
> 
> On Fri, Sep 5, 2014 at 1:06 PM, Don deJuan  wrote:
>> 
>>  
>> On 09/05/2014 10:04 AM, William Hermans wrote:
>>  
>>  
>>>   
>>>  
>>>  
>>>  
 Why compile anything?  For the proposed project (Greenhouse control)
   speed is not any sort of priority so use an interpreted language, the
   obvious choice on BBB is Python.
  
>>>  
>>>  
>>>  Well, the obvious choice to me is Nodejs, and am betting since this person
>>> has 35 years experience in related fields, that C is a possibility as well.
>>>  
>>>  
>>>  I've only been programming for 20 or so years . . . so what the hell do i
>>> know ?
>>>  
>>>  
>>> 
>>>  
>>>  
>>> On Fri, Sep 5, 2014 at 1:51 AM,  wrote:
>>>  
 William Hermans  wrote:
>  > [-- text/plain, encoding 7bit, charset: UTF-8, 51 lines --]
>  >
>  > You need to find and read sources about embedded Linux. Then, since
> your
>  > project could be done using any number of languages, you need to figure
>  > that out too. Past that, you're going to have to figure out what
> hardware
>  > you're going to use. Which will indicate if you're using SPI. I2C,
> UART,
>  > onboard ADC's or PWM's etc.
>  >
>  > In your shoes, I'd start off with and continue using these
> instructions:
>  > https://eewiki.net/display/linuxonarm/BeagleBone+Black. You can use
> either
>  > Debian or Ubuntu with these build instructions. I've been using these
>  > instructions since last year ( around 14 or slightly more months ), and
>  > they're very consistent.
>  >
>  > You could also start off with a premade Debian console image if you
> like.
>  >
>  > You can definitely compile natively on the board, but if you plan on
> cross
>  > compiling, you're going to need to understand the gcc toolchain
> thoroughly.
>  > For setup and use.
>  >
  Why compile anything?  For the proposed project (Greenhouse control)
  speed is not any sort of priority so use an interpreted language, the
  obvious choice on BBB is Python.
  
  ... and I am also a long in the tooth software engineer with maybe 30
  years of experience writing C, but I'd still recommend going with
  Python on this sort of project.
  
  --
  Chris Green
   
  
 ·
  
  --
  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.
>>>  
>>  
>>  I actually have done a similar control for aeroponics room setups. We are
>> releasing it public in roughly a month once the boards come back and we
>> finish testing on the new hardware run.
>>  
>>  Very easily can be adapted to greenhouse control as I am sure you're after
>> the same things, water, temp, humidity, vpd, ph, ppm, disolved oxygen, dew
>> point, flood detection, co2, lumens/lux, uvb, darkness light leak detection
>> and all the rest of the goodness for optimal environmental control. Even the
>> cooling opener could be adjusted/adapted to fit to automate opening roof
>> panels. 
>>  
>>  Ours is all in python 

Re: [beagleboard] Re: trying to learn enough to get started

[William Hermans]

>
> *Ours is all in python and php with darkhttpd as the webserver. I dispise
> nodejs, it reminds me of the cluster that ruby gems are. *

And this is why there is no easy guide. At least from a programing aspect.
No two people are going to agree on how it should be done, and what is used
to get it done.

Nodejs does however get a bad rap I think. The stigma of javascript comes
with it. Which is its self often misunderstood. Nothing is perfect however
. . .



On Fri, Sep 5, 2014 at 1:06 PM, Don deJuan  wrote:

>  On 09/05/2014 10:04 AM, William Hermans wrote:
>
>   *Why compile anything?  For the proposed project (Greenhouse control)*
>> * speed is not any sort of priority so use an interpreted language, the*
>> * obvious choice on BBB is Python.*
>>
>
>  Well, the obvious choice to me is Nodejs, and am betting since this
> person has 35 years experience in related fields, that C is a possibility
> as well.
>
>  I've only been programming for 20 or so years . . . so what the hell do i
> know ?
>
>
> On Fri, Sep 5, 2014 at 1:51 AM,  wrote:
>
>> William Hermans  wrote:
>> > [-- text/plain, encoding 7bit, charset: UTF-8, 51 lines --]
>> >
>> > You need to find and read sources about embedded Linux. Then, since your
>> > project could be done using any number of languages, you need to figure
>> > that out too. Past that, you're going to have to figure out what
>> hardware
>> > you're going to use. Which will indicate if you're using SPI. I2C, UART,
>> > onboard ADC's or PWM's etc.
>> >
>> > In your shoes, I'd start off with and continue using these instructions:
>> > https://eewiki.net/display/linuxonarm/BeagleBone+Black. You can use
>> either
>> > Debian or Ubuntu with these build instructions. I've been using these
>> > instructions since last year ( around 14 or slightly more months ), and
>> > they're very consistent.
>> >
>> > You could also start off with a premade Debian console image if you
>> like.
>> >
>> > You can definitely compile natively on the board, but if you plan on
>> cross
>> > compiling, you're going to need to understand the gcc toolchain
>> thoroughly.
>> > For setup and use.
>> >
>> Why compile anything?  For the proposed project (Greenhouse control)
>> speed is not any sort of priority so use an interpreted language, the
>> obvious choice on BBB is Python.
>>
>> ... and I am also a long in the tooth software engineer with maybe 30
>> years of experience writing C, but I'd still recommend going with
>> Python on this sort of project.
>>
>> --
>> Chris Green
>>  ·
>>
>> --
>> 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.
>
>
> I actually have done a similar control for aeroponics room setups. We are
> releasing it public in roughly a month once the boards come back and we
> finish testing on the new hardware run.
>
> Very easily can be adapted to greenhouse control as I am sure you're after
> the same things, water, temp, humidity, vpd, ph, ppm, disolved oxygen, dew
> point, flood detection, co2, lumens/lux, uvb, darkness light leak detection
> and all the rest of the goodness for optimal environmental control. Even
> the cooling opener could be adjusted/adapted to fit to automate opening
> roof panels.
>
> Ours is all in python and php with darkhttpd as the webserver. I dispise
> nodejs, it reminds me of the cluster that ruby gems are.
>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] Re: custom cape i2c bus

[kyle]

So it appears you should expect to see a device between 0x20 through 0x27 
from the datasheets.   The device address is 0*010* when not shifted 
for the R/W bit.   That corresponds to 0x20 as the base chip address and 
the A1,A2, and A3 pins can set up to 7 other address for the final three 
bits.   I2C can be really confusing in how the addresses are specified in 
various datasheets.  Linux reports the 7 bit address of devices it finds in 
hexadecimal.


I see your output shows devices at 0x20, 0x22, 0x26, and 0x28.   That 
appears to be the correct* hecxidecimal*, *7-bit,* addresses for the chips? 
 Do you have 4 chips wired up?

-- 
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: trying to learn enough to get started

[Don deJuan]

On 09/05/2014 10:04 AM, William Hermans wrote:
>
> /Why compile anything?  For the proposed project (Greenhouse control)/
> /speed is not any sort of priority so use an interpreted language,
> the/
> /obvious choice on BBB is Python./
>
>
> Well, the obvious choice to me is Nodejs, and am betting since this
> person has 35 years experience in related fields, that C is a
> possibility as well.
>
> I've only been programming for 20 or so years . . . so what the hell
> do i know ?
>
>
> On Fri, Sep 5, 2014 at 1:51 AM, mailto:c...@isbd.net>> wrote:
>
> William Hermans mailto:yyrk...@gmail.com>> wrote:
> > [-- text/plain, encoding 7bit, charset: UTF-8, 51 lines --]
> >
> > You need to find and read sources about embedded Linux. Then,
> since your
> > project could be done using any number of languages, you need to
> figure
> > that out too. Past that, you're going to have to figure out what
> hardware
> > you're going to use. Which will indicate if you're using SPI.
> I2C, UART,
> > onboard ADC's or PWM's etc.
> >
> > In your shoes, I'd start off with and continue using these
> instructions:
> > https://eewiki.net/display/linuxonarm/BeagleBone+Black. You can
> use either
> > Debian or Ubuntu with these build instructions. I've been using
> these
> > instructions since last year ( around 14 or slightly more months
> ), and
> > they're very consistent.
> >
> > You could also start off with a premade Debian console image if
> you like.
> >
> > You can definitely compile natively on the board, but if you
> plan on cross
> > compiling, you're going to need to understand the gcc toolchain
> thoroughly.
> > For setup and use.
> >
> Why compile anything?  For the proposed project (Greenhouse control)
> speed is not any sort of priority so use an interpreted language, the
> obvious choice on BBB is Python.
>
> ... and I am also a long in the tooth software engineer with maybe 30
> years of experience writing C, but I'd still recommend going with
> Python on this sort of project.
>
> --
> Chris Green
> ·
>
> --
> 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.

I actually have done a similar control for aeroponics room setups. We
are releasing it public in roughly a month once the boards come back and
we finish testing on the new hardware run.

Very easily can be adapted to greenhouse control as I am sure you're
after the same things, water, temp, humidity, vpd, ph, ppm, disolved
oxygen, dew point, flood detection, co2, lumens/lux, uvb, darkness light
leak detection and all the rest of the goodness for optimal
environmental control. Even the cooling opener could be adjusted/adapted
to fit to automate opening roof panels.

Ours is all in python and php with darkhttpd as the webserver. I dispise
nodejs, it reminds me of the cluster that ruby gems are.


-- 
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: Why did my BB die ?

[kyle]

This was a big reason why I chose to use an I2C external ADC for measuring 
raw battery voltage in a project of mine.   Gating that voltage from 
hitting the pins prior to PMIC startup was way more complicated than 
hooking up a 4 channel ADC on the I2C bus and using that powered by the 
3.3V rail.  It's easy to overlook that need to keep inputs isolated until 
power is fully on for the BBB.

-- 
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: trying to learn enough to get started

[max]

Chuck,

You might like to take a look at node-RED (http://nodered.org) which is a 
browser based visual tool for 'wiring the Internet of Things' and I reckon 
a greenhouse counts as a Thing. It is written in Javascript, running in 
node.js, and runs fine on small embedded Linux machines like the Raspberry 
Pi and the BeagleBone Black. There are explicit 'how to set up' 
instructions for both these boards on the web site. You can start by 
'wiring up' analogue & digital input pins to function blocks which make 
calculations and decisions, back to output pins, or to other things like 
Internet services. For example, you could make it send an alert to your 
phone (or an email, or a tweet) when the temperature goes over a limit.

You can write Javascript inside 'function blocks' for simple tasks, or if 
your task warrants it, extend the environment by writing your own 'node' - 
also in Javascript. It's all open source so you can look under the hood & 
see how it works. There is an active, helpful developer community emerging 
around it.

Whatever you decide to do, enjoy doing it!

Max

On Thursday, 4 September 2014 03:24:01 UTC+1, ccrisle...@gmail.com wrote:
>
> I have a significant project that I want to accomplish this fall/winter. I 
> would like to build a digital controller for my greenhouse. I have been a 
> software engineer for 35 years so the programming will be easy. I don't 
> have any experience with microprocessors and need to learn so that I can 
> do. What introductory and intermediate sources of information would people 
> recommend? I am thinking about a BBB running Ubuntu but am open to 
> suggestions.
>
> Thank you,
> Chuck Crisler
>

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

Re: [beagleboard] debian testing: 2014-09-03 (goodbye vfat release)

[John Syn]

From:  William Hermans 
Reply-To:  "beagleboard@googlegroups.com" 
Date:  Friday, September 5, 2014 at 12:19 PM
To:  "beagleboard@googlegroups.com" 
Subject:  Re: [beagleboard] debian testing: 2014-09-03 (goodbye vfat
release)

>> So, we are offering more protection, as windows user's can't randomly delete
>> it.
> 
> That should read "clueless users", since I'm a windows user myself and have
> never had that problem :P
All windows users are clueless ;-)
> 
> 
> 
> On Fri, Sep 5, 2014 at 12:16 PM, Robert Nelson 
> wrote:
>> On Fri, Sep 5, 2014 at 7:14 AM, Vesa Jääskeläinen  wrote:
>>> >
>>> > On 04/09/14 21:24, Robert Nelson wrote:
 >>
 >> Howdy!
 >>
 >> I just pushed out another round of images for testing.
 >>
 >> There's really only "one" big change with this image, the sorta change
 >> that will re-write every wiki document.
 >>
 >> NO VFAT PARTITION REQUIRED!!!
 >>
 >> Let me repeat that... THE VFAT "boot" PARTITION IS NOT REQUIRED! ;)
 >>
 >> So far i've only got it to reliabley work on omap4+ bootroms (which
 >> include the am335x).. so beagle/beagle-xm, not yet...
 >>
>>> > MBR/GPT's MBR emu is at the first sectors of the card. So are you using
>>> > relocateable MBR/GPT? Or how are you handling that issue?
>> 
>> Traditionally it's been a msdos partition setup... Either way, the
>> first file MLO gets stored at 128k
>> 
>>> > Would it be wise to also support backup boot loader in case first one gets
>>> > corrupt? -- if I recon correctly the bootrom should also support that.
>> 
>> We never had a backup boot loader previously.. It was just stored in
>> the "fat" partition as a file and was also shared over usb as a
>> "gadget usb flash drive".
>> 
>> So, we are offering more protection, as windows user's can't randomly delete
>> it.
>> 
>> Regards,
>> 
>> --
>> Robert Nelson
>> http://www.rcn-ee.com/
>> 
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com
>>  .
>> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


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

Re: [beagleboard] debian testing: 2014-09-03 (goodbye vfat release)

[William Hermans]

>
> *So, we are offering more protection, as windows user's can't randomly
> delete it.*
>

That should read "clueless users", since I'm a windows user myself and have
never had that problem :P


On Fri, Sep 5, 2014 at 12:16 PM, Robert Nelson 
wrote:

> On Fri, Sep 5, 2014 at 7:14 AM, Vesa Jääskeläinen 
> wrote:
> >
> > On 04/09/14 21:24, Robert Nelson wrote:
> >>
> >> Howdy!
> >>
> >> I just pushed out another round of images for testing.
> >>
> >> There's really only "one" big change with this image, the sorta change
> >> that will re-write every wiki document.
> >>
> >> NO VFAT PARTITION REQUIRED!!!
> >>
> >> Let me repeat that... THE VFAT "boot" PARTITION IS NOT REQUIRED! ;)
> >>
> >> So far i've only got it to reliabley work on omap4+ bootroms (which
> >> include the am335x).. so beagle/beagle-xm, not yet...
> >>
> > MBR/GPT's MBR emu is at the first sectors of the card. So are you using
> > relocateable MBR/GPT? Or how are you handling that issue?
>
> Traditionally it's been a msdos partition setup... Either way, the
> first file MLO gets stored at 128k
>
> > Would it be wise to also support backup boot loader in case first one
> gets
> > corrupt? -- if I recon correctly the bootrom should also support that.
>
> We never had a backup boot loader previously.. It was just stored in
> the "fat" partition as a file and was also shared over usb as a
> "gadget usb flash drive".
>
> So, we are offering more protection, as windows user's can't randomly
> delete it.
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] debian testing: 2014-09-03 (goodbye vfat release)

[Robert Nelson]

On Fri, Sep 5, 2014 at 7:14 AM, Vesa Jääskeläinen  wrote:
>
> On 04/09/14 21:24, Robert Nelson wrote:
>>
>> Howdy!
>>
>> I just pushed out another round of images for testing.
>>
>> There's really only "one" big change with this image, the sorta change
>> that will re-write every wiki document.
>>
>> NO VFAT PARTITION REQUIRED!!!
>>
>> Let me repeat that... THE VFAT "boot" PARTITION IS NOT REQUIRED! ;)
>>
>> So far i've only got it to reliabley work on omap4+ bootroms (which
>> include the am335x).. so beagle/beagle-xm, not yet...
>>
> MBR/GPT's MBR emu is at the first sectors of the card. So are you using
> relocateable MBR/GPT? Or how are you handling that issue?

Traditionally it's been a msdos partition setup... Either way, the
first file MLO gets stored at 128k

> Would it be wise to also support backup boot loader in case first one gets
> corrupt? -- if I recon correctly the bootrom should also support that.

We never had a backup boot loader previously.. It was just stored in
the "fat" partition as a file and was also shared over usb as a
"gadget usb flash drive".

So, we are offering more protection, as windows user's can't randomly delete it.

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

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

Re: [beagleboard] Re: Cross compiling using Eclipse and Ubuntu 64bit 12.04

[William Hermans]

Ok, now run this:

ldd /bin/ls

This should tell you which ABI is physically running on your board. It
should be either *arm-linux-gnueab* or
*arm-linux-gnueabhf *
If the output of ldd /bin/ls is arm-linux-gnueab then you're golden.
However I suspect the output will be arm-linux-gnueabhf.  IN which case
you're using the wrong toolchain.

If the output is confusing to you, just paste the output in a message to
us, and we can let you know.


On Thu, Sep 4, 2014 at 7:12 PM,  wrote:

> Is this the compiler info you need. i'm a Linux novice so it may not be
> what you want.
> compiler   -I/usr/arm-linux-gnueabi/include/c++/4.6.3 -O0 -g3 -Wall -c
> -fmessage-length=0
>
> Linux kernal - Linux ubuntu 3.2.0-67-generic #101-Ubuntu SMP Tue Jul 15
> 17:46:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>
> I downloaded the 12.04 version of Ubuntu from Ubuntu's website.
>
>
>  --
> 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] USB Camera on BBB (Debian GNU/Linux 7)

[William Hermans]

Robert, thanks. However since we're talking 3.8.13* hotplug still is an
issue ?

amerello, have you tried loading these modules manually with modprobe ? Or
have you manually edited /etc/modules to include these there ?


On Fri, Sep 5, 2014 at 11:45 AM, Robert Nelson 
wrote:

> On Thu, Sep 4, 2014 at 5:03 PM,   wrote:
> > Hello,
> >   Could someone give me a hand? I'm having trouble getting a USB Camera
> to
> > work on my BeagleBone Black.
> >  I'm using a 5V@1A adapter (I thought it could be a power issue), but it
> > didn't solve it. I can provide the following information of my system:
> >
> > $ uname -a
> > Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l
> > GNU/Linux
> >
> > $ lsusb
> > Bus 001 Device 002: ID 1871:0101 Aveo Technology Corp.
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> >
> > $ lsmod
> > Module  Size  Used by
> > uvcvideo   53354  0
> > videobuf2_vmalloc   2418  1 uvcvideo
> > g_multi47670  2
> > libcomposite   14299  1 g_multi
> >
> > $dmesg | less
> > ...
> > [ 1196.227457] usb usb1: usb wakeup-resume
> > [ 1196.227556] usb usb1: usb auto-resume
> > [ 1196.227607] hub 1-0:1.0: hub_resume
> > [ 1196.227706] hub 1-0:1.0: port 1: status 0101 change 0001
> > [ 1196.329800] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 
> > [ 1196.329910] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s
> > [ 1196.435171] usb 1-1: new high-speed USB device number 3 using
> musb-hdrc
> > [ 1196.562835] usb 1-1: skipped 1 descriptor after configuration
> > [ 1196.562886] usb 1-1: skipped 5 descriptors after interface
> > [ 1196.562929] usb 1-1: skipped 1 descriptor after endpoint
> > [ 1196.562967] usb 1-1: skipped 9 descriptors after interface
> > [ 1196.563301] usb 1-1: default language 0x0409
> > [ 1196.564922] usb 1-1: udev 3, busnum 1, minor = 2
> > [ 1196.564969] usb 1-1: New USB device found, idVendor=1871,
> idProduct=0101
> > [ 1196.565009] usb 1-1: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=0
> > [ 1196.565044] usb 1-1: Product: USB2.0 Camera
> > [ 1196.565079] usb 1-1: Manufacturer: AVEO Technology Corp.
> > [ 1196.566432] usb 1-1: usb_probe_device
> > [ 1196.566483] usb 1-1: configuration #1 chosen from 1 choice
> > [ 1196.566782] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
> > [ 1196.568276] uvcvideo 1-1:1.0: usb_probe_interface
> > [ 1196.568333] uvcvideo 1-1:1.0: usb_probe_interface - got id
> > [ 1196.568476] uvcvideo: Found UVC 1.00 device USB2.0 Camera (1871:0101)
> > [ 1196.574639] input: USB2.0 Camera as
> >
> /devices/ocp.3/4740.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input2
> > [ 1196.575902] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
> > [ 1196.578270] hub 1-0:1.0: state 7 ports 1 chg  evt 0002
> > [ 1196.578369] hub 1-0:1.0: port 1 enable change, status 0503
> > [ 1199.015323] usb 1-1: usb auto-suspend, wakeup 0
> > [ 1199.029051] hub 1-0:1.0: hub_suspend
> > [ 1199.029145] usb usb1: bus auto-suspend, wakeup 1
> >
> > $ ls -al /dev/video0
> > crw-rw---T+ 1 root video 81, 0 Sep  4 23:45 /dev/video0
> >
> > But when I try to capture some image it fails. I tried with streamer,
> > mjpg-streamer and ffmpeg but always get timeout. My impression is that
> not
> > all the modules are being loaded. For instance when I plug the camera on
> my
> > laptop I get the following modules on lsmod:
> >
> > $ lsmod
> > ...
> > uvcvideo   80885  0
> > videobuf2_vmalloc  13216  1 uvcvideo
> > videobuf2_memops   13362  1 videobuf2_vmalloc
> > videobuf2_core 40664  1 uvcvideo
> > videodev  134688  2 uvcvideo,videobuf2_core
> > ...
> >
> > The 3 last aren't being loaded on the BBB. Do you have any suggestions?
> What
> > could it be?
>
> They are built-in:
>
>
> https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.8/patches/defconfig#L2574
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] USB Camera on BBB (Debian GNU/Linux 7)

[Robert Nelson]

On Thu, Sep 4, 2014 at 5:03 PM,   wrote:
> Hello,
>   Could someone give me a hand? I'm having trouble getting a USB Camera to
> work on my BeagleBone Black.
>  I'm using a 5V@1A adapter (I thought it could be a power issue), but it
> didn't solve it. I can provide the following information of my system:
>
> $ uname -a
> Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l
> GNU/Linux
>
> $ lsusb
> Bus 001 Device 002: ID 1871:0101 Aveo Technology Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> $ lsmod
> Module  Size  Used by
> uvcvideo   53354  0
> videobuf2_vmalloc   2418  1 uvcvideo
> g_multi47670  2
> libcomposite   14299  1 g_multi
>
> $dmesg | less
> ...
> [ 1196.227457] usb usb1: usb wakeup-resume
> [ 1196.227556] usb usb1: usb auto-resume
> [ 1196.227607] hub 1-0:1.0: hub_resume
> [ 1196.227706] hub 1-0:1.0: port 1: status 0101 change 0001
> [ 1196.329800] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 
> [ 1196.329910] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s
> [ 1196.435171] usb 1-1: new high-speed USB device number 3 using musb-hdrc
> [ 1196.562835] usb 1-1: skipped 1 descriptor after configuration
> [ 1196.562886] usb 1-1: skipped 5 descriptors after interface
> [ 1196.562929] usb 1-1: skipped 1 descriptor after endpoint
> [ 1196.562967] usb 1-1: skipped 9 descriptors after interface
> [ 1196.563301] usb 1-1: default language 0x0409
> [ 1196.564922] usb 1-1: udev 3, busnum 1, minor = 2
> [ 1196.564969] usb 1-1: New USB device found, idVendor=1871, idProduct=0101
> [ 1196.565009] usb 1-1: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [ 1196.565044] usb 1-1: Product: USB2.0 Camera
> [ 1196.565079] usb 1-1: Manufacturer: AVEO Technology Corp.
> [ 1196.566432] usb 1-1: usb_probe_device
> [ 1196.566483] usb 1-1: configuration #1 chosen from 1 choice
> [ 1196.566782] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
> [ 1196.568276] uvcvideo 1-1:1.0: usb_probe_interface
> [ 1196.568333] uvcvideo 1-1:1.0: usb_probe_interface - got id
> [ 1196.568476] uvcvideo: Found UVC 1.00 device USB2.0 Camera (1871:0101)
> [ 1196.574639] input: USB2.0 Camera as
> /devices/ocp.3/4740.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input2
> [ 1196.575902] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
> [ 1196.578270] hub 1-0:1.0: state 7 ports 1 chg  evt 0002
> [ 1196.578369] hub 1-0:1.0: port 1 enable change, status 0503
> [ 1199.015323] usb 1-1: usb auto-suspend, wakeup 0
> [ 1199.029051] hub 1-0:1.0: hub_suspend
> [ 1199.029145] usb usb1: bus auto-suspend, wakeup 1
>
> $ ls -al /dev/video0
> crw-rw---T+ 1 root video 81, 0 Sep  4 23:45 /dev/video0
>
> But when I try to capture some image it fails. I tried with streamer,
> mjpg-streamer and ffmpeg but always get timeout. My impression is that not
> all the modules are being loaded. For instance when I plug the camera on my
> laptop I get the following modules on lsmod:
>
> $ lsmod
> ...
> uvcvideo   80885  0
> videobuf2_vmalloc  13216  1 uvcvideo
> videobuf2_memops   13362  1 videobuf2_vmalloc
> videobuf2_core 40664  1 uvcvideo
> videodev  134688  2 uvcvideo,videobuf2_core
> ...
>
> The 3 last aren't being loaded on the BBB. Do you have any suggestions? What
> could it be?

They are built-in:

https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.8/patches/defconfig#L2574

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

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

Re: [beagleboard] Re: USB Camera on BBB (Debian GNU/Linux 7)

[William Hermans]

>
> *$ lsmod*
> *...*
> *uvcvideo   80885  0 *
> *videobuf2_vmalloc  13216  1 uvcvideo*
> *videobuf2_memops   13362  1 videobuf2_vmalloc*
> *videobuf2_core 40664  1 uvcvideo*
> *videodev  134688  2 uvcvideo,videobuf2_core*
> *...*
>
> *The 3 last aren't being loaded on the BBB. Do you have any suggestions?
> What could it be?*
> *Thanks a lot for any hints!*

Did you make sure those modules actually exist on the BBB ?



On Fri, Sep 5, 2014 at 11:07 AM, gern  wrote:

> hello
>
> I am no expert but I have found qv4l2 a very good tool to help debug
> webcams.  Often I find the default resolutions are to high for these small
> boards
>
> sudo apt-get install qv4l2
>
> On Friday, 5 September 2014 00:03:41 UTC+2, Alejandro Merello wrote:
>>
>> Hello,
>>   Could someone give me a hand? I'm having trouble getting a USB Camera
>> to work on my BeagleBone Black.
>>  I'm using a 5V@1A adapter (I thought it could be a power issue), but it
>> didn't solve it. I can provide the following information of my system:
>>
>> $ uname -a
>> Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l
>> GNU/Linux
>>
>> $ lsusb
>> *Bus 001 Device 002: ID 1871:0101 Aveo Technology Corp. *
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>
>> $ lsmod
>> Module  Size  Used by
>>
>> *uvcvideo   53354  0 videobuf2_vmalloc   2418  1 uvcvideo*
>> g_multi47670  2
>> libcomposite   14299  1 g_multi
>>
>> $dmesg | less
>> ...
>> [ 1196.227457] usb usb1: usb wakeup-resume
>> [ 1196.227556] usb usb1: usb auto-resume
>> [ 1196.227607] hub 1-0:1.0: hub_resume
>> [ 1196.227706] hub 1-0:1.0: port 1: status 0101 change 0001
>> [ 1196.329800] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 
>> [ 1196.329910] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s
>> [ 1196.435171] usb 1-1: new high-speed USB device number 3 using musb-hdrc
>> [ 1196.562835] usb 1-1: skipped 1 descriptor after configuration
>> [ 1196.562886] usb 1-1: skipped 5 descriptors after interface
>> [ 1196.562929] usb 1-1: skipped 1 descriptor after endpoint
>> [ 1196.562967] usb 1-1: skipped 9 descriptors after interface
>> [ 1196.563301] usb 1-1: default language 0x0409
>> [ 1196.564922] usb 1-1: udev 3, busnum 1, minor = 2
>> [ 1196.564969] usb 1-1: New USB device found, idVendor=1871,
>> idProduct=0101
>> [ 1196.565009] usb 1-1: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [ 1196.565044] usb 1-1: Product: USB2.0 Camera
>> [ 1196.565079] usb 1-1: Manufacturer: AVEO Technology Corp.
>> [ 1196.566432] usb 1-1: usb_probe_device
>> [ 1196.566483] usb 1-1: configuration #1 chosen from 1 choice
>> [ 1196.566782] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
>>
>>
>>
>> *[ 1196.568276] uvcvideo 1-1:1.0: usb_probe_interface[ 1196.568333]
>> uvcvideo 1-1:1.0: usb_probe_interface - got id[ 1196.568476] uvcvideo:
>> Found UVC 1.00 device USB2.0 Camera (1871:0101)[ 1196.574639] input: USB2.0
>> Camera as
>> /devices/ocp.3/4740.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input2*
>> [ 1196.575902] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
>> [ 1196.578270] hub 1-0:1.0: state 7 ports 1 chg  evt 0002
>> [ 1196.578369] hub 1-0:1.0: port 1 enable change, status 0503
>> [ 1199.015323] usb 1-1: usb auto-suspend, wakeup 0
>> [ 1199.029051] hub 1-0:1.0: hub_suspend
>> [ 1199.029145] usb usb1: bus auto-suspend, wakeup 1
>>
>> $ ls -al /dev/video0
>> crw-rw---T+ 1 root video 81, 0 Sep  4 23:45 /dev/video0
>>
>> But when I try to capture some image it fails. I tried with streamer,
>> mjpg-streamer and ffmpeg but always get timeout. My impression is that not
>> all the modules are being loaded. For instance when I plug the camera on my
>> laptop I get the following modules on lsmod:
>>
>> $ lsmod
>> ...
>> uvcvideo   80885  0
>> videobuf2_vmalloc  13216  1 uvcvideo
>>
>>
>> *videobuf2_memops   13362  1 videobuf2_vmallocvideobuf2_core
>> 40664  1 uvcvideovideodev  134688  2 uvcvideo,videobuf2_core*
>> ...
>>
>> The 3 last aren't being loaded on the BBB. Do you have any suggestions?
>> What could it be?
>> Thanks a lot for any hints!
>>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

RE: [beagleboard] Re: Is it possible to root Beaglebone Black Android image

[William Pretty Security]

Where did you get the image ???

 

"No one could make a greater mistake than he who did nothing because he could 
do only a little."

"All that is necessary for the triumph of evil is that good men do nothing" 
Edmond Burke (1729 - 1797)

http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book

 

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of iom...@gmail.com
Sent: Friday, September 05, 2014 11:15 AM
To: beagleboard@googlegroups.com
Subject: [beagleboard] Re: Is it possible to root Beaglebone Black Android image

 

I'm just seeing this post. I'm amazed that no one has replied yet. I am 
desperately looking for this solution. Every android tool I have for rooting 
does not work on BBB. This is the 1st time I could not root an android 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.
For more options, visit https://groups.google.com/d/optout.



No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4015/8159 - Release Date: 09/05/14

-- 
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] Read USB through GPIO

[William Pretty Security]

Nope L

 

There are some serial io’s and I2C busses available …..

 

"No one could make a greater mistake than he who did nothing because he could 
do only a little."

"All that is necessary for the triumph of evil is that good men do nothing" 
Edmond Burke (1729 - 1797)

http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book

 

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of samthomasdigi...@gmail.com
Sent: Thursday, September 04, 2014 6:04 PM
To: beagleboard@googlegroups.com
Subject: [beagleboard] Read USB through GPIO

 

Hi There!

 

I have a feeling the answer to this question will be no. But, does anybody know 
if it is possible to mount a USB device through the GPIO pins? I need to 
connect two powered devices to the BBB and would rather not use a USB hub 
because of the added weight.

 

Thanks!

 

Sam

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



No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4015/8159 - Release Date: 09/05/14

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

[beagleboard] Re: USB Camera on BBB (Debian GNU/Linux 7)

[gern]

hello

I am no expert but I have found qv4l2 a very good tool to help debug 
webcams.  Often I find the default resolutions are to high for these small 
boards

sudo apt-get install qv4l2 

On Friday, 5 September 2014 00:03:41 UTC+2, Alejandro Merello wrote:
>
> Hello,
>   Could someone give me a hand? I'm having trouble getting a USB Camera to 
> work on my BeagleBone Black.
>  I'm using a 5V@1A adapter (I thought it could be a power issue), but it 
> didn't solve it. I can provide the following information of my system:
>
> $ uname -a
> Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l 
> GNU/Linux
>
> $ lsusb
> *Bus 001 Device 002: ID 1871:0101 Aveo Technology Corp. *
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> $ lsmod
> Module  Size  Used by
>
> *uvcvideo   53354  0 videobuf2_vmalloc   2418  1 uvcvideo*
> g_multi47670  2 
> libcomposite   14299  1 g_multi
>
> $dmesg | less
> ...
> [ 1196.227457] usb usb1: usb wakeup-resume
> [ 1196.227556] usb usb1: usb auto-resume
> [ 1196.227607] hub 1-0:1.0: hub_resume
> [ 1196.227706] hub 1-0:1.0: port 1: status 0101 change 0001
> [ 1196.329800] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 
> [ 1196.329910] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s
> [ 1196.435171] usb 1-1: new high-speed USB device number 3 using musb-hdrc
> [ 1196.562835] usb 1-1: skipped 1 descriptor after configuration
> [ 1196.562886] usb 1-1: skipped 5 descriptors after interface
> [ 1196.562929] usb 1-1: skipped 1 descriptor after endpoint
> [ 1196.562967] usb 1-1: skipped 9 descriptors after interface
> [ 1196.563301] usb 1-1: default language 0x0409
> [ 1196.564922] usb 1-1: udev 3, busnum 1, minor = 2
> [ 1196.564969] usb 1-1: New USB device found, idVendor=1871, idProduct=0101
> [ 1196.565009] usb 1-1: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=0
> [ 1196.565044] usb 1-1: Product: USB2.0 Camera
> [ 1196.565079] usb 1-1: Manufacturer: AVEO Technology Corp.
> [ 1196.566432] usb 1-1: usb_probe_device
> [ 1196.566483] usb 1-1: configuration #1 chosen from 1 choice
> [ 1196.566782] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
>
>
>
> *[ 1196.568276] uvcvideo 1-1:1.0: usb_probe_interface[ 1196.568333] 
> uvcvideo 1-1:1.0: usb_probe_interface - got id[ 1196.568476] uvcvideo: 
> Found UVC 1.00 device USB2.0 Camera (1871:0101)[ 1196.574639] input: USB2.0 
> Camera as 
> /devices/ocp.3/4740.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input2*
> [ 1196.575902] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
> [ 1196.578270] hub 1-0:1.0: state 7 ports 1 chg  evt 0002
> [ 1196.578369] hub 1-0:1.0: port 1 enable change, status 0503
> [ 1199.015323] usb 1-1: usb auto-suspend, wakeup 0
> [ 1199.029051] hub 1-0:1.0: hub_suspend
> [ 1199.029145] usb usb1: bus auto-suspend, wakeup 1
>
> $ ls -al /dev/video0 
> crw-rw---T+ 1 root video 81, 0 Sep  4 23:45 /dev/video0
>
> But when I try to capture some image it fails. I tried with streamer, 
> mjpg-streamer and ffmpeg but always get timeout. My impression is that not 
> all the modules are being loaded. For instance when I plug the camera on my 
> laptop I get the following modules on lsmod:
>
> $ lsmod
> ...
> uvcvideo   80885  0 
> videobuf2_vmalloc  13216  1 uvcvideo
>
>
> *videobuf2_memops   13362  1 videobuf2_vmallocvideobuf2_core 
> 40664  1 uvcvideovideodev  134688  2 uvcvideo,videobuf2_core*
> ...
>
> The 3 last aren't being loaded on the BBB. Do you have any suggestions? 
> What could it be?
> Thanks a lot for any hints!
>

-- 
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] Welcome the Fall 2014 Beagle Class to the group

[Jason Kridner]

Looking forward to it!

Current hot topics:
* 3.14 kernel with USB DMA, 3D graphics support and more fixes/updates
* Capemgr/overlay, cape and userspace pinmuxing (cape-universal) support
* Simplified PRU usage
* Debugifying BoneScript
* Python library improvements
* Demos of cool stuff coming out of http://beagleboard.org/gsoc and
http://www.ti.com/ep-mcu-msp-mcugen-mspblog-20140823-mc1-en#DIY_with_TI:_Intern_Edition_.2F.2F_2014


On Fri, Sep 5, 2014 at 11:13 AM, Mark A. Yoder 
wrote:

> The purpose of this posting is to announce that I'm once again teaching
> an Embedded Linux class based on the BeagleBone Black [1].  I'm
> teaching as open-source as I can and have have posted many of course
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and
> suggestions for interesting course projects.  For example we are starting
> BoneScript today and hope to be writing simple kernel module 5 weeks from
> now.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark
>
> --Prof. Mark A. Yoder
>   Rose-Hulman Institute of Technology [4]
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman
> [2] http://elinux.org/index.php?title=Category:ECE597
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises
> [4]  http://www.rose-hulman.edu
>
> --
> 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] How to enable SPI devices on 3.14 kernel?

[Jason Lange]

On Friday, 29 August 2014 10:37:09 UTC-7, RobertCNelson wrote:
>
>
>
> 2nd thought, the uart conflicts.. 
> so disable: 
>
> #include "am335x-bone-basic-proto-cape.dtsi" 
> -> 
> /* #include "am335x-bone-basic-proto-cape.dtsi" */ 
>
> Then add spi0: 
> #include "am335x-bone-spi0-spidev.dtsi" 
>
> Then spi1: 
> #include "am335x-bone-spi1-spidev.dtsi" 
> or 
> #include "am335x-bone-spi1a-spidev.dtsi" 
>
> then make/sudo make install/sudo reboot 
>
>  
..I think I should add this for completion

Also do:

#include "am335x-boneblack-nxp-hdmi-audio.dtsi"

to:

/*#include "am335x-boneblack-nxp-hdmi-audio.dtsi"*/ 

and if you want hdmi do:

/* #include "am335x-boneblack-nxp-hdmi-no-audio.dtsi"*/

to:

 #include "am335x-boneblack-nxp-hdmi-no-audio.dtsi"

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

Re: [beagleboard] BeagleBone Black DDR3 RAM Voltage levels

[Gerald Coley]

Ahh. Correct so that needs to be added to the EEPROM to work or
a custom UBoot created for non conforming boards, those without EEPROM or
EEPROM with different information in the EEPROM.

Thanks Robert for checking!

Gerald
.






On Fri, Sep 5, 2014 at 12:38 PM, Robert Nelson 
wrote:

> On Fri, Sep 5, 2014 at 12:32 PM, Gerald Coley 
> wrote:
> > SW is supposed to set it to 1.35V. Sounds like it got dropped somewhere
> > because initially it did.. It was designed this way because when it was
> > designed, the PMIC defaulted to 1.5V. Since the design there is a
> TPS65217D
> > that was release later that supports the 1.35V initial setting.
>
> It should be set here:
>
>
> http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=0739e6021a21e71d7d0f5c840b793ce7fdf98fae;hb=HEAD#l275
>
> 269 /*
> 270  * Increase USB current limit to 1300mA or 1800mA and
> set
> 271  * the MPU voltage controller as needed.
> 272  */
> 273 if (dpll_mpu_opp100.m == MPUPLL_M_1000) {
> 274 usb_cur_lim =
> TPS65217_USB_INPUT_CUR_LIMIT_1800MA;
> 275 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1325MV;
> 276 } else {
> 277 usb_cur_lim =
> TPS65217_USB_INPUT_CUR_LIMIT_1300MA;
> 278 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1275MV;
> 279 }
>
>
> But that only happens if you have the "beaglebone black" header in eeprom:
>
> 262 /*
> 263  * Override what we have detected since we know if we
> have
> 264  * a Beaglebone Black it supports 1GHz.
> 265  */
> 266 if (board_is_bone_lt(&header))
>
> So you'll have to override that check.
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[beagleboard] Re: debian testing: 2014-09-03 (goodbye vfat release)

[Jason Lange]

This is good.

I really like that when I plug it into my desktop usb port I now have the 
whole root file system mounting and available for overview from my 
desktop.  So with only a usb connection I can ssh into 192.168.7.2 where I 
do most of my work but I can still mouse around the file system with a gui 
overview without the overhead of a desktop running on the BBB.

Note:

I started with this image :
http://rcn-ee.net/deb/testing/2014-09-04/console/bone-debian-7.6-console-armhf-2014-09-04-2gb.img.xz

which has just one ext4 partition.  No fat. No cholesterol.
(console images are anorexic to began with, so I had to force feed it a 
mass of debs to build up its strength.)

I don't know what happens to your gadget functionality if you convert from 
an existing system

Thank you Robert.

-- 
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] Can "allocated pins" on BBB be used as GPIOs ?

[halfbrain]

 it finally works :-)))

Thanks so much guys for your tips and help, espacially william.

I just added 

*optargs=capemgr.disable_partno=BB-BONE-EMMC-2G*

in the uEnv.txt file to disable all the emmc Pins. now I have more than 
enough pins for my project.



Am Donnerstag, 4. September 2014 22:48:05 UTC+2 schrieb William Hermans:
>
> From my own blog site:
>
> optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>
> This is both for hdmi video and audio. This was prior to later kernel 
> version "images" that now use two different uEnv.txt files. You have a 
> first stage uEnv.txt file and a second stage uEnv.txt file ( for loading 
> secondary environment variables ).
>
> here is an example of the secondary uEnv.txt file which sits in /boot/ on 
> the rootfs.
>
> *#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 
>> *
>>
>> *uname_r=3.8.13-bone62*
>>
>> *#dtb=*
>>
>> *cmdline=quiet init=/lib/systemd/systemd*
>>
>> *##Example*
>> *#cape_disable=capemgr.disable_partno=*
>> *#cape_enable=capemgr.enable_partno=*
>>
>> *##Disable HDMI/eMMC*
>>
>> *#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G*
>>
>> *##Disable HDMI*
>> *#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>>
>> *##Disable eMMC*
>> *#cape_disable=capemgr.disable_partno=BB-BONE-EMMC-2G*
>>
>> *##Audio Cape (needs HDMI Audio disabled)*
>> *#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI*
>> *#cape_enable=capemgr.enable_partno=BB-BONE-AUDI-02*
>>
>>
>>
>> *##enable BBB: eMMC Flasher:*
>> *##make sure, these tools are installed: dosfstools rsync*
>> *#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v2.sh*
>>
>
> I believe that came out of RCN's August 5th LXDE standalone image.
>
>
> On Thu, Sep 4, 2014 at 1:39 PM, halfbrain  > wrote:
>
>> Thank you Brandon and William for your answers and tips. It seems that 
>> you both write about the same method... changing some lines of code in the 
>> uEnv.txt etc
>>
>> I will try this one out as soon as possible and will hopefully give you a 
>> positive feedback then ;-)
>>
>> Am Donnerstag, 4. September 2014 22:30:54 UTC+2 schrieb Brandon I:
>>>
>>> halfbrain,
>>>
>>> > - If I used the EMMC pins I would need to boot from SD Card everytime? 
>>>
>>> Correct. You'll use the beaglebone white/sd card images. The beaglebone 
>>> will automatically boot from the SD card since it wont be able to find the 
>>> EMMC.
>>>
>>> > - And if I used the HMDI Pins it wouldn't be possible to connect the 
>>> uHdmi Cable to the bbb and connect some screen to it? Because they are 
>>> connected to the same pins?
>>>
>>> No HDMI if you disable HDMI, but you can still ssh/vnc in.
>>>
>>> The way I'm suggesting is the proper way to disable built in overlays 
>>> that are loaded at boot. For some reason, only the hdmi and emmc interfaces 
>>> are added as overlays that can be disabled at boot. i2c and the likes are 
>>> hard coded in the dts file. Why? I don't know. Maybe there's a good reason, 
>>> probably not.
>>>
>>> --Brandon
>>>
>>>
>>> On Thu, Sep 4, 2014 at 7:28 AM, halfbrain  wrote:
>>>
 Thanks for your Answer Brandon

 Just a few questions for my Information:
 - If I used the EMMC pins I would need to boot from SD Card everytime? 
 - And if I used the HMDI Pins it wouldn't be possible to connect the 
 uHdmi Cable to the bbb and connect some screen to it? Because they are 
 connected to the same pins?

 The way you unallocated the pins and the way john recommend me to 
 unallocate the pins seem to be very different. To be honest I don't 
 understand the difference of the two ways. Which way is the easier one and 
 can this way be used to unallocate every pin on the bbb? I just wan't to 
 make things trickier than they are :-) But i'm very thankful for your help 
 so far ;-)

 Am Mittwoch, 3. September 2014 22:00:16 UTC+2 schrieb Brandon I:

> halfbrain, I forgot to mention, you should tie the eMMC cmd and clock 
> pins low on P8.20 and P8.21, as suggested by the wiki: 
> http://elinux.org/Beagleboard:BeagleBoneBlack#Onboard_eMMC
>
> On Wednesday, September 3, 2014 12:58:09 PM UTC-7, Brandon I wrote:
>>
>> halfbrain,
>>
>> If you're using angstrom or debian, you can disable the emmc by 
>> adding this to the optargs in uEnv.txt on the usb mass storage 
>> partition: capemgr.disable_partno=BB-BONE-EMMC-2G
>>
>> If you're not using hdmi, you can free up those 
>> too: capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,
>> BB-BONE-EMMC-2G
>>
>>
>> On Saturday, August 23, 2014 1:11:22 AM UTC-7, halfbrain wrote:
>>>
>>> Would be nice if you could explain how to disable eMMC on debian. I 
>>> ran out of GPIO's in my project. Tried to use P9_19 and P9_20 (both 
>>> I2C's) 
>>> in the device tree overlay but since i d

Re: [beagleboard] BBB unresponsive to VDD_5V

[Jon Escombe]

Thanks Gerald, have submitted a request..

Regards,
Jon

On 05/09/14 18:20, Gerald Coley wrote:

Go the RMA route so it can be looked at.

Gerald


On Fri, Sep 5, 2014 at 12:08 PM, Jon E mailto:jesco...@googlemail.com>> wrote:

Hi,

Similar to a couple of older threads I've found on searching, one of
my BBB's (a rev B) has recently stopped powering up from VDD_5V
(either the barrel jack or P9 connector).

Not sure what might have triggered this, nothing had changed in
hardware setup for some time, power was permanently supplied from a
5V wall wart and it was being cleanly shutdown from software each
day, and restarted from the on-board power button. Only things
connected were ethernet, a USB RF dongle, and a hall effect sensor
(powered from VDD_3V3B). Have since removed everything, and just
attached a serial debug cable.

Timing to failure is a bit variable, from nothing at all, to a brief
flash of the power LED, to getting several seconds into boot before
it dies (have also tried running from a bench supply, but just the
same results). I suppose the PMIC is shutting things down for a
reason (it draws no current in this state), but it is still working
fine from the USB_DC line.

So I'm a bit stumped. Any ideas, or should I look for an RMA?

Thanks in advance,
Jon


--
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBone Black DDR3 RAM Voltage levels

[Robert Nelson]

On Fri, Sep 5, 2014 at 12:32 PM, Gerald Coley  wrote:
> SW is supposed to set it to 1.35V. Sounds like it got dropped somewhere
> because initially it did.. It was designed this way because when it was
> designed, the PMIC defaulted to 1.5V. Since the design there is a TPS65217D
> that was release later that supports the 1.35V initial setting.

It should be set here:

http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=0739e6021a21e71d7d0f5c840b793ce7fdf98fae;hb=HEAD#l275

269 /*
270  * Increase USB current limit to 1300mA or 1800mA and set
271  * the MPU voltage controller as needed.
272  */
273 if (dpll_mpu_opp100.m == MPUPLL_M_1000) {
274 usb_cur_lim = TPS65217_USB_INPUT_CUR_LIMIT_1800MA;
275 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1325MV;
276 } else {
277 usb_cur_lim = TPS65217_USB_INPUT_CUR_LIMIT_1300MA;
278 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1275MV;
279 }


But that only happens if you have the "beaglebone black" header in eeprom:

262 /*
263  * Override what we have detected since we know if we have
264  * a Beaglebone Black it supports 1GHz.
265  */
266 if (board_is_bone_lt(&header))

So you'll have to override that check.

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

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

Re: [beagleboard] max microsdxc size

[Robert Nelson]

On Thu, Sep 4, 2014 at 7:12 PM, thatwasfunny  wrote:
>
> I have a chance to get a 128 GB microsdxc card for cheap.  Does the
> Beaglebone Black support a card this size?  Thanks.

Nope..

only "SD/SDHC"

http://en.wikipedia.org/wiki/Secure_Digital#Overview

The "SDXC" spec came out "after" the ip was designed..

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

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

Re: [beagleboard] BeagleBone Black DDR3 RAM Voltage levels

[Gerald Coley]

SW is supposed to set it to 1.35V. Sounds like it got
dropped somewhere because initially it did.. It was designed this way
because when it was designed, the PMIC defaulted to 1.5V. Since the design
there is a TPS65217D that was release later that supports the
1.35V initial setting.

Yep, I meant to do that and Yes it is OK, however I prefer the SW folks fix
UBoot, if it isn't too much trouble.

Gerald


On Fri, Sep 5, 2014 at 12:36 AM,  wrote:

>
> Hello,
> I've been working to create an industrial temperature derivative of the
> BBB(BeagleBoneBlack).  In doing so I've noticed that the DDR3 SDRAM part
> numbers that are used are DDR3L or 1.35V parts.  However, the design uses
> the TPS65217C device which automatically sets the DDR3 voltage to 1.5 volts
> upon power up.  After going through the Uboot source, I found that software
> does not change the DCDC1 from it's default value of 1.5V.
>
> I believe the datasheet for the Micron part says that even though it
> supports DDR3L 1.35V mode, it can also run at 1.5V range and will be in
> DDR3 mode.
>
> Was this by design?  Mostly I'm just looking for a "Yep, we meant to do
> that and it's A-OK"
>
> ==
>
> This e-mail, including any attachments, is intended for the exclusive use
> of the person(s) to which it is addressed and may contain proprietary,
> confidential and/or privileged information. If the reader of this e-mail is
> not the intended recipient or his or her authorized agent, any review, use,
> printing, copying, disclosure, dissemination or distribution of this e-mail
> is strictly prohibited. If you think that you have received the e-mail in
> error, please notify the sender immediately by return e-mail, delete this
> communication and destroy all copies.
>
> ==
>
> --
> 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] Read USB through GPIO

[samthomasdigital]

Hi There!

I have a feeling the answer to this question will be no. But, does anybody 
know if it is possible to mount a USB device through the GPIO pins? I need 
to connect two powered devices to the BBB and would rather not use a USB 
hub because of the added weight.

Thanks!

Sam

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

[beagleboard] Re: BBB 24-bit LCD using device tree

[tanar . ulric]

Thanks for the pointer David.  I'd reviewed that before, but hadn't noticed 
the extra steps at the bottom.  Unfortunately, those still don't get 24 bit 
video going (per fbset).  So, I'm still wondering if anyone knows if the 
tilcdc in 3.8.13-bone50 kernel is supporting 24 bit modes, or if I need to 
get a different video driver.

On Tuesday, September 2, 2014 9:02:49 AM UTC-7, David Anders wrote:
>
>  http://elinux.org/24bit_LCD_for_BBB
>

-- 
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: Is it possible to root Beaglebone Black Android image

[iomari]

I'm just seeing this post. I'm amazed that no one has replied yet. I am 
desperately looking for this solution. Every android tool I have for 
rooting does not work on BBB. This is the 1st time I could not root an 
android 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: glibc_2.17 not found

[ward . willats]

Simon:

THANK YOU!

Had the same problem using a cross compiler I built on OSX that was far in 
advance of the BBB wheezy image.

I added libstdc++6 to the sources list because we needed that too.

Works great now!

-- Ward

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

[beagleboard] BeagleBone Black DDR3 RAM Voltage levels

[jason]

Hello,
I've been working to create an industrial temperature derivative of the 
BBB(BeagleBoneBlack).  In doing so I've noticed that the DDR3 SDRAM part 
numbers that are used are DDR3L or 1.35V parts.  However, the design uses 
the TPS65217C device which automatically sets the DDR3 voltage to 1.5 volts 
upon power up.  After going through the Uboot source, I found that software 
does not change the DCDC1 from it's default value of 1.5V.

I believe the datasheet for the Micron part says that even though it 
supports DDR3L 1.35V mode, it can also run at 1.5V range and will be in 
DDR3 mode.

Was this by design?  Mostly I'm just looking for a "Yep, we meant to do 
that and it's A-OK"

-- 
==

This e-mail, including any attachments, is intended for the exclusive use 
of the person(s) to which it is addressed and may contain proprietary, 
confidential and/or privileged information. If the reader of this e-mail is 
not the intended recipient or his or her authorized agent, any review, use, 
printing, copying, disclosure, dissemination or distribution of this e-mail 
is strictly prohibited. If you think that you have received the e-mail in 
error, please notify the sender immediately by return e-mail, delete this 
communication and destroy all copies.

==

-- 
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] max microsdxc size

[thatwasfunny]

I have a chance to get a 128 GB microsdxc card for cheap.  Does the 
Beaglebone Black support a card this size?  Thanks.

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

[beagleboard] Re: glibc_2.17 not found

[ward . willats]

Simon:

THANK YOU!

I was cross compiling with a custom built chain on OSX and of course it was 
more current than wheezy and had the same problem.

I did add libstdc++6 to the package list because we are crazy enough to do 
that stuff and I was getting errors from the dynaloader for that too.

Works great now!

-- Ward

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

[beagleboard] error p8_11

[keo . lcms]

I all,
I have problème i want out in P8_11 but I have error 

error: analogWrite: P8_11 does not support analogWrite()

Why , 
What i do for use this pin ?
thank a lot for reply :)

-- 
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: Why did my BB die ?

[jason]

   
   1. The voltage sequencing mentioned by Gerald is big and is probably the 
   real failure mode.  In this design, the AIN pins will see voltage long 
   before the CPU/PMIC (Power Management IC) is up and running.  Basically, 
   when a voltage is applied to the analog pins (or any IO pins for that 
   matter) before the IO rail is up, the chip tries to power itself through 
   the pin clamping diodes and can really cause havoc on the silicon. The chip 
   just wasn't made to be powered this way.
   2. Did you check that the 1Ohm resistor didn't blow or that the voltage 
   across it didn't exceed the limit for the ADC inputs?  If it does fail open 
   for some reason, the voltage would far exceed the max voltage on the Analog 
   pins.  Might want to add some protection there in case that resistor ever 
   does blow, or the voltage across it exceeds the max analog voltage.
   3. Also note that the 1Ohm resistor isn't just powering the BBB, it's 
   charging the battery!  Chances are the solar panel was putting too much 
   juice into the battery and caused the 1Ohm resistor to have a much larger 
   voltage across it.
   4. You might move the 1Ohm resistor to the ground leg between the 
   battery and the solar panel, instead of between the solar panel and the 
   battery.

On Monday, August 25, 2014 1:56:37 AM UTC-5, A Daviel wrote:
>
> I'm trying to run a Beagleboard Black from solar power, and I set it up 
> per the attached schematic.
> The analog inputs are used to measure the BB system voltage, the battery 
> voltage, and the current from the solar panel by measuring the voltage 
> either side of a one ohm resistor in the ground lead (500mA from the panel 
> should give 500mV, less than the 1.8V maximum)
>
> I'd run it on USB power from a PC for several days, then from a car 12V 
> USB adapter on the 12V battery, with no problem, with a  proto board cape 
> to measure
> the battery voltage. Also with a 5V supply via the coax power connector.
>
> Then I connected the solar panel, nominal 4W 12V, and left it outside 
> while the sun rose in the sky. The BB was OK for a while, then died. It 
> appears to be completely defunct - no flashing LEDs, on whatever supply 
> (battery, USB etc.)
>
> When I checked voltages, it did seem that there was a bad connection to 
> the battery terminals. The no-load output voltage of the  panel is  in 
> excess of the nominal 12V, so the obvious suggestion is that the input 
> voltage overpowered the BB. But with the BB and battery disconnected, the 
> USB adapter was still producing 5.25V output with an input voltage of some 
> 20V, and I assume (though I have no specs) that this is normal - a car 
> supply voltage can rise to at least 14V under charge, so a car adapter 
> should be able to handle more than 12V.
>
>
>
-- 
==

This e-mail, including any attachments, is intended for the exclusive use 
of the person(s) to which it is addressed and may contain proprietary, 
confidential and/or privileged information. If the reader of this e-mail is 
not the intended recipient or his or her authorized agent, any review, use, 
printing, copying, disclosure, dissemination or distribution of this e-mail 
is strictly prohibited. If you think that you have received the e-mail in 
error, please notify the sender immediately by return e-mail, delete this 
communication and destroy all copies.

==

-- 
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: Cross compiling using Eclipse and Ubuntu 64bit 12.04

[mrbarre7612]

Is this the compiler info you need. i'm a Linux novice so it may not be 
what you want. 
compiler   -I/usr/arm-linux-gnueabi/include/c++/4.6.3 -O0 -g3 -Wall -c 
-fmessage-length=0

Linux kernal - Linux ubuntu 3.2.0-67-generic #101-Ubuntu SMP Tue Jul 15 
17:46:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

I downloaded the 12.04 version of Ubuntu from Ubuntu's website. 


-- 
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: GPIO toggle Kernel Module for Beaglebone

[csumik]

does this kernel module will help me for my linux kernel 3.8.13-bone47 
which is installed in my beagelbone black

thanking you

sumik chakka

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

[beagleboard] USB Camera on BBB (Debian GNU/Linux 7)

[amerello]

Hello,
  Could someone give me a hand? I'm having trouble getting a USB Camera to 
work on my BeagleBone Black.
 I'm using a 5V@1A adapter (I thought it could be a power issue), but it 
didn't solve it. I can provide the following information of my system:

$ uname -a
Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l 
GNU/Linux

$ lsusb
*Bus 001 Device 002: ID 1871:0101 Aveo Technology Corp. *
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ lsmod
Module  Size  Used by

*uvcvideo   53354  0 videobuf2_vmalloc   2418  1 uvcvideo*
g_multi47670  2 
libcomposite   14299  1 g_multi

$dmesg | less
...
[ 1196.227457] usb usb1: usb wakeup-resume
[ 1196.227556] usb usb1: usb auto-resume
[ 1196.227607] hub 1-0:1.0: hub_resume
[ 1196.227706] hub 1-0:1.0: port 1: status 0101 change 0001
[ 1196.329800] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 
[ 1196.329910] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s
[ 1196.435171] usb 1-1: new high-speed USB device number 3 using musb-hdrc
[ 1196.562835] usb 1-1: skipped 1 descriptor after configuration
[ 1196.562886] usb 1-1: skipped 5 descriptors after interface
[ 1196.562929] usb 1-1: skipped 1 descriptor after endpoint
[ 1196.562967] usb 1-1: skipped 9 descriptors after interface
[ 1196.563301] usb 1-1: default language 0x0409
[ 1196.564922] usb 1-1: udev 3, busnum 1, minor = 2
[ 1196.564969] usb 1-1: New USB device found, idVendor=1871, idProduct=0101
[ 1196.565009] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[ 1196.565044] usb 1-1: Product: USB2.0 Camera
[ 1196.565079] usb 1-1: Manufacturer: AVEO Technology Corp.
[ 1196.566432] usb 1-1: usb_probe_device
[ 1196.566483] usb 1-1: configuration #1 chosen from 1 choice
[ 1196.566782] usb 1-1: adding 1-1:1.0 (config #1, interface 0)



*[ 1196.568276] uvcvideo 1-1:1.0: usb_probe_interface[ 1196.568333] 
uvcvideo 1-1:1.0: usb_probe_interface - got id[ 1196.568476] uvcvideo: 
Found UVC 1.00 device USB2.0 Camera (1871:0101)[ 1196.574639] input: USB2.0 
Camera as 
/devices/ocp.3/4740.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input2*
[ 1196.575902] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
[ 1196.578270] hub 1-0:1.0: state 7 ports 1 chg  evt 0002
[ 1196.578369] hub 1-0:1.0: port 1 enable change, status 0503
[ 1199.015323] usb 1-1: usb auto-suspend, wakeup 0
[ 1199.029051] hub 1-0:1.0: hub_suspend
[ 1199.029145] usb usb1: bus auto-suspend, wakeup 1

$ ls -al /dev/video0 
crw-rw---T+ 1 root video 81, 0 Sep  4 23:45 /dev/video0

But when I try to capture some image it fails. I tried with streamer, 
mjpg-streamer and ffmpeg but always get timeout. My impression is that not 
all the modules are being loaded. For instance when I plug the camera on my 
laptop I get the following modules on lsmod:

$ lsmod
...
uvcvideo   80885  0 
videobuf2_vmalloc  13216  1 uvcvideo


*videobuf2_memops   13362  1 videobuf2_vmallocvideobuf2_core 
40664  1 uvcvideovideodev  134688  2 uvcvideo,videobuf2_core*
...

The 3 last aren't being loaded on the BBB. Do you have any suggestions? 
What could it be?
Thanks a lot for any hints!

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

Re: [beagleboard] BBB unresponsive to VDD_5V

[Gerald Coley]

Go the RMA route so it can be looked at.

Gerald


On Fri, Sep 5, 2014 at 12:08 PM, Jon E  wrote:

> Hi,
>
> Similar to a couple of older threads I've found on searching, one of my
> BBB's (a rev B) has recently stopped powering up from VDD_5V (either the
> barrel jack or P9 connector).
>
> Not sure what might have triggered this, nothing had changed in hardware
> setup for some time, power was permanently supplied from a 5V wall wart and
> it was being cleanly shutdown from software each day, and restarted from
> the on-board power button. Only things connected were ethernet, a USB RF
> dongle, and a hall effect sensor (powered from VDD_3V3B). Have since
> removed everything, and just attached a serial debug cable.
>
> Timing to failure is a bit variable, from nothing at all, to a brief flash
> of the power LED, to getting several seconds into boot before it dies (have
> also tried running from a bench supply, but just the same results). I
> suppose the PMIC is shutting things down for a reason (it draws no current
> in this state), but it is still working fine from the USB_DC line.
>
> So I'm a bit stumped. Any ideas, or should I look for an RMA?
>
> Thanks in advance,
> Jon
>
>  --
> 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: SPI, I2C ports at Beaglebone Black

[Matheus Luiz]

Ok, thank you my friend, I actually had looked at this site, but need not 
necessarily be I2C, SPI can be. I just need to communicate with the I/O. 
Thanks for answering.

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

[beagleboard] BBB unresponsive to VDD_5V

[Jon E]

Hi,

Similar to a couple of older threads I've found on searching, one of my 
BBB's (a rev B) has recently stopped powering up from VDD_5V (either the 
barrel jack or P9 connector).

Not sure what might have triggered this, nothing had changed in hardware 
setup for some time, power was permanently supplied from a 5V wall wart and 
it was being cleanly shutdown from software each day, and restarted from 
the on-board power button. Only things connected were ethernet, a USB RF 
dongle, and a hall effect sensor (powered from VDD_3V3B). Have since 
removed everything, and just attached a serial debug cable.

Timing to failure is a bit variable, from nothing at all, to a brief flash 
of the power LED, to getting several seconds into boot before it dies (have 
also tried running from a bench supply, but just the same results). I 
suppose the PMIC is shutting things down for a reason (it draws no current 
in this state), but it is still working fine from the USB_DC line. 

So I'm a bit stumped. Any ideas, or should I look for an RMA?

Thanks in advance,
Jon

-- 
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: trying to learn enough to get started

[William Hermans]

>
> *Why compile anything?  For the proposed project (Greenhouse control)*
> * speed is not any sort of priority so use an interpreted language, the*
> * obvious choice on BBB is Python.*
>

Well, the obvious choice to me is Nodejs, and am betting since this person
has 35 years experience in related fields, that C is a possibility as well.

I've only been programming for 20 or so years . . . so what the hell do i
know ?


On Fri, Sep 5, 2014 at 1:51 AM,  wrote:

> William Hermans  wrote:
> > [-- text/plain, encoding 7bit, charset: UTF-8, 51 lines --]
> >
> > You need to find and read sources about embedded Linux. Then, since your
> > project could be done using any number of languages, you need to figure
> > that out too. Past that, you're going to have to figure out what hardware
> > you're going to use. Which will indicate if you're using SPI. I2C, UART,
> > onboard ADC's or PWM's etc.
> >
> > In your shoes, I'd start off with and continue using these instructions:
> > https://eewiki.net/display/linuxonarm/BeagleBone+Black. You can use
> either
> > Debian or Ubuntu with these build instructions. I've been using these
> > instructions since last year ( around 14 or slightly more months ), and
> > they're very consistent.
> >
> > You could also start off with a premade Debian console image if you like.
> >
> > You can definitely compile natively on the board, but if you plan on
> cross
> > compiling, you're going to need to understand the gcc toolchain
> thoroughly.
> > For setup and use.
> >
> Why compile anything?  For the proposed project (Greenhouse control)
> speed is not any sort of priority so use an interpreted language, the
> obvious choice on BBB is Python.
>
> ... and I am also a long in the tooth software engineer with maybe 30
> years of experience writing C, but I'd still recommend going with
> Python on this sort of project.
>
> --
> Chris Green
> ·
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] Re: Yet another newbie "how to get started"

[William Hermans]

You can find free legitimate reading material easily on the web. LDD (
Linux Device Drivers is one example ).

Not to mention sites like

http://www.debianhelp.co.uk/ddcommand.htm and
https://wiki.debian.org/NetworkConfiguration

Note that both those came up off of a google search, so yeah google is
probably the most important resource.




On Fri, Sep 5, 2014 at 7:11 AM, Joshua Datko  wrote:

>
>
> Tim Cole  writes:
>
> > Agreed -- you can't learn a damned thing without putting in your own
> > skull time. Perhaps I'm too distrustful of internet search engines --
> > I like a good reference handbook. If there isn't one available, I'll
> > just have to make do.
>
> By far, the number one reference on the BeagleBone Black is the System
> Reference Manual:
>
> https://github.com/CircuitCo/BeagleBone-Black/blob/master/BBB_SRM.pdf?raw=true
>
> It's impressively complete.
>
> However, that mainly covers the hardware. Since hardware doesn't change
> as often as software (although it's becoming more that way) any other
> reference is a snapshot in time, especially for Linux resources.
>
> In increasing specificity, one would need (supplied with links to books
> I like):
>
> - A good Linux reference
> http://www.nostarch.com/howlinuxworks.htm
>
> - A good Debian reference
> http://www.nostarch.com/debian.htm
>
> - A good embedded Linux reference
> http://www.amazon.com/Linux-Embedded-Systems-Experts-Voice/dp/1430272279
>
> - A good Linux programming reference
> http://www.nostarch.com/tlpi
>
> The difficulty in writing books on the BeagleBone is that the community
> moves incredibly fast. This is the sign of a healthy and vibrant
> community.
>
> Josh
>
> p.s. There are, of course, great *free* resources too. One would have to
> use a distrustful search engine to find them :p
>
> --
> 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: installing centos on bbblk?

[Mike Opoien]

awesome- thanks for the reply.  thats a great help.  much appreciated.


On Friday, September 5, 2014 8:16:40 AM UTC-5, Mike Opoien wrote:
>
> I would like to install centos on my black.  Is this possible from CD rom?
>

-- 
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] ROS Hydro on BBB

[Alan Federman]

For those of you attempting to run ROS (Robot Operating System) on Ubuntu 
12.04, 12.10, 13.04 - the ARM repositories currently are missing a key 
component call 'tf'.  his component is important if you actually want to 
have a robot that can move.  Instruction for installing ROS in arm are at:

http://wiki.ros.org/hydro/Installation/UbuntuARM




-- 
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] Welcome the Fall 2014 Beagle Class to the group

[Mark A. Yoder]

The purpose of this posting is to announce that I'm once again teaching 
an Embedded Linux class based on the BeagleBone Black [1].  I'm 
teaching as open-source as I can and have have posted many of course 
materials on eLinux.org [2] and github[3].

I'm always open to ideas on what topics to include in the class and 
suggestions for interesting course projects.  For example we are starting
BoneScript today and hope to be writing simple kernel module 5 weeks from 
now.

Class, please respond to this posting.  Others, please welcome my class.

--Mark 

--Prof. Mark A. Yoder 
  Rose-Hulman Institute of Technology [4] 

[1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
[2] http://elinux.org/index.php?title=Category:ECE597 
[3] https://github.com/MarkAYoder/BeagleBoard-exercises 
[4]  http://www.rose-hulman.edu 

-- 
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: How do I find out what image my brand new Beaglebone Black is running?

[Mark A. Yoder]

jgold:
 Try: *cat /etc/dogtag *

I think the May image is the latest released image, that is the image that 
ships on the Bone.  There was a new test image pushed yesterday 
(4-Sep-2014).

--Mark


On Friday, September 5, 2014 1:48:36 AM UTC-4, jgold wrote:
>
> I just got a Beaglebone Black from Adafruit.  It came with debian 
> pre-installed. In going though the getting started guide, one of the first 
> things it recommends to do is update the image. That's probably a good idea 
> but the lastest image is from May so I probably already have it.  I'd like 
> to check before going to all the work of flashing a new image but I can't 
> seem to determine the version I'm currently running.  It seems like 
> something everyone would want to know before they do an update.  Anyone 
> know how to find it?
>
> Thanks.
>
>

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

[beagleboard] Re: SPI, I2C ports at Beaglebone Black

[Joshua Datko]

Matheus Luiz 
writes:

> Hi guys, i'm have problems at how to use i2c and SPI ports in
> Beaglebone Black, anyone can help me? Exist some tutorials i can
> follow?

I like this tutorial on I2C: http://datko.net/2013/11/03/bbb_i2c/

Of course, I might be biased :p


-- 
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: Yet another newbie "how to get started"

[Joshua Datko]

Tim Cole  writes:

> Agreed -- you can't learn a damned thing without putting in your own
> skull time. Perhaps I'm too distrustful of internet search engines --
> I like a good reference handbook. If there isn't one available, I'll
> just have to make do.

By far, the number one reference on the BeagleBone Black is the System
Reference Manual:
https://github.com/CircuitCo/BeagleBone-Black/blob/master/BBB_SRM.pdf?raw=true

It's impressively complete.

However, that mainly covers the hardware. Since hardware doesn't change
as often as software (although it's becoming more that way) any other
reference is a snapshot in time, especially for Linux resources.

In increasing specificity, one would need (supplied with links to books
I like):

- A good Linux reference
http://www.nostarch.com/howlinuxworks.htm

- A good Debian reference
http://www.nostarch.com/debian.htm

- A good embedded Linux reference
http://www.amazon.com/Linux-Embedded-Systems-Experts-Voice/dp/1430272279

- A good Linux programming reference
http://www.nostarch.com/tlpi

The difficulty in writing books on the BeagleBone is that the community
moves incredibly fast. This is the sign of a healthy and vibrant
community.

Josh

p.s. There are, of course, great *free* resources too. One would have to
use a distrustful search engine to find them :p

-- 
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] installing centos on bbblk?

[Robert Nelson]

On Fri, Sep 5, 2014 at 8:16 AM, Mike Opoien  wrote:
> I would like to install centos on my black.  Is this possible from CD rom?

sure you can "install" it.. It won't boot/run/etc...

There was an 'effort' to re-build centos as "redsleeve" no idea about
it's progress..

If you want "arm" and "redhat" use "fedora" as they have an official release

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

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

[beagleboard] installing centos on bbblk?

[Mike Opoien]

I would like to install centos on my black.  Is this possible from CD rom?

-- 
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] SPI, I2C ports at Beaglebone Black

[Matheus Luiz]

Hi guys, i'm have problems at how to use i2c and SPI ports in Beaglebone 
Black, anyone can help me? Exist some tutorials i can follow?

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

Re: [beagleboard] debian testing: 2014-09-03 (goodbye vfat release)

[Vesa Jääskeläinen]

On 04/09/14 21:24, Robert Nelson wrote:

Howdy!

I just pushed out another round of images for testing.

There's really only "one" big change with this image, the sorta change
that will re-write every wiki document.

NO VFAT PARTITION REQUIRED!!!

Let me repeat that... THE VFAT "boot" PARTITION IS NOT REQUIRED! ;)

So far i've only got it to reliabley work on omap4+ bootroms (which
include the am335x).. so beagle/beagle-xm, not yet...

MBR/GPT's MBR emu is at the first sectors of the card. So are you using 
relocateable MBR/GPT? Or how are you handling that issue?


Would it be wise to also support backup boot loader in case first one 
gets corrupt? -- if I recon correctly the bootrom should also support that.


--
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone Black Rebooting Several Times Every Day

[Greg Kelley]

Robert, I just looked at the kernel in this image (3.8.13-bone64) and that 
was the first image I flashed after receiving the BBB. I had USB hot plug 
issues with that kernel version so I upgraded to 3.16.0. It would not 
recognize an external USB Hub plugged in after startup, only when plugged 
in at power up and would not recognize any USB devices hot plugged into the 
Hub. Not a problem with 3.14, 3.15, 3.16 when I was testing.

On Thursday, September 4, 2014 2:28:58 PM UTC-4, RobertCNelson wrote:
>
> On Thu, Sep 4, 2014 at 1:26 PM, Greg Kelley  > wrote: 
>
> Greg, please give this image a shot. 
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-09-03 
>
> It includes all the "3.8" kernel fixes since the May release came out.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

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

Re: [beagleboard] Beaglebone Black Rebooting Several Times Every Day

[Greg Kelley]

Hi Robert, I reflashed the original distro and it ran for about a half hour 
and rebooted so I have determined it is a hardware issue, (probably a 
grounding problem according to the vendor so perhaps there is a QC issue at 
element14) so I have returned the element14 BBB to the vendor for a refund 
and ordered a CircuitCo BBB from Adafruit. Will arrive Monday so will have 
it up and running on Tuesday. I plan to upgrade the kernel to 3.14.17-bone8 
which is close to what you recommended for stability and long term support. 
I can give the 2014-09-13 image a try before kernel upgrade if you need me 
to test but it will be on a new BBB and not the 'problem child'. Thanks for 
all you hard work, makes maintaining a BBB pretty painless.

On Thursday, September 4, 2014 2:28:58 PM UTC-4, RobertCNelson wrote:
>
>
> Greg, please give this image a shot. 
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-09-03 
>
> It includes all the "3.8" kernel fixes since the May release came out.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

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

[beagleboard] Re: How to SSH to BeagleBone's IP Address through USB cable on FreeBSD

[cl]

rayche...@gmail.com wrote:
> [-- text/plain, encoding 7bit, charset: UTF-8, 17 lines --]
> 
> I bought BBB today. It is a very cute board.After I install the drivers 
> this board provided, I can  SSH to  BeagleBone's IP Address through USB 
> cable on Windows 7. I have an FreeBSD 10 laptop, I try to  SSH to  
> BeagleBone's IP Address through USB cable on FreeBSD but I can't. It shows 
> "ssh: connect to host 192.168.7.2 port 22: Operation timed out". 
> Should I install any driver on FreeBSD? Or What can I do to make it works 
> like on win 7?
> 
Do you have a home LAN?  I.e. are your PCs plugged into a router or
some such?  If so it's far easier IMHO to just use the ethernet
connection on the BBB and plug that into one of the LAN connections on
the router.  You can still use the USB to power the BBB, or you can
separate it completely from the PC and power it from a USB charger.

-- 
Chris Green
·

-- 
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: trying to learn enough to get started

[cl]

William Hermans  wrote:
> [-- text/plain, encoding 7bit, charset: UTF-8, 51 lines --]
> 
> You need to find and read sources about embedded Linux. Then, since your
> project could be done using any number of languages, you need to figure
> that out too. Past that, you're going to have to figure out what hardware
> you're going to use. Which will indicate if you're using SPI. I2C, UART,
> onboard ADC's or PWM's etc.
> 
> In your shoes, I'd start off with and continue using these instructions:
> https://eewiki.net/display/linuxonarm/BeagleBone+Black. You can use either
> Debian or Ubuntu with these build instructions. I've been using these
> instructions since last year ( around 14 or slightly more months ), and
> they're very consistent.
> 
> You could also start off with a premade Debian console image if you like.
> 
> You can definitely compile natively on the board, but if you plan on cross
> compiling, you're going to need to understand the gcc toolchain thoroughly.
> For setup and use.
> 
Why compile anything?  For the proposed project (Greenhouse control)
speed is not any sort of priority so use an interpreted language, the
obvious choice on BBB is Python.

... and I am also a long in the tooth software engineer with maybe 30
years of experience writing C, but I'd still recommend going with
Python on this sort of project.

-- 
Chris Green
·

-- 
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 do I find out what image my brand new Beaglebone Black is running?

[William Pretty Security]

“ uname –a “   ;-)

 

"No one could make a greater mistake than he who did nothing because he could 
do only a little."

"All that is necessary for the triumph of evil is that good men do nothing" 
Edmond Burke (1729 - 1797)

http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book

 

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of jgold
Sent: Friday, September 05, 2014 1:49 AM
To: beagleboard@googlegroups.com
Subject: [beagleboard] How do I find out what image my brand new Beaglebone 
Black is running?

 

I just got a Beaglebone Black from Adafruit.  It came with debian 
pre-installed. In going though the getting started guide, one of the first 
things it recommends to do is update the image. That's probably a good idea but 
the lastest image is from May so I probably already have it.  I'd like to check 
before going to all the work of flashing a new image but I can't seem to 
determine the version I'm currently running.  It seems like something everyone 
would want to know before they do an update.  Anyone know how to find it?

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.



No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4015/8155 - Release Date: 09/04/14

-- 
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: question about I/O expansion

[TJF]

Why do you think you'll need any cape?

BBB has more then 15 free GPIOs and 7 analog inputs. You can simply build 
your prototype board to adjust the voltages (GPIO @ 3.3V, ADC @ 1.8 V) and 
feed the signals to the header pins.

-- 
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 do I find out what image my brand new Beaglebone Black is running?

[William Hermans]

You're sure the latest image is from may ?

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


On Thu, Sep 4, 2014 at 10:48 PM, jgold  wrote:

> I just got a Beaglebone Black from Adafruit.  It came with debian
> pre-installed. In going though the getting started guide, one of the first
> things it recommends to do is update the image. That's probably a good idea
> but the lastest image is from May so I probably already have it.  I'd like
> to check before going to all the work of flashing a new image but I can't
> seem to determine the version I'm currently running.  It seems like
> something everyone would want to know before they do an update.  Anyone
> know how to find it?
>
> 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.