[beagleboard] Re: [beagle-alpha] Default Images and: California: SB-327 Information privacy: connected devices.

[Joshua Datko]

On Fri, Oct 5, 2018 at 1:26 PM Robert Nelson  wrote:

> So to meet (1), should we just use the "serial number" on the side of
> the board, or mac address, etc...?

I don't recall how that sticker is generated but if the board "knows"
that value than I think this would be fine. MACs have the issue of
broadcasting themselves over networks. I believe the point of this
legislation, and IANAL, is to prevent the mass baby-cam like spying
where all credentials are default and never changed.

Thus, while the password is just a sticker on the board, it solves
this requirement.

A more user-friendly one is perhaps a QR code somewhere but has
logistical and supply-chain complications.

>
> Or to meet (2), require use to change default password, the problem,
> #2 States: "before access is granted"...  My initial fix is "after
> access is granted"...

I would agree.

>
> Or Option 3: ship the boards blank... ;)

Would also meet the requirement, but my wink-detection is working I
think, so from a usability perspective, probably not ideal.

>
> and what about "root:root"... do we nuke "root" by default and just
> let the user init it...

Are you asking if the root password should be root and/or if we should
allow root over ssh?

If this was a server (and sometimes beagles tend to be), I think best
practices would be:

- no root login (over ssh or serial)
- ssh via pubkey only

But sometimes the beagle is just this hardware hacking tool, ya know?
And in this case it's a big pain to remember the unique password when
all you want this thing to do is dump a SPI flash and return the
results.

The problem is when a hardware-hacking beagle gets plugged into the
internet with default passwords and then shuts down half the Internet
so somebody's minecraft server gets taken down.

I'm not sure what to recommend. I could see a path where there is the
sticker password and then on first connect there are some init steps
depending on use case. But if you connect with the browser first
(which admittedly, I never do) then this flow probably wouldn't work.

So, changing the default password to the sticker value would otherwise
meet those requirements I think.

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

Re: [beagleboard] New BBB Cape, should I bother with the EEPROM?

[Joshua Datko]

Ah yes, makes sense, 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAC7jEXc2J-yA9_dPiWFXpieC1JyCdqS2nZ3xVEzZjwDxPhkzcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] New BBB Cape, should I bother with the EEPROM?

[Joshua Datko]

I'm making a limited use BBB cape, that uses I2C from P9_19/20 and UART 
from P9_24/26, should I bother putting the EEPROM on there for id? The SRM 
still says yes, but I think the new style is uboot overlays? 

In this case, I know the BBB will always have this cape, and no others, 
attached. (Software later in the boot process can handle with the case when 
it's not really attached).

I know there has been some discussion but the SRM conflicts with that and I 
can't remember the conclusion.

I mean, it's easy enough to put on there but my impression is that it is 
essentially not used anymore by uboot or the kernel.

Thanks,

Josh

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

[beagleboard] Re: [beagle-alpha] Building a device tree overlay for your new PocketCape design

[Joshua Datko]

Hey Jason,

First of all thanks for all the work (and from many others on this) for the
BeagleBone et. al.!

This is just my 2c and it's probably worth that much.

What I would say is that it shouldn't matter that the board uses device
tree or . What designers of capes want, I think, is
the ability to configure the beaglebone (or pocket beagle) as they like.
With the device tree, as you've shown, this is how one accomplishes that
task.

But I'm stumbled through building device tree fragments before and it's a
bit painful.

What I would suggest is a tool that makes device tree generation easier.
This probably should be a GUI (with scripting option). But as a HW designer
for a cape, if I could click pins on a GUI, set modes, defaults, etc... and
out spit a device tree fragment, I would think that'd be cool.

I'm also not volunteering to build this :) But if the device tree fragment
is the output, clearly a nicer frontend can be made to produce this. And I
realize there's all sorts of complexity here, I'm just suggest the idea of
a tool to more easily produce device tree fragments.

Josh

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

Re: [beagleboard] Secure state/Monitor mode

[Joshua Datko]

Last I looked into this, there is a HS (high security) version of the
processor that supports the features you mention. Or, at least secure
boot. I have never been able to find the guy that knows the guy to get
the NDA signed to find out more though.

On Thu, Apr 14, 2016 at 4:03 PM, val  wrote:
>
> Hi, sorry for my english.
> Suppose I want to implement my own firmware for BBB (particularly),
> specifically - UEFI. (In fact, I am working on it, but by now I am to far
> from the hardware part yet.) And also I want at least to try to implement my
> own Secure world software stack (It's not necessarily should relate to UEFI,
> but might be realated to it as well, for example for the Secure Boot stuff,
> UEFI by itself even clearly states it should run in the privileged
> non-secure state on aarch32). Especially - the Monitor software. AM3358
> having cortex-a8 inside it has the Security Extension inside, so the problem
> lays only in availability of TrustZone hardware components for programming
> them for third parties. The TI's TRM on Sitara am3358 states the ROM code
> starts in the secure state and then switches into non-secure state before
> transferring control to its payload, thus to my possible FW. The question
> is, whether third parties like me are able to get into the chain of trust in
> order to supply their own Secure world firmware/OS and especially - the
> Monitor code? Does TI give such a possibility? And if so, what should be
> done from my side? Maybe somebody knows this.
> Thanks!
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

Re: [beagleboard] Cape no longer working

[Joshua Datko]

gpio1_17 is tied to the reset line of the ATmega on the cape and is
meant to be toggled from userspace to allow for, well, resetting.
Besides the obvious this allows users to reset the ATmega to upload
sketches with avrdude (using UART4).

So, while it sounds odd to make it an LED, if that makes it easier to
toggle then writing a 1/0 to the gpio? (I'm not familiar with the LED
feature), then sure, easier is better I think.

gpio1_13 is an input from the ATAES132, so I don't think it would
qualify. I never made a linux driver for that chip and I'm not aware
of people using it (but people tend to be discrete about what they use
crypto hardware for :P )

Lastly, this TPM only uses those i2c pins I believe that the TPM is
(now) setup correctly hardware/software wise.

-- 
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] Cape no longer working

[Joshua Datko]

Great! Thanks so much.

Sorry about missing that for a while, I need to keep up a bit better :/

Josh

-- 
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] End of Life or wildly popular?

[Joshua Datko]

https://www.sparkfun.com/products/12857
On Apr 3, 2016 15:53, "Sean McMahon"  wrote:

> I've been looking around and it appears there are no BeagleBoard Black's
> available for sale.
>
> Is this because it is EOL?  The SRM hasn't been updated since 2014
>
> Thanks,
> Seán
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] Re: versions puzzle with mifare card reader

[Joshua Datko]

Maybe another option is to use libnfc? IIRC, that was all user space and
didn't require the kernel driver.
On Apr 1, 2016 04:58, "toni incog"  wrote:

> fired-up an amd64 jessie and that is working even without libacsccid1,
> puzzling.
>
> --
> 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] BBB Jessie 8.3 boot default eMMC or sd card?

[Joshua Datko]

On Wed, Mar 23, 2016 at 10:34 AM, Robert Nelson  wrote:

> We've kept the instructions the same, recommending users hold the boot
> button, to help work around some issues on versions of u-boot from
> 2013/2014..

Great thanks! I've been pushing that button for so long now... not
pushing it would feel like that scene from LOST ;)

-- 
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 Jessie 8.3 boot default eMMC or sd card?

[Joshua Datko]

Is the default boot the eMMC or the sd card?

I thought it was the eMMC but I'm helping out some friends and they
took the latest Jessie 8.3 console flasher image, stuck in the sd
card, turned on the BBB, and it flashed without holding the user boot
button.

I'm not sure what they were running previously :(

I wouldn't have thought that would work and I don't have a spare BBB
at the moment to try it, so I was wondering if 1.) I'm confused or 2.)
something changed or 3.) someone can upgrade my knowledge of how the
BBB boots.

Josh

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

Re: [beagleboard] Beaglebone Green I2C

[Joshua Datko]

So random potentially-not-helpful-but-maybe-so advice:

UUs indicate that the kernel is using that address, via some module.
So, on your BBB perhaps it's a cape and the module was loaded? UUs I
think, don't necessarily guarantee you have a device there, just that
kernel has loaded a module that's claimed that address (I might be
wrong on this).

But presumably, by "work" you mean that the i2c device (what is it?)
actually works on the BBB besides just showing up?

Also, maybe check a different i2c bus? i.e. do i2c-detect on -r 1/2 etc...



On Thu, Feb 18, 2016 at 12:21 AM, davidj  wrote:
>
> I started working with the Exadler DMCC and a Beaglebone Black for a motor
> control application and it is working OK. I bought some BBG's as they are
> neater for what I am doing (we don't need a power connector or HDMI) but the
> I2C won't work. There are actually 2 I2C boards added to the BBB. I2C
> detects them on the BBB but not the BBG.
>
> The results for i2cdetect are below. I have tried mutliple BBG's with the
> same result.
>
> Working unit (Beaglebone black)
>
> root@beaglebone:/Development/# i2cdetect -r 0
>
>
>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>
> 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
>
> 30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
>
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 70: UU -- -- -- -- -- -- --
>
>
>
>
> The one that won’t work (Beaglebone Green)
>
> root@beaglebone:/Development/# i2cdetect -r 0
>
>
>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>
> 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
>
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 70: -- -- -- -- -- -- -- --
>
>
> Does any one have any suggestions for the cause?
>
> --
> 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] AWS iot on BeagleBone Green -HelloWorld.js error, aws nodejs sdk example error

[Joshua Datko]

Just a guess...

CERT_NOT_YET_VALID means that the X.509 certificate presented to your
beaglebone from AWS has a NOT BEFORE date that is LATER than your
system time. Your time is probably not set correctly on your
beaglebone. Try manually updating your time or installing ntp.

Josh

-- 
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: Using the BBB for an IoT device

[Joshua Datko]

I recommend you look at MQTT. MQTT is a popular pub/sub system and has a 
nice C library 
(https://www.eclipse.org/paho/files/mqttdoc/Cclient/index.html). You need 
the client and then a MQTT broker, and for that I'd recommend running a 
mosquitto server (http://mosquitto.org/) on some version of Linux.

What's nice is that once you have your data in MQTT, you can easily push it 
to pretty much any other thing using those hipster programming languages 
;). If you search around there's a github repo where there are some nice 
MQTT-to-pretty-much-anything plugin for you.

For your setup, you'd run your BBB as the client and either host a MQTT 
server on your LAN (perhaps with another BBB) or run your own MQTT server 
remotely. Than bridge your MQTT server to whatever data mining solution you 
want.

Josh

-- 
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: SSH login through UART5

[Joshua Datko]

I'm not sure why you want to do this, but you'll have a much better time 
using SSH over ethernet.

I would think the path forward involves:

1.) Getting a TCP stack running over serial instead of Ethernet.
2.) Telling sshd to use your serial-tcp-stack.

Maybe start with this: 
https://stackoverflow.com/questions/19941357/tcp-ip-over-serial-port

I imagine it's going to be a lot of hacking together things, but if you can 
get TCP/IP over serial than you might have some luck.

The other thing that comes to mind is that serial is a point-to-point link, 
so why not just screen (open normal tty) to bring up a terminal? If you 
trust the connecting computer and you can physically see the wires 
connecting to the BBB, I think there is a low chance that your serial comms 
will be intercepted. 

Good luck.

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

Re: [beagleboard] BeagleBone Cape EEPROM format update

[Joshua Datko]

Gerald,

That makes sense. It sounds like, from the SRM's standpoint this data
is required whether or not software makes use of it.

Thanks for the response,

Josh

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

[beagleboard] BeagleBone Cape EEPROM format update

[Joshua Datko]

The SRM defines a very specific format for BeagleBone Black cape 
EEPROMs[1]. AFAIK, the only fields that are actually required are the Board 
Name and Version, which is used on boot to load the appropriate DTS file. 
If this is the case can we change the other fields to optional? 

There's a lot of great meta information in there, but if it's not required 
can the documentation be changed to make it explicitly not required?

Josh

[1] Table 17, section 8.2.4, page 101 
of 
https://github.com/CircuitCo/BeagleBone-Black/blob/master/BBB_SRM.pdf?raw=true

-- 
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: Seriously Confused

[Joshua Datko]

Curt Carpenter 1cjcarpenter-fodfmywu...@public.gmane.org writes:

 Am I correct in understanding that there is no documentation that
 would have pointed me to the /sys/bus/iio/devices/iio:device0
 directory and given me some guidance on what it contained?

Ok. You enticed me to provide a more detailed answer :) I started
thinking about the question, How do I use the ADC on this board and the
answer can't be just: use python? I'll try to point out some
assumptions and links to docs. I'm not an expert on this, so perhaps
there is a better way.

1.) You have to know that the linux kernel is the mechanism to provide
software interfaces to the hardware.

2.) The kernel does have documentation for most major
subsystems. Granted, some documentation is in the form of comments,
but it is there. If you downloaded the kernel or use the free electrons
site to search for adc you'd find this:
http://lxr.free-electrons.com/source/drivers/staging/iio/Documentation/overview.txt.
 This
is the root documentation on using the kernel's Industrial I/O subsystem
or IIO. If you root around in that directory, you'll find the
definitive guide to using this interface.

2.a.) The kernel documentation often assumes you are familiar with the
kernel :) It's a bit circular I guess. There is a great book, Linux
Device Drivers, which is available for free:
http://lwn.net/Kernel/LDD3/. The kernel version is quite old now (2.6)
but the *basics* are helpful for understanding what's going on. Just
remember that it was a snapshot in time.

OK. So that's the IIO interface. But how do you know the BeagleBone has
the hardware to use it?

There a few pieces of knowledge you have to connect here. The first is
that one would expect a driver for TI's ADC for the AM335x to be in the
kernel. Some more searching through the sources reveals this:
https://github.com/beagleboard/linux/blob/master/drivers/iio/adc/ti_am335x_adc.c

That looks like a likely candidate. Then, we need a method to map this
driver to the hardware. The more generic question is, how does the
kernel know what hardware lies beneath it? From what I understand, this
is done with the *device tree.* So, you need to find the device tree
file that defines the use of this driver. This looks like it here:

https://github.com/beagleboard/linux/blob/e29980c36939818c225a233284535cff73d9ed53/arch/arm/boot/dts/am33xx.dtsi#L808

But, that's a generic device tree for the AM3XX series, what about the
more specific BeagleBone black? More searching:
https://github.com/beagleboard/linux/search?p=2q=am33xx.dtsi

From there you should see the mapping to the registers in the TRM.

I'm not familiar with the particular driver *at all*, so this may not be
the correct pairing. :) However, this is the process that generally
works for me and I don't think it's too off base. If it is, hopefully
somebody will correct me here.

Josh

-- 
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: Seriously Confused

[Joshua Datko]

Curt Carpenter 1cjcarpenter-fodfmywu...@public.gmane.org writes:

 I keep searching for some sort of definitive guide to using the IO
 capabilities of the board, but have had no luck.  There is nothing on
 software in the SRM, and memory-mapping to the registers described in
 the data sheet seems to be frowned upon.

I know of no definitive guide. There are some well written blog posts
but as with anything on the Internet, it's important to consider the
date it was published.

The bonescript analogRead module can handle this, so you could do all
this from the Cloud9 browser IDE. If you want to use javascript that is,
I prefer python (see next question).


 Can anyone point me to an entry point into all these mysteries?
 Where do I go to find the definitive guide to reading the analog
 inputs under Debian, for example?

Anytime I've done ADC on the Bone I've used this python library:
https://github.com/alexanderhiam/PyBBIO. 

The python snippet is something like this:

import Adafruit_BBIO.ADC as ADC
ADC.setup()
ADC.read(self.pin)

 What commands are available?  Why
 would anyone want to use file IO to do simple GPIO operations when it
 is so much faster to just memory-map the GPIO registers?

This question seems to arise quite often and there are a few right
answers. To me, directly using memory-map regions breaks down a certain
level of software and Linux abstractions. An analogous question,
perhaps, is: Why not just run everything as root? By using Linux from
userspace, you are sacrificing some of the performance but you gain the
ability to use a myriad of third-party libraries and your choice of
programming language.

You probably would get better performance if you made your own kernel
module for whatever you were trying to do, but that may not be the
easiest route if you just want to read an analog value.

Hope some of this helps,

Josh

-- 
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] rcn apt repo warning

[Joshua Datko]

It seems like I'm getting the following warning when doing an apt-get 
update:

Fetched 4596 kB in 24s (184 kB/s)   
   
Reading package lists... Done
W: Size of file 
/var/lib/apt/lists/repos.rcn-ee.net_debian_dists_wheezy_main_binary-armhf_Packages.gz
 is not what the server reported 33143 39486
~  uname -a
Linux hotblack 3.8.13-bone63 #1 SMP Mon Aug 11 20:08:34 UTC 2014 armv7l 
GNU/Linux
~  


It was confirmed by one other person on #beagle.

I don't have proposed resolutions, I'm just noting the issue.

-Josh

-- 
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: Accelerated Crypto Functions from C code

[Joshua Datko]

This is my understanding of the Crypto hardware on the BeagleBone. I've
blogged about it here: http://datko.net/?s=crypto+acceleration but I'll
try to summarize what I've learned. Part of the problem, is that the
crypto hardware on the processor is protected by a NDA from TI (most
crypto hardware is). I have not signed a NDA with TI.

1. I've blogged about this here:
http://datko.net/?s=crypto+acceleration, this is probably the openssl
code to which you are referring.

2. I believe the kernel can access the crypto hardware with the OMAP
drivers. But as the docs are NDA'd, I'm not positive.

3. To use the hardware from userspace, the kernel driver somehow needs
an interface to userspace. I believe the cryptodev module will do
this. Therefore, if you build cryptodev you *should* be able to use the
HW crypto drivers and therefore the hardware.

My assumption is that the OMAP drivers in the kernel provide access to
the crypto hardware on the AM3358. I haven't confirmed this.

If you, or anybody else, wants to pick up this task, I'd be happy to
clarify some of my experiments so far. However, I don't think I have the
cycles to work on this in the near future.

Josh

-- 
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] [Announce] BeagleBone for Secret Agents

[Joshua Datko]

I'd like to announce that my book, BeagleBone for Secret Agents, is now
available at the publisher, Packt Publishing:
https://www.packtpub.com/hardware-and-creative/beaglebone-secret-agents

Dead-tree versions will ship soon, so I'm told.

The book is five chapters, with a self contained project in each
one. Each chapter focuses on a different privacy enhancing technology:

Chapter 1: Sets up a complete embedded IDE with Emacs[1].

Chapter 2: Build a Tor bridge and add a front panel interface to the
bridge to adjust the bandwidth usage.

Chapter 3: Explore BeagleBone capes, in particular, the
CryptoCape. Combines a Fingerprint sensor[2] with the ATmega328p on the
Cape.

Chapter 4: Uses the Trusted Platform Module and a keypad to seal a GPG
on the device.

Chapter 5: IRC all the things! Use the BBB to run a IRC Gateway with
BiltBee and ZNC and configure Off-the-record messaging on each.

Happy Hacking!

Josh


[1] I consider Emacs a privacy enhancing technology. :p
[2] Fingerprint sensors are a bit privacy-removing, but I discuss that
in the book

-- 
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: RFC: Add mode setting to bone-pinmux-helper

[Joshua Datko]

Jason Kridner jkridner-hcmAuCOw+vXj4SYmN/t...@public.gmane.org writes:


 https://github.com/cdsteinkuehler/beaglebone-universal-io/commit/e742ff15f7abbc2cf80141ea49269eb0a2f2a8b3

 Approach looks good to me. I know the dropping of the pin assignment
 in the i2c device tree itself will cause some heartache for some.

 I don't see where you removed the definition of the i2c pin settings
 themselves. Will not removing those entries cause headaches by someone
 assuming they are used or is it comfortable for them to simply be
 there by reference? I suspect it would only be an issue if a bug was
 found in the setting and someone missed that the real mode was coming
 from the helper.


I've been trying to follow along with these changes and I admit, I
haven't been able to keep up.

Some questions:

1. My Cape DTS does not explicitly call out for i2c2 [1], with this
change does that, and all capes using i2c2, need to be fixed?

2. Is the default mode of pins P_19/20, once user space is reached, GPIO
or i2c2?

Josh


[1] 
https://github.com/RobertCNelson/linux-stable-rcn-ee/blob/29723a20cdfe75e81e964739284643ab32a38231/arch/arm/boot/dts/am335x-bone-crypto-00a0.dtsi

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

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

[Joshua Datko]

Tim Cole timcole-bjeeyj9ojedqt0dzr+a...@public.gmane.org writes:

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

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

It's impressively complete.

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

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

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

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

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

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

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

Josh

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

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

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

[Joshua Datko]

Matheus Luiz mortin.luizz-pkbjnfxxiarbdgjk7y7...@public.gmane.org
writes:

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

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

Of course, I might be biased :p


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

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

[Joshua Datko]

murrellr-ywtbtysyrb+lz21kgmr...@public.gmane.org writes:


 1.  Load Putty on my PC.
 2.  Establish a SSH terminal session to the board.
 3.  Write my program using VIM (a horrible program to drop on a
 novice, it has a very steep learning curve) or nano (not much
 better).
 4.  Compile and link my program with gcc, after having to learn its
 command-line interface.
 5.  Run my program under the gnu debugger, another command-line tool
 with a steep learning curve.

I use Emacs. It's much better than vim. (/me ducks and runs after
trolling a holy war... :p )


 So, now my question.  Is there a easy to use, Windows, graphical
 integrated development environment for developing native Angstrom
 Linux programs for this board?


I don't use Eclipse, but those that do AND work on the BeagleBone say
that Derek Molloy has a good tutorial on setting up a GUI IDE:

http://derekmolloy.ie/beaglebone/setting-up-eclipse-on-the-beaglebone-for-c-development/


-- 
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: Programming an arduino remotely using UART4 on the BeagleBone Black

[Joshua Datko]

This is the script I used to upload to an ATmega328p, 3.3V, 8Mhz on
UART4:
https://github.com/jbdatko/BBB_ATmega328P_flasher/blob/master/upload.sh

In the avrdude line I specify 57600, which works well for me. The
OpenROV cape uses an attached ATmega like this and so does the
CryptoCape: https://www.sparkfun.com/products/12773

Josh

-- 
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] Device overlays moved from /lib/firmware to ?

[Joshua Datko]

Where did the device tree overlays move to? They used to be in 
/lib/firmware and I remember discussion of them being consolidated into one 
file, but I can't find that discussion (my google fu is weak today).


I used to echo Cape names to the capemgr to enable the overlay, but I can't 
remember the name of the (virtual) cape and I can't find the list :)


Thanks,


Josh


BBB Version info for reference:


uname -a 
Linux arm 3.8.13-bone60 #1 SMP Mon Jul 7 16:45:52 UTC 2014 armv7l GNU/Linux
cat /proc/version 
Linux version 3.8.13-bone60 (root@imx6q-wandboard-2gb-0) (gcc version 4.9.0 
(Debian 4.9.0-7) ) #1 SMP Mon Jul 7 16:45:52 UTC 2014
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux testing (jessie)
Release: testing
Codename: jessie

-- 
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: Working with python on Beagle Bone Black

[Joshua Datko]

For Python fans, I've found the PyBBIO library to very 
accessible: https://github.com/alexanderhiam/PyBBIO

You'll probably need to ssh into the BBB at some point. You could run 
Python and Twisted and make one of those fancy web apps the kids are 
talking about. Then you could do everything from the desktop. Or you could 
use bonescript and the cloud9 IDE and probably have javascript call python 
code, but that would get weird I think.

-- 
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: i2c write bot working with /dev/i2c-1 in beaglebone black

[Joshua Datko]

The /dev/i2c-* may not correspond to the processor's definition e.g. the
BBB's i2c2 may be mapped to /dev/i2c-1.

I wrote a blog post about this which goes into the details and shows
example C code. This may help: http://datko.net/2013/11/03/bbb_i2c/

The example there is a read, but I've used a similar setup for writes
without issue.

Josh

-- 
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: Some upcoming BeagleBone books

[Joshua Datko]

Phillip,

Thanks for the review comments and posting this!

For those interested in the Secret Agents book, here is a discount code
that you can use to obtain a discounted pre-order: BBSAeB.

Josh

-- 
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] Boot BBB into single user mode

[Joshua Datko]

I'd like to boot my BBB into single user mode. It's a REV C BBB, with 
Debian Jessie (latest RCN image) on a microSD. I tried adding 
mmc_args=single to uEnv.txt but that didn't seem to work.

Any ideas?

Thanks,

Josh

-- 
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] Boot BBB into single user mode

[Joshua Datko]

Spot on, thank you.

Josh

-- 
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] Debian Jessie image md5sum mismatch

[Joshua Datko]

I'm not calculating the same md5sum for the Debian Jessie image located
here: http://elinux.org/BeagleBoardDebian#Debian_Testing_.28jessie.29

The webpage states:

md5sum debian-jessie-console-armhf-2014-07-06.tar.xz
17bb222d1f0f6c81bde902a7a8928a67 debian-jessie-console-armhf-2014-07-06.tar.xz

But I receive:

md5sum debian-jessie-console-armhf-2014-07-06.tar.xz 
21bffa6ea4fb6242a684a507f2f54518 debian-jessie-console-armhf-2014-07-06.tar.xz

I've downloaded it twice with the same result. It does untar but I'm not
sure what to make of the mismatch...

Josh

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

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_ richard_hubb...@lavabit.com wrote:

 On Thu, 29 May 2014 16:17:53 -0700 (PDT)
 Joshua Datko jbda...@gmail.com 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] 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 eric.f...@gmail.com 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 jbda...@gmail.com 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

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

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

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 eric.f...@gmail.com 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 jbda...@gmail.com 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 workTM.

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

[beagleboard] Re: BBB: lack of memory

[Joshua Datko]

If you don't need X, you can reclaim space by removing x11-common. I
like to run on the eMMC myself, mainly because I keep loosing the micro
SD cards :)

I recommend looking through the installed packages and removing what you
don't need. There is a great Debian wiki page on how to do this:
https://wiki.debian.org/ListInstalledPackages .

This command also appears to work as well:

dpkg-query -Wf '${Installed-Size}\t${Package}\n' | sort -n

Lastly, I've seen recommendations to install the wajig package to
determine the size of all packages installed. However, it takes about
14.4 MB:

The following NEW packages will be installed:
  python3 python3-apt python3-minimal python3.2 python3.2-minimal wajig
0 upgraded, 6 newly installed, 0 to remove and 60 not upgraded.
Need to get 4,514 kB of archives.
After this operation, 14.4 MB of additional disk space will be used.
Do you want to continue [Y/n]? n

Ironically, you may not have enough space to install this package :p

Josh

-- 
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: lack of memory

[Joshua Datko]

Sorry, I just realized that you an Angstrom user...

I'm not sure about package management in Angstrom, good luck :)

-- 
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: UART-4

[Joshua Datko]

I did a blog post showing how to use UART4 to talk to an ATmega328p
[1]. My ATmega was at 3.3V though, so you'll need to use logic level
converters (MOSFETs) to convert between your 5V micro and the Beagle,
which operates at 3.3V logic levels. This blog post [2] uses the 5V
version and shows how to use the logic level converters.

If you have a recent debian image, you can enable UART 4 with the
following command:

echo BB-UART4 | sudo tee /sys/devices/bone_capemgr.*/slots

If you don't have the BB-UART4-00A0.dtbo in /lib/firmware, you should
probably upgrade your BBB.

After that command, you should see /dev/ttyO4 appear, which is the UART
you seek.

You may need to change the baud rate of your serial line, do that with
this command:

sudo stty -F /dev/ttyO4 9600

Good luck,

Josh


[1] http://datko.net/2013/11/11/bbb_atmega328p/
[2] 
http://www.instructables.com/id/Program-an-Arduino-using-BeagleBone-without-USB/?ALLSTEPS

-- 
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: path of least resistance to Debian

[Joshua Datko]

I don't always use my Mac, but when I do, I follow this guide:
https://learn.adafruit.com/beaglebone-black-installing-operating-systems/mac-os-x

I have always run with the eMMC flasher image, but space is getting
tight on the 2GB image. I can't speak to performance. If storage is an
issue, you can wait for a rev C with the 4GB eMMC, or use the micro SD.

Not sure about #4.

Josh


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

[Joshua Datko]

I'm downloading the flasher image now to test on the CryptoCape. I'll
let you know how it goes.

Josh

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

[Joshua Datko]

I'm ok with that. As much as I'd like everyone to have a CryptoCape, I'm
fine with users who have a CryptoCape having to download some extra
software. The user must take ownership of the TPM anyway, so I don't
think it should be in the default image.  (Maybe when the Rev C comes
out with 4GB... :p )

Thanks for backporting the driver!

Josh



-- 
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: Using i2c channel without recompiling the kernel

[Joshua Datko]

The bus names are a bit confusing, but the BBB's i2c-2, on pins P19/20,
can be sometimes labeled i2c-1 in Linux.

Anyway, this usually does the trick to get the third i2c bus:

root@arm:~# echo BB-I2C1  /sys/devices/bone_capemgr.8/slots
root@arm:~# ls -l /sys/bus/i2c/devices/i2c-*
lrwxrwxrwx 1 root root 0 Nov  3 21:49 /sys/bus/i2c/devices/i2c-0 - 
../../../devices/ocp.2/44e0b000.i2c/i2c-0
lrwxrwxrwx 1 root root 0 Nov  3 21:49 /sys/bus/i2c/devices/i2c-1 - 
../../../devices/ocp.2/4819c000.i2c/i2c-1
lrwxrwxrwx 1 root root 0 Nov  3 21:50 /sys/bus/i2c/devices/i2c-2 - 
../../../devices/ocp.2/4802a000.i2c/i2c-2

I did a blog post about it here: http://datko.net/2013/11/03/bbb_i2c/

Josh


-- 
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] Cape EEPROM and DTS file for I2C-2

[Joshua Datko]

I'm making a cape that has several devices on the BBB's i2c-2 bus.  Should 
I:

1.) Set the bits in the EEPROM for i2c2?  (in which case I think the mode 
bits should be 0x73?)
2.) Create the I2C-2 fragment in the dts?

Since i2c-2 is enabled by default, do I need to explicitly set it? (this is 
the motivation behind the questions above).  I noticed the Weather cape 
just added the drivers for the attached modules and did not specifically 
create an i2c-2 
fragment: 
https://github.com/beagleboard/cape-firmware/blob/master/dts/cape-bone-weather-00A0.dts

Josh

-- 
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 Black Cape Compatibity

[Joshua Datko]

How does one get a cape on this list?  I've been working with SparkFun to 
build the CryptoCape [1], which I think will be ready in just over a month. 
 Do I need to provide the EEPROM file or just send a cape to someone at 
BeagleBoard.org to test it out?

Josh


[1] http://beagleboard.org/project/cryptocape

On Thursday, May 16, 2013 9:58:16 AM UTC-6, David Anders wrote:

 A list of the status of capes that can be used with the BeagleBone Black 
 can be found at:

 http://www.elinux.org/BeagleBone_Black_Capes


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

[Joshua Datko]

Is the CapeMgr in the 3.13 kernel series?

I installed Debian wheezy via the eMMC flasher script and then upgraded to 
3.13 (http://rcn-ee.net/deb/wheezy-armhf/v3.13.2-bone5/).

However, I don't see the capemgr in /sys/devices nor any message in dmesg:

ls /sys/devices/
44e10800.pinmux  breakpointhdmi.9  ocp.3 pmu.0  soc.1 
system  virtual
ARMv7 Cortex-A8  fixedregulator.8  leds.7  platform  soc0   software 
 tracepoint

Is this supposed to be case?  If so, what is the paradigm to do things like 
this:

echo am33xx_pwm  $SLOTS
echo bone_pwm_P8_13  $SLOTS

(where SLOTS=/sys/devices/bone_capemgr.8/slots)

Thanks,

Josh

-- 
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/groups/opt_out.

[beagleboard] The Hashlet, a secure authentication BeagleBone Black Mini Cape, now available on Tindie

[Joshua Datko]

This is a one-time post to announce that the Hashlet, a secure 
authentication mini-cape that I've developed, is now available on Tindie 
[1].

The Hashlet provides a hardware random number generator, implements the 
SHA256 algorithm in hardware, and enables Message Authentication Codes 
(MACs) through keyed hashes.  It communicates with the BBB over I2C.

I've also developed a command line application that abstracts the details 
of the 80 page datasheet, which is available as GPLv3 code on Github [2]. 
 The hardware design is also on the GitHub page.

Tutorials are posted on my blog [3].

Happy Hacking!

Josh

p.s. I'll be at SparkFun Electronics next week as a hacker-in-residence 
working on the CryptoCape! [4]

[1] https://www.tindie.com/products/cryptotronix/hashlet/
[2] https://github.com/cryptotronix/hashlet
[3] http://cryptotronix.com/blog/
[4] http://datko.net/cryptocape/

-- 
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/groups/opt_out.

Re: [beagleboard] Re: I2C and Invensense MPU6050 Driver

[Joshua Datko]

I'm not sure I understand exactly what you are asking, but you can access
the i2c bus directly through linux file descriptors (i.e. like any other
normal file).  No special device drivers are needed and if you are using
P_19 and P-20, it's enabled by default w/o custom device trees.

I made a blog post of resources which might help:
http://datko.net/2013/11/03/bbb_i2c/




On Thu, Dec 26, 2013 at 9:25 PM, Andrew Dai the...@andrewdai.co wrote:

 Setting the SLEEP bit seemed to have done the trick, everything seems to
 work now! (or at least at the surface)

 I apologize for any beginner questions (this is my first trip into the
 wonderful world of embedded linux). What is the difference between the
 file approach and i2c?
 I was planning on using something like the Adafruit_BBIO library (
 http://learn.adafruit.com/setting-up-io-python-library-on-beaglebone-black)
 and accessing the chip through i2c. My understanding is that that approach
 would be basically the same as using the command line tools (i2cdetect,
 i2cdump/set/get etc). Using this method, I have no use for anything driver
 or device tree related... correct?



 On Mon, Dec 23, 2013 at 4:41 PM, clarkbriggs...@gmail.com wrote:

 Andrew,
 You have made some progress.  i2cdetect can see it.  Your pin connections
 seem to be ok, compared to the ones posted earlier.  According to the
 device docs, it will come up in sleep mode upon power up.   The SLEEP
 bit is apparently Bit6 in Register 0x6B.  Set it to 0 to leave the sleep
 mode.

 Maybe that helps.

 We got as far as using the MPU6050 and the MPU9150 via file I/O thru
 /dev/i2c.  We never got the Invensense driver to work.  It still looks like
 no one replying to the posts here has either.  The disadvantage of the
 file I/O access approach is that it seems very slow compared to the
 relatively few I2C bus cycles required.

 Clark


 On Sunday, December 22, 2013 8:45:23 AM UTC-8, Andrew Dai wrote:

 So has anyone figured out how to get the MPU6050 to respond?
 I dont know too much about how all this works but all I've done is
 root@beaglebone:~# i2cdetect -y -r 1
  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- --
 70: -- -- -- -- -- -- -- --
 root@beaglebone:~# i2cdump -y 1 0x68
 No size specified (using byte-data access)
  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f0123456789abcdef
 00: 81 7d 00 1d 3c cd fc ae 05 44 08 5c 28 8f 6e 90?}.?D?\(?n?
 10: d4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00?...
 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 60: 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00...@
 70: 00 00 00 00 00 68 00 00 00 00 00 00 00 00 00 00.h..
 80: 81 7d 00 1d 3c cd fc ae 05 44 08 5c 28 8f 6e 90?}.?D?\(?n?
 90: d4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00?...
 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 e0: 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00...@
 f0: 00 00 00 00 00 68 00 00 00 00 00 00 00 00 00 00.h..

 I cant get my board (sparkfun breakout board) to respond to anything...
 i2cset doesn't affect the board... did I wire something wrong?
 VDD to Pin 3 (3.3V)
 Gnd to Pin 1
 SCL to Pin 19
 SDA to Pin 20
 VIO to Pin 3 (3.3) -- I'm not quite sure what this does but I get
 nothing back when I disconnect it.

 Any help will be greatly appreciated!

 Thanks,
 Andrew

 On Saturday, November 16, 2013 10:27:19 PM UTC-5, clarkbr...@gmail.comwrote:

 Mark,
 I poked briefly at the reference you provided.  The write up looks very
 much the same as the Invensense MPU6050 driver in the Angstrom on the
 Black.  This seems reasonable.  The Invensense author has done a good job
 of getting it into the Linux tree and the various distributions have picked
 it up.  Apparently, the MPU 60x0 family of MEMS IMUs is widely used and
 popular.
 The Anstrom driver reads nice.  No one here has yet to get it to load
 and respond.
 Clark
 On Thursday, November 14, 2013 1:40:35 PM UTC-8, Mark A. Yoder wrote:

 It looks like someone has done a nice port to Andriod[1].  How hard
 would it be to port it to Angstrom?

 --Mark

 [1] 

Re: [beagleboard] Re: Help with I2C on BBB in Debian

[Joshua Datko]

Thanks Maycon,

That did the trick.

Josh


On Sun, Oct 27, 2013 at 8:53 AM, may...@magsoft.com.br wrote:

 Sory, please read...
 echo BB-I2C1  /sys/devices/bone_capemgr.??**??/slots
 Maycon


 On Sunday, October 27, 2013 12:50:32 PM UTC-2, may...@magsoft.com.brwrote:

 The Debian maps the i2c-0 to i2c0, and i2c-1 to i2c2, if you use
 echo BB-I2C2  /sys/devices/bone_capemgr.??**??/slots
 this enables i2c-2 maped to i2c1 on BBB in all cases the bus is
 configured with pull-ups, be careful with
 capacitance in line, long wires can add...
 i2c0 - internal
 i2c1 - pins 17-18
 i2c2 - pins 19-20
 Maycon

 On Saturday, October 26, 2013 4:38:27 PM UTC-2, Joshua Datko wrote:


 In the default Debian imagine, can any I2C bus be used from the P9
 expansion header, without rebuilding the kernel?  If so, which pins?  (19 
 20, or 17  18?)

 When I run i2cdetect, I have two I2C buses, but I'm not sure which buses
 they map to on the BBB:

 i2c-0 i2c OMAP I2C adapter I2C adapter
 i2c-1 i2c OMAP I2C adapter I2C adapter

 Assuming I have a working I2C slave device, if I wire SDA to P9_20, SCL
 to P9_19, 3.3V power to P9_3, GND to P9_1, would one expect the device to
 show up on the i2c bus (the breakout board already has a pull-up resistor)?

 Josh

  --
 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/7reYt7Tmdjs/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/groups/opt_out.


-- 
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/groups/opt_out.

Re: [beagleboard] Re: I2C and Invensense MPU6050 Driver

[Joshua Datko]

So I've been struggling with I2C.  Somebody on this list gave me the tip to 
do:

echo BB-I2C1  /sys/devices/bone_capemgr.??**??/slots

which enables the third I2C bus and my device then was visible via 
i2cdetect -y -r 1 on pins P9_19 and P9_20.  Although, after doing that, 
you'll have an i2c1 and a i2c2 bus, so might want to check both.  But, I'm 
not quite sure why this works :)

In my case, I don't think there is device tree entry for the device I'm 
using, so I was planning on interacting with it over raw I2C.

Hope this helps,

Josh


On Thursday, October 31, 2013 2:32:46 PM UTC-6, Jason Kridner wrote:

 On Tue, Oct 29, 2013 at 2:19 PM, Jason Kridner 
 jkri...@beagleboard.orgjavascript: 
 wrote: 
  
  On Thu, Oct 17, 2013 at 6:12 PM,  clarkbr...@gmail.com javascript: 
 wrote: 
   AIW: 
   I went back thru the adafruit library and didn't find anything 
 specific on 
   I2C, although it is listed as a topic.  I have been looking at their 
 github 
   adafruit-beaglebone-io-python library. I also found and looked thru 
 PyBBIO. 
   Even tho I'm not using Python, I can see the access mechanisms that 
 they 
   use. 
   I can use the MPU6050 device ok enough just reading via 
 /dev/i2c/i2c-x, but 
   that is too slow. 
   I'm trying to figure out how to invoke and use the inv-mpu6050 driver 
 and 
   adafruit doesn't use that. 
   Thx -- Clark 
   
   On Thursday, October 17, 2013 9:47:44 AM UTC-7, AIW wrote: 
   
   Some good info on I2C tools at http://www.acmesystems.it/i2c. 
   
   Python and the adafruit BBIO I2C library makes it very easy to use 
 I2C on 
   Beaglebone Black as well. Python import smbus is fairly easy to use 
 too. 
   Some examples of use is available in the code I provide for my radio 
 project 
   herewww.aiwindustries.com. 
   
   Not trying to sell the product, but I know that the I2C function was 
   giving me some issues so I'm just trying to help the community. 
 Python code 
   is available to download and look at usage so feel free. 
   
   On Tuesday, October 15, 2013 5:02:59 PM UTC-5, 
   clarkbr...@gmail.comwrote: 
   
   We are using the Invensense MPU6050 IMU on I2C with Beaglebone Black 
   (Angstrom 3.8.13). We can use I2C-tools and file I/O thru /dev/i2c 
 but the 
   read speed is disappointingly slow.  We only read the 3x gyros and 
 3x accels 
   (each one byte at a time plus the 2 byte temperature reading) and it 
 takes 
   ~2msecs.  My estimate of the I2C bus cycles for a block read 
 suggests this 
   should take ~160 bus cycles or .38msec on a 400MHz I2C bus. 
  
  You are running at 400kHz, not 400MHz, right?  I2C doesn't do 400MHz. 
  
   
   The distribution includes the Invensense driver inv-mpu6050.ko but 
 there 
   is no indication that reading through /dev/i2c invokes it.  This is 
 a very 
   popular IMU and Invensense widely distributes the driver over many 
 Linux 
   platforms.  The driver source includes “successful installation will 
 create 
   two directories under /sys/bus/iio/devices” and lists the files 
 there (aka 
   functions). I can never get these to show up. 
   
   I can “insmod 
   
 /lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050/inv-mpu6050.ko” and 
   “echo inv-mpu6050 0x68  /sys/class/i2c-adapter/i2c-1/new_device”. 
 This 
   causes a new directory named 1-0068 to show in 
   /sys/class/i2c-adapter/i2c-1with entries like name and modalias but 
 no 
   functions.  It never shows in /sys/bus/iio/devices. 
  
  I don't have an MPU6050, but I just ordered a couple on express 
  overnight from Sparkfun. 

 I bought https://www.sparkfun.com/products/11028 and played with it 
 briefly before being distracted and again today, but I don't 
 understand why I'm not able to get it to reply to me. 

 I have the following connections: 
 VCC: P9_4 (VDD_3V3) 
 GNC: P9_1 (GND) 
 INT: P9_11 (GPIO) 
 FSYNC: - 
 SCL: P9_19 (I2C2_SCL) 
 SDA: P9_20 (I2C2_SDA) 
 VIO: P9_3 (VDD_3V3) 
 CLK: - 
 ASCL: - 
 ASDA: - 

 I then perform: 

 root@beaglebone:~# i2cdetect -y -r 1 
  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 
 00:  -- -- -- -- -- -- -- -- -- -- -- -- -- 
 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
 50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 
 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
 70: -- -- -- -- -- -- -- -- 

 Very confused why it doesn't show up. 

 Since you have it responding to you, how do you have it wired? 

  
  Here's the behavior I'm seeing without the board connected: 
  
  root@beaglebone:/lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050# 
 ls 
  inv-mpu6050.ko 
  root@beaglebone:/lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050# 
  dmesg | tail -1 
  [ 2992.799594] i2c i2c-1: new_device: Instantiated device inv-mpu6050 at 
 0x68 
  

Re: [beagleboard] Re: I2C and Invensense MPU6050 Driver

[Joshua Datko]

Nevemind, that may be unrelated.  I just rebooted and my device enumerated 
fine.  I think what's confusing (me) is the I2C2 by the SRM (P9_19/20) 
shoes up as I2C1...

some output:

ebian@arm:~$ ls -l /sys/bus/i2c/devices/i2c-*
lrwxrwxrwx 1 root root 0 Nov  1 04:02 /sys/bus/i2c/devices/i2c-0 - 
../../../devices/ocp.2/44e0b000.i2c/i2c-0
lrwxrwxrwx 1 root root 0 Nov  1 04:02 /sys/bus/i2c/devices/i2c-1 - 
../../../devices/ocp.2/4819c000.i2c/i2c-1
debian@arm:~$ su
Password:
root@arm:/home/debian# i2cdetect -r 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n] Y
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --



On Thursday, October 31, 2013 9:57:08 PM UTC-6, Joshua Datko wrote:

 So I've been struggling with I2C.  Somebody on this list gave me the tip 
 to do:

 echo BB-I2C1  /sys/devices/bone_capemgr.??**??/slots

 which enables the third I2C bus and my device then was visible via 
 i2cdetect -y -r 1 on pins P9_19 and P9_20.  Although, after doing that, 
 you'll have an i2c1 and a i2c2 bus, so might want to check both.  But, I'm 
 not quite sure why this works :)

 In my case, I don't think there is device tree entry for the device I'm 
 using, so I was planning on interacting with it over raw I2C.

 Hope this helps,

 Josh


 On Thursday, October 31, 2013 2:32:46 PM UTC-6, Jason Kridner wrote:

 On Tue, Oct 29, 2013 at 2:19 PM, Jason Kridner jkri...@beagleboard.org 
 wrote: 
  
  On Thu, Oct 17, 2013 at 6:12 PM,  clarkbr...@gmail.com wrote: 
   AIW: 
   I went back thru the adafruit library and didn't find anything 
 specific on 
   I2C, although it is listed as a topic.  I have been looking at their 
 github 
   adafruit-beaglebone-io-python library. I also found and looked thru 
 PyBBIO. 
   Even tho I'm not using Python, I can see the access mechanisms that 
 they 
   use. 
   I can use the MPU6050 device ok enough just reading via 
 /dev/i2c/i2c-x, but 
   that is too slow. 
   I'm trying to figure out how to invoke and use the inv-mpu6050 driver 
 and 
   adafruit doesn't use that. 
   Thx -- Clark 
   
   On Thursday, October 17, 2013 9:47:44 AM UTC-7, AIW wrote: 
   
   Some good info on I2C tools at http://www.acmesystems.it/i2c. 
   
   Python and the adafruit BBIO I2C library makes it very easy to use 
 I2C on 
   Beaglebone Black as well. Python import smbus is fairly easy to use 
 too. 
   Some examples of use is available in the code I provide for my radio 
 project 
   herewww.aiwindustries.com. 
   
   Not trying to sell the product, but I know that the I2C function was 
   giving me some issues so I'm just trying to help the community. 
 Python code 
   is available to download and look at usage so feel free. 
   
   On Tuesday, October 15, 2013 5:02:59 PM UTC-5, 
   clarkbr...@gmail.comwrote: 
   
   We are using the Invensense MPU6050 IMU on I2C with Beaglebone 
 Black 
   (Angstrom 3.8.13). We can use I2C-tools and file I/O thru /dev/i2c 
 but the 
   read speed is disappointingly slow.  We only read the 3x gyros and 
 3x accels 
   (each one byte at a time plus the 2 byte temperature reading) and 
 it takes 
   ~2msecs.  My estimate of the I2C bus cycles for a block read 
 suggests this 
   should take ~160 bus cycles or .38msec on a 400MHz I2C bus. 
  
  You are running at 400kHz, not 400MHz, right?  I2C doesn't do 400MHz. 
  
   
   The distribution includes the Invensense driver inv-mpu6050.ko but 
 there 
   is no indication that reading through /dev/i2c invokes it.  This is 
 a very 
   popular IMU and Invensense widely distributes the driver over many 
 Linux 
   platforms.  The driver source includes “successful installation 
 will create 
   two directories under /sys/bus/iio/devices” and lists the files 
 there (aka 
   functions). I can never get these to show up. 
   
   I can “insmod 
   
 /lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050/inv-mpu6050.ko” and 
   “echo inv-mpu6050 0x68  /sys/class/i2c-adapter/i2c-1/new_device”. 
 This 
   causes a new directory named 1-0068 to show in 
   /sys/class/i2c-adapter/i2c-1with entries like name and modalias but 
 no 
   functions.  It never shows in /sys/bus/iio/devices. 
  
  I don't have an MPU6050, but I just ordered a couple on express 
  overnight from Sparkfun. 

 I bought https://www.sparkfun.com/products/11028 and played with it 
 briefly before being distracted and again today, but I don't 
 understand why I'm not able to get it to reply to me. 

 I have the following connections: 
 VCC: P9_4

[beagleboard] Help with I2C on BBB in Debian

[Joshua Datko]

In the default Debian imagine, can any I2C bus be used from the P9 
expansion header, without rebuilding the kernel?  If so, which pins?  (19  
20, or 17  18?)

When I run i2cdetect, I have two I2C buses, but I'm not sure which buses 
they map to on the BBB:

i2c-0 i2c OMAP I2C adapter I2C adapter 
i2c-1 i2c OMAP I2C adapter I2C adapter

Assuming I have a working I2C slave device, if I wire SDA to P9_20, SCL to 
P9_19, 3.3V power to P9_3, GND to P9_1, would one expect the device to show 
up on the i2c bus (the breakout board already has a pull-up resistor)?

Josh

-- 
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/groups/opt_out.

Re: [beagleboard] How to create a Debian eMMC flasher image?

[Joshua Datko]

Thanks Robert,

I ran the setup_sdcard.sh like this: sudo ./setup_sdcard.sh --img
myimage.img --dtb beaglebone --uboot bone.  This seemed to do the trick.
 The script complained about dependencies, which I installed, but it
probably should also check for the parted package.  Parted was not
originally installed, which caused the script to fail. I'll look around the
script and see if I can submit a pull request.

It looks like I can add packages in /var/pkg_list.sh.  But if I wanted to
add a repo besides the normal repositories, like one would normally do to
/etc/apt/sources.list, I didn't see (or understand) how I could set this up.

Josh



On Thu, Oct 24, 2013 at 8:14 PM, Robert Nelson robertcnel...@gmail.comwrote:

 On Thu, Oct 24, 2013 at 9:03 PM, Joshua Datko jbda...@gmail.com wrote:
 
  How does one build the Debian eMMC flasher image from
  http://elinux.org/BeagleBoardDebian#eMMC:_BeagleBone_Black ?
 
  First of all, thanks to R. Nelson for making this, it's great!
 
  I'd like customize the kernel and add some packages and provide a similar
  image of my own.  I think I'm good with how to create and configure the
  kernel, but I don't get how to create a rootfs and then install armhf
  packages into the rootfs so that I can bundle up everything.

 So it's just a two stage process.

 https://github.com/RobertCNelson/omap-image-builder
 First using omap-image-builder i just run the ./build_image.sh script

 Which create the base console image you see here:
 http://elinux.org/BeagleBoardDebian#Demo_Image

 Next the setup_sdcard.sh is ran with --img filename vs --mmc
 /dev/sdX and the --bbb-flasher is enabled that enables/runs this
 script on bootup:


 https://github.com/RobertCNelson/tools/blob/master/scripts/beaglebone-black-copy-microSD-to-eMMC.sh

 that flashes the eMMC...

 Note: the omap-image-builder script was more written for consistency
 and building all the images i push out every month then for ease of
 use. Sometimes it's easier to just fork the repo and copy the
 build_kernel.sh script and minimize it for your own needs..

 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 a topic in the
 Google Groups BeagleBoard group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/beagleboard/gkVwuE7324U/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/groups/opt_out.


-- 
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/groups/opt_out.

[beagleboard] How to create a Debian eMMC flasher image?

[Joshua Datko]

How does one build the Debian eMMC flasher image from 
http://elinux.org/BeagleBoardDebian#eMMC:_BeagleBone_Black ?

First of all, thanks to R. Nelson for making this, it's great!

I'd like customize the kernel and add some packages and provide a similar 
image of my own.  I think I'm good with how to create and configure the 
kernel, but I don't get how to create a rootfs and then install armhf 
packages into the rootfs so that I can bundle up everything.

Thanks,

Josh

-- 
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/groups/opt_out.

[beagleboard] BBB CryptoCape group

[Joshua Datko]

I'm working on BBB Cape that extends the cryptographic capabilities of the 
BBB, aptly called the CryptoCape[1].  For those that are interested in 
helping or lurking, I've setup a Google group[2] which is open to the 
public so feel free to sign up.

While this list is amazing, I want a lower-volume and more topic-focused 
area to talk about adding trusted boot capabilities, crypto acceleration 
and the like.

Josh

[1] http://beagleboard.org/project/CryptoCape/ 
[2] https://groups.google.com/forum/#!forum/cryptocape

-- 
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/groups/opt_out.

Re: [beagleboard] Re: OpenSSL with Crypto Acceleration on BBB

[Joshua Datko]

Thanks George!

The haveged project looks interesting, I'll have to check it out.

In the case anyone wants to help pick this up, these are my notes so far:

1. There are various documents that mention the HW_RNG.[1][2]

2. I've tried to configure the TRNG in kernel 3.8.13-bone26 and I did
not see Devices-Char Devices-Hardware Random (etc..)-OMAP4 Random

3. OMAP RNG appears to depend on CONFIG_HW_RANDOM  (
CONFIG_ARCH_OMAP16XX || CONFIG_ARCH_OMAP2PLUS ).[3] I believe
CONFIG_HW_RANDOM is set and CONFIG_ARCH_OMAP2PLUS was set.

4. There were some patches back in August[4] on this.  But it wasn't
clear to me whether they are in 3.8.13 or not.

I was planning on the following approach:

1. Try building the kernel to see if omap-rng builds a .o or a .ko
2. Try grabbing a later kernel to see if it's there.
3. Try applying the patches directly.
4. Re-visit my assumption that CONFIG_ARCH_OMAP2PLUS is enabled,
because then, based on the logic above, I shouldn't see the OMAP-RNG.

If I make any breakthroughs, I'll keep the list posted.  If others are
working on this, please do the same!

Josh


Footnotes:

[1] http://www.ti.com/lit/wp/spry198/spry198.pdf

[2] http://processors.wiki.ti.com/index.php/Cryptography_Users_Guide

[3] http://cateee.net/lkddb/web-lkddb/HW_RANDOM_OMAP.html

[4] http://comments.gmane.org/gmane.linux.ports.arm.omap/102520

On Tue, Oct 8, 2013 at 12:07 AM, George B geor...@gmail.com wrote:
 Hmm, looks like:

 apt-get install haveged

 was all I needed.  While it isn't the hwrng, it is a nice entropy generator.

 http://freecode.com/projects/haveged


 On Monday, October 7, 2013 10:58:55 PM UTC-7, George B wrote:

 I would be very interested in this topic as well.  The application I have
 in mind for this BBB relies on making varying amounts of SSL connections.
 In a test today I believe I ran the pool out of entropy and some handshakes
 would hang for a while before completing (typical SSL handshake would take
 about 1/2 a second but some would hang for 2 to 4 seconds before
 completing).  Basically the performance is such that I can't use it for the
 desired application but getting the hwrng working would likely change
 everything.  This unit is operating headless with no kbd/mouse or anything
 except network connected.  I finally did break down and installed rng-tools
 to use /dev/urandom to seed /dev/random but I see that as basically a
 quick/dirty workaround.  Even tried adding randomsound to add some entropy
 but that didn't seem to make any difference.

 On Friday, October 4, 2013 11:43:14 AM UTC-7, Joshua Datko wrote:

 I have not yet tried to get the HWRNG working on the BBB.  According
 to the TI Crypto page [1], you just need to reconfigure your kernel
 and it should add /dev/hwrng support.  If anybody has gotten this
 working recently, I'd like to know :)

 Josh

 [1] http://processors.wiki.ti.com/index.php/Cryptography_Users_Guide

 On Fri, Oct 4, 2013 at 12:25 PM, rh_ richard...@lavabit.com wrote:
  On Fri, 4 Oct 2013 13:29:24 -0400
  Przemek Klosowski
  przemek@gmail.com wrote:

 --
 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/ZFrCs9ZHCP4/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/groups/opt_out.

-- 
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/groups/opt_out.

Re: [beagleboard] Re: OpenSSL with Crypto Acceleration on BBB

[Joshua Datko]

I have not yet tried to get the HWRNG working on the BBB.  According
to the TI Crypto page [1], you just need to reconfigure your kernel
and it should add /dev/hwrng support.  If anybody has gotten this
working recently, I'd like to know :)

Josh

[1] http://processors.wiki.ti.com/index.php/Cryptography_Users_Guide

On Fri, Oct 4, 2013 at 12:25 PM, rh_ richard_hubb...@lavabit.com wrote:
 On Fri, 4 Oct 2013 13:29:24 -0400
 Przemek Klosowski
 przemek.klosow...@gmail.com wrote:


 Eh, AES is AES: given the key, the encrypted bits sent on the network
 must be the same whether generated in software or hardware. The
 breakage, if real, is in the infrastructure, such as the RNG for key
 generation.

 So then I need to make sure that the kernel is configured not to use hardware
 like neon to do the RNG part of ssl encryption but it's ok to accelerate AES 
 for
 ssl. Is this right?

 --
 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/ZFrCs9ZHCP4/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/groups/opt_out.

-- 
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/groups/opt_out.

[beagleboard] OpenSSL with Crypto Acceleration on BBB

[Joshua Datko]

OpenSSL with Crypto Acceleration on BBB

I'm excited to say I've got OpenSSL using crypto acceleration working on 
the BBB using debian!  (at least, I'm pretty sure based on my OpenSSL tests 
;) )

The quick instructions are:

1. Download R. Nelson's kernel headers for Debian (since that's what I was 
using).
2. Make the cryptodev kernel module*
3. Recompile OpenSSL to use CRYPTODEV

*I had to tweak arch/arm/include/asm/timex.h to change the line
#include mach/timex.h to read: #include
usr/src/linux-headers-3.8.13-bone26/arch/arm/include/asm/timex.h

Detailed instructions are on my website:
http://datko.net/2013/10/03/howto_crypto_beaglebone_black/

Josh

Here's the output of the openssl-tests:

Without cryptodev

debian@arm:~/openssl-1.0.1e/cryptodev-linux-1.6$ time openssl speed -evp 
aes-128-cbc
Doing aes-128-cbc for 3s on 16 size blocks: 2666405 aes-128-cbc's in 2.99s
Doing aes-128-cbc for 3s on 64 size blocks: 905987 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 256 size blocks: 240811 aes-128-cbc's in 2.99s
Doing aes-128-cbc for 3s on 1024 size blocks: 61145 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 8192 size blocks: 7677 aes-128-cbc's in 3.00s
OpenSSL 1.0.1e 11 Feb 2013
built on: Mon Mar 18 21:48:12 UTC 2013
options:bn(64,32) rc4(ptr,char) des(idx,cisc,16,long) aes(partial) 
blowfish(ptr)
compiler: gcc -fPIC -DOPENSSLPIC -DZLIB -DOPENSSLTHREADS -DREENTRANT 
-DDSODLFCN -DHAVEDLFCNH -DLENDIAN -DTERMIO -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-DFORTIFY_SOURCE=2 -Wl,-z,relro -Wa,--noexecstack -Wall
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
aes-128-cbc 14268.39k 19327.72k 20617.93k 20870.83k 20963.33k

real 0m15.114s
user 0m15.031s
sys 0m0.041s

With cryptodev

debian@arm:/usr/local/ssl/bin$ time /usr/local/ssl/bin/openssl speed -evp 
aes-128-cbc
Doing aes-128-cbc for 3s on 16 size blocks: 28166 aes-128-cbc's in 0.04s
Doing aes-128-cbc for 3s on 64 size blocks: 22445 aes-128-cbc's in 0.03s
Doing aes-128-cbc for 3s on 256 size blocks: 29933 aes-128-cbc's in 0.05s
Doing aes-128-cbc for 3s on 1024 size blocks: 16018 aes-128-cbc's in 0.04s
Doing aes-128-cbc for 3s on 8192 size blocks: 4861 aes-128-cbc's in 0.02s
OpenSSL 1.0.1e 11 Feb 2013
built on: Fri Oct 4 01:48:18 UTC 2013
options:bn(64,32) rc4(ptr,char) des(idx,cisc,16,long) aes(partial) 
idea(int) blowfish(ptr)
compiler: gcc -DOPENSSLTHREADS -DREENTRANT -DDSODLFCN -DHAVEDLFCNH 
-DHAVECRYPTODEV -DUSECRYPTDEVDIGESTS -march=armv7-a -Wa,--noexecstack 
-DTERMIO -O3 -Wall -DOPENSSLBNASMMONT -DOPENSSLBNASMGF2m -DSHA1ASM 
-DSHA256ASM -DSHA512ASM -DAESASM -DGHASH_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
aes-128-cbc 11266.40k 47882.67k 153256.96k 410060.80k 1991065.60k

real 0m15.326s
user 0m0.225s
sys 0m5.990s

-- 
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/groups/opt_out.