Re: [beagleboard] Re: Applying voltage to I/O pins when unpowered

[James Lim]

Thanks for the inputs! I will check out the AM3358 datasheet for more 
information.

James

On Tuesday, May 27, 2014 8:51:57 PM UTC+6, Gerald wrote:
>
> No, it has protection on it. It is not on the expansion headers.
>
> Gerald
>
>
>
> On Tue, May 27, 2014 at 9:45 AM, DLF > 
> wrote:
>
>> Hello Gerald
>>
>> Is the serial debug header included in the scope of the "expansion 
>> headers"?  
>>
>> The reason I ask is that last week I was mucking about with my serial 
>> debug cable and I was wondering if I follow the SRM, how can I capture the 
>> debug/bootup info via putty/serial connection if the BBB isn't connected 
>> (via usb to my computer) before the BBB is powered up?
>>
>> Once again many thanks for all your efforts here.  I do enjoy learning* 
>> with my BBB
>>
>> DLF
>>
>> * last night I burt my finger because my temperture sensor was plugged in 
>> backwards   what a great learning experinece ;)
>>  
>> -- 
>> 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.

[beagleboard] apt-get upgrade crashes beagle bone black (shuts down)

[Eric Fort]

I just flashed my beagle bone black with
images_BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img after verifying the
md5sum and aot-get update.  when I issue apt-get upgrade the board
initially looks to be properly processing the download and install of files
then shuts downmight there be a problem with the image?  If not, what else
could be going wrong?

Eric

-- 
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] The CryptoCape is now available at SparkFun Electronics

[Mike]

On 05/29/2014 10:01 PM, Eric Fort wrote:
Are you guys talking about the crypto cape or the RTC cape?  The 
crypto capediscussed in this thread uses a ds3231 not a ds1307.  Also 
why anyone *needs* the rtc cape I don't get.  just keep the rtc rail 
powered on the processor.  That I believe is a software issue.


Eric



The Cryptocape RTC is what I was specifically asking about.  The ds1307 
modules handles several rtc chips.


enum ds_type {
ds_1307,
ds_1337,
ds_1338,
ds_1339,
ds_1340,
ds_1388,
ds_3231,
m41t00,
mcp7941x,
rx_8025,
last_ds_type /* always last */
/* rs5c372 too?  different address... */
};

I'd be happy to pursue keeping the rtc rail powered.  I have no clue 
where this is or would be handled in software.  I'm far from being any 
kind of good programmer, and know far to little about hardware at this 
level.  Just a long time sys admin willing to learn it if pointed in the 
right direction.


Mike


On Thu, May 29, 2014 at 6:31 PM, Joshua Datko > wrote:


The RTC uses the ds1307 kernel driver and you're correct, it shows
up as rtc1. It is loaded when the capemgr instantiates the device
tree, since the driver is in the CryptoCape DTS file. So you
shouldn't need any init.d/systemd scripting it should "just work"TM.

You'll have to set the clock once and then it should hold pretty
well. In testing think I had a bum battery b/c it depleted rather
quickly. Once I changed batteries it seems to be holding steady.


On Thu, May 29, 2014 at 7:28 PM, Mike mailto:bellyac...@gmail.com>> wrote:

On 05/29/2014 07:17 PM, Joshua Datko wrote:

The CryptoCape, a collaboration between SparkFun and
myself, is now available for purchase at SparkFun
Electronics [1]. In short, the cape adds some hardware
crypto chips, a RTC with battery, and an ATmega328p which
is designed to be flashed from the Beagle. It will be
officially announced on the "new products Friday" post
tomorrow, but I think this group deserved an early
announcement.

Thanks to BeagleBoard.org for making a great platform and
special thanks to Robert Nelson for backporting the TPM
driver to 3.8.

This community is awesome; I've learned so much by
following this list. Thanks to everyone who shares their
time and knowledge.

There's only 1 left :)

Happy Hacking!

Josh

[1] https://www.sparkfun.com/products/12773

How is the RTC implemented at the software level?  More to the
point perhaps, how early in the boot process does the system
time get set from (presumably) rtc1?

About a month or so ago I setup a battery backed RTC, along
with a fairly current systemd.  Systemd have chosen to rewrite
hwclock and last I looked it still only honored/used rtc0.
 Perhaps I didn't explain the situation good enough on the
systemd mailing list, but I couldn't seem to get past anyone
not understanding why a board wouldn't have a battery backed
RTC on board.  Having said all that I did get it working just
using init.d scripts.  Just seems like such an ugly hack when
the whole point of systemd is to essential do away with all
the scripts.

The board looks like something very interesting to explore.
 I'm sure one will find its' way here when cash flow permits.

Mike


-- 
For more options, visit http://beagleboard.org/discuss

--- You received this message because you are subscribed to a
topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/beagleboard/NhMSP9ywlzg/unsubscribe.
To unsubscribe from this group and all its topics, send an
email to beagleboard+unsubscr...@googlegroups.com
.

For more options, visit https://groups.google.com/d/optout.


-- 
For more options, visit http://beagleboard.org/discuss

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


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

Re: [beagleboard] The CryptoCape is now available at SparkFun Electronics

[Joshua Datko]

Eric,

You are correct, the CryptoCape has the DS3231. However, it use accessed
via software via the ds1037 kernel driver. That driver is compatible with
the 3231: http://lxr.free-electrons.com/source/drivers/rtc/rtc-ds1307.c,
line 36. I haven't tried any of the other features like the Time of Day
alarm so I'm not sure if that's supported with this driver.

I put the battery on the CryptoCape so that the RTC will maintain time [1]
when the cryptocape is physically removed from the Beagle and [2] when the
Beagle is not connected to power.

Thanks for the questions!


On Thu, May 29, 2014 at 8:01 PM, Eric Fort  wrote:

> Are you guys talking about the crypto cape or the RTC cape?  The crypto
> capediscussed in this thread uses a ds3231 not a ds1307.  Also why anyone
> *needs* the rtc cape I don't get.  just keep the rtc rail powered on the
> processor.  That I believe is a software issue.
>
> Eric
>
>
> On Thu, May 29, 2014 at 6:31 PM, Joshua Datko  wrote:
>
>> The RTC uses the ds1307 kernel driver and you're correct, it shows up as
>> rtc1. It is loaded when the capemgr instantiates the device tree, since the
>> driver is in the CryptoCape DTS file. So you shouldn't need any
>> init.d/systemd scripting it should "just work"TM.
>>
>> You'll have to set the clock once and then it should hold pretty well. In
>> testing think I had a bum battery b/c it depleted rather quickly. Once I
>> changed batteries it seems to be holding steady.
>>
>>
>> On Thu, May 29, 2014 at 7:28 PM, Mike  wrote:
>>
>>> On 05/29/2014 07:17 PM, Joshua Datko wrote:
>>>
 The CryptoCape, a collaboration between SparkFun and myself, is now
 available for purchase at SparkFun Electronics [1]. In short, the cape adds
 some hardware crypto chips, a RTC with battery, and an ATmega328p which is
 designed to be flashed from the Beagle. It will be officially announced on
 the "new products Friday" post tomorrow, but I think this group deserved an
 early announcement.

 Thanks to BeagleBoard.org for making a great platform and special
 thanks to Robert Nelson for backporting the TPM driver to 3.8.

 This community is awesome; I've learned so much by following this list.
 Thanks to everyone who shares their time and knowledge.

 There's only 1 left :)

 Happy Hacking!

 Josh

 [1] https://www.sparkfun.com/products/12773

  How is the RTC implemented at the software level?  More to the point
>>> perhaps, how early in the boot process does the system time get set from
>>> (presumably) rtc1?
>>>
>>> About a month or so ago I setup a battery backed RTC, along with a
>>> fairly current systemd.  Systemd have chosen to rewrite hwclock and last I
>>> looked it still only honored/used rtc0.  Perhaps I didn't explain the
>>> situation good enough on the systemd mailing list, but I couldn't seem to
>>> get past anyone not understanding why a board wouldn't have a battery
>>> backed RTC on board.  Having said all that I did get it working just using
>>> init.d scripts.  Just seems like such an ugly hack when the whole point of
>>> systemd is to essential do away with all the scripts.
>>>
>>> The board looks like something very interesting to explore.  I'm sure
>>> one will find its' way here when cash flow permits.
>>>
>>> Mike
>>>
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> --- You received this message because you are subscribed to a topic in
>>> the Google Groups "BeagleBoard" group.
>>> To unsubscribe from this topic, visit https://groups.google.com/d/
>>> topic/beagleboard/NhMSP9ywlzg/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> beagleboard+unsubscr...@googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/NhMSP9ywlzg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] The CryptoCape is now available at SparkFun Electronics

[Eric Fort]

Are you guys talking about the crypto cape or the RTC cape?  The crypto
capediscussed in this thread uses a ds3231 not a ds1307.  Also why anyone
*needs* the rtc cape I don't get.  just keep the rtc rail powered on the
processor.  That I believe is a software issue.

Eric


On Thu, May 29, 2014 at 6:31 PM, Joshua Datko  wrote:

> The RTC uses the ds1307 kernel driver and you're correct, it shows up as
> rtc1. It is loaded when the capemgr instantiates the device tree, since the
> driver is in the CryptoCape DTS file. So you shouldn't need any
> init.d/systemd scripting it should "just work"TM.
>
> You'll have to set the clock once and then it should hold pretty well. In
> testing think I had a bum battery b/c it depleted rather quickly. Once I
> changed batteries it seems to be holding steady.
>
>
> On Thu, May 29, 2014 at 7:28 PM, Mike  wrote:
>
>> On 05/29/2014 07:17 PM, Joshua Datko wrote:
>>
>>> The CryptoCape, a collaboration between SparkFun and myself, is now
>>> available for purchase at SparkFun Electronics [1]. In short, the cape adds
>>> some hardware crypto chips, a RTC with battery, and an ATmega328p which is
>>> designed to be flashed from the Beagle. It will be officially announced on
>>> the "new products Friday" post tomorrow, but I think this group deserved an
>>> early announcement.
>>>
>>> Thanks to BeagleBoard.org for making a great platform and special thanks
>>> to Robert Nelson for backporting the TPM driver to 3.8.
>>>
>>> This community is awesome; I've learned so much by following this list.
>>> Thanks to everyone who shares their time and knowledge.
>>>
>>> There's only 1 left :)
>>>
>>> Happy Hacking!
>>>
>>> Josh
>>>
>>> [1] https://www.sparkfun.com/products/12773
>>>
>>>  How is the RTC implemented at the software level?  More to the point
>> perhaps, how early in the boot process does the system time get set from
>> (presumably) rtc1?
>>
>> About a month or so ago I setup a battery backed RTC, along with a fairly
>> current systemd.  Systemd have chosen to rewrite hwclock and last I looked
>> it still only honored/used rtc0.  Perhaps I didn't explain the situation
>> good enough on the systemd mailing list, but I couldn't seem to get past
>> anyone not understanding why a board wouldn't have a battery backed RTC on
>> board.  Having said all that I did get it working just using init.d
>> scripts.  Just seems like such an ugly hack when the whole point of systemd
>> is to essential do away with all the scripts.
>>
>> The board looks like something very interesting to explore.  I'm sure one
>> will find its' way here when cash flow permits.
>>
>> Mike
>>
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> --- You received this message because you are subscribed to a topic in
>> the Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/
>> topic/beagleboard/NhMSP9ywlzg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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] The CryptoCape is now available at SparkFun Electronics

[Mike]

On 05/29/2014 09:31 PM, Joshua Datko wrote:
The RTC uses the ds1307 kernel driver and you're correct, it shows up 
as rtc1. It is loaded when the capemgr instantiates the device tree, 
since the driver is in the CryptoCape DTS file. So you shouldn't need 
any init.d/systemd scripting it should "just work"TM.


Yes, this is nearly identical to the setup I did.  Created a dto for the 
ds1307, loaded it at boot, all good.  The device is there, it has very 
good time.  The system still needs to be told to *use* that time.


If memory serves Robert updates a time value that gets loaded so if your 
on a fairly current image your time is somewhat current.


I'll be more than happy to RTFM, or experiment if pointed in the right 
direction.  I've not seen any indication that simply adding a battery 
backed RTC, loading it via capemgr will cause the system (kernel) to use 
that device for obtaining a somewhat sane time value.


Mike
You'll have to set the clock once and then it should hold pretty well. 
In testing think I had a bum battery b/c it depleted rather quickly. 
Once I changed batteries it seems to be holding steady.



On Thu, May 29, 2014 at 7:28 PM, Mike > wrote:


On 05/29/2014 07:17 PM, Joshua Datko wrote:

The CryptoCape, a collaboration between SparkFun and myself,
is now available for purchase at SparkFun Electronics [1]. In
short, the cape adds some hardware crypto chips, a RTC with
battery, and an ATmega328p which is designed to be flashed
from the Beagle. It will be officially announced on the "new
products Friday" post tomorrow, but I think this group
deserved an early announcement.

Thanks to BeagleBoard.org for making a great platform and
special thanks to Robert Nelson for backporting the TPM driver
to 3.8.

This community is awesome; I've learned so much by following
this list. Thanks to everyone who shares their time and knowledge.

There's only 1 left :)

Happy Hacking!

Josh

[1] https://www.sparkfun.com/products/12773

How is the RTC implemented at the software level?  More to the
point perhaps, how early in the boot process does the system time
get set from (presumably) rtc1?

About a month or so ago I setup a battery backed RTC, along with a
fairly current systemd.  Systemd have chosen to rewrite hwclock
and last I looked it still only honored/used rtc0.  Perhaps I
didn't explain the situation good enough on the systemd mailing
list, but I couldn't seem to get past anyone not understanding why
a board wouldn't have a battery backed RTC on board.  Having said
all that I did get it working just using init.d scripts.  Just
seems like such an ugly hack when the whole point of systemd is to
essential do away with all the scripts.

The board looks like something very interesting to explore.  I'm
sure one will find its' way here when cash flow permits.

Mike


-- 
For more options, visit http://beagleboard.org/discuss

--- You received this message because you are subscribed to a
topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/beagleboard/NhMSP9ywlzg/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to beagleboard+unsubscr...@googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.


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

For more options, visit https://groups.google.com/d/optout.


--
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] The CryptoCape is now available at SparkFun Electronics

[Joshua Datko]

The RTC uses the ds1307 kernel driver and you're correct, it shows up as
rtc1. It is loaded when the capemgr instantiates the device tree, since the
driver is in the CryptoCape DTS file. So you shouldn't need any
init.d/systemd scripting it should "just work"TM.

You'll have to set the clock once and then it should hold pretty well. In
testing think I had a bum battery b/c it depleted rather quickly. Once I
changed batteries it seems to be holding steady.


On Thu, May 29, 2014 at 7:28 PM, Mike  wrote:

> On 05/29/2014 07:17 PM, Joshua Datko wrote:
>
>> The CryptoCape, a collaboration between SparkFun and myself, is now
>> available for purchase at SparkFun Electronics [1]. In short, the cape adds
>> some hardware crypto chips, a RTC with battery, and an ATmega328p which is
>> designed to be flashed from the Beagle. It will be officially announced on
>> the "new products Friday" post tomorrow, but I think this group deserved an
>> early announcement.
>>
>> Thanks to BeagleBoard.org for making a great platform and special thanks
>> to Robert Nelson for backporting the TPM driver to 3.8.
>>
>> This community is awesome; I've learned so much by following this list.
>> Thanks to everyone who shares their time and knowledge.
>>
>> There's only 1 left :)
>>
>> Happy Hacking!
>>
>> Josh
>>
>> [1] https://www.sparkfun.com/products/12773
>>
>>  How is the RTC implemented at the software level?  More to the point
> perhaps, how early in the boot process does the system time get set from
> (presumably) rtc1?
>
> About a month or so ago I setup a battery backed RTC, along with a fairly
> current systemd.  Systemd have chosen to rewrite hwclock and last I looked
> it still only honored/used rtc0.  Perhaps I didn't explain the situation
> good enough on the systemd mailing list, but I couldn't seem to get past
> anyone not understanding why a board wouldn't have a battery backed RTC on
> board.  Having said all that I did get it working just using init.d
> scripts.  Just seems like such an ugly hack when the whole point of systemd
> is to essential do away with all the scripts.
>
> The board looks like something very interesting to explore.  I'm sure one
> will find its' way here when cash flow permits.
>
> Mike
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> --- You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/beagleboard/NhMSP9ywlzg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] The CryptoCape is now available at SparkFun Electronics

[Mike]

On 05/29/2014 07:17 PM, Joshua Datko wrote:
The CryptoCape, a collaboration between SparkFun and myself, is now 
available for purchase at SparkFun Electronics [1]. In short, the cape 
adds some hardware crypto chips, a RTC with battery, and an ATmega328p 
which is designed to be flashed from the Beagle. It will be officially 
announced on the "new products Friday" post tomorrow, but I think this 
group deserved an early announcement.


Thanks to BeagleBoard.org for making a great platform and special 
thanks to Robert Nelson for backporting the TPM driver to 3.8.


This community is awesome; I've learned so much by following this 
list. Thanks to everyone who shares their time and knowledge.


There's only 1 left :)

Happy Hacking!

Josh

[1] https://www.sparkfun.com/products/12773

How is the RTC implemented at the software level?  More to the point 
perhaps, how early in the boot process does the system time get set from 
(presumably) rtc1?


About a month or so ago I setup a battery backed RTC, along with a 
fairly current systemd.  Systemd have chosen to rewrite hwclock and last 
I looked it still only honored/used rtc0.  Perhaps I didn't explain the 
situation good enough on the systemd mailing list, but I couldn't seem 
to get past anyone not understanding why a board wouldn't have a battery 
backed RTC on board.  Having said all that I did get it working just 
using init.d scripts.  Just seems like such an ugly hack when the whole 
point of systemd is to essential do away with all the scripts.


The board looks like something very interesting to explore.  I'm sure 
one will find its' way here when cash flow permits.


Mike

--
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] The CryptoCape is now available at SparkFun Electronics

[Eric Fort]

yes, yes, it may have been posted in 2 places.  If you'd like to see
the revised board files I'll pass them along.  It took all of 5 minutes in
eagle to make the update and add 2 more 3 way solder jumpers (or change
them to header type jumpers for ease of end user configurability for
slightly increased parts cost  thinking I'll go back and add both in
parallel and the header version can remain unpopulated or filled later at
user descretion.

Eric


On Thu, May 29, 2014 at 6:05 PM, Joshua Datko  wrote:

> Hey Eric, thanks for the question, where did I read that before ;)
>
> Thanks for the recommendation, I'll look into the bus select option.
>
> The goal of this board is not to provide cryptographic acceleration,
> because you are correct, the AM335x does have accelerators already (drivers
> in 3.13). The purpose rather, is to provide key isolation. So the
> RSA/ECC/MAC keys stay in the respective chips. For ECDSA for example, the
> private key never leaves the chip. In the AM335x case, you'd have to
> provide the key somehow in software.
>
> Also, the AM335x doesn't have any asymmetric crypto options. The TPM
> provides RSA-2048 and the ECC108: ECDSA with three NIST curves.
>
>
>  On Thu, May 29, 2014 at 6:52 PM, Eric Fort  wrote:
>
>>  ok, the data interface for all these chips sits in the i2c bus, so it
>> looks like for much real encryption work this cape will be really slow,
>> bottle necked and constrained by the chosen bus and it's bandwidth.  I
>> might also suggest for a rev 2 adding a set of 3 way jumpers such that it
>> can sit on either i2c1 or i2c2. the inclusion of solder jumpers for pullups
>> or not on the i2c bus was a good choice.  I also fail to see what this cape
>> does or assists with that the AM3358/AM3359 does not already do with it's
>> on board cryptographic abilities  which do at a minimum AES, SHA, & MD5,
>> and possibly others.
>>
>> Eric
>>
>>
>> On Thu, May 29, 2014 at 4:17 PM, Joshua Datko  wrote:
>>
>>> The CryptoCape, a collaboration between SparkFun and myself, is now
>>> available for purchase at SparkFun Electronics [1]. In short, the cape adds
>>> some hardware crypto chips, a RTC with battery, and an ATmega328p which is
>>> designed to be flashed from the Beagle. It will be officially announced on
>>> the "new products Friday" post tomorrow, but I think this group deserved an
>>> early announcement.
>>>
>>> Thanks to BeagleBoard.org for making a great platform and special thanks
>>> to Robert Nelson for backporting the TPM driver to 3.8.
>>>
>>> This community is awesome; I've learned so much by following this list.
>>> Thanks to everyone who shares their time and knowledge.
>>>
>>> There's only 1 left :)
>>>
>>> Happy Hacking!
>>>
>>> Josh
>>>
>>> [1] https://www.sparkfun.com/products/12773
>>>
>>> --
>>> 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 a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/NhMSP9ywlzg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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] The CryptoCape is now available at SparkFun Electronics

[Joshua Datko]

Hey Eric, thanks for the question, where did I read that before ;)

Thanks for the recommendation, I’ll look into the bus select option.

The goal of this board is not to provide cryptographic acceleration,
because you are correct, the AM335x does have accelerators already (drivers
in 3.13). The purpose rather, is to provide key isolation. So the
RSA/ECC/MAC keys stay in the respective chips. For ECDSA for example, the
private key never leaves the chip. In the AM335x case, you’d have to
provide the key somehow in software.

Also, the AM335x doesn’t have any asymmetric crypto options. The TPM
provides RSA-2048 and the ECC108: ECDSA with three NIST curves.


On Thu, May 29, 2014 at 6:52 PM, Eric Fort  wrote:

> ok, the data interface for all these chips sits in the i2c bus, so it
> looks like for much real encryption work this cape will be really slow,
> bottle necked and constrained by the chosen bus and it's bandwidth.  I
> might also suggest for a rev 2 adding a set of 3 way jumpers such that it
> can sit on either i2c1 or i2c2. the inclusion of solder jumpers for pullups
> or not on the i2c bus was a good choice.  I also fail to see what this cape
> does or assists with that the AM3358/AM3359 does not already do with it's
> on board cryptographic abilities  which do at a minimum AES, SHA, & MD5,
> and possibly others.
>
> Eric
>
>
> On Thu, May 29, 2014 at 4:17 PM, Joshua Datko  wrote:
>
>> The CryptoCape, a collaboration between SparkFun and myself, is now
>> available for purchase at SparkFun Electronics [1]. In short, the cape adds
>> some hardware crypto chips, a RTC with battery, and an ATmega328p which is
>> designed to be flashed from the Beagle. It will be officially announced on
>> the "new products Friday" post tomorrow, but I think this group deserved an
>> early announcement.
>>
>> Thanks to BeagleBoard.org for making a great platform and special thanks
>> to Robert Nelson for backporting the TPM driver to 3.8.
>>
>> This community is awesome; I've learned so much by following this list.
>> Thanks to everyone who shares their time and knowledge.
>>
>> There's only 1 left :)
>>
>> Happy Hacking!
>>
>> Josh
>>
>> [1] https://www.sparkfun.com/products/12773
>>
>> --
>> 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/NhMSP9ywlzg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] The CryptoCape is now available at SparkFun Electronics

[Eric Fort]

ok, the data interface for all these chips sits in the i2c bus, so it looks
like for much real encryption work this cape will be really slow, bottle
necked and constrained by the chosen bus and it's bandwidth.  I might also
suggest for a rev 2 adding a set of 3 way jumpers such that it can sit on
either i2c1 or i2c2. the inclusion of solder jumpers for pullups or not on
the i2c bus was a good choice.  I also fail to see what this cape does or
assists with that the AM3358/AM3359 does not already do with it's on board
cryptographic abilities  which do at a minimum AES, SHA, & MD5, and
possibly others.

Eric


On Thu, May 29, 2014 at 4:17 PM, Joshua Datko  wrote:

> The CryptoCape, a collaboration between SparkFun and myself, is now
> available for purchase at SparkFun Electronics [1]. In short, the cape adds
> some hardware crypto chips, a RTC with battery, and an ATmega328p which is
> designed to be flashed from the Beagle. It will be officially announced on
> the "new products Friday" post tomorrow, but I think this group deserved an
> early announcement.
>
> Thanks to BeagleBoard.org for making a great platform and special thanks
> to Robert Nelson for backporting the TPM driver to 3.8.
>
> This community is awesome; I've learned so much by following this list.
> Thanks to everyone who shares their time and knowledge.
>
> There's only 1 left :)
>
> Happy Hacking!
>
> Josh
>
> [1] https://www.sparkfun.com/products/12773
>
> --
> 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] Announce: Flasher Changes

[Eric Fort]

It would seem that a piece of "official" documentation ought to be updated
then.   As of 5:21pm Pacific time on 29MAY2014
http://beagleboard.org/Getting%20Started#update still reflects the old
pattern.  I'd propose the following sentence be added, "flasher images
dated after  automatically power down the board upon
completion, thus all 4 USRx LEDs will be off."

Eric


On Fri, May 16, 2014 at 7:53 AM, Robert Nelson 
wrote:

> So while debugging an issue with the "flasher" script when flashing a
> large number of boards. We are yanking power when all 4 led's are on. It
> seems to reason, eventually the "flashing" microSD might just get corrupt.
>
> So in the interest of making the "flashing" microSD more reliable and of
> course to mess up every single new user, as every existing blogs/wiki/etc
> everywhere will now be wrong.
>
> The "flashing" is now done when all 4 led's are off. (As the board has
> physically been shutdown by the script.)
>
> * Of course, some os's like ubuntu 14.04 like to just randomly crash when
> shutting down with our v3.8.x kernel, so while it "halted*" all 4 led's are
> sometimes still on.
>
> ubuntu 14.04: (it shut down, but randomly the 4 led's are still on)
> [  100.173493] (NULL device *): gadget not registered.
> [  100.187875] System halted
>
> * Whereas Debian Wheezy it works just fine.. ;)
>
> So back to your regularly scheduled hacking time!
>
> 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] Announce: Flasher Changes

[Eric Fort]

On Sun, May 18, 2014 at 1:19 PM, Robert Nelson 
wrote:

>
>
>
> On Fri, May 16, 2014 at 7:24 PM, Eric Fort  wrote:
>
>> As an alternative or maybe in conjunction you could have the 4 LED's
>> blink together in the following order:
>> 000111010100011101110111000111010001 (DONE) with a bit duration
>> somewhere between 250 & 62.5 milliseconds, 1 representing on, and 0
>> representing off and the string repeating a number of times prior to off or
>> infinitely.  come to think of this, have the script as it's final task
>> compute an MD5 or similar checksum on what was just written to verify a
>> proper write and on success start flashing the above sequence.  if
>> somewhere along the process something went wrong causing it to exit, halt,
>> or otherwise not obtain success it could blink
>> 00010101110100010111000101000101110101 (FAIL) using the same timing as
>> above.  Just a thought
>>
>
> It would be cooler if it did the cylon back n forth while flashing..
>
>
Yes, but the morse sequence actually conveys something meaningful (an exit
code of sorts) kinda like the audio post codes of old in the pc world.
This eliminates the need for a serial console when flashing.

Eric


> 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: The CryptoCape is now available at SparkFun Electronics

[Joshua Datko]

It's a cape that has the following security ICs on the Beagle's i2c2 bus:

- Atmel TPM (RSA 2048)
- Atmel ATSHA204 (SHA/HMAC256)
- Atmel ATECC108 (ECDSA)
- Atmel ATAES132 (AES-128-CCM)

Plus an EEPROM and a 5pmm RTC.

It also contains an ATmega328p, which is loaded with the 3.3V pro mini
bootloader. The ATmega is also connected on the i2c2 bus so the Beagle and
the 328p can communicate over i2c.

Also, you can upload sketches from the Beagle's UART4 to flash the ATmega.

The SparkFun product page is here, with a hookup guide:
https://www.sparkfun.com/products/12773

The eLinux page is here: http://elinux.org/Cryptotronix:CryptoCape

The SparkFun page talks about each IC in more detail.

Josh


On Thu, May 29, 2014 at 5:23 PM, rh_  wrote:

> On Thu, 29 May 2014 16:17:53 -0700 (PDT)
> Joshua Datko  wrote:
>
> > The CryptoCape, a collaboration between SparkFun and myself, is now
> > available for purchase at SparkFun Electronics [1]. In short, the
> > cape adds some hardware crypto chips, a RTC with battery, and an
> > ATmega328p which is designed to be flashed from the Beagle. It will
> > be officially announced on the "new products Friday" post tomorrow,
> > but I think this group deserved an early announcement.
>
> What is it?
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/NhMSP9ywlzg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] Using GPIO

[Mike]

>
> Fair enough:
>
> beaglebone:~# config-pin -q p9.18
> P9_18 Mode: gpio Direction: out Value: 1
>  
> Did some probing on the hardware and it looks fine. Guess I was having 
> another issue.
>
> I am using the pre-loaded cape-universal in 3.8.13 bone50 release and 
although I can execute:
config-pin -l P9_21

the command
config-pin -q P9_21
gives me:

*cape-universal overlay not foundrun "config-pin overlay cape-universal" to 
load the cape*
But running that changes nothing - still get same thing.

-- 
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] The CryptoCape is now available at SparkFun Electronics

[Joshua Datko]

The CryptoCape, a collaboration between SparkFun and myself, is now 
available for purchase at SparkFun Electronics [1]. In short, the cape adds 
some hardware crypto chips, a RTC with battery, and an ATmega328p which is 
designed to be flashed from the Beagle. It will be officially announced on 
the "new products Friday" post tomorrow, but I think this group deserved an 
early announcement.

Thanks to BeagleBoard.org for making a great platform and special thanks to 
Robert Nelson for backporting the TPM driver to 3.8. 

This community is awesome; I've learned so much by following this list. 
Thanks to everyone who shares their time and knowledge.

There's only 1 left :)

Happy Hacking!

Josh

[1] https://www.sparkfun.com/products/12773

-- 
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: CapeMgr in 3.13?

[Mike]

It looks like in 3.8.13 bone50 Charles Steinkuehler's cape-universal is 
pre-loaded, so yes I'll nail my config based on it for the life of the 
project.

-- 
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: BeagleBone Enhanced

[William Hermans]

>
> *Our board had only one Ethernet connector, but a board with two that one
> could program as a router/firewall might be interesting.*


Indeed. I was thinking this myself, but also as something that could be
placed inline for networking traffic monitoring / filtering.


On Thu, May 29, 2014 at 3:11 PM,  wrote:

> FYI, we made a board for a special project with a Gigabit Ethernet PHY,and
> it works pretty well, getting about 300MB throughput. We've also made
> boards with Bluetooth. It's a very flexible platform and seems to play
> pretty well with other hardware. Our board had only one Ethernet connector,
> but a board with two that one could program as a router/firewall might be
> interesting.
>
>
> On Monday, May 26, 2014 4:33:30 AM UTC-7, asan...@gmail.com wrote:
>>
>> Hi All
>>
>> We are thinking of doing a BeagleBone compatible board with some enhanced
>> features. Rather than guess at what people want we would like your input,
>> what extra interfaces or devices would you like on the board?
>>
>> Either us the link to the form below or post in the thread.
>>
>> BB Enhanced 
>> form
>>
>> Personally I would like extra USB ports (with one on a header to
>> connector to a cape) and maybe 1GByte of RAM.
>>
>> David
>> SanCloud
>>
>  --
> 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: BeagleBone Enhanced

[lee]

FYI, we made a board for a special project with a Gigabit Ethernet PHY,and 
it works pretty well, getting about 300MB throughput. We've also made 
boards with Bluetooth. It's a very flexible platform and seems to play 
pretty well with other hardware. Our board had only one Ethernet connector, 
but a board with two that one could program as a router/firewall might be 
interesting.


On Monday, May 26, 2014 4:33:30 AM UTC-7, asan...@gmail.com wrote:
>
> Hi All
>
> We are thinking of doing a BeagleBone compatible board with some enhanced 
> features. Rather than guess at what people want we would like your input, 
> what extra interfaces or devices would you like on the board?
>
> Either us the link to the form below or post in the thread.
>
> BB Enhanced form 
> 
>
> Personally I would like extra USB ports (with one on a header to connector 
> to a cape) and maybe 1GByte of RAM.
>
> David
> SanCloud
>

-- 
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: 3 proposed patches for next 3.8.13-bone5x update

[Scott Michel]

Wow. That was fast. My e-mail is in the patches, so... I'm sure the bug 
reports will trickle in...


-scooter

On Thursday, May 29, 2014 1:58:05 PM UTC-7, RobertCNelson wrote:
>
> On Thu, May 29, 2014 at 2:32 PM, Scott Michel  > wrote: 
> > I've attached three patches for consideration in the Robert Nelson's 
> > 3.8.13-bone5x update, all of which are independent of each other (i.e., 
> you 
> > can patch your kernel with any one of them, separate from the others): 
> > 
> > 0001-am335x-features 
> > 
> > Detect AM335x-specific features and CPU version. Doesn't do anything 
> > significant, other than accurately report the CPU and SGX, L2 cache 
> presence 
> > in the bootup dmesg output. 
> > 
> > 
> > 0002-element14-bb-view-lcd-capes 
> > 
> >  Add Element14's "BB-VIEW" LCD cape device trees to firmware/capes. 
> > 
> > 
> > 0003-sitara_rb_swap_workaround 
> > 
> > Create a workaround to the TI Sitara red/blue swap erratum through 
> device 
> > tree properties, 'bgrx_16bpp' and 'bgrx_24bpp'. The 'bgrx_16bpp' 
> property 
> > swaps red and blue if 16bpp color depth is used and the LCD cape itself 
> > swaps red and blue at higher color depths (i.e., the cape designer 
> "fixed" 
> > the problem by swapping signals). The 'bgrx_24bpp' property swaps red 
> and 
> > blue at the 24bpp color depth, which addresses TI's erratum. 
> > 
> > 
> > Also, the tilcdc LCD driver queries the panel's panel-info/bpp device 
> tree 
> > property to find the preferred BPP when initializing the console 
> > framebuffer. This was originally hardcoded into the driver at 16bpp. If 
> the 
> > panel says that it wants 32bpp, the framebuffer initializes to a 
> preferred 
> > 32bpp. 
> > 
> > 
> > I've been testing these changes relative to Robert's linux-dev 
> 3.8.15-bone53 
> > tag. They may apply cleanly against earlier tags, but I can't guarantee 
> they 
> > will. 
> > 
> > I'm sure I have canonical kernel source formatting issues; comments, 
> testing 
> > and suggestions are welcome (and advocacy for inclusion in Robert's 
> > linux-dev git repo also helpful.) 
>
> Thanks!  They are all queue'd up: 
>
>
> https://github.com/RobertCNelson/bb-kernel/commit/5e50ae5c219b52bf70193bffdef7c07c8b26b90f
>  
>
> Just have to run a few checks on the lcd3/lcd7 as this did revert the 
> custom touchscreen filtering. 
>
> I'm "pretty" sure we fixed the adc issue in: 
>
> https://github.com/RobertCNelson/bb-kernel/commit/3a66618d3bbd86a4e7655e07bc48838fb967d5ed
>  
>
> So it shouldn't be needed anymore now.. 
>
> 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: Best way to connect to Arduino via serial?

[PLyttle]

the 7-12 volt is the 'raw' power spec. This is converted to 5volt on the 
board. This is normally the main system power.
When you connect 3v3 to the VCC pin the board runs at 3v3. Technically the 
AVR chip is overclocked at this voltage, but I never have seen an arduino 
fail doing this. 

Try it, what can you lose? You make your system a whole lot simpler, using 
only 3 volt logic.

LP

On Thursday, May 29, 2014 9:51:36 PM UTC+2, myersco...@gmail.com wrote:
>
> Cool. Would something like this work? I was looking for a thru-hole 
> equivalent since I'm not good enough at soldering to try surface-mount yet 
> :)
>
> http://www.digikey.com/product-detail/en/SN74LV125AN/296-34037-5-ND/1594902
>
>
>
> LP - I don't think that my Arduino can run at 3v3; the specs say that it 
> can run between 7-12v and has a 5v operating voltage. Thanks though :)
>

-- 
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] Using Beagle board to get RSSI of a device

[Robert Nelson]

On Thu, May 29, 2014 at 2:51 AM,   wrote:
> Hi Richard,
>
> Thanks for your reply. I am not quite sure how to find out the driver for
> TL-WN722n on our ubuntu systems.  We didn't have to actually install any
> driver on the beagle board (running Ubuntu 12.04 LTS omap) or the stand
> alone PC (Ubuntu 12.04) for our project. Can you assist in helping out to
> find the driver version for TL-WN722n wireless adapter to see if that is the
> reason.

Well... "uname -r" for both is a start.

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] Using Beagle board to get RSSI of a device

[Przemek Klosowski]

On Thu, May 29, 2014 at 3:51 AM,   wrote:
> Hi Richard,
>
> Thanks for your reply. I am not quite sure how to find out the driver for
> TL-WN722n on our ubuntu systems.  We didn't have to actually install any
> driver on the beagle board (running Ubuntu 12.04 LTS omap) or the stand
> alone PC (Ubuntu 12.04) for our project. Can you assist in helping out to
> find the driver version for TL-WN722n wireless adapter to see if that is the
> reason.
>

I don't know what driver you're using---presumably it's a standard
kernel driver included in both your systems and on my desktop as well,
but I don't see anything matching that WN722n designation. I think
they use the atheros drivers.

In order to find out the versions, you need to look at the messages
the driver logs when it loads. I don't have them loaded on my system
so let me use a driver that I do have, the e1000e network driver: when
I do 'dmesg | grep e1000e' I get

e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k

so my driver version is 2.3.2-k. Find out what driver is used by your
hardware and check its version on both systems in the same way.

-- 
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: 3 proposed patches for next 3.8.13-bone5x update

[Robert Nelson]

On Thu, May 29, 2014 at 2:32 PM, Scott Michel  wrote:
> I've attached three patches for consideration in the Robert Nelson's
> 3.8.13-bone5x update, all of which are independent of each other (i.e., you
> can patch your kernel with any one of them, separate from the others):
>
> 0001-am335x-features
>
> Detect AM335x-specific features and CPU version. Doesn't do anything
> significant, other than accurately report the CPU and SGX, L2 cache presence
> in the bootup dmesg output.
>
>
> 0002-element14-bb-view-lcd-capes
>
>  Add Element14's "BB-VIEW" LCD cape device trees to firmware/capes.
>
>
> 0003-sitara_rb_swap_workaround
>
> Create a workaround to the TI Sitara red/blue swap erratum through device
> tree properties, 'bgrx_16bpp' and 'bgrx_24bpp'. The 'bgrx_16bpp' property
> swaps red and blue if 16bpp color depth is used and the LCD cape itself
> swaps red and blue at higher color depths (i.e., the cape designer "fixed"
> the problem by swapping signals). The 'bgrx_24bpp' property swaps red and
> blue at the 24bpp color depth, which addresses TI's erratum.
>
>
> Also, the tilcdc LCD driver queries the panel's panel-info/bpp device tree
> property to find the preferred BPP when initializing the console
> framebuffer. This was originally hardcoded into the driver at 16bpp. If the
> panel says that it wants 32bpp, the framebuffer initializes to a preferred
> 32bpp.
>
>
> I've been testing these changes relative to Robert's linux-dev 3.8.15-bone53
> tag. They may apply cleanly against earlier tags, but I can't guarantee they
> will.
>
> I'm sure I have canonical kernel source formatting issues; comments, testing
> and suggestions are welcome (and advocacy for inclusion in Robert's
> linux-dev git repo also helpful.)

Thanks!  They are all queue'd up:

https://github.com/RobertCNelson/bb-kernel/commit/5e50ae5c219b52bf70193bffdef7c07c8b26b90f

Just have to run a few checks on the lcd3/lcd7 as this did revert the
custom touchscreen filtering.

I'm "pretty" sure we fixed the adc issue in:
https://github.com/RobertCNelson/bb-kernel/commit/3a66618d3bbd86a4e7655e07bc48838fb967d5ed

So it shouldn't be needed anymore now..

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] audio cape working but fails to load with DVI-D cape in stack

[Eric Fort]

Now that the audio cape works (when it's the only thing in the
stack...) I'm trying to get it and the DVI-D cape working together.
when I place the DVI-D cape on the stack the audio players (aplay,
timidity, mpg123, etc appear to play just fine but no audio is output
through the headphones and the audio cape is *NOT* shown when I "cat
/sys/devices/bone_capemgr.8/slots".  here's some commands and outpu
tbelow:

any idea what the problem could be?

Thanks,

Eric

root@beaglebone:~# cat /sys/devices/bone_capemgr.8/slots
 0: 54:PF---
 1: 55:P---L BeagleBone DVI-D CAPE,00A1,Beagleboardtoys,BB-BONE-DVID-01
 2: 56:PF---
 3: 57:PF---
root@beaglebone:~# aplay -l
 List of PLAYBACK Hardware Devices 
card 0: EVM [DA830 EVM], device 0: AIC3X tlv320aic3x-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
root@beaglebone:~# dmesg|tail
[ 2283.585864] ALSA sound/core/pcm_lib.c:1910 playback write error
(DMA or IRQ trouble?)
[ 6377.266708] bone-capemgr bone_capemgr.8: part_number
'BB-BONE-AUDI-02', version 'N/A'
[ 6377.266909] bone-capemgr bone_capemgr.8: slot #5: generic override
[ 6377.266960] bone-capemgr bone_capemgr.8: bone: Using override
eeprom data at slot 5
[ 6377.267014] bone-capemgr bone_capemgr.8: slot #5: 'Override Board
Name,00A0,Override Manuf,BB-BONE-AUDI-02'
[ 6377.267286] bone-capemgr bone_capemgr.8: slot #5: Requesting part
number/version based 'BB-BONE-AUDI-02-00A0.dtbo
[ 6377.267341] bone-capemgr bone_capemgr.8: slot #5: Requesting
firmware 'BB-BONE-AUDI-02-00A0.dtbo' for board-name 'Override Board
Name', version '00A0'
[ 6377.271408] bone-capemgr bone_capemgr.8: slot #5: dtbo
'BB-BONE-AUDI-02-00A0.dtbo' loaded; converting to live tree
[ 6377.273052] bone-capemgr bone_capemgr.8: slot #5: BB-BONE-AUDI-02
conflict P9.31 (#1:BB-BONE-DVID-01)
[ 6377.283102] bone-capemgr bone_capemgr.8: slot #5: Failed verification
root@beaglebone:~#
root@beaglebone:~# tail /var/log/messages
May 15 02:19:29 beaglebone kernel: [   43.516222] IPv6:
ADDRCONF(NETDEV_UP): eth0: link is not ready
May 15 02:19:31 beaglebone kernel: [   45.506446] libphy:
4a101000.mdio:00 - Link is Up - 100/Full
May 15 02:19:31 beaglebone kernel: [   45.506557] IPv6:
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 29 16:30:01 beaglebone kernel: [ 6377.266708] bone-capemgr
bone_capemgr.8: part_number 'BB-BONE-AUDI-02', version 'N/A'
May 29 16:30:01 beaglebone kernel: [ 6377.266909] bone-capemgr
bone_capemgr.8: slot #5: generic override
May 29 16:30:01 beaglebone kernel: [ 6377.266960] bone-capemgr
bone_capemgr.8: bone: Using override eeprom data at slot 5
May 29 16:30:01 beaglebone kernel: [ 6377.267014] bone-capemgr
bone_capemgr.8: slot #5: 'Override Board Name,00A0,Override
Manuf,BB-BONE-AUDI-02'
May 29 16:30:01 beaglebone kernel: [ 6377.267286] bone-capemgr
bone_capemgr.8: slot #5: Requesting part number/version based
'BB-BONE-AUDI-02-00A0.dtbo
May 29 16:30:01 beaglebone kernel: [ 6377.267341] bone-capemgr
bone_capemgr.8: slot #5: Requesting firmware
'BB-BONE-AUDI-02-00A0.dtbo' for board-name 'Override Board Name',
version '00A0'
May 29 16:30:01 beaglebone kernel: [ 6377.271408] bone-capemgr
bone_capemgr.8: slot #5: dtbo 'BB-BONE-AUDI-02-00A0.dtbo' loaded;
converting to live tree
root@beaglebone:~#
root@beaglebone:~# date
Thu May 29 20:19:04 UTC 2014
root@beaglebone:~# uptime
 20:19:31 up  5:35,  1 user,  load average: 0.00, 0.01, 0.05
root@beaglebone:~# uname -a
Linux beaglebone 3.8.13-bone54 #1 SMP Wed May 21 01:39:15 UTC 2014
armv7l GNU/Linux
root@beaglebone:~#

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

[beagleboard] Re: User LED forward to GPIO

[TJF]

Hello faimbs,

the USER LEDs are allready connected to GPIO-1, pins 21 to 24. By default 
these pins are configured as outputs.

An easy (and fast) alternative to control USER LEDs is libpruio 
. No need for file access to 
control the status, just call a function to switch the LED on or off. Find 
the example sos.c in the package that makes the USER LED-3 blinking in SOS 
code:

   - description: 
   
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ChaExamples.html#SubExaSos
   - source code: 
   
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/sos_8c_source.html

*libpruio can do the pin muxing and control all GPIOs (a*s well as ADC 
inputs)*. You only need a simple device tree overlay to switch on the PRUSS*. 
All the other stuff is in your source code (single source). Your program 
doesn't need root privileges (but the user needs read/write access to 
*/dev/uio5*, see DOC: Preparation 

 
for details).

Am Mittwoch, 7. Mai 2014 20:32:36 UTC+2 schrieb faimbs:
>
> Hello!
>
> Can I forward the User Led to the GPIO?
> I want to build my own Expansion Board and need this LED.
>
> OR is this function already connectet to some GPIO?
>
> Thank you!
>
>

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

Re: [beagleboard] Re: Best way to connect to Arduino via serial?

[Gerald Coley]

It should. Make sure you hook it up correctly and make the powered side be
the BBB side.

Gerald



On Thu, May 29, 2014 at 2:51 PM,  wrote:

> Cool. Would something like this work? I was looking for a thru-hole
> equivalent since I'm not good enough at soldering to try surface-mount yet
> :)
>
> http://www.digikey.com/product-detail/en/SN74LV125AN/296-34037-5-ND/1594902
>
>
>
> LP - I don't think that my Arduino can run at 3v3; the specs say that it
> can run between 7-12v and has a 5v operating voltage. Thanks though :)
>
> --
> 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] u-boot: invalid extent block

[Christof Meerwald]

Hi,

I tried to upgrade to kernel 2.15.0-rc7-bone1
(http://rcn-ee.net/deb/trusty-armhf/v3.15.0-rc7-bone1/), but all I got
was an error from u-boot "invalid extent block". I am assuming this is
a bug in u-boot - is there any fix available (updated u-boot?) or
would I have to move the kernel to a fat filesystem (from an ext4 fs)
to work around the issue?


Christof

-- 

http://cmeerw.org  sip:cmeerw at cmeerw.org
mailto:cmeerw at cmeerw.org   xmpp:cmeerw at cmeerw.org

-- 
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: Best way to connect to Arduino via serial?

[myerscountry12]

Cool. Would something like this work? I was looking for a thru-hole 
equivalent since I'm not good enough at soldering to try surface-mount yet 
:)

http://www.digikey.com/product-detail/en/SN74LV125AN/296-34037-5-ND/1594902



LP - I don't think that my Arduino can run at 3v3; the specs say that it 
can run between 7-12v and has a 5v operating voltage. Thanks though :)

-- 
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 Bbone image on BBB

[Aswin]

Hi,
Is it possible to install an image written for Beaglebone White on 
Beaglebone Black?
http://downloads.angstrom-distribution.org/demo/beaglebone/archive/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.05-beaglebone-2012.11.22.img.xz

I tried installing the image by extracting (7zip), writing to SD card 
(Win32DiskImager), inserting into BBB while powered off and keeping the 
boot button pressed while applying power. But none of the user LEDs turn 
on. If I power up BBB without boot button pressed, three user LEDs turn on 
sequentially and remain so without blinking.

I do not have an LCD screen, so don't know have a way to know if a login 
screen or anything of that sort is supposed to appear.

-- 
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] Eclipse C and Remote Debugging

[Simon Platten]

Can you suggest a good site for setting up eclipse with the Linaro 
toolchain, I've got the toolchain installed on ubuntu 14.04 in:

/home/simon/gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_linux

In eclipse, I have created a C Project and in the Properties under C/C++ 
Build, Settings, I have the Cross Settings, Prefix set to:

arm-linux-gnueabihf-

Path set to:

/home/simon/gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_linux/bin

Cross GCC Compiler, Command set to gcc
Cross GCC Linker, Command set to gcc
Cross GCC Assemlber, Command set to as

When I build the project I get:
/bin/sh: arm-linux-gnueabihf-gcc: command not foundHelloWorldBBB
 C/C++ Problem





On Thursday, 29 May 2014 20:33:52 UTC+1, Simon Platten wrote:
>
> Thank you Robert,  I've now reflashed both my Beaglebone Blacks with 
> Debian and have downloaded the linaro toolchain, so far everything has gone 
> really well...about to set-up eclipse on my ubuntu virtualbox and then try 
> remote debugging.
>
> On Wednesday, 28 May 2014 21:12:37 UTC+1, RobertCNelson wrote:
>>
>>
>>
>>
>> On Wed, May 28, 2014 at 3:06 PM, Simon Platten  
>> wrote:
>>
>>>  Thank you, I'll look into it and give it a go.
>>>
>>> Are they're any shortfalls to be aware of, anything that isn't supported?
>>>
>>
>> Well, right now we support more devices and capes out of the box then the 
>> last official Angstrom release, but if you notice something we broke kernel 
>> wise just ping us. We tried to test everything, but everyone has unique 
>> hardware.
>>
>> Otherwise the biggest change, it's a "armhf" ("gnueabihf") based system, 
>> so your "gnueabi" compiler won't work. (Well i did had the 'armel' library) 
>> so "hello world" "gnueabi" applications will run, but nothing more complex 
>> then that.
>>
>> 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] QT Creator and remote desktop

[Aswin]

Hi,

Will a QT application developed and run on BBB be displayed on a remote 
desktop connection (x11vnc on BBB and ssvnc on lapton running LinuxMint)?
I have done everything as given in Derek Molloy's video but the intended 
GUI does not appear on my laptop screen. Terminal doesn't display any error 
either. It's as if the application runs fine, but just that it can't be 
displayed on the screen.

-- 
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] Eclipse C and Remote Debugging

[Simon Platten]

Thank you Robert,  I've now reflashed both my Beaglebone Blacks with Debian 
and have downloaded the linaro toolchain, so far everything has gone really 
well...about to set-up eclipse on my ubuntu virtualbox and then try remote 
debugging.

On Wednesday, 28 May 2014 21:12:37 UTC+1, RobertCNelson wrote:
>
>
>
>
> On Wed, May 28, 2014 at 3:06 PM, Simon Platten 
> 
> > wrote:
>
>>  Thank you, I'll look into it and give it a go.
>>
>> Are they're any shortfalls to be aware of, anything that isn't supported?
>>
>
> Well, right now we support more devices and capes out of the box then the 
> last official Angstrom release, but if you notice something we broke kernel 
> wise just ping us. We tried to test everything, but everyone has unique 
> hardware.
>
> Otherwise the biggest change, it's a "armhf" ("gnueabihf") based system, 
> so your "gnueabi" compiler won't work. (Well i did had the 'armel' library) 
> so "hello world" "gnueabi" applications will run, but nothing more complex 
> then that.
>
> 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] 3 proposed patches for next 3.8.13-bone5x update

[Scott Michel]

I've attached three patches for consideration in the Robert Nelson's 
3.8.13-bone5x update, all of which are independent of each other (i.e., you 
can patch your kernel with any one of them, separate from the others):

0001-am335x-features

Detect AM335x-specific features and CPU version. Doesn't do anything 
significant, other than accurately report the CPU and SGX, L2 cache 
presence in the bootup dmesg output.


0002-element14-bb-view-lcd-capes

 Add Element14's "BB-VIEW" LCD cape device trees to firmware/capes.


0003-sitara_rb_swap_workaround

Create a workaround to the TI Sitara red/blue swap erratum through device 
tree properties, 'bgrx_16bpp' and 'bgrx_24bpp'. The 'bgrx_16bpp' property 
swaps red and blue if 16bpp color depth is used and the LCD cape itself 
swaps red and blue at higher color depths (i.e., the cape designer "fixed" 
the problem by swapping signals). The 'bgrx_24bpp' property swaps red and 
blue at the 24bpp color depth, which addresses TI's erratum.


Also, the tilcdc LCD driver queries the panel's panel-info/bpp device tree 
property to find the preferred BPP when initializing the console 
framebuffer. This was originally hardcoded into the driver at 16bpp. If the 
panel says that it wants 32bpp, the framebuffer initializes to a preferred 
32bpp.


I've been testing these changes relative to Robert's linux-dev 
3.8.15-bone53 tag. They may apply cleanly against earlier tags, but I can't 
guarantee they will.

I'm sure I have canonical kernel source formatting issues; comments, 
testing and suggestions are welcome (and advocacy for inclusion in Robert's 
linux-dev git repo also helpful.)


-scooter

 

-- 
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.
commit 06f24dee9ba97e9dd3f2fff843b442aafe5f76e4
Author: B. Scott Michel 
Date:   Thu May 29 09:56:48 2014 -0700

am335x_feature_detection

Identify AM335x chip versions, detect and enable chip-specific
features such as the SGX GPU's presence and L2 cache.

diff --git a/arch/arm/mach-omap2/control.h b/arch/arm/mach-omap2/control.h
index 12d8468..7adefd4 100644
--- a/arch/arm/mach-omap2/control.h
+++ b/arch/arm/mach-omap2/control.h
@@ -402,6 +402,12 @@
 #define		FEAT_NEON_NONE		1
 
 
+/* AM335X DEV_FEATURES register */
+#define AM335X_DEV_FEATURES0x604
+
+#define AM335X_SGX_SHIFT		29
+#define AM335X_SGX_MASK			(1 << AM335X_SGX_SHIFT)
+
 #ifndef __ASSEMBLY__
 #ifdef CONFIG_ARCH_OMAP2PLUS
 extern void __iomem *omap_ctrl_base_get(void);
diff --git a/arch/arm/mach-omap2/id.c b/arch/arm/mach-omap2/id.c
index 45cc7ed4..9486a02 100644
--- a/arch/arm/mach-omap2/id.c
+++ b/arch/arm/mach-omap2/id.c
@@ -289,6 +289,29 @@ void __init ti81xx_check_features(void)
 	omap3_cpuinfo();
 }
 
+void __init am33xx_check_features(void)
+{
+	omap_features = OMAP3_HAS_NEON;
+
+/*
+	 * am335x() fixups:
+	 * - The DEV_FEATURES register knows whether the SoC has SGX.
+	 */
+	if (soc_is_am335x()) {
+		u32 status;
+
+		status = omap_ctrl_readl(AM335X_DEV_FEATURES);
+
+		if (((status & AM335X_SGX_MASK) >> AM335X_SGX_SHIFT) == 1) {
+			omap_features |= OMAP3_HAS_SGX;
+		}
+
+		omap_features |= OMAP3_HAS_L2CACHE;
+	}
+
+	omap3_cpuinfo();
+}
+
 void __init omap3xxx_check_revision(void)
 {
 	u32 cpuid, idcode;
@@ -399,8 +422,25 @@ void __init omap3xxx_check_revision(void)
 		}
 		break;
 	case 0xb944:
-		omap_revision = AM335X_REV_ES1_0;
-		cpu_rev = "1.0";
+		switch (rev) {
+		case 0:
+			omap_revision = AM335X_REV_ES1_0;
+			cpu_rev = "1.0";
+			break;
+		case 1:
+			omap_revision = AM335X_REV_ES2_0;
+			cpu_rev = "2.0";
+			break;
+		case 2:
+			omap_revision = AM335X_REV_ES2_1;
+			cpu_rev = "2.1";
+			break;
+		default:
+			/* Assume 1.0 silicon errata if invalid. */
+			omap_revision = AM335X_REV_ES1_0;
+			cpu_rev = "1.0";
+			break;
+		}
 		break;
 	case 0xb8f2:
 		switch (rev) {
diff --git a/arch/arm/mach-omap2/io.c b/arch/arm/mach-omap2/io.c
index 5c445ca..522864c 100644
--- a/arch/arm/mach-omap2/io.c
+++ b/arch/arm/mach-omap2/io.c
@@ -568,7 +568,7 @@ void __init am33xx_init_early(void)
 	omap2_set_globals_prm(AM33XX_L4_WK_IO_ADDRESS(AM33XX_PRCM_BASE));
 	omap2_set_globals_cm(AM33XX_L4_WK_IO_ADDRESS(AM33XX_PRCM_BASE), NULL);
 	omap3xxx_check_revision();
-	ti81xx_check_features();
+	am33xx_check_features();
 	am33xx_voltagedomains_init();
 	am33xx_powerdomains_init();
 	am33xx_clockdomains_init();
diff --git a/arch/arm/mach-omap2/soc.h b/arch/arm/mach-omap2/soc.h
index f31d907..068893e 100644
--- a/arch/arm/mach-omap2/soc.h
+++ b/arch/arm/mach-omap2/soc.h
@@ -387,6 +387,8 @@ IS_OMAP_TYPE(3430, 0x3430)
 
 #define AM335X_CLASS		0x33500033
 #define AM335X_REV_ES1_0	AM335X_CLASS
+#define AM335X_REV_ES2_0	(AM335X_CLASS | (0x1 << 8))
+#define AM335X_R

Re: [beagleboard] BBB LCD3 Cape and inactivity

[Colin Bester]

I'd agree except I am seeing it with two different LCD modules BB-View and Cape 
LCD3 & LCD4 - different designs, different circuit, different manufacturer.

I'll have to noodle on it.

~C

On May 29, 2014, at 1:42 PM, John Syn  wrote:

> 
> From: Colin Bester 
> Reply-To: 
> Date: Thursday, May 29, 2014 at 6:45 AM
> To: 
> Subject: Re: [beagleboard] BBB LCD3 Cape and inactivity
> 
>> I just managed to get around to looking a little deeper into this and 
>> connected an oscilloscope to EHRPWM1A (which I figure is pin P9_14) and 
>> confirm that when writing a zero to brightness (using echo 0 > 
>> /sys/class/backlight/backlight.11/brightness) that the pin is low. Likewise 
>> write a '50' sets a 50% duty cycle and LCD brightens. I haven't set up 
>> environment to compile and test using 'c' files yet.
>> 
>> With low on pin P9_14 the LCD is still visible.
> 
> In that case this is a hardware issue. P9_14 is connected to the enable pin 
> of the LED backplane driver so the leds should turn off. 
> 
> Regards,
> John

Internet Disclaimer
_

This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and may be protected by law. 
If you are not the intended recipient, you should delete this message and are 
hereby notified that any disclosure, copying, or distribution of this message, 
or the taking of any action based on it, is strictly prohibited.
_



-- 
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: Best way to connect to Arduino via serial?

[PLyttle]

power your arduino from 3v3, It'll do fine.

LP

On Thursday, May 29, 2014 6:38:48 PM UTC+2, myersco...@gmail.com wrote:
>
> Hi!
>
> I currently have an Arduino Mega 2560, and have pre-ordered one of the new 
> BBB rev C's. The Arduino collects data from environmental sensors placed 
> around our house, and among other functions, is set up to dump the data 
> from the sensors over serial.
>
> I'm planning to have the BBB connected to the Mega over serial to collect 
> the data, store it in a database, and notify me via push messages should 
> something go out of the ordinary.
>
> However, I'm concerned about blowing up the BBB, since there are a lot of 
> caveats about making sure that things are sequenced properly and that no 
> power is applied to the BBB inputs before it's ready.
>
> I know that the Arduino outputs 5v signals, and the BBB can only handle 
> 3v3, so to address that, I've built a logic converter board based off of 
> some ZVNL120A mosfets, following Phillips' App Note AN97055.
>
> My big question is - what's the best way to prevent damage to the BBB? 
> Should I add some extra mosfets inline with the rx and tx lines, and 
> control the operation of the mosfets from the BBB (so that when the BBB is 
> off, the serial connection to the Arduino is disconnected)? Or is there 
> some other way that I should handle this?
>
> Thanks much!
>

-- 
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 LCD3 Cape and inactivity

[John Syn]

From:  Colin Bester 
Reply-To:  
Date:  Thursday, May 29, 2014 at 6:45 AM
To:  
Subject:  Re: [beagleboard] BBB LCD3 Cape and inactivity

> I just managed to get around to looking a little deeper into this and
> connected an oscilloscope to EHRPWM1A (which I figure is pin P9_14) and
> confirm that when writing a zero to brightness (using echo 0 >
> /sys/class/backlight/backlight.11/brightness) that the pin is low. Likewise
> write a ¹50¹ sets a 50% duty cycle and LCD brightens. I haven¹t set up
> environment to compile and test using OEc¹ files yet.
> 
> With low on pin P9_14 the LCD is still visible.
In that case this is a hardware issue. P9_14 is connected to the enable pin
of the LED backplane driver so the leds should turn off.

Regards,
John
> 
> With debian version I now have running, I have not seen the LCD goto sleep yet
> - still have to look into this.
> 
> ~C
> 
> 
> On May 26, 2014, at 8:03 PM, John Syn  wrote:
> 
>> 
>> From:  Colin Bester 
>> Reply-To:  
>> Date:  Monday, May 26, 2014 at 4:54 PM
>> To:  
>> Subject:  Re: [beagleboard] BBB LCD3 Cape and inactivity
>> 
>>> Was wondering if you have come up with any further solution? I can write '0'
>>> to backlight brightness but while this dims the display significantly it
>>> doesn't switch if off.
>> Have you checked that EHRPWM1A is low when you dim the display? Here are two
>> files that will control the backlight.
>> 
>> /driver/video/backlight/pwm_bl.c
>> /driver/pwm/pwm-tiehrpwm.c
>> 
>> Regards
>> John
> 
> 
> 
> -- 
> 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] WL18xx with Beaglebone Black on Debian

[Jesse Forgues]

Anyone have the WL1835MOD cape working with BBB using Debian?

Trying to follow the instructions on TIs wiki but its for Angstrom 
only: 
http://processors.wiki.ti.com/index.php/Using_the_WL18xx_Cape_with_BeagleBone_Black

I'll get to this in the next few weeks when I have a moment but curious if 
anyone had a jump start on this.

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

Re: [beagleboard] Reference OS.

[Jason Kridner]

On Thu, May 29, 2014 at 1:00 PM, David Farning  wrote:
> As a new comer to the BeagleBone one of my biggest challenges has been
> related to the numerous choice of operating systems for the board.
> Based on the various threads on this and other lists, it does not seem
> that I am alone.

I agree with Gerald, but I'll try to address some of your concerns
from my perspective as well.

The variety and changing nature of software does create some support
challenges. Part of our strategy has been to make BeagleBoard.org
hardware a first-class citizen of various community software projects.
In that light, you can get lots of support for those projects in their
normal support channels and come here to figure out the
BeagleBoard/BeagleBone-specific details.

>
> Would be possible to achieve consensus around a single OS as the ref
> Operating System for the BBB? While I support individuals freely
> choosing which distribution best meets their needs, the overall
> project would be best served by focusing on the foundation.
>
> Shipping the BBB rev C with Debian starts to set Debian as the defacto 
> standard.

A reference, certainly. Not sure what the implication is of a "defacto
standard". All operating systems are welcome here.

>
> 1. Would it be possible/reasonable to suggest that other BeagleBone
> users migrate from Angstrom to Debian?

Possible, yes. Reasonable, depends. If Angstrom does what you need,
then why not stay with it?

> 2. Would it be possible/reasonable to articulate that the BeagleBone
> community will focus their development and support efforts on Debian?

The community is diverse and supports many software systems. There's
some focus on Debian, but we should be working with Fedora, Arch,
FreeBSD and lots of others too. There is a bit of a BeagleBone
out-of-box-experience, but it is meant as just a gateway on to deeper
learning and development.

> 3. Would it be possible/reasonable to suggest that support on this
> mailing list will focus on Debian?

No. We try to avoid forking lists when when can. Impressions of that
have been mixed, but I think if there is enough interest in creating a
Debian support list focused on BeagleBone Black, then someone will
make it and attract community members there. Personally, I like having
this one list with all the topics and relying on people to create
reasonable subject lines. Folks can tag messages as well to put them
in various categories.

>
> My concern is that with out clear community consensus, the BBB faces
> unnecessary fragmentation which would reduce that value of the project

Is there a specific contribution you are looking at making?

>
> David
>
> --
> 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] Reference OS.

[William Hermans]

Jjust pick a distro ( all are Linux, e.g. OS ), and stick with it. I will
however let you know, that the best supported distro right now is Debian.
Robert does a bang up job, and is very active on these groups. Not to
mention that Debian is well documented on the internet, where 90% + of any
ones answers can be answered by using google.

This post of yours seems circular in relation to the last post or two
you've made on these groups. Dancing around the same subjects. SO my advice
to you is just pick *SOMETHING* (I would recommend Debian ),  start
learning one thing at a time, and do not stress out on the whole big
picture ( all at once )

I would also recommend that you setup a virtual machine with Debian on it
to toy around with until you feel comfortable with various aspects as you
learn them. The only way you're going to learn is by doing.


On Thu, May 29, 2014 at 10:31 AM, Alexander Holler wrote:

> Am 29.05.2014 19:07, schrieb Gerald Coley:
>
>  We ship Debian on every BBB we ship. However, trying to dictate to the
>> community what every person uses, that seems to me to be "not open
>> source".
>> We have no plans to dictate to people what they do and what OS they
>> prefer.
>>
>> Open source means just that . Fragmentation. I do not plan for us to
>> become
>> Microsoft.  Causing people to leave the project because you did not choose
>> Android, that would in my opinion reduce the value of the project.
>>
>
> Besides that only the kernel matters. If you have a working kernel, you
> can use almost every Linux distribution (or other OS which do use the Linux
> kernel like Android).
>
> Unfortunatley that doesn't make things easier as a working kernel is stuff
> for dreams itself (meant in general, not in regard to the Beagle boards).
>
> Regards,
>
> Alexander Holler
>
>
> --
> 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] Best way to connect to Arduino via serial?

[Gerald Coley]

Just add a buffer like is the one on the BBB schematic for use by the debug
port. Or, just use the debug port on the BBB for your serial connection..


Gerald


On Thu, May 29, 2014 at 11:38 AM,  wrote:

> Hi!
>
> I currently have an Arduino Mega 2560, and have pre-ordered one of the new
> BBB rev C's. The Arduino collects data from environmental sensors placed
> around our house, and among other functions, is set up to dump the data
> from the sensors over serial.
>
> I'm planning to have the BBB connected to the Mega over serial to collect
> the data, store it in a database, and notify me via push messages should
> something go out of the ordinary.
>
> However, I'm concerned about blowing up the BBB, since there are a lot of
> caveats about making sure that things are sequenced properly and that no
> power is applied to the BBB inputs before it's ready.
>
> I know that the Arduino outputs 5v signals, and the BBB can only handle
> 3v3, so to address that, I've built a logic converter board based off of
> some ZVNL120A mosfets, following Phillips' App Note AN97055.
>
> My big question is - what's the best way to prevent damage to the BBB?
> Should I add some extra mosfets inline with the rx and tx lines, and
> control the operation of the mosfets from the BBB (so that when the BBB is
> off, the serial connection to the Arduino is disconnected)? Or is there
> some other way that I should handle this?
>
> Thanks much!
>
> --
> 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] Reference OS.

[Alexander Holler]

Am 29.05.2014 19:07, schrieb Gerald Coley:

We ship Debian on every BBB we ship. However, trying to dictate to the
community what every person uses, that seems to me to be "not open source".
We have no plans to dictate to people what they do and what OS they prefer.

Open source means just that . Fragmentation. I do not plan for us to become
Microsoft.  Causing people to leave the project because you did not choose
Android, that would in my opinion reduce the value of the project.


Besides that only the kernel matters. If you have a working kernel, you 
can use almost every Linux distribution (or other OS which do use the 
Linux kernel like Android).


Unfortunatley that doesn't make things easier as a working kernel is 
stuff for dreams itself (meant in general, not in regard to the Beagle 
boards).


Regards,

Alexander Holler

--
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] Anyone else interested in obtaining a mikroBUS Cape ?

[Mark Grosen]

Ok, I can go for 2 at this price. I can do PayPal or check or  to pay
you. I'll need to cover US shipping, too. Slow boat is fine - no rush.

Mark



Mark


On Thu, May 29, 2014 at 9:53 AM, motortest_guy wrote:

> I priced out two for me and two for you.
> Since we aren't Europe, we don't have to pay VAT, but the shipping
> (carriage)
> is pricey @ € 31,00.
>
> The shipping price seems fixed for 1 or more boards up to some limit I'm
> sure.
> I may also want to get a couple of 'Click' boards if the shipping doesn't
> go up.
>
> When I put in for a quantity of 10 boards the shipping went up to € 39,00
> for a total of  €  149,00
>
>
> Products
>   # Product Unit price Quantity Net amount 1 *BeagleBone mikroBUS 
> Cape*
> mikroBUS Cape for BeagleBone
> € 11,00 4 € 44,00 Subtotal € 44,00 Carriage net € 31,00 Net amount € 75,00 VAT
> (20%) 0 *Total amount* *€ 75,00*
>
>
>   Shopping cart  4 *BeagleBone mikroBUS 
> Cape* Total
> amount: € 44,00
>
>
> On Wednesday, May 28, 2014 1:17:20 PM UTC-6, Mark Grosen wrote:
>
>> How much is the shipping? I see the base price is ~$18 including VAT. I
>> would take 2 at this price plus a reasonable shared shipping cost.
>>
>> Mark
>>
>>
>>
>> Mark
>>
>>
>> On Tue, May 27, 2014 at 3:13 PM, motortest_guy wrote:
>>
>>>
>>> https://www.tigal.com/wiki/doku.php?id=tigalcapes:bb_mikrobus_cape
>>>
>>> I want to get one, but the freight cost to get it across the ocean is
>>> double the cost of the board.
>>> If I order one, I might get a few more to sell to folks interested in
>>> the States.
>>>
>>> Mouser (In States) carries many if the Click boards, but doesn't carry
>>> the adapter cape (above).
>>>
>>> http://www.mouser.com/new/mikroelektronika/mikroelektronikaClick/
>>>
>>> --
>>> 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.
>

-- 
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] Best way to connect to Arduino via serial?

[myerscountry12]

Hi!

I currently have an Arduino Mega 2560, and have pre-ordered one of the new 
BBB rev C's. The Arduino collects data from environmental sensors placed 
around our house, and among other functions, is set up to dump the data 
from the sensors over serial.

I'm planning to have the BBB connected to the Mega over serial to collect 
the data, store it in a database, and notify me via push messages should 
something go out of the ordinary.

However, I'm concerned about blowing up the BBB, since there are a lot of 
caveats about making sure that things are sequenced properly and that no 
power is applied to the BBB inputs before it's ready.

I know that the Arduino outputs 5v signals, and the BBB can only handle 
3v3, so to address that, I've built a logic converter board based off of 
some ZVNL120A mosfets, following Phillips' App Note AN97055.

My big question is - what's the best way to prevent damage to the BBB? 
Should I add some extra mosfets inline with the rx and tx lines, and 
control the operation of the mosfets from the BBB (so that when the BBB is 
off, the serial connection to the Arduino is disconnected)? Or is there 
some other way that I should handle this?

Thanks much!

-- 
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] Reference OS.

[Mike]

On 05/29/2014 01:00 PM, David Farning wrote:

Shipping the BBB rev C with Debian starts to set Debian as the defacto standard.

1. Would it be possible/reasonable to suggest that other BeagleBone
users migrate from Angstrom to Debian?
2. Would it be possible/reasonable to articulate that the BeagleBone
community will focus their development and support efforts on Debian?
3. Would it be possible/reasonable to suggest that support on this
mailing list will focus on Debian?

My concern is that with out clear community consensus, the BBB faces
unnecessary fragmentation which would reduce that value of the project

David

I'd say that your first sentence above pretty much covers all your 
listed points.  Robert has done an excellent job of creating an easy way 
for users to use Debian.  Now that rev. C ships with a Debian install 
seems to me the path is clear.


I've looked into Angstrom in the past, seems to be a dying project 
IMNSHO.  The website has only recently been brought back online and much 
of it is dead links.


Robert probably said it best recently, Linux is Linux.  If I had a dime 
for every time I've said that to people I've mentored I'd be a much 
wealthier man.  Nearly all have come back to where I started them, 
namely Debian.  They wander and stumble around because distro x supports 
this piece of hardware, or I can't do this on distro y. Once they pass a 
point on the learning curve they start to see the light.


Your last sentence pretty much describes the Linux community in 
general.  Many debate for the one core distro/desktop/browser/whatever.  
Human nature such as it is will never allow a consensus.  In the end 
it's about a users choice


My 2cents or so.

Mike

--
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] Reference OS.

[Gerald Coley]

We ship Debian on every BBB we ship. However, trying to dictate to the
community what every person uses, that seems to me to be "not open source".
We have no plans to dictate to people what they do and what OS they prefer.

Open source means just that . Fragmentation. I do not plan for us to become
Microsoft.  Causing people to leave the project because you did not choose
Android, that would in my opinion reduce the value of the project.

Gerald



On Thu, May 29, 2014 at 12:00 PM, David Farning  wrote:

> As a new comer to the BeagleBone one of my biggest challenges has been
> related to the numerous choice of operating systems for the board.
> Based on the various threads on this and other lists, it does not seem
> that I am alone.
>
> Would be possible to achieve consensus around a single OS as the ref
> Operating System for the BBB? While I support individuals freely
> choosing which distribution best meets their needs, the overall
> project would be best served by focusing on the foundation.
>
> Shipping the BBB rev C with Debian starts to set Debian as the defacto
> standard.
>
> 1. Would it be possible/reasonable to suggest that other BeagleBone
> users migrate from Angstrom to Debian?
> 2. Would it be possible/reasonable to articulate that the BeagleBone
> community will focus their development and support efforts on Debian?
> 3. Would it be possible/reasonable to suggest that support on this
> mailing list will focus on Debian?
>
> My concern is that with out clear community consensus, the BBB faces
> unnecessary fragmentation which would reduce that value of the project
>
> David
>
> --
> 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] Reference OS.

[David Farning]

As a new comer to the BeagleBone one of my biggest challenges has been
related to the numerous choice of operating systems for the board.
Based on the various threads on this and other lists, it does not seem
that I am alone.

Would be possible to achieve consensus around a single OS as the ref
Operating System for the BBB? While I support individuals freely
choosing which distribution best meets their needs, the overall
project would be best served by focusing on the foundation.

Shipping the BBB rev C with Debian starts to set Debian as the defacto standard.

1. Would it be possible/reasonable to suggest that other BeagleBone
users migrate from Angstrom to Debian?
2. Would it be possible/reasonable to articulate that the BeagleBone
community will focus their development and support efforts on Debian?
3. Would it be possible/reasonable to suggest that support on this
mailing list will focus on Debian?

My concern is that with out clear community consensus, the BBB faces
unnecessary fragmentation which would reduce that value of the project

David

-- 
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] Custom Beaglbone Black from Circuitco

[David Funk]

On Wed, May 28, 2014 at 3:28 PM, sixvolts  wrote:

> I've been trying to talk to the people CircuitCo about building a run of
> the beaglebone black boards for a commercial project, but I can't seem to
> get anyone to respond to emails and the two people I have phone numbers for
> are always busy.
>
> My understanding was that proper etiquette was to not poach boards from
> the distributors if you build a device around the beaglebone and have them
> produced for you. I even spoke to someone at a CircuitCo booth at a
> conference last year (DesignWest - where the beaglebone black was
> "launched") and they indicated this was common already for the original
> beagleboards/bones.
>
> I can't get anyone local interested in building them because of some of
> the minimum order quantities on some of the parts (like the emmc).
>
> Anyone at CircuitCo around? I have money and need around 100 boards made.
>


Good grief! your last two lines explain everything!  It's obvious you
haven't a clue how PCB manufacturing works and seem determined to make the
system fit your world view.

Your 100 board run does not even come close to their minimum order quantity
requirements!  Yes, they are avoiding you!  You don't meet requirements!
 You seem to be unable to grasp the concept that your requirement is too
small for their requirements, hence now you've become a pest and a
nuisance! They can't help you and don't want to be bothered by you anymore!


There are many, many other board shops out there!  Do your homework, Google
can help, Nuts and Volts magazine/website can help.

The hobby oriented board shops consider this a very complex design, which
it is and many will not take it.  The ones that will take it are going to
charge a lot.  Many will only do 4 layer boards and won't touch BBB.  Then
you have to worry about testing.  Many won't test for you and the ones that
will are going to charge a lot to setup a test plan.  Do you even know how
to specify what you want tested?  You can't just say that you want a
"functional board." It doesn't work that way.


This is the realities of PCB manufacturing. Are you really ready for the
big time?




-david

-- 
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] Anyone else interested in obtaining a mikroBUS Cape ?

[motortest_guy]

I priced out two for me and two for you.
Since we aren't Europe, we don't have to pay VAT, but the shipping 
(carriage)
is pricey @ € 31,00.

The shipping price seems fixed for 1 or more boards up to some limit I'm 
sure.
I may also want to get a couple of 'Click' boards if the shipping doesn't 
go up.

When I put in for a quantity of 10 boards the shipping went up to € 39,00 
for a total of  €  149,00


Products
  # Product Unit price Quantity Net amount 1 *BeagleBone mikroBUS 
Cape* 
mikroBUS Cape for BeagleBone
€ 11,00 4 € 44,00 Subtotal € 44,00 Carriage net € 31,00 Net amount € 75,00 VAT 
(20%) 0 *Total amount* *€ 75,00*
 
 
  Shopping cart  4 *BeagleBone mikroBUS 
Cape* Total 
amount: € 44,00 


On Wednesday, May 28, 2014 1:17:20 PM UTC-6, Mark Grosen wrote:

> How much is the shipping? I see the base price is ~$18 including VAT. I 
> would take 2 at this price plus a reasonable shared shipping cost.
>
> Mark
>
>
>
> Mark
>
>
> On Tue, May 27, 2014 at 3:13 PM, motortest_guy 
> 
> > wrote:
>
>>
>> https://www.tigal.com/wiki/doku.php?id=tigalcapes:bb_mikrobus_cape
>>
>> I want to get one, but the freight cost to get it across the ocean is 
>> double the cost of the board.
>> If I order one, I might get a few more to sell to folks interested in the 
>> States.
>>
>> Mouser (In States) carries many if the Click boards, but doesn't carry 
>> the adapter cape (above).
>>
>> http://www.mouser.com/new/mikroelektronika/mikroelektronikaClick/
>>  
>> -- 
>> 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] Re: Here is the BeagleBone Debian (beta) image you want to test

[Robert Nelson]

On Thu, May 29, 2014 at 9:50 AM, Robert Nelson  wrote:
> On Thu, May 29, 2014 at 9:48 AM, Robert Nelson  
> wrote:
>> On Thu, May 29, 2014 at 1:00 AM,   wrote:
>>> On Wednesday, May 28, 2014 2:37:13 PM UTC-7, RobertCNelson wrote:

 It's there just an older version of systemd where it was prefixed.
 systemd-
>>>
>>> Follow-on question: any risk in moving to the latest version of systemd?
>>> The version on the flasher is 44, the version on freedesktop.org is 213 and
>>> two years newer...
>>
>> This is just the way Debian works. "stable" aka Wheezy is frozen, so
>> only bug fixes are allowed.  As we start getting closer to Debian
>> Jessie's freeze date, I'll start pushing out offical testing images.
>>
>> But there's nothing stopping you from running:
>>
>> sudo sed -i 's/wheezy/jessie/g' /etc/apt/sources.list
>> sudo apt-get update
>> sudo apt-get upgrade
>>
>> Then you'll get systemd 204
>>
>> http://packages.qa.debian.org/s/systemd.html
>
> Of course, i just noticed, the stable backport of systemd
> 204-8~bpo70+1 is available right now.

Enable:

deb http://ftp.debian.org/debian wheezy-backports main contrib non-free
deb-src http://ftp.debian.org/debian wheezy-backports main contrib non-free

in /etc/apt/sources.list


sudo apt-get update
sudo apt-get -t wheezy-backports install systemd
sudo reboot

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: Here is the BeagleBone Debian (beta) image you want to test

[Robert Nelson]

On Thu, May 29, 2014 at 9:48 AM, Robert Nelson  wrote:
> On Thu, May 29, 2014 at 1:00 AM,   wrote:
>> On Wednesday, May 28, 2014 2:37:13 PM UTC-7, RobertCNelson wrote:
>>>
>>> It's there just an older version of systemd where it was prefixed.
>>> systemd-
>>
>> Follow-on question: any risk in moving to the latest version of systemd?
>> The version on the flasher is 44, the version on freedesktop.org is 213 and
>> two years newer...
>
> This is just the way Debian works. "stable" aka Wheezy is frozen, so
> only bug fixes are allowed.  As we start getting closer to Debian
> Jessie's freeze date, I'll start pushing out offical testing images.
>
> But there's nothing stopping you from running:
>
> sudo sed -i 's/wheezy/jessie/g' /etc/apt/sources.list
> sudo apt-get update
> sudo apt-get upgrade
>
> Then you'll get systemd 204
>
> http://packages.qa.debian.org/s/systemd.html

Of course, i just noticed, the stable backport of systemd
204-8~bpo70+1 is available right now.

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: Here is the BeagleBone Debian (beta) image you want to test

[Robert Nelson]

On Thu, May 29, 2014 at 1:00 AM,   wrote:
> On Wednesday, May 28, 2014 2:37:13 PM UTC-7, RobertCNelson wrote:
>>
>> It's there just an older version of systemd where it was prefixed.
>> systemd-
>
> Follow-on question: any risk in moving to the latest version of systemd?
> The version on the flasher is 44, the version on freedesktop.org is 213 and
> two years newer...

This is just the way Debian works. "stable" aka Wheezy is frozen, so
only bug fixes are allowed.  As we start getting closer to Debian
Jessie's freeze date, I'll start pushing out offical testing images.

But there's nothing stopping you from running:

sudo sed -i 's/wheezy/jessie/g' /etc/apt/sources.list
sudo apt-get update
sudo apt-get upgrade

Then you'll get systemd 204

http://packages.qa.debian.org/s/systemd.html

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: BBB with 3.14 + barefs....no LCD 4Dsytem-43T

[Robert Nelson]

On Thu, May 29, 2014 at 9:32 AM, silsil  wrote:
> if i use "debian-7.5-console..." with 3.8, lcd works well
> after I install 3.14 with this script ( install-me) on Robert nelson:
> http://rcn-ee.net/deb/wheezy-armhf/v3.14.4-bone4/
> when i reboot with 3.14LCD stop and always BLACK
>
> is it problem about 3.14 kernel ?

I wouldn't call it a problem. Just not a feature of the v3.14.x based
kernel yet.

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: BBB with 3.14 + barefs....no LCD 4Dsytem-43T

[silsil]

if i use "debian-7.5-console..." with 3.8, lcd works well
after I install 3.14 with this script ( install-me) on Robert nelson:
http://rcn-ee.net/deb/wheezy-armhf/v3.14.4-bone4/
when i reboot with 3.14LCD stop and always BLACK

is it problem about 3.14 kernel ?

Thanks 


Il giorno giovedì 29 maggio 2014 14:06:33 UTC+2, silsil ha scritto:
>
> I use eeewiki.net tutorial fot installing 3.14, u-boot, etc... + debian 
> barefs by Robert Nelson.
> I've 4Dcape 43-T, but doesnt workit is always black, no boot logo, no 
> console
> led's is power on.
>
> i test with minfs, but same result's
> i test with rootfs with 3.8, and it works well
>
> how i enable LCD cape with barefs or minfs ?
>
>
> 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] Custom Beaglbone Black from Circuitco

[Maxim Podbereznyy]

Gerald, exactly!

I have so many RFQ for 100 or even 1000pcs and people just can't understand
that so small volume is not even a volume for an assembly line and
consequently unit prices are higher than BBB price. These people just
purchase BBB for commercial projects although they should not. Distributors
simply accept their orders

If you want low cost than order at least 10k. For example I don't even know
any Chinese factory which can accept orders less than 10k and even for 10k
they will charge at least 100% of components cost. It's business, nothing
personal. No one will donate your dreams


2014-05-29 17:10 GMT+04:00 Gerald Coley :

> Not to mention. If you build a custom BBB, and make 100 pieces, the cost
> will be around $300 to $500 a board after you pay the NRE and high cost of
> buying only 00 boards. .The reson this board is low a sit is is that we add
> a three zeros to the 100 number. That is the way this business works.
>
> Gerald
>
>
>
> On Thu, May 29, 2014 at 8:07 AM, David Lambert  wrote:
>
>>  Well said Gerald! The BBB is so much more than just a reference design.
>> It has been instantiated at a very low cost. I get sick when I hear of so
>> much crap being thrown at the team, just because its huge success has
>> caused some supply issues.
>> Rant over.
>>
>> Dave.
>>
>>
>> On 05/29/2014 08:00 AM, Gerald Coley wrote:
>>
>> I gave you the design for free. All the schematics, CAD files, and BOM.
>> You are free to build it yourself at any place you want. There is no NRE
>> charge. No license.
>>
>>  Sorry that I can't be your personal engineering and manufacturing
>> operation.
>>
>>  Gerald
>>
>>
>>
>> On Thu, May 29, 2014 at 7:50 AM, Eric Fort  wrote:
>>
>>> Hey, wait!  Gerald does not suck!  Gerald, and the entire beagleboard
>>> team are awesome and totally rock!  We as a community probably give
>>> Gerald the most workload and highest amount of stress though.  Yes, we
>>> have been given a great foundation in beagle on which to build.  If
>>> you need something substantially more custom you've got much of the
>>> work already completed, and any rework and redesign not only is your
>>> own but really ought be contributed back to the community as well (if
>>> you do a derivitive work of the board rather than a clean sheet)
>>>
>>> Eric
>>>
>>> On Thu, May 29, 2014 at 4:38 AM, David Farning 
>>> wrote:
>>> > I agree completely.
>>> >
>>> > With the understanding that there are shops which can do small custom
>>> > orders at reasonable prices, the conversation shifts from
>>> > BeagleBoard.orc / Circuit Co / Gerald sucks for not meeting my
>>> > specific needs... to how can I build on the foundation that
>>> > BeagleBoard.org et. al have laid to needs.
>>> >
>>> > David
>>> >
>>> >
>>> > On Wed, May 28, 2014 at 11:58 PM, Eric Fort 
>>> wrote:
>>> >> While CircuitCo incurs some risk in expanding production capacity on a
>>> >> board that "anyone can step in and manufacture a clone" of, and
>>> >> Embedest *is* making a clone of as a second source I will still hold
>>> >> out when purchasing beagleboard products for those sourced from
>>> >> CircuitCo as their quality has always been consistant and of the
>>> >> highest degree and their servive has been excellent.  So long as
>>> >> others make the same observation that does help lessen some of the
>>> >> risk.
>>> >>
>>> >> As far as getting circa 100 boards made, I know there are shops that
>>> >> will do single quantities and with that the case a quantity of 100 is
>>> >> not unreasonable, just gotta shop around a bit.  I may know a few
>>> >> places to get you going so if interested, pm me.  then again at a
>>> >> qty of 100
>>> http://www.digikey.com/product-detail/en/BB-BBLK-100/BB-BBLK-100-REVC-ND/4842545
>>> >> may be an option.
>>> >>
>>> >>
>>> >>
>>> >> On Wed, May 28, 2014 at 6:19 PM, David Farning 
>>> wrote:
>>> >>> Some shops are really good at churning out small (100 to 10,000
>>> units)
>>> >>> runs of a product. They have perfected the art of retooling the line.
>>> >>>
>>> >>> In the current situation, it appears that our beaglebone friends are
>>> >>> in the process of convincing the money people to make the investment
>>> >>> to increase manufacturing capacity. The new equipment required to
>>> >>> increase capacity costs serious money.
>>> >>>
>>> >>> When one considers that the BBB is open and anyone can step in and
>>> >>> manufacture a clone and bypass then R&D costs TI and Circuit Co have
>>> >>> already invested, the risks start getting pretty high.
>>> >>>
>>> >>> What might seemed antagonizing slow to us on the outside, requires
>>> >>> serious thought and planing on the inside. It can be challenging to
>>> >>> communicate this when companies work as part of communities.
>>> >>>
>>> >>> On Wed, May 28, 2014 at 6:32 PM, William Hermans 
>>> wrote:
>>>  Gerald, I am just curious. Hypothetically speaking, what would it
>>> take to
>>>  retool to make a custom board ? I am not looking for an "IN" or
>>>

Re: [beagleboard] BBB LCD3 Cape and inactivity

[Colin Bester]

I just managed to get around to looking a little deeper into this and connected 
an oscilloscope to EHRPWM1A (which I figure is pin P9_14) and confirm that when 
writing a zero to brightness (using echo 0 > 
/sys/class/backlight/backlight.11/brightness) that the pin is low. Likewise 
write a '50' sets a 50% duty cycle and LCD brightens. I haven't set up 
environment to compile and test using 'c' files yet.

With low on pin P9_14 the LCD is still visible.

With debian version I now have running, I have not seen the LCD goto sleep yet 
- still have to look into this.

~C


On May 26, 2014, at 8:03 PM, John Syn  wrote:

> 
> From: Colin Bester 
> Reply-To: 
> Date: Monday, May 26, 2014 at 4:54 PM
> To: 
> Subject: Re: [beagleboard] BBB LCD3 Cape and inactivity
> 
>> Was wondering if you have come up with any further solution? I can write '0' 
>> to backlight brightness but while this dims the display significantly it 
>> doesn't switch if off.
> 
> Have you checked that EHRPWM1A is low when you dim the display? Here are two 
> files that will control the backlight.
> 
> /driver/video/backlight/pwm_bl.c
> /driver/pwm/pwm-tiehrpwm.c
> 
> Regards
> John



-- 
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] Custom Beaglbone Black from Circuitco

[Gerald Coley]

Not to mention. If you build a custom BBB, and make 100 pieces, the cost
will be around $300 to $500 a board after you pay the NRE and high cost of
buying only 00 boards. .The reson this board is low a sit is is that we add
a three zeros to the 100 number. That is the way this business works.

Gerald



On Thu, May 29, 2014 at 8:07 AM, David Lambert  wrote:

>  Well said Gerald! The BBB is so much more than just a reference design.
> It has been instantiated at a very low cost. I get sick when I hear of so
> much crap being thrown at the team, just because its huge success has
> caused some supply issues.
> Rant over.
>
> Dave.
>
>
> On 05/29/2014 08:00 AM, Gerald Coley wrote:
>
> I gave you the design for free. All the schematics, CAD files, and BOM.
> You are free to build it yourself at any place you want. There is no NRE
> charge. No license.
>
>  Sorry that I can't be your personal engineering and manufacturing
> operation.
>
>  Gerald
>
>
>
> On Thu, May 29, 2014 at 7:50 AM, Eric Fort  wrote:
>
>> Hey, wait!  Gerald does not suck!  Gerald, and the entire beagleboard
>> team are awesome and totally rock!  We as a community probably give
>> Gerald the most workload and highest amount of stress though.  Yes, we
>> have been given a great foundation in beagle on which to build.  If
>> you need something substantially more custom you've got much of the
>> work already completed, and any rework and redesign not only is your
>> own but really ought be contributed back to the community as well (if
>> you do a derivitive work of the board rather than a clean sheet)
>>
>> Eric
>>
>> On Thu, May 29, 2014 at 4:38 AM, David Farning 
>> wrote:
>> > I agree completely.
>> >
>> > With the understanding that there are shops which can do small custom
>> > orders at reasonable prices, the conversation shifts from
>> > BeagleBoard.orc / Circuit Co / Gerald sucks for not meeting my
>> > specific needs... to how can I build on the foundation that
>> > BeagleBoard.org et. al have laid to needs.
>> >
>> > David
>> >
>> >
>> > On Wed, May 28, 2014 at 11:58 PM, Eric Fort 
>> wrote:
>> >> While CircuitCo incurs some risk in expanding production capacity on a
>> >> board that "anyone can step in and manufacture a clone" of, and
>> >> Embedest *is* making a clone of as a second source I will still hold
>> >> out when purchasing beagleboard products for those sourced from
>> >> CircuitCo as their quality has always been consistant and of the
>> >> highest degree and their servive has been excellent.  So long as
>> >> others make the same observation that does help lessen some of the
>> >> risk.
>> >>
>> >> As far as getting circa 100 boards made, I know there are shops that
>> >> will do single quantities and with that the case a quantity of 100 is
>> >> not unreasonable, just gotta shop around a bit.  I may know a few
>> >> places to get you going so if interested, pm me.  then again at a
>> >> qty of 100
>> http://www.digikey.com/product-detail/en/BB-BBLK-100/BB-BBLK-100-REVC-ND/4842545
>> >> may be an option.
>> >>
>> >>
>> >>
>> >> On Wed, May 28, 2014 at 6:19 PM, David Farning 
>> wrote:
>> >>> Some shops are really good at churning out small (100 to 10,000 units)
>> >>> runs of a product. They have perfected the art of retooling the line.
>> >>>
>> >>> In the current situation, it appears that our beaglebone friends are
>> >>> in the process of convincing the money people to make the investment
>> >>> to increase manufacturing capacity. The new equipment required to
>> >>> increase capacity costs serious money.
>> >>>
>> >>> When one considers that the BBB is open and anyone can step in and
>> >>> manufacture a clone and bypass then R&D costs TI and Circuit Co have
>> >>> already invested, the risks start getting pretty high.
>> >>>
>> >>> What might seemed antagonizing slow to us on the outside, requires
>> >>> serious thought and planing on the inside. It can be challenging to
>> >>> communicate this when companies work as part of communities.
>> >>>
>> >>> On Wed, May 28, 2014 at 6:32 PM, William Hermans 
>> wrote:
>>  Gerald, I am just curious. Hypothetically speaking, what would it
>> take to
>>  retool to make a custom board ? I am not looking for an "IN" or
>> anything I
>>  am just curious. I'm thinking it would be a huge hassle to say the
>> least.
>> 
>>  I've never worked in a PCB fab before, but worked for a CNC shop
>> many moons
>>  ago, and retooling for even the most basic part ( door lock keyways
>> ), would
>>  take a full day or two just for the setup, and a week or slightly
>> longer to
>>  shake out the bugs. Meanwhile, the company is "losing" money until
>> things
>>  are running smoothly again.
>> 
>> 
>>  On Wed, May 28, 2014 at 1:42 PM, Gerald Coley <
>> ger...@beagleboard.org>
>>  wrote:
>> >
>> > 100 boards is not a lot of boards. Especially when you have
>> distributors
>> > screaming for 50,000 boards to fill their large POs..
>

Re: [beagleboard] Custom Beaglbone Black from Circuitco

[David Lambert]

Well said Gerald! The BBB is so much more than just a reference design. 
It has been instantiated at a very low cost. I get sick when I hear of 
so much crap being thrown at the team, just because its huge success has 
caused some supply issues.

Rant over.

Dave.

On 05/29/2014 08:00 AM, Gerald Coley wrote:
I gave you the design for free. All the schematics, CAD files, and 
BOM. You are free to build it yourself at any place you want. There is 
no NRE charge. No license.


Sorry that I can't be your personal engineering and manufacturing 
operation.


Gerald



On Thu, May 29, 2014 at 7:50 AM, Eric Fort > wrote:


Hey, wait!  Gerald does not suck!  Gerald, and the entire beagleboard
team are awesome and totally rock!  We as a community probably give
Gerald the most workload and highest amount of stress though.  Yes, we
have been given a great foundation in beagle on which to build.  If
you need something substantially more custom you've got much of the
work already completed, and any rework and redesign not only is your
own but really ought be contributed back to the community as well (if
you do a derivitive work of the board rather than a clean sheet)

Eric

On Thu, May 29, 2014 at 4:38 AM, David Farning mailto:dfarn...@gmail.com>> wrote:
> I agree completely.
>
> With the understanding that there are shops which can do small
custom
> orders at reasonable prices, the conversation shifts from
> BeagleBoard.orc / Circuit Co / Gerald sucks for not meeting my
> specific needs... to how can I build on the foundation that
> BeagleBoard.org et. al have laid to needs.
>
> David
>
>
> On Wed, May 28, 2014 at 11:58 PM, Eric Fort mailto:eric.f...@gmail.com>> wrote:
>> While CircuitCo incurs some risk in expanding production
capacity on a
>> board that "anyone can step in and manufacture a clone" of, and
>> Embedest *is* making a clone of as a second source I will still
hold
>> out when purchasing beagleboard products for those sourced from
>> CircuitCo as their quality has always been consistant and of the
>> highest degree and their servive has been excellent.  So long as
>> others make the same observation that does help lessen some of the
>> risk.
>>
>> As far as getting circa 100 boards made, I know there are shops
that
>> will do single quantities and with that the case a quantity of
100 is
>> not unreasonable, just gotta shop around a bit.  I may know a few
>> places to get you going so if interested, pm me.  then
again at a
>> qty of 100

http://www.digikey.com/product-detail/en/BB-BBLK-100/BB-BBLK-100-REVC-ND/4842545
>> may be an option.
>>
>>
>>
>> On Wed, May 28, 2014 at 6:19 PM, David Farning
mailto:dfarn...@gmail.com>> wrote:
>>> Some shops are really good at churning out small (100 to
10,000 units)
>>> runs of a product. They have perfected the art of retooling
the line.
>>>
>>> In the current situation, it appears that our beaglebone
friends are
>>> in the process of convincing the money people to make the
investment
>>> to increase manufacturing capacity. The new equipment required to
>>> increase capacity costs serious money.
>>>
>>> When one considers that the BBB is open and anyone can step in and
>>> manufacture a clone and bypass then R&D costs TI and Circuit
Co have
>>> already invested, the risks start getting pretty high.
>>>
>>> What might seemed antagonizing slow to us on the outside, requires
>>> serious thought and planing on the inside. It can be
challenging to
>>> communicate this when companies work as part of communities.
>>>
>>> On Wed, May 28, 2014 at 6:32 PM, William Hermans
mailto:yyrk...@gmail.com>> wrote:
 Gerald, I am just curious. Hypothetically speaking, what
would it take to
 retool to make a custom board ? I am not looking for an "IN"
or anything I
 am just curious. I'm thinking it would be a huge hassle to
say the least.

 I've never worked in a PCB fab before, but worked for a CNC
shop many moons
 ago, and retooling for even the most basic part ( door lock
keyways ), would
 take a full day or two just for the setup, and a week or
slightly longer to
 shake out the bugs. Meanwhile, the company is "losing" money
until things
 are running smoothly again.


 On Wed, May 28, 2014 at 1:42 PM, Gerald Coley
mailto:ger...@beagleboard.org>>
 wrote:
>
> 100 boards is not a lot of boards. Especially when you have
distributors
> screaming for 50,000 boards to fill their large POs..
>
> Gerald
>
>
>
> On Wed, May 28, 2014 at 3:38 PM, sixvolts
mailto:drewko.

Re: [beagleboard] Re: Using RS485 in the serial ports

[lexduplessis]

 

Hi Robert

I agree with Mickae1 because I have several Debian Images that work 
perfectly but some of the the RS485 structure in serial.h never gets 
changed will applying patch.sh. It says that 
0007-omap-RS485-support-by-Michael-Musset.patch is applied but later when I 
pass the structure in code it gives an error in regards to the the 
directional pin that is not defined or something another which leads me 
back to serial.h which is missing the patched RS 485 structure. Just found 
in those cases to manually edit omap-serial.c and serial.h which resolves 
this problem.

Love your work and do learn something new every day.

Regards

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

Re: [beagleboard] Using Beagle board to get RSSI of a device

[suleman . rai]

Hi Richard,

Thanks for your reply. I am not quite sure how to find out the driver 
for TL-WN722n on our ubuntu systems.  We didn't have to actually install 
any driver on the beagle board (running Ubuntu 12.04 LTS omap) or the stand 
alone PC (Ubuntu 12.04) for our project. Can you assist in helping out to 
find the driver version for TL-WN722n wireless adapter to see if that is 
the reason.

Thanks.


On Tuesday, May 27, 2014 10:31:36 PM UTC+8, RobertCNelson wrote:
>
> On Mon, May 26, 2014 at 4:53 AM,  > 
> wrote: 
> > I am working on a project using BeagleBoard-xM. The goal of the project 
> is 
> > to get received signal strength indicator (RSSI) of a mobile device in 
> the 
> > vicinity of the board. . We use TL-WN722n wireless usb adapter to get 
> RSSI 
> > of a mobile device. 
> > 
> > All the code implementations have been successfully made. We can get 
> RSSI of 
> > a particular device using its MAC Address. However we are encountering a 
> > problem in that the RSSI doesn't change much when we move our device to 
> > different points in the test area. 
> > 
> > If we connect the wireless adapter directly to a PC and run our code on 
> the 
> > standalone PC we get accurate results. However running the same code on 
> the 
> > board doesn't produce the same results. We used tcpdump and wireshark to 
> get 
> > RSSI on the board and we get the same bad results. So this eliminates 
> the 
> > possibility that there is something wrong with the code. 
> > 
> > Can someone provide an insight as to what might be different on the 
> board 
> > compared to a PC that cause this difference in RSSI? 
>
> Are you using the "exact" same linux driver version for the TL-WN722n 
> on both the BeagleBoard-xM and standalone pc? 
>
> 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] How to enable hardware time-stamping function in beaglebone ?

[sun19920218]

I know that AM335x supports IEEE 1588 hardware time-stamping function,
but I can only see beaglebone support software timestamping by entering # 
ethtool 
-T *eth0*.

I want to implement PTP with Linuxptp : http://linuxptp.sourceforge.net/
This website says I must enable CPTS driver for AM335x, and somebody told 
me that I need to make kernel options enable, which are 
CONFIG_PTP_1588_CLOCK  and CONFIG_TI_CPTS .

I found out a config here 
: 
http://kernel.opensuse.org/cgit/kernel-source/commit/?id=3033c3d5de970fcea641776cf8dd136b6dfe7df5
or here : https://dev.openwrt.org/changeset/38692

But I don't know how to get started with it... I am using Angstrom, kernel 
version 3.8.
Could somebody teach me how to enable hardware timestamping function in an 
easy way？ 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] kernel 3.14 + barefs how enable 4Dsystem LCD ?

[info . silvio]

I test 3.14 kernel and barefs debian from Robert nelson, but 4Dcape-43T 
dosent work; no boot logo, no terminal
I want install light debian without Xserver
After i think use QT server.

I use eeewiki.net for BBB for install always on my SDcard.

i test with barefs and minfs, but LCD is always BLACK.
How I enable 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] Custom Beaglbone Black from Circuitco

[Gerald Coley]

I gave you the design for free. All the schematics, CAD files, and BOM. You
are free to build it yourself at any place you want. There is no NRE
charge. No license.

Sorry that I can't be your personal engineering and manufacturing operation.

Gerald



On Thu, May 29, 2014 at 7:50 AM, Eric Fort  wrote:

> Hey, wait!  Gerald does not suck!  Gerald, and the entire beagleboard
> team are awesome and totally rock!  We as a community probably give
> Gerald the most workload and highest amount of stress though.  Yes, we
> have been given a great foundation in beagle on which to build.  If
> you need something substantially more custom you've got much of the
> work already completed, and any rework and redesign not only is your
> own but really ought be contributed back to the community as well (if
> you do a derivitive work of the board rather than a clean sheet)
>
> Eric
>
> On Thu, May 29, 2014 at 4:38 AM, David Farning  wrote:
> > I agree completely.
> >
> > With the understanding that there are shops which can do small custom
> > orders at reasonable prices, the conversation shifts from
> > BeagleBoard.orc / Circuit Co / Gerald sucks for not meeting my
> > specific needs... to how can I build on the foundation that
> > BeagleBoard.org et. al have laid to needs.
> >
> > David
> >
> >
> > On Wed, May 28, 2014 at 11:58 PM, Eric Fort  wrote:
> >> While CircuitCo incurs some risk in expanding production capacity on a
> >> board that "anyone can step in and manufacture a clone" of, and
> >> Embedest *is* making a clone of as a second source I will still hold
> >> out when purchasing beagleboard products for those sourced from
> >> CircuitCo as their quality has always been consistant and of the
> >> highest degree and their servive has been excellent.  So long as
> >> others make the same observation that does help lessen some of the
> >> risk.
> >>
> >> As far as getting circa 100 boards made, I know there are shops that
> >> will do single quantities and with that the case a quantity of 100 is
> >> not unreasonable, just gotta shop around a bit.  I may know a few
> >> places to get you going so if interested, pm me.  then again at a
> >> qty of 100
> http://www.digikey.com/product-detail/en/BB-BBLK-100/BB-BBLK-100-REVC-ND/4842545
> >> may be an option.
> >>
> >>
> >>
> >> On Wed, May 28, 2014 at 6:19 PM, David Farning 
> wrote:
> >>> Some shops are really good at churning out small (100 to 10,000 units)
> >>> runs of a product. They have perfected the art of retooling the line.
> >>>
> >>> In the current situation, it appears that our beaglebone friends are
> >>> in the process of convincing the money people to make the investment
> >>> to increase manufacturing capacity. The new equipment required to
> >>> increase capacity costs serious money.
> >>>
> >>> When one considers that the BBB is open and anyone can step in and
> >>> manufacture a clone and bypass then R&D costs TI and Circuit Co have
> >>> already invested, the risks start getting pretty high.
> >>>
> >>> What might seemed antagonizing slow to us on the outside, requires
> >>> serious thought and planing on the inside. It can be challenging to
> >>> communicate this when companies work as part of communities.
> >>>
> >>> On Wed, May 28, 2014 at 6:32 PM, William Hermans 
> wrote:
>  Gerald, I am just curious. Hypothetically speaking, what would it
> take to
>  retool to make a custom board ? I am not looking for an "IN" or
> anything I
>  am just curious. I'm thinking it would be a huge hassle to say the
> least.
> 
>  I've never worked in a PCB fab before, but worked for a CNC shop many
> moons
>  ago, and retooling for even the most basic part ( door lock keyways
> ), would
>  take a full day or two just for the setup, and a week or slightly
> longer to
>  shake out the bugs. Meanwhile, the company is "losing" money until
> things
>  are running smoothly again.
> 
> 
>  On Wed, May 28, 2014 at 1:42 PM, Gerald Coley  >
>  wrote:
> >
> > 100 boards is not a lot of boards. Especially when you have
> distributors
> > screaming for 50,000 boards to fill their large POs..
> >
> > Gerald
> >
> >
> >
> > On Wed, May 28, 2014 at 3:38 PM, sixvolts 
> wrote:
> >>
> >> There are plenty of things that get built and sold in those kinds of
> >> numbers, like specialized instruments.
> >>
> >>
> >>
> >> On Wednesday, May 28, 2014 3:33:49 PM UTC-5, Robert P. J. Day wrote:
> >>>
> >>> On Wed, 28 May 2014, sixvolts wrote:
> >>>
> >>> > I've been trying to talk to the people CircuitCo about building a
> >>> > run of the beaglebone black boards for a commercial project, but
> I
> >>> > can't seem to get anyone to respond to emails and the two people
> I
> >>> > have phone numbers for are always busy. My understanding was that
> >>> > proper etiquette was to not poach boards from the distributors if
> >>> > you buil

Re: [beagleboard] Custom Beaglbone Black from Circuitco

[Eric Fort]

Hey, wait!  Gerald does not suck!  Gerald, and the entire beagleboard
team are awesome and totally rock!  We as a community probably give
Gerald the most workload and highest amount of stress though.  Yes, we
have been given a great foundation in beagle on which to build.  If
you need something substantially more custom you've got much of the
work already completed, and any rework and redesign not only is your
own but really ought be contributed back to the community as well (if
you do a derivitive work of the board rather than a clean sheet)

Eric

On Thu, May 29, 2014 at 4:38 AM, David Farning  wrote:
> I agree completely.
>
> With the understanding that there are shops which can do small custom
> orders at reasonable prices, the conversation shifts from
> BeagleBoard.orc / Circuit Co / Gerald sucks for not meeting my
> specific needs... to how can I build on the foundation that
> BeagleBoard.org et. al have laid to needs.
>
> David
>
>
> On Wed, May 28, 2014 at 11:58 PM, Eric Fort  wrote:
>> While CircuitCo incurs some risk in expanding production capacity on a
>> board that "anyone can step in and manufacture a clone" of, and
>> Embedest *is* making a clone of as a second source I will still hold
>> out when purchasing beagleboard products for those sourced from
>> CircuitCo as their quality has always been consistant and of the
>> highest degree and their servive has been excellent.  So long as
>> others make the same observation that does help lessen some of the
>> risk.
>>
>> As far as getting circa 100 boards made, I know there are shops that
>> will do single quantities and with that the case a quantity of 100 is
>> not unreasonable, just gotta shop around a bit.  I may know a few
>> places to get you going so if interested, pm me.  then again at a
>> qty of 100 
>> http://www.digikey.com/product-detail/en/BB-BBLK-100/BB-BBLK-100-REVC-ND/4842545
>> may be an option.
>>
>>
>>
>> On Wed, May 28, 2014 at 6:19 PM, David Farning  wrote:
>>> Some shops are really good at churning out small (100 to 10,000 units)
>>> runs of a product. They have perfected the art of retooling the line.
>>>
>>> In the current situation, it appears that our beaglebone friends are
>>> in the process of convincing the money people to make the investment
>>> to increase manufacturing capacity. The new equipment required to
>>> increase capacity costs serious money.
>>>
>>> When one considers that the BBB is open and anyone can step in and
>>> manufacture a clone and bypass then R&D costs TI and Circuit Co have
>>> already invested, the risks start getting pretty high.
>>>
>>> What might seemed antagonizing slow to us on the outside, requires
>>> serious thought and planing on the inside. It can be challenging to
>>> communicate this when companies work as part of communities.
>>>
>>> On Wed, May 28, 2014 at 6:32 PM, William Hermans  wrote:
 Gerald, I am just curious. Hypothetically speaking, what would it take to
 retool to make a custom board ? I am not looking for an "IN" or anything I
 am just curious. I'm thinking it would be a huge hassle to say the least.

 I've never worked in a PCB fab before, but worked for a CNC shop many moons
 ago, and retooling for even the most basic part ( door lock keyways ), 
 would
 take a full day or two just for the setup, and a week or slightly longer to
 shake out the bugs. Meanwhile, the company is "losing" money until things
 are running smoothly again.


 On Wed, May 28, 2014 at 1:42 PM, Gerald Coley 
 wrote:
>
> 100 boards is not a lot of boards. Especially when you have distributors
> screaming for 50,000 boards to fill their large POs..
>
> Gerald
>
>
>
> On Wed, May 28, 2014 at 3:38 PM, sixvolts  wrote:
>>
>> There are plenty of things that get built and sold in those kinds of
>> numbers, like specialized instruments.
>>
>>
>>
>> On Wednesday, May 28, 2014 3:33:49 PM UTC-5, Robert P. J. Day wrote:
>>>
>>> On Wed, 28 May 2014, sixvolts wrote:
>>>
>>> > I've been trying to talk to the people CircuitCo about building a
>>> > run of the beaglebone black boards for a commercial project, but I
>>> > can't seem to get anyone to respond to emails and the two people I
>>> > have phone numbers for are always busy. My understanding was that
>>> > proper etiquette was to not poach boards from the distributors if
>>> > you build a device around the beaglebone and have them produced for
>>> > you. I even spoke to someone at a CircuitCo booth at a conference
>>> > last year (DesignWest - where the beaglebone black was "launched")
>>> > and they indicated this was common already for the original
>>> > beagleboards/bones.
>>> >
>>> > I can't get anyone local interested in building them because of some
>>> > of the minimum order quantities on some of the parts (like the
>>> > emmc).
>>> >
>>> > Anyone a

Re: [beagleboard] Re: MediaTek (Logic Supply) Wi-Fi adapter for BBB and Debian

[Casey Atherton]

Alternatively, you can use the included wicd utility to manage your network 
connections.  To make it work with the UWN200, you will need to edit the 
config file to point to the right interface:
/etc/wicd/manager-settings.conf



Then you can use wicd-curses to connect to your access point.  I set mine 
to autoconnect, and DHCP takes no time at all.  And yes, a 5V AC adapter 
connected to the wall is always recommended when using any peripherals.





On Sunday, May 25, 2014 11:22:49 AM UTC-4, William Hermans wrote:
>
> If you can, and make your IP config static, the interface should come up 
> faster. Also, although I am not sure what it is, I think there is a "fix" 
> to shorten how long it takes for DHCP configs to come up.
>
>
> On Sun, May 25, 2014 at 4:52 AM, Russ Hall 
> > wrote:
>
>> You are right! I studied the Debian documentation yesterday and modified 
>> my /etc/network/interfaces file, and it did work! It isn't fast to come up, 
>> taking about 90 seconds, and probably needs the 5V adapter connected, too. 
>> I made exactly the changes you put here. Quotes should be around the names 
>> in lines 3 and 4.
>>
>>
>> On Saturday, May 24, 2014 10:19:21 AM UTC-5, Trevize Daneel wrote:
>>>
>>> No, you don't need a monitor you should be good. 
>>> You can always check this site for your chipset :
>>> http://en.wikipedia.org/wiki/Comparison_of_open_source_wireless_drivers
>>> also type dmesg to see if you have any errors
>>> type lsmod to see if your kernel module is loaded
>>> But ra0 is your network interface name and iwlist shows it which means 
>>> you have your dongle recognized. 
>>> Have you initialized you network interface?  Type "ifconfig -a" to 
>>> check if you have ra0 listed.If so, add this to your 
>>> /etc/network/interfaces and reboot to and check again. 
>>>
>>>  
>>> auto ra0
>>> iface ra0 inet dhcp
>>> wpa-ssid YOUR-SSID-HERE
>>> wpa-psk YOUR-PASSWORD-HERE
>>>  
>>>
>>>
>>> On Saturday, May 24, 2014 4:29:57 PM UTC+3, Russ Hall wrote:

 The new Debian version did not change non-installation of the Wi-Fi 
 adapter. I still can't figure out what is missing. Here is a sample from 
 terminal:

 debian@beaglebone:~$ iwlist scan

 ra0   Failed to read scan data : Network is down
 loInterface doesn't support scanning.
 eth0  Interface doesn't support scanning.
 usb0  Interface doesn't support scanning.

 debian@beaglebone:~$ iwconfig

 ra0   Ralink STA  
 lono wireless extensions.
 eth0  no wireless extensions.
 usb0  no wireless extensions.

 debian@beaglebone:~$ sudo ifup ra0
 Ignoring unknown interface ra0=ra0.

 debian@beaglebone:~$ 

 This installation is possible via terminal, no? Or must I get a 
 monitor, keyboard, and mouse connected to BBB?


 On Thursday, May 22, 2014 11:34:39 AM UTC-5, Russ Hall wrote:
>
> If anyone could please write a small tutorial on getting this adapter 
> working on the Rev. C BBB it would be appreciated. It was said that 
> Debian 
> already supported this hardware but it does not work. Compiling my own 
> drivers is not user-friendly! I downloaded the driver files from MediaTek 
> and it has 254 files in one directory.
>
  -- 
>> 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] Re: Here is the BeagleBone Debian (beta) image you want to test

[David Farning]

This is a quirk of Debian.

Systemd represents a pretty fundamental shift to Linux distributions.
Conservative distributions like Debian have taken a wait and see
approach before adopting it. As a result the version of systemd in
Debian stable, Sid, is pretty old.

One option would be look at using the current development version of
Debian, Jessie, which will become the next stable release later this
year or early next year.

As with everything it is and engineering trade off; old and stable vs.
new and awesome :)


David

On Thu, May 29, 2014 at 1:00 AM,   wrote:
> On Wednesday, May 28, 2014 2:37:13 PM UTC-7, RobertCNelson wrote:
>>
>> It's there just an older version of systemd where it was prefixed.
>> systemd-
>
> Follow-on question: any risk in moving to the latest version of systemd?
> The version on the flasher is 44, the version on freedesktop.org is 213 and
> two years newer...
>
> --
> 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] BBB with 3.14 + barefs....no LCD 4Dsytem-43T

[silsil]

I use eeewiki.net tutorial fot installing 3.14, u-boot, etc... + debian 
barefs by Robert Nelson.
I've 4Dcape 43-T, but doesnt workit is always black, no boot logo, no 
console
led's is power on.

i test with minfs, but same result's
i test with rootfs with 3.8, and it works well

how i enable LCD cape with barefs or minfs ?


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] Cross compiling for Ubuntu 14.04

[Nuno Sucena Almeida]

On 05/28/2014 08:46 PM, Andrew Core wrote:
> dpkg -i *.deb

In general, not specific to this case, using dpkg -i is usually not
recommended, you could try gdebi (from gdebi-core) to check the
dependencies for you.

regards,
Nuno

-- 
http://aeminium.org/nuno/

-- 
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] Custom Beaglbone Black from Circuitco

[David Farning]

I agree completely.

With the understanding that there are shops which can do small custom
orders at reasonable prices, the conversation shifts from
BeagleBoard.orc / Circuit Co / Gerald sucks for not meeting my
specific needs... to how can I build on the foundation that
BeagleBoard.org et. al have laid to needs.

David


On Wed, May 28, 2014 at 11:58 PM, Eric Fort  wrote:
> While CircuitCo incurs some risk in expanding production capacity on a
> board that "anyone can step in and manufacture a clone" of, and
> Embedest *is* making a clone of as a second source I will still hold
> out when purchasing beagleboard products for those sourced from
> CircuitCo as their quality has always been consistant and of the
> highest degree and their servive has been excellent.  So long as
> others make the same observation that does help lessen some of the
> risk.
>
> As far as getting circa 100 boards made, I know there are shops that
> will do single quantities and with that the case a quantity of 100 is
> not unreasonable, just gotta shop around a bit.  I may know a few
> places to get you going so if interested, pm me.  then again at a
> qty of 100 
> http://www.digikey.com/product-detail/en/BB-BBLK-100/BB-BBLK-100-REVC-ND/4842545
> may be an option.
>
>
>
> On Wed, May 28, 2014 at 6:19 PM, David Farning  wrote:
>> Some shops are really good at churning out small (100 to 10,000 units)
>> runs of a product. They have perfected the art of retooling the line.
>>
>> In the current situation, it appears that our beaglebone friends are
>> in the process of convincing the money people to make the investment
>> to increase manufacturing capacity. The new equipment required to
>> increase capacity costs serious money.
>>
>> When one considers that the BBB is open and anyone can step in and
>> manufacture a clone and bypass then R&D costs TI and Circuit Co have
>> already invested, the risks start getting pretty high.
>>
>> What might seemed antagonizing slow to us on the outside, requires
>> serious thought and planing on the inside. It can be challenging to
>> communicate this when companies work as part of communities.
>>
>> On Wed, May 28, 2014 at 6:32 PM, William Hermans  wrote:
>>> Gerald, I am just curious. Hypothetically speaking, what would it take to
>>> retool to make a custom board ? I am not looking for an "IN" or anything I
>>> am just curious. I'm thinking it would be a huge hassle to say the least.
>>>
>>> I've never worked in a PCB fab before, but worked for a CNC shop many moons
>>> ago, and retooling for even the most basic part ( door lock keyways ), would
>>> take a full day or two just for the setup, and a week or slightly longer to
>>> shake out the bugs. Meanwhile, the company is "losing" money until things
>>> are running smoothly again.
>>>
>>>
>>> On Wed, May 28, 2014 at 1:42 PM, Gerald Coley 
>>> wrote:

 100 boards is not a lot of boards. Especially when you have distributors
 screaming for 50,000 boards to fill their large POs..

 Gerald



 On Wed, May 28, 2014 at 3:38 PM, sixvolts  wrote:
>
> There are plenty of things that get built and sold in those kinds of
> numbers, like specialized instruments.
>
>
>
> On Wednesday, May 28, 2014 3:33:49 PM UTC-5, Robert P. J. Day wrote:
>>
>> On Wed, 28 May 2014, sixvolts wrote:
>>
>> > I've been trying to talk to the people CircuitCo about building a
>> > run of the beaglebone black boards for a commercial project, but I
>> > can't seem to get anyone to respond to emails and the two people I
>> > have phone numbers for are always busy. My understanding was that
>> > proper etiquette was to not poach boards from the distributors if
>> > you build a device around the beaglebone and have them produced for
>> > you. I even spoke to someone at a CircuitCo booth at a conference
>> > last year (DesignWest - where the beaglebone black was "launched")
>> > and they indicated this was common already for the original
>> > beagleboards/bones.
>> >
>> > I can't get anyone local interested in building them because of some
>> > of the minimum order quantities on some of the parts (like the
>> > emmc).
>> >
>> > Anyone at CircuitCo around? I have money and need around 100 boards
>> > made.
>>
>>   not many manufacturers would consider 100 units much of a "run".
>> that's not the sort of number that's going to get you much attention.
>> just an observation.
>>
>> rday
>>
>> --
>>
>> 
>> Robert P. J. Day Ottawa, Ontario, CANADA
>> http://crashcourse.ca
>>
>> Twitter:   http://twitter.com/rpjday
>> LinkedIn:   http://ca.linkedin.com/in/rpjday
>> ===