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

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

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

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] New BBB Cape, should I bother with the EEPROM?

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.

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

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

Re: [beagleboard] Secure state/Monitor mode

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

Re: [beagleboard] Cape no longer working

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

Re: [beagleboard] Cape no longer working

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

Re: [beagleboard] End of Life or wildly popular?

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,

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

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

Re: [beagleboard] BBB Jessie 8.3 boot default eMMC or sd card?

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

[beagleboard] BBB Jessie 8.3 boot default eMMC or sd card?

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

Re: [beagleboard] Beaglebone Green I2C

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

Re: [beagleboard] AWS iot on BeagleBone Green -HelloWorld.js error, aws nodejs sdk example error

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

[beagleboard] Re: Using the BBB for an IoT device

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

[beagleboard] Re: SSH login through UART5

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:

Re: [beagleboard] BeagleBone Cape EEPROM format update

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

[beagleboard] BeagleBone Cape EEPROM format update

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

[beagleboard] Re: Seriously Confused

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

[beagleboard] Re: Seriously Confused

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

[beagleboard] rcn apt repo warning

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

[beagleboard] Re: Accelerated Crypto Functions from C code

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

[beagleboard] [Announce] BeagleBone for Secret Agents

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

[beagleboard] Re: RFC: Add mode setting to bone-pinmux-helper

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

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

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

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

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

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

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

[beagleboard] Re: Programming an arduino remotely using UART4 on the BeagleBone Black

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:

[beagleboard] Device overlays moved from /lib/firmware to ?

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

[beagleboard] Re: Working with python on Beagle Bone Black

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

[beagleboard] Re: i2c write bot working with /dev/i2c-1 in beaglebone black

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

[beagleboard] Re: Some upcoming BeagleBone books

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

[beagleboard] Boot BBB into single user mode

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

Re: [beagleboard] Boot BBB into single user mode

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

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

[beagleboard] The CryptoCape is now available at SparkFun Electronics

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

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

: 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

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

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

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

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

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

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

[beagleboard] Re: BBB: lack of memory

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:

[beagleboard] Re: BBB: lack of memory

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

[beagleboard] Re: UART-4

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

[beagleboard] Re: path of least resistance to Debian

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

[beagleboard] Re: Here is the BeagleBone Debian (rc) image you want to test (2014-04-14)

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

[beagleboard] Re: Here is the BeagleBone Debian (rc) image you want to test (2014-04-14)

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

[beagleboard] Re: Using i2c channel without recompiling the kernel

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

[beagleboard] Cape EEPROM and DTS file for I2C-2

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

[beagleboard] Re: BeagleBone Black Cape Compatibity

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]

[beagleboard] CapeMgr in 3.13?

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 breakpoint

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

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)

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

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

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

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

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

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

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

, 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

[beagleboard] Help with I2C on BBB in Debian

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

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

(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

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

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

[beagleboard] BBB CryptoCape group

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

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

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

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

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]

[beagleboard] OpenSSL with Crypto Acceleration on BBB

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