Hi Ron
Did you cater for inputs above 14V? If powering from 12V lead-acid
batteries, they typically charge at 14.4-15V but I'd certainly expect
spikes of higher and I wouldn't want to plug in anything that couldn't take
up to 16V safely. I see you have a 15V zener on there so the regulator
won't
On 9 January 2014 21:51, rh_ richard_hubb...@lavabit.com wrote:
On Thu, 9 Jan 2014 08:36:27 -0800 (PST)
Martin AA6E martin.s.ew...@gmail.com
wrote:
This article by Bruce Schneier is sobering, and it applies to most of
us building embedded systems. Some of us may get security updates
Would plugging and unplugging the usb cause problems?
On kernel 3.8.13, yes it would. Turn it off and on, does it come back up?
If so, try upgrading to kernel 3.13 - should fix your USB issues.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you
I've used a Huawei E3131 USB dongle which has an external antenna socket -
not hard to setup under Linux, as it presents itself as an ethernet
interface. There's nothing BeagleBone specific about setup, the steps
documented here are for debian:
I assume you mean the one at http://lhuet.github.io/blog/? Interesting, I
would have expected more difference between soft/hard float on the BBB.
Your Raspberry Pi results comparison doesn't surprise me at all however!
What a difference Arm7 makes...
On 3 January 2014 10:55, Laurent H.
Hi Bruce
For RS-232 by far the easiest way to do it is order some of these:
http://www.ebay.co.uk/itm/2PCS-High-Compatiablity-USB-to-232-RS232-Adaptor-Converter-PL-2303HX-MAX232-/271358227870.
I've ordered a few, they work well.
There are other types but if it's definitely RS-232 you're using
Try du -shcx /* to see how much disk space directory is taking, then drill
down from there. If I had to guess, and yes I'd suggest /var/log is a good
bet...
On 31 December 2013 04:01, james.wang@gmail.com wrote:
So, I just noticed that after I boot Angstrom on BBB, the available memory
not the cape manager so much,
it's the ability to change the mode of the pins as described here:
https://groups.google.com/forum/#!msg/beagleboard/YqONs50YKWU/VuVsbBhQNl0J.
On 30 December 2013 22:37, Robert Nelson robertcnel...@gmail.com wrote:
On Mon, Dec 30, 2013 at 3:37 PM, Mike Bremford m
was created, a bus scan incorrectly finds no devices.
Thanks Robert!
On 31 December 2013 15:25, Robert Nelson robertcnel...@gmail.com wrote:
Well, i got 3 of these working on 3.13 last night..
On Tue, Dec 31, 2013 at 6:23 AM, Mike Bremford m...@bfo.com wrote:
Uh, well for me it's the virtual
It's P9.18, P9.17 - there's nothing in the logs either I'm afraid.
On 31 December 2013 16:55, Robert Nelson robertcnel...@gmail.com wrote:
On Tue, Dec 31, 2013 at 10:34 AM, Mike Bremford m...@bfo.com wrote:
I see what you're doing, patching am335x which is presumably loaded
directly
Aside from hotplug there is nothing wrong with USB in kernel 3.8.x. I have
even installed, and booted from a USB hard drive using 3.8.13-bone26.
Nope, not the case. My kernel was hanging, no logs, nothing on serial
console under 3.8.13. No hotplugging, good hub etc., no babble interrupt
- the
wrote:
Excellent summary Paulo. I would add one level:
0) Novice user level - Expects a shrink wrapped system to just work
like Windows, but without the crashes ;)
A very Happy New Year to all,
Dave.
On 12/30/2013 03:13 AM, Paulo Ferreira wrote:
On 30/12/2013, at 02:03, Mike Bremford
TI Supports their kernel at
git://git.yoctoproject.org/meta-ti
which contains linux-3.12
Angstrom is based on openembedded-core and meta-openembedded, but is not
using the standard repos.
You need to check out the Yocto-1.5 branch to get access to the latest
stuff though.
If you clone
That's a Java ME class, and I expect you're running Java SE aren't you?
There's no reason that I'm aware of to run the micro-edition on hardware
like the BBB, it's easily got enough grunt to run the full JVM.
I'm accessing GPIO, I2C, SPI from J2SE using JNA (
https://github.com/twall/jna) which
Not sure about the OP, but I'm using
https://github.com/abrasive/shairportand it works well.
On 16 December 2013 14:08, taffson a.hir...@gmail.com wrote:
May I ask what package or projects you use for Airplay receiver emulation?
On Monday, 16 December 2013 02:38:47 UTC+1, Michelangelo
That looks familiar. Try these threads:
https://groups.google.com/forum/#!msg/beagleboard/ge7kwDXxMC8/2ZS4ggbTZBgJ
https://groups.google.com/d/msg/beagleboard/YqONs50YKWU/VuVsbBhQNl0J
On 12 December 2013 13:09, Renato Riolino renato.neocor...@gmail.comwrote:
Hi,
I'm trying to enable all the
I've used SPI exactly once so am far from an expert, but I did successfully
hook up a 16550 series UART using SPI1_D0 as MOSI, SPI1_D1 as MISO,
SPI1_SCLK as SCLK and SPI1_CS0 as the chip select, which worked with
/dev/spidev1.0 (I used SPI mode 0, and I loaded the BB-SPIDEV1 virtual cape
from
There is no UART3 RX, I believe the pin wasn't exposed for some reason.
UART5 works fine (and I too have a GPS wired to it and working nicely)
under kernel 3.8. Although you have to disable the HDMI, see
http://www.logicsupply.com/blog/2013/07/18/disabling-the-beaglebone-black-hdmi-cape/.
You
Why not use a Teensy? http://pjrc.com/teensy. You can set it to emulate a
USB keyboard very easily: plug the Teensy into your Beaglebone and your I2C
into the Teensy, and you're done - no drivers required. They're nice little
boards and very well supported, I've used them for a few projects, and
that causes the
problems for me.
Can you maybe suggest the best way how I should address the UART in my
software, I haven't seen any examples for the UART programming using c/c++
on beaglebone online.
Thanks
On 28 November 2013 18:35, Mike Bremford m...@bfo.com wrote:
It's the shell
I'm really not sure this question at all. UART4 Tx a single wire which is
high by default. Put a multimeter on the uart4tx pin to confirm this. If
you send data to it then it goes out in blocks of N bits (N normally being
10 - start bit, 8 data bits, stop bit), then returns to the default state
Following on from this:
https://groups.google.com/d/msg/beagleboard/ge7kwDXxMC8/2ZS4ggbTZBgJ
Where the HDMI is active despite being apparently disabled, I think I know
why: you can't change the mode of *any* of the pins in kernel 3.12
Here's my test. First, I check the state of the pinmux for
and BB-UART5 for kernel 3.12, I'm attaching them here as well in
bb-uart-dts-312.tar.gz
On 19 November 2013 18:34, Mike Bremford m...@bfo.com wrote:
The .dtbo's distributed with Robert's 3.12 kernel binary exhibit the
symptoms I described, but no I haven't compiled from DTS source (because I
an easy fix.
On 19 November 2013 16:06, selsin...@gmail.com wrote:
On Thursday, November 7, 2013 11:09:09 PM UTC, Mike Bremford wrote:
Not for me they're not! The UART DTBOs are not working correctly under
3.12: BB-UART1 creates /dev/ttyO2, not /dev/ttyO1 as it should. BB-UART2
and 4 are also
I've used Robert Nelsons scripts for this - if you installed using his
kernel and the steps outlined here:
http://elinux.org/BeagleBoardUbuntu#Flasher then you'll have
/boot/uboot/scripts/tools/beaglebone-black-copy-eMMC-to-microSD.sh.
I ran this to backup my eMMC to SD, then verified the results
Search ebay for LM2596 buck converter. Variable output up to 3A, 10 for
$10 from China. I'm running my setup from a 12V car battery through these.
There are buck/boost converters to be had on ebay too, they're a bit more
expensive but still probably cheaper than you can make them yourself.
On 13
If they're analog, surely you'd just hook them up to the analog pins and
read them the normal way? Probably with a couple of resistors to reduce
the voltage range to 1.8V?
http://learn.adafruit.com/measuring-light-with-a-beaglebone-black?view=all
Out of curiousity is there a reason you're using
I switched up to Kernel 3.12 and that certainly fixed my stability issues
with USB - haven't seen any USB related issues since then, wireless is
fine, 3G modem is fine, everything working. Unfortunately I've lost my
UARTs, but that's a different story and no doubt one that will resolve
itself as
, November 9, 2013 5:09:23 AM UTC-5, Mike Bremford wrote:
If they're analog, surely you'd just hook them up to the analog pins and
read them the normal way? Probably with a couple of resistors to reduce
the voltage range to 1.8V? http://learn.adafruit.
com/measuring-light-with-a-beaglebone
Not for me they're not! The UART DTBOs are not working correctly under
3.12: BB-UART1 creates /dev/ttyO2, not /dev/ttyO1 as it should. BB-UART2
and 4 are also incorrectly out by one, and UART5 doesn't load at all.
The UART DTBOs are definitely NOT working correctly under 3.12.
On 7 November
Hi Robert
Thanks for this. I'm still seeing a difference with the UARTs loaded from
the device-tree overlays in /lib/firmware: I ask for BB-UART1, 2, 4 and 5,
I get /dev/ttyO2, ttyO3, ttyO5 and an error in /var/log/syslog -
of_resolve: Could not find symbol 'uart6' (I've disabled the HDMI cape,
31 matches
Mail list logo
