beagleboneblack

So I've properly attached DHT22 Humidity Sensor to my BeagleBone Black Rev C. I'm running OS Mavericks on my MacBook Pro and I followed the directions provided by Adafruit on how to use my DHT22 The website I used was pretty clear: https://learn.adafruit.com/dht-humidity-sensing-on-raspberry-pi-with-gdocs-logging/software-install-updated Also here is the github files I cloned: https://github.com/adafruit/Adafruit_Python_DHT I put in these lines: git clone https://github.com/adafruit/Adafruit_Python_DHT.git cd Adafruit_Python_DHT sudo apt-get upgrade sudo apt-get install build-essential python

here is a very minimal C++11 Thread API code that I am trying to compile #include<iostream> #include<thread> using namespace std; void threadFunction(void) { cout<<"hello from thread:";//<<this_thread::get_id()<<endl; } int main() { std::thread t(threadFunction); t.join(); return 0; } On Compiling this as g++ thread1.cpp -pthread -std=c++11 I get the following error pure virtual method called terminate called without an active exception Aborted What wrong, can someone please help Note that I am compiling this on Beaglebone Black with ARM A8 processor This is a bug in either libstdc++ or Clang,

Has anyone had any success running mongodb on the beaglebone black? do I have to install a different flavor of linux to get this to work or can I use angstrom. MongoDB (as at 2.4) does not officially support ARM processors. You can watch/upvote SERVER-1811 in the issue tracker, however I wouldn't expect this to get much traction until there are 64-bit server-class ARM processors commonly available. In general a 32-bit low power ARM processor with limited memory (512Mb RAM on the BeagleBone Black) is not a great fit for a memory-mapped database server like MongoDB. Due to the use of memory

I'm having trouble getting UART enabled. I've gone through many different directions on how to enable and troubleshoot from updating the uEnv.txt file to updating the kernel. I've come to conclude that it may be an issue with using a different kernel than the instructions, but I'm not sure? I don't know very much about the Beaglebone and I'm still learning. Whenever I try to test UART by using Python and typing the following: import Adafruit_BBIO.UART as UART UART.setup("UART1") I get the error: File "stdin", line 1, in module RuntimeError: Unable to export UART channel. I'm also starting to

Has anybody ported Chipsee 7 inch LCD on Linux kernel 3.14 or later ? Is there any patch available for the same ? If no patches any suggestion porting Chipsee LCD support from Linux kernel 3.8 to Linux kernel 3.14 ? Update: `/* * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/ * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License version 2 as * published by the Free Software Foundation. */ /dts-v1/; #include "am33xx.dtsi" #include "am335x-bone-common.dtsi" &ldo3_reg { regulator-min-microvolt =

With the default Debian installation in a BeableBone Black you can access it via USB as different devices: mass storage device, virtual ethernet and virtual serial uart. This is accomplished with the g_multi module. You can review its configuration via files in /sys/module/g_multi/parameters/ . I am trying to use it only as a mass storage device but with other disk/block device, not the second partition in the boot block device. I have checked that it is always the same partition not matter if it is /dev/mmcblk1p2 (when I have a microSD inserted on boot) or /dev/mmcblk0p2 (without it). I have

As per my understanding chosen node is used to send boot arguments to the kernel. The following is the chosen node of the existing device code (am335x-bone-common.dtsi). chosen { stdout-path = &uart0; }; So, I have modified chosen node to pass kernel arguments. chosen { bootargs = "console=ttyO0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait"; stdout-path = &uart0; }; While bringing up the board I encountered KERNEL PANIC, Here is the log { https://pastebin.com/XHyrsmfG } FYI: These are the u-boot commands issued on serial console(minicom) inorder to port kernel and devicetree using

How do I permanently remove cloud9, bonescript, gateone, etc., from the BeagleBone Black Debian (wheezy) distribution? I can disable them with these commands: systemctl disable cloud9.service systemctl disable gateone.service systemctl disable bonescript.service systemctl disable bonescript.socket systemctl disable bonescript-autorun.service systemctl disable avahi-daemon.service systemctl disable gdm.service systemctl disable mpd.service And the disabling survives a reboot, but sometimes when I install a package, some systemd trigger will re-enable them. How can I permanently remove them? Try