[beagleboard] Re: os x trouble making SD image

2017-05-20 Thread mron 
Never mind about the password, I didn't read what it was asking for 
carefully.

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

[beagleboard] Re: os x trouble making SD image

2017-05-20 Thread mron 
Everything's good now. Thanks for the help. I was able to flash the latest 
image, it took a couple tries, but it's in. I can now boot from the SD card.

What is the default sudo password? I want to install some software.

Thanks again,

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

Re: [beagleboard] Re: Surefire PRU - Setup.

2017-05-20 Thread William Hermans 
oops, https://github.com/wphermans/bb-info is the top most path . . .

On Sat, May 20, 2017 at 6:27 PM, William Hermans  wrote:

> By the way these are my own preffered "pin mux mode" "spread sheet" PDF
> files for working with various pins: https://github.com/wphermans/
> bb-info/blob/master/BeagleboneBlackP8HeaderPinMuxModes.pdf
>
> I do not recall who made these, but links in the PDF's themselves lead
> back to who created them. Whom also derived the information in these files
> from Derrek Molloy.
>
> So I do not claim the material at all. I just wanted a location that was
> easy for me to find, and would never go away. My git seemed to be as good a
> place as any, for me.
>
> On Sat, May 20, 2017 at 6:14 PM, William Hermans 
> wrote:
>
>> Greg,
>>
>> You know what. If I were you, I would get a Beaglebone black or green,
>> and make learning about it your favorite hobby. This way, you could
>> experiment with various things, until you're happy with what you end up
>> using.
>>
>> If memory is serving me correctly yes, you're using a blue. Yes, yes, but
>> the hardware is largely the same, and most if not all the software will be
>> exactly the same.
>>
>> So yes, buy a beaglebone, take it home, and start experimenting. Then I
>> would probably not worry about HAVING to have hardware connected up with
>> it. There is a lot you can do by experimenting with software only. How, and
>> where to explore the GPIO subsystem. Which will then lead to being able to
>> tell if you've configured your overlay file at boot correctly. etc, etc.
>>
>> On Sat, May 20, 2017 at 6:01 PM, Gerald Coley 
>> wrote:
>>
>>> I decided not to copy what was in the TRM into the SRM. That is why the
>>> SRM is specific to the BBB. And the TRM gets updated failry often by TI.
>>>
>>>
>>>
>>> Gerald
>>>
>>>
>>>
>>>
>>>
>>> *From:* beagleboard@googlegroups.com [mailto:beagleboard@googlegrou
>>> ps.com] *On Behalf Of *William Hermans
>>> *Sent:* Saturday, May 20, 2017 8:00 PM
>>> *To:* beagleboard@googlegroups.com
>>> *Subject:* Re: [beagleboard] Re: Surefire PRU - Setup.
>>>
>>>
>>>
>>> System reference manual SRM, Technical reference manual TRM.
>>>
>>>
>>>
>>> On Sat, May 20, 2017 at 5:58 PM, William Hermans 
>>> wrote:
>>>
>>> No, prior to uboot overlays, overlays were loaded from the initrd, at
>>> best. Also we need to understand that the board file(also an overlay of
>>> sorts - but required )is seperate from all this discussion.
>>>
>>>  I do not understand why you would have "field people" playing around
>>> with hardware overlays though. Once your hardware is finalized, it should
>>> never change. Which is one small reason why I personally find Universal IO
>>> unnecessary for my own purposes.
>>>
>>> The problem I've seen with explanations, and documentation on device
>>> tree, is that no one explains it really well. Additionally, as a new player
>>> into device tree overlays. Its not clear where to get information from.
>>> See, you need to understand the pin-ctrl subsystem, gpio subsystem . . .
>>> list goes one, and on . . .A lot of this information has to be found from
>>> the Linux kernel source documentation.HOWEVER, you do not necessarily need
>>> to memorize all of this. We ( programmers ) just need a reference that does
>>> not goes on, and on for days about silly details we do not need to know to
>>> get our jobs done. Nothing like this exists.
>>>
>>> Anyway, in order to learn, you need to "do".
>>>
>>>
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/beagleboard/CALHSORrAaF4Z%2B%3DUZRq%2Bi_oMFRM_K88noC7y5D
>>> %3D9MQAkeRUovrw%40mail.gmail.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.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/beagleboard/a67232f2a5a94c10abc16cc8ff83aa70%40winhexbeu
>>> s11.winus.mail
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

-- 
For more options, visit

Re: [beagleboard] Re: Surefire PRU - Setup.

2017-05-20 Thread William Hermans 
By the way these are my own preffered "pin mux mode" "spread sheet" PDF
files for working with various pins:
https://github.com/wphermans/bb-info/blob/master/BeagleboneBlackP8HeaderPinMuxModes.pdf

I do not recall who made these, but links in the PDF's themselves lead back
to who created them. Whom also derived the information in these files from
Derrek Molloy.

So I do not claim the material at all. I just wanted a location that was
easy for me to find, and would never go away. My git seemed to be as good a
place as any, for me.

On Sat, May 20, 2017 at 6:14 PM, William Hermans  wrote:

> Greg,
>
> You know what. If I were you, I would get a Beaglebone black or green, and
> make learning about it your favorite hobby. This way, you could experiment
> with various things, until you're happy with what you end up using.
>
> If memory is serving me correctly yes, you're using a blue. Yes, yes, but
> the hardware is largely the same, and most if not all the software will be
> exactly the same.
>
> So yes, buy a beaglebone, take it home, and start experimenting. Then I
> would probably not worry about HAVING to have hardware connected up with
> it. There is a lot you can do by experimenting with software only. How, and
> where to explore the GPIO subsystem. Which will then lead to being able to
> tell if you've configured your overlay file at boot correctly. etc, etc.
>
> On Sat, May 20, 2017 at 6:01 PM, Gerald Coley 
> wrote:
>
>> I decided not to copy what was in the TRM into the SRM. That is why the
>> SRM is specific to the BBB. And the TRM gets updated failry often by TI.
>>
>>
>>
>> Gerald
>>
>>
>>
>>
>>
>> *From:* beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
>> *On Behalf Of *William Hermans
>> *Sent:* Saturday, May 20, 2017 8:00 PM
>> *To:* beagleboard@googlegroups.com
>> *Subject:* Re: [beagleboard] Re: Surefire PRU - Setup.
>>
>>
>>
>> System reference manual SRM, Technical reference manual TRM.
>>
>>
>>
>> On Sat, May 20, 2017 at 5:58 PM, William Hermans 
>> wrote:
>>
>> No, prior to uboot overlays, overlays were loaded from the initrd, at
>> best. Also we need to understand that the board file(also an overlay of
>> sorts - but required )is seperate from all this discussion.
>>
>>  I do not understand why you would have "field people" playing around
>> with hardware overlays though. Once your hardware is finalized, it should
>> never change. Which is one small reason why I personally find Universal IO
>> unnecessary for my own purposes.
>>
>> The problem I've seen with explanations, and documentation on device
>> tree, is that no one explains it really well. Additionally, as a new player
>> into device tree overlays. Its not clear where to get information from.
>> See, you need to understand the pin-ctrl subsystem, gpio subsystem . . .
>> list goes one, and on . . .A lot of this information has to be found from
>> the Linux kernel source documentation.HOWEVER, you do not necessarily need
>> to memorize all of this. We ( programmers ) just need a reference that does
>> not goes on, and on for days about silly details we do not need to know to
>> get our jobs done. Nothing like this exists.
>>
>> Anyway, in order to learn, you need to "do".
>>
>>
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/beagleboard/CALHSORrAaF4Z%2B%3DUZRq%2Bi_oMFRM_
>> K88noC7y5D%3D9MQAkeRUovrw%40mail.gmail.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.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/beagleboard/a67232f2a5a94c10abc16cc8ff83aa70%
>> 40winhexbeus11.winus.mail
>> 
>> .
>>
>> 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.
To view this discussion on

Re: [beagleboard] Re: Surefire PRU - Setup.

2017-05-20 Thread William Hermans 
Greg,

You know what. If I were you, I would get a Beaglebone black or green, and
make learning about it your favorite hobby. This way, you could experiment
with various things, until you're happy with what you end up using.

If memory is serving me correctly yes, you're using a blue. Yes, yes, but
the hardware is largely the same, and most if not all the software will be
exactly the same.

So yes, buy a beaglebone, take it home, and start experimenting. Then I
would probably not worry about HAVING to have hardware connected up with
it. There is a lot you can do by experimenting with software only. How, and
where to explore the GPIO subsystem. Which will then lead to being able to
tell if you've configured your overlay file at boot correctly. etc, etc.

On Sat, May 20, 2017 at 6:01 PM, Gerald Coley 
wrote:

> I decided not to copy what was in the TRM into the SRM. That is why the
> SRM is specific to the BBB. And the TRM gets updated failry often by TI.
>
>
>
> Gerald
>
>
>
>
>
> *From:* beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
> *On Behalf Of *William Hermans
> *Sent:* Saturday, May 20, 2017 8:00 PM
> *To:* beagleboard@googlegroups.com
> *Subject:* Re: [beagleboard] Re: Surefire PRU - Setup.
>
>
>
> System reference manual SRM, Technical reference manual TRM.
>
>
>
> On Sat, May 20, 2017 at 5:58 PM, William Hermans 
> wrote:
>
> No, prior to uboot overlays, overlays were loaded from the initrd, at
> best. Also we need to understand that the board file(also an overlay of
> sorts - but required )is seperate from all this discussion.
>
>  I do not understand why you would have "field people" playing around with
> hardware overlays though. Once your hardware is finalized, it should never
> change. Which is one small reason why I personally find Universal IO
> unnecessary for my own purposes.
>
> The problem I've seen with explanations, and documentation on device tree,
> is that no one explains it really well. Additionally, as a new player into
> device tree overlays. Its not clear where to get information from. See, you
> need to understand the pin-ctrl subsystem, gpio subsystem . . . list goes
> one, and on . . .A lot of this information has to be found from the Linux
> kernel source documentation.HOWEVER, you do not necessarily need to
> memorize all of this. We ( programmers ) just need a reference that does
> not goes on, and on for days about silly details we do not need to know to
> get our jobs done. Nothing like this exists.
>
> Anyway, in order to learn, you need to "do".
>
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/CALHSORrAaF4Z%2B%3DUZRq%2Bi_oMFRM_K88noC7y5D%
> 3D9MQAkeRUovrw%40mail.gmail.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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/a67232f2a5a94c10abc16cc8ff83aa
> 70%40winhexbeus11.winus.mail
> 
> .
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORr_SNNF%3DaHV-P8k0s59PM%3DUL39ZdQPgW6FtXpE7jr6FQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: [beagleboard] Re: Surefire PRU - Setup.

2017-05-20 Thread Gerald Coley 
I decided not to copy what was in the TRM into the SRM. That is why the SRM is 
specific to the BBB. And the TRM gets updated failry often by TI.

Gerald


From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of William Hermans
Sent: Saturday, May 20, 2017 8:00 PM
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] Re: Surefire PRU - Setup.

System reference manual SRM, Technical reference manual TRM.

On Sat, May 20, 2017 at 5:58 PM, William Hermans 
> wrote:
No, prior to uboot overlays, overlays were loaded from the initrd, at best. 
Also we need to understand that the board file(also an overlay of sorts - but 
required )is seperate from all this discussion.

 I do not understand why you would have "field people" playing around with 
hardware overlays though. Once your hardware is finalized, it should never 
change. Which is one small reason why I personally find Universal IO 
unnecessary for my own purposes.
The problem I've seen with explanations, and documentation on device tree, is 
that no one explains it really well. Additionally, as a new player into device 
tree overlays. Its not clear where to get information from. See, you need to 
understand the pin-ctrl subsystem, gpio subsystem . . . list goes one, and on . 
. .A lot of this information has to be found from the Linux kernel source 
documentation.HOWEVER, you do not necessarily need to memorize all of this. We 
( programmers ) just need a reference that does not goes on, and on for days 
about silly details we do not need to know to get our jobs done. Nothing like 
this exists.
Anyway, in order to learn, you need to "do".

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORrAaF4Z%2B%3DUZRq%2Bi_oMFRM_K88noC7y5D%3D9MQAkeRUovrw%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a67232f2a5a94c10abc16cc8ff83aa70%40winhexbeus11.winus.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Surefire PRU - Setup.

2017-05-20 Thread William Hermans 
System reference manual SRM, Technical reference manual TRM.

On Sat, May 20, 2017 at 5:58 PM, William Hermans  wrote:

> No, prior to uboot overlays, overlays were loaded from the initrd, at
> best. Also we need to understand that the board file(also an overlay of
> sorts - but required )is seperate from all this discussion.
>
>  I do not understand why you would have "field people" playing around with
> hardware overlays though. Once your hardware is finalized, it should never
> change. Which is one small reason why I personally find Universal IO
> unnecessary for my own purposes.
>
> The problem I've seen with explanations, and documentation on device tree,
> is that no one explains it really well. Additionally, as a new player into
> device tree overlays. Its not clear where to get information from. See, you
> need to understand the pin-ctrl subsystem, gpio subsystem . . . list goes
> one, and on . . .A lot of this information has to be found from the Linux
> kernel source documentation.HOWEVER, you do not necessarily need to
> memorize all of this. We ( programmers ) just need a reference that does
> not goes on, and on for days about silly details we do not need to know to
> get our jobs done. Nothing like this exists.
>
> Anyway, in order to learn, you need to "do".
>

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

Re: [beagleboard] Re: Surefire PRU - Setup.

2017-05-20 Thread William Hermans 
No, prior to uboot overlays, overlays were loaded from the initrd, at best.
Also we need to understand that the board file(also an overlay of sorts -
but required )is seperate from all this discussion.

 I do not understand why you would have "field people" playing around with
hardware overlays though. Once your hardware is finalized, it should never
change. Which is one small reason why I personally find Universal IO
unnecessary for my own purposes.

The problem I've seen with explanations, and documentation on device tree,
is that no one explains it really well. Additionally, as a new player into
device tree overlays. Its not clear where to get information from. See, you
need to understand the pin-ctrl subsystem, gpio subsystem . . . list goes
one, and on . . .A lot of this information has to be found from the Linux
kernel source documentation.HOWEVER, you do not necessarily need to
memorize all of this. We ( programmers ) just need a reference that does
not goes on, and on for days about silly details we do not need to know to
get our jobs done. Nothing like this exists.

Anyway, in order to learn, you need to "do".

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

Re: [beagleboard] Re: Surefire PRU - Setup.

2017-05-20 Thread ercolano7777 


On Saturday, May 20, 2017 at 4:42:46 PM UTC-7, ercola...@gmail.com wrote:
>
>
> On Thursday, May 18, 2017 at 3:58:03 PM UTC-7, William Hermans wrote:
>
>> [..]along with the TRM, or whatever documentation that makes the most 
>> sense to you. [..]
>>
>  
> For fun, I tried to determine what 0x37 means. You referred to the "TRM", 
> which I take to mean the Sitara Tech Ref Manual (rev c).. that ~2300 page 
> monster! ;) Spent a bit of time in there, but was unable to figure out 
> which table was relevant.
>

Oh, OK, I think "the TRM" must refer to this one 
 instead (I think), while 
bigger (4300 pages), it's a bit easier on my eyes, as it seems to have info 
more relevant to a software person than this other one 

 
I was looking at which seems more hardware somehow. I'm still a bit new to 
this all.

The latter was the first link google returned when searching for 
"beaglebone technical reference manual".. they call it the 'system 
technical reference manual', but seems to be a different thing.

The former also has a good description of the on-chip hardware peripherals 
(PWM, UART, etc).

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

[beagleboard] RE: [beagle-alpha] Re: Quick update regarding BeagleBone Blue documentation

2017-05-20 Thread Clark Briggs 
Jason,
I’ve been reading/lurking aka not running one.
Trouble shooting says ssh uses root and blank. I thought that was different now.
Ok, maybe that section is not in getting started. But check it.
Clark

From: beagle-al...@googlegroups.com [mailto:beagle-al...@googlegroups.com] On 
Behalf Of Jason Kridner
Sent: Friday, May 19, 2017 10:16 AM
To: James Strawson 
Cc: beagleboard@googlegroups.com
Subject: [beagle-alpha] Re: Quick update regarding BeagleBone Blue documentation

I think I've completed the getting-started portion and now need to move to 
updating bone101.

Everyone please look at 
http://jadonk.github.io/beaglebone-getting-started/START.htm and let me know if 
anything needs further adjustment on that page itself.

On Fri, May 5, 2017 at 9:11 PM James Strawson 
> wrote:
I have pinouts listed in the individual manual pages for encoders, i2c, uart, 
etc. Diagrams would be better but the info is here.

http://strawsondesign.com/#!manual-encoders
http://strawsondesign.com/#!manual-i2c
http://strawsondesign.com/#!manual-spi
http://strawsondesign.com/#!manual-uart
http://strawsondesign.com/#!manual-adc


Dept. Mechanical & Aerospace Engineering
University of California, San Diego

On Fri, May 5, 2017 at 11:19 AM, Jason Kridner 
> wrote:
I'm still not making that much headway in the Blue documentation at the moment, 
but I figure I can at least make an FAQ to help some new users.

https://github.com/beagleboard/beaglebone-blue/wiki/Frequently-Asked-Questions-(FAQ)

The big thing to point out, however, is that a ton of good documentation is 
already at http://www.strawsondesign.com/#!manual-install.

I think the big thing missing right now is a good guide for the connector 
pinouts that avoid needing to reference the schematic.

For my work-in-progress update on the getting-started page, see 
http://jadonk.github.io/beaglebone-getting-started/START.htm.

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

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

Re: [beagleboard] Re: Debian Testing (2017-04-30) U-Boot Overlays are now enabled by Default

2017-05-20 Thread fedorov . rus 
I tried to use bone-debian-8.7-lxqt-4gb-armhf-2017-03-19-4gb.img.xz and I 
had problems described here: 
https://groups.google.com/forum/#!topic/beagleboard/FasKfwC_2Z8

I get:
fatal: unable to access '
https://github.com/StrawsonDesign/Robotics_Cape_Installer.git/': Failed to 
connect to github.com port 443: Connection refused
and apt-get update does not work.

I can ping google.com.

I would appreciate any help fixing it.

On Thursday, May 18, 2017 at 3:45:56 PM UTC-7, fedor...@gmail.com wrote:
>
> Robert, thank you!
>
> I do not know why but after I upgraded U-boot to the latest version, I was 
> not able to set Ethernet connection through USB.
> I will try one more time later today.
>
> On Thursday, May 18, 2017 at 3:07:52 PM UTC-7, RobertCNelson wrote:
>>
>> On Wed, May 17, 2017 at 11:17 PM,   wrote: 
>> > Hello Everyone, 
>> > 
>> > I am not able to enable ADC overlay, I am not sure what I am doing 
>> wrong: 
>>
>> First see: 
>>
>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays 
>>
>> and verify you are running the latest version of u-boot: 
>>
>>
>> > 
>> > dtb=am335x-boneblack.dtb 
>>
>> drop this, u-boot will decide what *.dtb to use 
>>
>> > 
>> > enable_uboot_overlays=1 
>> > disable_uboot_overlays_emmc=1 
>> > disable_uboot_overlays_video=1 
>> > disable_uboot_overlays_audio=1 
>> > disable_uboot_overlays_wireless=1 
>> > #disable_uboot_overlays_adc=1 
>> > 
>> > uboot_overlay_adc=/lib/firmware/BB-ADC-00A0.dtbo 
>>
>> Drop the uboot_overlay, adc will automatically be loaded. 
>>
>> > 
>> > cmdline=coherent_pool=1M quiet 
>> > 
>> > Thank you for help! 
>>
>> Regards, 
>>
>> -- 
>> Robert Nelson 
>> https://rcn-ee.com/ 
>>
>

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

Re: [beagleboard] Re: Surefire PRU - Setup.

2017-05-20 Thread ercolano7777 

On Thursday, May 18, 2017 at 3:58:03 PM UTC-7, William Hermans wrote:
>
> So a lot of text there to "Wade" through so I'll try to answer the 
> questions you have in order. Without the "Sea of text" ;)
>

No walls of text; OK, will try to keep it shorter.

I think Universal IO, which includes the shell script config-pin is a 
> really cool tool for getting started. Especially, when all you want to do 
> is get down to writing code for the hardware. However, at the same time I 
> strongly feel that it is not a permanent solution for configuring the 
> hardware, especially for a production system. For many reasons, partly 
> because there can be some glitches, and partly because now we have uboot 
> overlays, that one can load through the second stage bootloader. Which also 
> means, for a production system you can have your pins, and hardware 
> configured exactly how it needs to be. Prior to Linux being up and running. 
> If you script config-pin, this has to be done after Linux is running.
>

Definitely going to consider those concerns, and keep an eye out for 
them in my setup.

In my case I envisioned config-pin in /etc/rc.local to run once, and be 
able to run it in real time so field personnel can change/experiment. For 
instance to make a change for a pin to have a pull-up instead of without 
one.

I read dev tree files can only be loaded on boot (?), IIRC the binary 
is loaded ahead of the kernel in ram by the boot loader, so I think dev 
cycle for dev tree files is harder for the field person, as a recompile + 
reboot is needed each time. It's hard enough getting field people to just 
edit config files.

I'd also like to avoid field people seeing two ways of doing things. 
During support calls, one could compete with the other in unpredictable 
ways.. better to provide only one way to do something.


Let's take this:
> /* P8_07 (ZCZ ball R7 ) */ 
> P8_07_default_pin: pinmux_P8_07_default_pin { 
> pinctrl-single,pins = <0x090 0x37>; }; /* Mode 7, Pull-Up, RxActive */
>
> This is just part of configuring a pin. Obviously for P8_07. So for pins 
> that can be operating in GPIO mode. This will be the first entry in any of 
> the universal io overlay files. The first line after the comment is pretty 
> much just a "#define", or a "prototype" definition of the pin in question. 
> Kind of like prototyping a function in C. The second line after the comment 
> is the actual pin information. 0x090 being the pin, which is a kernel pin 
> identifier I think. The second number 0x37 is the mux, and pullup mode( put 
> simply ). You can read the TRM and get a much better explanation of the mux 
> / pullup mode register.
>

I see -- I'll do some reading to try to figure out what actually parses 
this info on boot, as I like to understand what tool/driver is looking at 
the file I'm configuring, in case I need to RTSL to figure out what's wrong 
when errors occur. If it's a built in kernel driver (cape driver maybe?)

I did read petazzoni's "Device Tree For Dummies" last night to try to 
determine the big picture, but it really lost me somewhere in the middle. 
Just too much.. stuff.. I didn't want to know or track down. It assumes a 
knowledge of the modern kernel terminology that I just don't have.

Anyway, check this out. 
> https://github.com/beagleboard/bb.org-overlays/blob/master/include/dt-bindings/board/am335x-bbw-bbb-base.h#L17
>  
> The point here, if you #include Robert's header file, you can use all the 
> BONE_Px_xx #defines in place of the actual "kernel pin value".
>

I see, so I take it these two lines would be equivalent, the lower one 
my construction:

pinctrl-single,pins = <0x090 0x37>; }; /* Mode 7, Pull-Up, RxActive */
pinctrl-single,pins = ; }; /* Mode 7, Pull-Up, RxActive */

..yes, symbols would be better than hex.

Which can( does for me ) remove a lot of tedious work trying to memorize, 
> or digging through documentation just to get a pin to work the way you 
> want. Additionally, there is another header file, which #define mux, and 
> other register modes. These two headers alone can take a lot of learning 
> pressure off your shoulders. Then if like me, you do know C very well ( I'm 
> assuming you do ), you can read through these source header files, along 
> with the TRM, or whatever documentation that makes the most sense to you. 
> Suddenly, that light at the end of the tunnel starts to appear. Pullup 
> modes, you simply OR together ( FOO | BAR )
>
 
Yes, it'd be much easier on the eyes if 0x37 could be a few macros 
OR'ed together instead. Would those values be found in, just guessing: 
https://github.com/beagleboard/bb.org-overlays/blob/master/include/dt-bindings/pinctrl/omap.h
 
 ? (Same project, different file)

I wouldn't mind magic numbers if the reference table was in the same 
document (ascii art preferred to a link, as links go stale).

For fun, I tried to determine what 0x37 means. You referred to the 
"TRM", which I take

Re: [beagleboard] Re: os x trouble making SD image

2017-05-20 Thread Robert Nelson 
On Sat, May 20, 2017 at 10:41 AM, mron  wrote:
> Robert, Thanks. I followed the link provided. There are a lot of images. I
> think this is the one I want:
>
> Jessie Snapshot iot
>
> Flasher: (iot) (All BeagleBone Variants)
>
> Get prebuilt image:
>
> wget
> https://rcn-ee.com/rootfs/bb.org/testing/2017-05-14/iot/BBB-blank-debian-8.8-iot-armhf-2017-05-14-4gb.img.xz
>
> Is this correct? BTW. Is there a way to edit a post after it's posted?

That one will work..

Nope, google groups is both a "forum" and an "email" list..  Don't
worry about your older post.

Regards,

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

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

[beagleboard] Re: Quick update regarding BeagleBone Blue documentation

2017-05-20 Thread Mark A. Yoder 
Jason:
  Looks good.  Could you also add some "Quick Links" at the top.  I can 
think of two that would be handy (but there may be others):
192.168.7.2  main page
192.168.7.2:3000  Cloud9 IDE

I'm thinking of a workshop setting where they could be told to open 
START.html and use the quick link to Cloud9.

--Mark

On Friday, May 19, 2017 at 1:17:05 PM UTC-4, Jason Kridner wrote:
>
> I think I've completed the getting-started portion and now need to move to 
> updating bone101. 
>
> Everyone please look at 
> http://jadonk.github.io/beaglebone-getting-started/START.htm and let me 
> know if anything needs further adjustment on that page itself. 
>
> On Fri, May 5, 2017 at 9:11 PM James Strawson  > wrote:
>
>> I have pinouts listed in the individual manual pages for encoders, i2c, 
>> uart, etc. Diagrams would be better but the info is here.
>>
>> http://strawsondesign.com/#!manual-encoders
>> http://strawsondesign.com/#!manual-i2c
>> http://strawsondesign.com/#!manual-spi
>> http://strawsondesign.com/#!manual-uart
>> http://strawsondesign.com/#!manual-adc
>>
>>
>> Dept. Mechanical & Aerospace Engineering
>> University of California, San Diego
>>
>> On Fri, May 5, 2017 at 11:19 AM, Jason Kridner > > wrote:
>>
>>> I'm still not making that much headway in the Blue documentation at the 
>>> moment, but I figure I can at least make an FAQ to help some new users.
>>>
>>>
>>> https://github.com/beagleboard/beaglebone-blue/wiki/Frequently-Asked-Questions-(FAQ
>>> ) 
>>>
>>> The big thing to point out, however, is that a ton of good documentation 
>>> is already at http://www.strawsondesign.com/#!manual-install. 
>>>
>>> I think the big thing missing right now is a good guide for the 
>>> connector pinouts that avoid needing to reference the schematic.
>>>
>>> For my work-in-progress update on the getting-started page, see 
>>> http://jadonk.github.io/beaglebone-getting-started/START.htm. 
>>>
>>> Patches welcome.
>>>
>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Beagle Alpha" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to beagle-alpha...@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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1be62c41-10a2-4fce-885c-404710edfca1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: os x trouble making SD image

2017-05-20 Thread mron 
Robert, Thanks. I followed the link provided. There are a lot of images. I 
think this is the one I want:

Jessie Snapshot iotFlasher: (iot) (All BeagleBone Variants)

Get prebuilt image:

wget 
https://rcn-ee.com/rootfs/bb.org/testing/2017-05-14/iot/BBB-blank-debian-8.8-iot-armhf-2017-05-14-4gb.img.xz

Is this correct? BTW. Is there a way to edit a post after it's posted?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4ab7a906-d598-48d7-9c27-70028447cd26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: os x trouble making SD image

2017-05-20 Thread Robert Nelson 
On Sat, May 20, 2017 at 10:10 AM, mron  wrote:
> Thanks for your replies. I tried the "boot button down" in the image and it
> boots up fine. Thanks. I am now trying to flash the emac with an updated
> image. I downloaded "BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz",
> checked the shasum and dd'd as before. I inserted to the SD and held the
> "boot" button as I powered up the BBB. Booting progresses to a login prompt
> for debian, then it hangs. Here's the console log output where it hangs:
>
> INFO: task mmcqd/0:74 blocked for more than 60 seconds.
>
> [  120.533398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
> this message.
>
> [  120.541728] Kernel panic - not syncing: hung_task: blocked tasks
>
> [  120.548109] [] (unwind_backtrace+0x1/0x9c) from []
> (panic+0x59/0x158)
>
> [  120.556771] [] (panic+0x59/0x158) from []
> (watchdog+0x19d/0x1c0)
>
> [  120.564962] [] (watchdog+0x19d/0x1c0) from []
> (kthread+0x6b/0x78)
>
> [  120.573248] [] (kthread+0x6b/0x78) from []
> (ret_from_fork+0x11/0x34)
>
> [  120.581797] drm_kms_helper: panic occurred, switching back to text
> console
>
>
> I've remade the image and tried several attempts.

Those are normal on "7.5-2014-05-14"  that was over 3 years ago..

vs images from last sunday:

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

Regards,

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

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

[beagleboard] Re: os x trouble making SD image

2017-05-20 Thread mron 
Thanks for your replies. I tried the "boot button down" in the image and it 
boots up fine. Thanks. I am now trying to flash the emac with an updated 
image. I downloaded "BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz", 
checked the shasum and dd'd as before. I inserted to the SD and held the 
"boot" button as I powered up the BBB. Booting progresses to a login prompt 
for debian, then it hangs. Here's the console log output where it hangs:

INFO: task mmcqd/0:74 blocked for more than 60 seconds.

[  120.533398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

[  120.541728] Kernel panic - not syncing: hung_task: blocked tasks

[  120.548109] [] (unwind_backtrace+0x1/0x9c) from [] 
(panic+0x59/0x158)

[  120.556771] [] (panic+0x59/0x158) from [] 
(watchdog+0x19d/0x1c0)

[  120.564962] [] (watchdog+0x19d/0x1c0) from [] 
(kthread+0x6b/0x78)

[  120.573248] [] (kthread+0x6b/0x78) from [] 
(ret_from_fork+0x11/0x34)

[  120.581797] drm_kms_helper: panic occurred, switching back to text 
console

I've remade the image and tried several attempts.
Thanks for any help.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/cb9e9eae-c4c5-430c-8e22-022ab4ec7a9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] hide navigation bar

2017-05-20 Thread gdbabu Krishnan 
hi,


i am building android for beagle bone black, i want to disable the 
navigation bar on android AOSP, i am using jelly bean could you tell me how 
to do this.


thanking you

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e02233ec-acb7-465b-89fb-1d6cf51393b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: os x trouble making SD image

2017-05-20 Thread William Hermans 
I do not use OSX myself, but have reports from a coworker that dd on OSX is
somehow incompatible with these images. e.g. images made with dd in OSX
fail, but work perfectly fine when created with Linux dd.

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