Hello all,
I am currently working on gesture recognition using OpenCV on Beaglbone
Black.
But i am having a problem while i am opening a window to capture a image
frame.It runs fine at 320x240.
But The screen flickers while i am capturing a image at 640x320 using
webcam from BBB.Same thing
Ok,
now I have
flashed BBB-eMMC-flasher-debian-7.8-console-armhf-2015-02-01-2gb.img to the
eMMC.
After that I did the following steps in the console:
- setting up the network card and nameserver.
# apt-get update
# apt-get upgrade
# apt-get install -y build-essential g++ curl libssl-dev
Thanks for sharing Toni. Here's
http://erlerobotics.com/blog/product/pixhawk-fire-cape/ the board he's
showing, available to everyone who wishes to reproduce.
El jueves, 22 de enero de 2015, 10:16:45 (UTC+1), toni incog escribió:
Master hacker Andrew Trdigell at LCA let bbb fly linux:
Hi everyone,
I'd like to express my gratitude to the community and introduce our work at
Erle
Robotics http://erlerobotics.com where we are pushing forward a Linux
autopilot for making drones based on the BBB.
It's worth mentioning that this initiative comes from the BeaglePilot
Last week at Erle Robotics we had our fist flight with a BBB (video
https://www.youtube.com/watch?v=AEracGWi9wM).
Together with the agreement with Canonical http://ubuntu.com/things we
expect drone apps to start flourishing over the world. BBB hackers you are
probably the right ones to come up
I accidently modified uEnv.txt file located in eMMC of my Beaglebone black.
Now the board is not booting. I can not even see BBB for serial connection
from terra term ( I installed all the drivers for Win 7). How can I get
access to the board? If I can just access to uboot I could reflash or
Hi Chris,
I'm having exactly the same problem. Did you ever find a solution? I'll
give Spark a call tomorrow and see if they might be of any assistance.
When I find an answer I'll be sure to post again.
On Sunday, December 14, 2014 at 7:02:22 AM UTC+4, Chris B. wrote:
Hi!
Just wondering
I had the exact same problem with P8_13. This solved it. Thanks!
On Tuesday, July 29, 2014 at 6:06:55 PM UTC-7, Energia wrote:
I've solved the problem by using pin P9_14 instead of P8_19. There seems
to be some limitations when you use P8_13 (EHRPWM2B) with P8_19 (EHRPWM2A).
--
For more
Hi,
Many thanks for your work on this. Any known issues with serial ports UART4
and UART1? I don't seem to be able to cat them with with the Jessie
2015-02-01 flasher snapshot. They're enabled and the devices are there. No
issues with the current 2014 image.
Many thanks
--
For more options,
I accidently modified uEnv.txt file located in eMMC of my Beaglebone black.
Now the board is not booting. I can not even see BBB for serial connection
from terra term (Windows 7 after drivers are installed). How can I get
access to the board? If I can just access to uboot I could reflash or
This seems to indicate otherwise. http://www.ti.com/product/am3358
Yes it won't be Windows 8 for x86 but Win 8 RT is for ARM and is basically
win 8 anyway.
Also Windows 8 RT is designed for the ARM architecture. Now about how to go
about licensing and acquiring it. I have no clue. I do
Hi,
over the uart port I would like to send out following hexadecimal string
C5C3010076.
Below there is a snippet of the code I have written but at the receiving
end the leading 0's are dropped.
I receive C5C31076 instead.
Could anyone give me a hint or a solution?
unsigned
Hello,
I would like to ask what is the diffewrent between the two kernel
1) kernel 3.8 from git://github.com/beagleboard/kernel.git
2) kernel 3.8 from https://www.kernel.org/
Patrick
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you
Q4: Robert (aka RobertCNelson)
Dear Robert,
With latest https://github.com/RobertCNelson/boot-scripts/tree/master/tools
I ran in a bit of trouble with the
bbb-eMMC-flasher-eewiki-ext4.sh
https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/bbb-eMMC-flasher-eewiki-ext4.sh
vs
Can you try modprobe 'g_ether' and adding g_ether to /etc/modules?
On Friday, February 6, 2015 at 6:32:23 PM UTC-5, Ian Bishop wrote:
Sorry, my lack of Linux knowledge let me down, I was running insmod
FILEPATH/g_ether.ko instead of going to the directory and running insmod.
I've done that
unsigned char tx_buf[9] = {0xC5,0xC3,0x01,0x00,0x00,0x00,0x00,0x00,0x76};
//unsigned is 0255 signed is -128127
unsigned char *p_tx_buf = tx_buf[0]; //points to the first element of
the tx_buf
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because
Thanks for the advice, Graham.
After disabling HDMI by editing uEnv.txt, I was able to gain functionality
of these pins:
8_36 (works but requires EHRPWM1A but that is already in use by 9_14)
8_45 (works but requires EHRPWM2A but that is already in use by 8_19)
8_46 (this one seems to work well)
i am not able to enable two chip select in spi0 ,
so plz provide me proper help
On Fri, Feb 6, 2015 at 10:28 PM, Jason Kridner jkrid...@beagleboard.org
wrote:
Can I assume you are doing 'echo BB-SPIDEV0
/sys/devices/bone_capemgr.*/slots' to enable spi0? Why is it a
problem?
On Fri, Feb 6,
How is that otherwise, you're just repeating exactly what I said:
Windows 8 cannot run on an ARM processor.
Windows RT can, but you're missing lots of drivers. And Windows Embedded
8 has never meant RT. There's Windows Embedded Compact 2013, and Windows
Embedded Handheld...
The only point of
Hi Robert, thanks for all the effort you put into this.
I'm trying the 2015-01-06 testing release with the 3.14 kernel and have
some issues and questions:
1. Since there are SGX modules availible, does that mean that hardware
accelerated graphics are working on this image?
2. I'm
Donovan:
In your Molloy book, read about device trees, which set the default
assignment
of the I/O pins. Also read about the pin-mux. And related topics like
pin-mux helper
and device tree overlays. Then find the reference in the book
to the BBBP8 and BBBP9 header file spread sheets on the
On 2/8/2015 5:25 PM, Sebastian wrote:
2. I'm having trouble understanding the new devicetree setup. I've had a
custom devicetreeoverlay in the old image that was working as expected but
I don't know how to activate it with the new kernel. Though I was able to
find this
Install one of the uSD card based distributions on a uSD card.
Boot from the uSD card, not the on-board eMMC.
cd /mnt
mkdir disk
mount /dev/mmcblk1p2 disk
cd disk
and you will see the root file system on the eMMC.
go find what you broke, and fix it.
sync
shutdown
remove the uSD and see if
23 matches
Mail list logo
