Re: [beagleboard] Re: [BBB][Angstrom Distribution] [RS485] Applying a custom Patch
Zachary, For your information, you don't need anymore to patch the kernel :p = https://github.com/RobertCNelson/linux-dev/commit/823fd45781f6e176ee1dc87062c95a010c7af588 On Tue, Jan 28, 2014 at 4:21 PM, Zachary Thorson zachthor...@gmail.comwrote: Now, I have developed an application which is combination of both send and recv. I mean , after sending one byte on UART from BBB to other host machine, I just wait for input bytes to receive(added receive timepout at 10 sec). Now in this cae, even if I do not send any character from host machine, BBB detects one/two arbitary bytes. Could you clarify what you mean by this? I am assuming you are essentially using one host as a master and one as the slave. Do you mean when neither end is transmitting, you are seeing arbitrary bytes, or that when the master sends a request out, you that same master sees bytes even if nothing is transmitted by either host? If the random bytes are all 0's or all 1's (0x00, 0xFF) that might indicate some problems in what the non-driven state of the line voltage is. If the bytes seem similar to what was being transmitted, you might be getting reflections if the line is not terminated properly. This seems that driver changes GPIO position (from send mode to recv mode) before transmitte buffer gets empty. Is this a guess from the behavior, or did you watch the signal lines, or use printk statements in the patch? Did any one has face this problem? Can you guys please share your thoughts on this? I have not seen this issue and have been using the patch at 38400 baud with an ADM2582 chip for a number of months now. -- 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. -- 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] Re: Connect two BeagleBoneBlack between USB serial cable with IP over USB
Ok thanks, i've made that yesterday. First BeagleBone: - Use default configuration as 192.168.7.2 as hardcoded ip and standard udhcp configuration that release 192.168.7.1 Second BeagleBone: - I've setted hardcoded default usb0 ip to 192.168.8.2 and udhcp to release 192.168.8.1. In this way i've solved the ip conflict. Wiring (i've attached a scheme): I've connected USB Host Port of BeagleBone 2 to USB mini port of BeagleBone 1. The Main problem is that: If i use hotplug and connect the USB Host after bootup, i can see the new Eth1 interface on Beaglebone 2, in this way i can use ifconfig to set manually the eth1 ip to 192.168.7.1 as like the Beaglebone 2 was the PC. In Coldplug way, with the usb host connected before the boot to usb min i see that only one ip interface is bring up in the BBB where i've connected the USB host. Why? Where i can work to adjust this ? Thanks, in advance Il giorno giovedì 30 gennaio 2014 00:49:50 UTC+1, Brandon I ha scritto: Yes it is! The beaglebone gets the ip from a hardcoded value and the dev PC gets the ip from a dhcp server running on the beaglebone. The beaglebones usb ip is set and the dhcp server is launched in the /usr/bin/g-ether-load.sh script, called by the the g-ether-load.service (run systemctl status g-ether-load to view details). At the bottom of this script you'll see: /sbin/ifconfig usb0 192.168.7.2 netmask 255.255.255.252 /usr/sbin/udhcpd -f -S /etc/udhcpd.conf That first line sets the beaglebones ip and subnet mask, the second fires up the dhcp server using the configuration file /etc/udhcpd.conf, seen here: start 192.168.7.1 end192.168.7.1 interface usb0 max_leases 1 option subnet 255.255.255.252 The start and end is the address range the server can assign to the dev PC. The subnet limits the network to http://www.subnet-calculator.com/the addresses 192.168.7.1 - 192.168.7.2 (with a broadcast address of 192.168.7.3). The problem is, when you attach two beaglebones to the same dev PC, the dhcp server on each beaglebone assigns an address of 192.168.7.1. Your dev PC says, wait, I can't have to interfaces with the same IP so refuses it...but, even if more ips were allowed, the dhcp protocol has no way to handle this crazy network topology, so everything gives up. To make two work on the same pc, change the hardcoded beaglebone ip in /usr/bin/g-ether-load.sh and the dhcp ip range in /etc/udhcpd.conf to a different subnet. Sticking with the 255.255.255.252 subnet mask, which allows 2 ips and a broadcast ip, the next subnet starts at 192.168.7.4, so assign the beaglebone to 192.168.7.5 and the dhcp range to 192.168.7.4 (or flipping the ips would work too, it's an arbitrary selection). -Brandon On Wednesday, January 29, 2014 1:32:01 AM UTC-8, Andrea Pola wrote: It's possible to connect two BeagleBoneBack using the IP over USB. One is acting like Dev PC and may have the 192.168.7.1 address and the other act as normal BBB using 192.168.7.2 address. I'm trying to do it, and i'm encountering problem. Someone has made anything about 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/groups/opt_out. attachment: Screenshot from 2014-01-30 10:03:56.png
[beagleboard] BBB and Franlkin U600 Mobile Broadband
My main goal is to find a Mobile Broadband (ie GSM or CDMA) radio that I can provide internet to my BBB with. I have purchased the Franklin U600 which works fine on desktop Ubuntu and windows 7. When I plug this USB device into the beagle bone and boot, it always freezes without fail after a short period. Doing a lsusb -vvv nearly always crashes it. The board locks up, and the LEDs freeze (usually 2 stuck on and 0,1,3 off). I have tried the following images: BBB-eMMC-flasher-2013.05.27.img BBB-eMMC-flasher-ubuntu-13.10-2014-01-24-2gb.img demo_beaglebone_BBB-eMMC-flasher-2013.09.04.img ubuntu-saucy-13.10-armhf-3.8.13-bone30.img All of these are running kernel 3.8. Looking at the output lsusb the U600 shows up as: Bus 001 Device 000: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB This leads me to believe that the U600 internally shows up as a USB hub (windows reports ~5 devices when plugged in for the very first time). Is it correct that 3.8 has a new device tree structure that may be causing reliability issues? Is there a BBB image that has an older kernel than 3.8 ? Thanks! Resources: http://askubuntu.com/questions/230168/how-to-make-franklin-u600-usb-modem-work http://f1sty.blogspot.com/2012/12/setting-up-sprint-3g4g-modem-franklin.html -- 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] BeagleBone Black: v3.8.13-bone37 kernel flash slowly fills up
On Wed, Jan 29, 2014 at 11:06 PM, Craig Mehan craigleeme...@gmail.com wrote: Ok I have done the pastebinits that you requested. Appears they sent ok. The memory usage was a bit more under control this flashing session, but still high and growing. A little miss-communication. You kinda need to share the http links... On usb devices connected, what started all this is trying to get the Asus USB-BT211 bluetooth dongle to work with the Beaglebone Black. I don't really remember if the dongle was plugged in for my original email. The pastebinits that were sent, do not have the dongle plugged in. After I did the pastebinits, I did plug in the dongle and did not see any real change in the memory used or rate of memory used. Although with both the first email I sent and this email I have not installed the bluetooth or atheros modules. On the bluetooth dongle subject, it appears I chose poorly from both experience and from the Google posts on this dongle. I did finally get the dongle to light up and pair with my phone after I did an aptitude install firmware-atheros. But, then the memory problem started rearing its head and I have not been back to that problem. I appreciate your attention to this and am happy to provide anymore data or run any tests needed. 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 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] Re: Angstrom Linux: Opencv and Python
Could you assist a beginner. I tried to run these on my BBB but I get the following error below. I have the latest Angstrom installed and updated. Please help! Downloading http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/libopencv-core2.3_2.3.1-r3_armv7a.ipk. wget: server returned error: HTTP/1.1 404 Not Found Collected errors: * opkg_download: Failed to download http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/libopencv-core2.3_2.3.1-r3_armv7a.ipk, wget returned 1. On Saturday, August 24, 2013 5:48:23 AM UTC-5, lacaym...@gmail.com wrote: Hmm... It seems that experts don't want to help beginners. :( Finally I found myself how to solve this problem by enter the following commands step by step by Terminal: opkg install http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/libopencv-core2.3_2.3.1-r3_armv7a.ipk opkg install http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/libopencv-imgproc2.3_2.3.1-r3_armv7a.ipk opkg install http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/libopencv-highgui2.3_2.3.1-r3_armv7a.ipk opkg install http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/libopencv-flann2.3_2.3.1-r3_armv7a.ipk opkg install http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/libopencv-features2d2.3_2.3.1-r3_armv7a.ipk opkg install http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/libopencv-calib3d2.3_2.3.1-r3_armv7a.ipk opkg install http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/libopencv-objdetect2.3_2.3.1-r3_armv7a.ipk opkg install http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/libopencv-ml2.3_2.3.1-r3_armv7a.ipk opkg install http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/libopencv-video2.3_2.3.1-r3_armv7a.ipk opkg install http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/libopencv-legacy2.3_2.3.1-r3_armv7a.ipk opkg install http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv7a/python/python-opencv_2.3.1-r3_armv7a.ipk -- 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: Availability - how come nobody has any BeagleBone Black to sell?
I saw 3 on the shelf at Microcenter in Marietta GA On Wed, Jan 29, 2014 at 4:38 PM, GauchoMan gord.fin...@gmail.com wrote: Gerald, I see on http://www.elinux.org/Beagleboard:BeagleBoneBlack#Board_Shipmentsthat there have been 11,375 shipped so far in January. I have had Qty 1 on back-order from Digikey since Jan 13th. I would have assumed that enough boards must have shipped to Digikey this month to cover back orders, and yet I am still waiting for one board? Any clues as to what is happening here? Regards, Gord Finlay On Monday, January 20, 2014 5:19:20 AM UTC-8, Gerald wrote: We are shipping boards as you can see form the daily updates on the support Wiki. They go to the distributors. They fill their back orders. No stock shows up because they are going to fill the back orders. When the distributors have extra boards, they will then show up as having inventory. Gerald On Sun, Jan 19, 2014 at 3:46 PM, skip...@gmail.com wrote: Have there been any 'official announcements' about the lack of stock yet? -- 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...@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. -- 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] Re: debian: test images (2014-01-29) (resend with correct topic..)
Which init script is enabled by default ? Do we have a choice of what init system to use ? Is this image also coming with a X server and desktop manager or it can be used as a minimal console only ? On Wednesday, January 29, 2014 9:25:22 PM UTC, RobertCNelson wrote: Lets keep this going, round 4... First, for tracking please report all bugs to: http://bugs.elinux.org/projects/debian-image-releases Fixes: 3.8.13-bone37 - 3.8.13-bone39 * rs485 support from Micka * dir-changeable propery for gpio-of-helper from Charles * cape-bone-proto from me *(new default pinmux) New Packages: python-pip, python-setuptools, python2.7-dev Fixes: systemd: limit journal to 8Mb (should fix ever expandign /var/logs issues) cape-bone-proto loaded on bootup by /etc/default/capemgr chromium: 32.0.1700.76 - 32.0.1700.102 nodejs: 0.10.24 - 0.10.25 https://github.com/beagleboard/am335x_pru_package.git /opt/source/am335x_pru_package multiarch: added /lib/ld-linux.so.3 (for those HelloWorld users with the wrong gcc armel compiler..) Adafruit_BBIO installed default apache moved from port 80 to 8080 (bonescript.socket takes over port 80) grow_partition.sh script for users of the microSD image.. * cd /opt/scripts/ * git pull * ./tools/grow_partition.sh * sudo reboot * (after a few minutes, df -h should use the whole disk..) bonescript-autorun.service enabled LCD3/LCD4/LCD7 users, xinput_calibrator is installed by default.. Can you please compare 3.8.13-bone36 with 3.8.13-bone39 to test Micka's touchcreen fix? I've tried to make it very easy to test via: cd /opt/scripts/tools sudo ./update_kernel.sh --kernel v3.8.13-bone36 sudo rm /etc/pointercal.xinput sudo reboot cd /opt/scripts/tools sudo ./update_kernel.sh --kernel v3.8.13-bone39 sudo rm /etc/pointercal.xinput sudo reboot So please compare and contrast bone36/bone39, as we really need testing from users.. Camera people (3.1MP and RadiumBoards): What userspace programs are we missing? gstreamer? OpenCV plugins? I really want to include a default shell script that'll take a picture and allow end users to validate the 3.1/Radium capes work.. (it'll be installed under /opt/scripts/capes/) Or even some html5 bone101 voodoo and show the image in the browser window? Questions? Should we switch to connman? (i'm still testing this too..) To test: apt-get remove wicd-* --purge apt-get install connman (no good gui with connman) Does your cape work? Does your wifi adapter work? Are we missing it's firmware? So go forward and test the first beta release. There are 3 files on the web server, depending on what you want to do. Using the same standard procedure found here: http://elinux.org/Beagleboard:Updating_The_Software http://rcn-ee.net/deb/testing/2014-01-29/ 3cc218e9303c6823035585364e2de2c0 ./BBB-eMMC-flasher-debian-7.3-2014-01-29-2gb.img.xz d7e00474379a85edcf6385bc9584466c ./bone-debian-7.3-2014-01-29-2gb.img.xz 2d0c043b311cc31bd6286c4c2058b174 ./debian-7.3-lxde-armhf-2014-01-29.tar.xz An eMMC flasher which can be installed to any 2GB or greater microSD card. [BBB-eMMC-flasher-debian-7.3-2014-01-29-2gb.img.xz] http://rcn-ee.net/deb/testing/2014-01-29/BBB-eMMC-flasher-debian-7.3-2014-01-29-2gb.img.xz It takes about 10-15 Minutes to dd microSD (2GB), 15 minutes to flash eMMC (look for full 4 LED's) 2GB standalone image that can be flashed to any 2GB or greater. [bone-debian-7.3-2014-01-29-2gb.img.xz] http://rcn-ee.net/deb/testing/2014-01-29/bone-debian-7.3-2014-01-29-2gb.img.xz It takes about 10-15 Minutes to dd microSD (2GB) To resize once booted: * cd /opt/scripts/ * git pull * ./tools/grow_partition.sh * sudo reboot Finally one of my classic setup_sdcard.sh. [debian-7.3-lxde-armhf-2014-01-22.tar.xz] http://rcn-ee.net/deb/testing/2014-01-29/debian-7.3-lxde-armhf-2014-01-29.tar.xz Note for users who use my classic setup_sdcard.sh script, here is the magic options to get the beaglebone project files + systemd. sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot bone --beagleboard.org-production --enable-systemd To rebuild git clone git://github.com/beagleboard/image-builder.git cd image-builder git checkout bb.org-v2014.01.29 -b tmp touch release ./beagleboard.org_image.sh 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 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: Availability - how come nobody has any BeagleBone Black to sell?
The line is moving and we are looking to get more parts in house sooner to increase the output. All it takes is one single part and we can't build a board. Gerald On Wed, Jan 29, 2014 at 5:33 PM, Ronny Julian k4rjjra...@gmail.com wrote: I saw 3 on the shelf at Microcenter in Marietta GA On Wed, Jan 29, 2014 at 4:38 PM, GauchoMan gord.fin...@gmail.com wrote: Gerald, I see on http://www.elinux.org/Beagleboard:BeagleBoneBlack#Board_Shipments that there have been 11,375 shipped so far in January. I have had Qty 1 on back-order from Digikey since Jan 13th. I would have assumed that enough boards must have shipped to Digikey this month to cover back orders, and yet I am still waiting for one board? Any clues as to what is happening here? Regards, Gord Finlay On Monday, January 20, 2014 5:19:20 AM UTC-8, Gerald wrote: We are shipping boards as you can see form the daily updates on the support Wiki. They go to the distributors. They fill their back orders. No stock shows up because they are going to fill the back orders. When the distributors have extra boards, they will then show up as having inventory. Gerald On Sun, Jan 19, 2014 at 3:46 PM, skip...@gmail.com wrote: Have there been any 'official announcements' about the lack of stock yet? -- 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...@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. -- 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. -- 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] Re: chipsee beaglebone lcd/dvi expansion kernel support
Hey, thank you very much for this, display and touch works excellent! Can you help me with *serial ports*? I cant get RS232 ports on Chipsee to work. Maybe need some more configuration... -Jukka torstai, 23. tammikuuta 2014 20.12.25 UTC+2 xris@googlemail.com kirjoitti: Hey guys, As promised. Ubuntu 12.04 BBB image for the Chipsee 7” 1024x600 LCD touchscreen. Grab it here: http://www.fileswap.com/dl/sdFGPZoIw6/ You should find yourself downloading bbb-ubuntu-12.04-for-community.xzhttp://www.fileswap.com/dl/sdFGPZoIw6/bbb-ubuntu-12.04-for-community.xz.html Just extract and write that to your SD card (4gb expected) with something like: *cat bbb-ubuntu-12.04-for-community.xz | xz -d /dev/sdX* Note it’s a raw sector dump NOT a tarball, so extract straight to your SD card device. (eg. /dev/sdx, NOT /dev/sdx1) Also note this image doesn’t install or boot from MMC so make sure you’ve got the SD card selected on the boot switch thing. Once the extract is complete, simply slap it into the BBB and boot. It should come up with the Chipsee splash screen but then boot into Ubuntu 12.04 after a while. Hope this helps. l8r, Xris. -- 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] PPS Support from GPIO
On 29/01/14 21:29, Lee Armstrong wrote: However isn't it actually pin 31? pin 31 (44e1087c) 0027 pinctrl-single that's pin 31 in the pinmux table, it's not a simple relationship from pinmux number to gpio number on my kernel there's 141 items in that list, but there are only 118 gpios. gpios0,12 have 32 pins, gpio 3 only has 22... according to the datasheet anyway... If you look in the kernel source.. arch/arm/mach-omap2/mux34xx.c seems to contain the mapping, although I can't say I understand how to read it I'm still not getting a PPS input there but am wondering now if the GPS needs a fix before it even outputs one at all. Probably, most gps modules I've encountered only output pps after you get a fix, the EM406A I'm using is like that. Depends on the module, but you may be able to check with an LED attached to the pps output. My EM406A has a 1uS pps pulse width, so you need a scope to see that. -- 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: debian: test images (2014-01-29) (resend with correct topic..)
On Wed, Jan 29, 2014 at 10:50 PM, vermins...@gmail.com wrote: Robert: Thanks for putting this up. I have the 2GB SD Image working and, thanks to your easy script, was able to expand it to use my entire 8Gb SD card. I'm sorry, but I'm still fairly new to this, so forgive me if I'm perplexed by simple things:) On my older Debian install, based on your eewiki from a few months ago, I was able to add both Dallas 1wire support and also enable the ADC's by adding the following line to uEnv.txt optargs=capemgr.enable_partno=BB-ADC,BB-W1 I already had compiled the BB-W1-00A0.dtbo based on HipsterCircuits blog example, and copied it to /lib/firmware This worked fine on the older Debian SD version But on today's new one, only the BB-ADC gets loaded into slot. I also tried only loading BB-W1, and only BB-ADC, and again, only BB-ADC works. The thing that confuses me is that if instead, after loading BB-ADC via uEnv.txt, I am in /lib/firmware and issue: echo BB-W1:00A0 /sys/devices/bone_capemgr.9/slots I then see that the BB-W1 overlay has been loaded and the one-wire temp sensor works as expected. Any clues? Thanks I'm not sure why, capemgr.enable_partno hasn't been as reliable.. Just edit /etc/default/capemgr and replace the one define to BB-W1 * and reboot.. it should load your BB-W1 on the next boot.. * Only one cape is support at this point, it was a quick hack.. See: https://github.com/beagleboard/image-builder/blob/master/target/init_scripts/capemgr-debian.sh https://github.com/beagleboard/image-builder/blob/master/target/init_scripts/capemgr 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 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: debian: test images (2014-01-29) (resend with correct topic..)
On Thu, Jan 30, 2014 at 4:48 AM, iustinian.in...@gmail.com wrote: Which init script is enabled by default ? The ones i enable.. Do we have a choice of what init system to use ? systemd: unless you disable it.. Is this image also coming with a X server and desktop manager or it can be used as a minimal console only ? It includes lxde, but you could remove it easily.. But I think your missing the point of this Image, so go read: http://beagleboard.org/blog/2014-01-04-happy-new-year/ The purpose of this image is to TEST what the next default image will be on the boards shipped. If your doing something custom, take a look here: http://elinux.org/BeagleBoardDebian#Demo_Image For a more minimal image.. 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 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: debian: test images (2014-01-10)
On Wed, Jan 29, 2014 at 8:38 PM, Louis McCarthy compeo...@gmail.com wrote: Darn , I was hoping I narrowed it down 800 x 480 is my resolution. Come to think of it, I think the last lock ups were through HDMI, to a 1680 x 1050 monitor. Nope there goes that theory, 480x272.. 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 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: Volumio - Audiophile Music Player on Beaglebone Black
Please see - resolved http://volumio.org/forum/prevent-my-hdmi-monitor-from-sleeping-while-playing-audio-t519.html On Tue, Jan 28, 2014 at 1:48 PM, vkarmar...@gmail.com wrote: Can you please clarify how to modify uEnv.txt so that the HDMI port (including music) does not blank after 10 minutes? On Tuesday, December 31, 2013 10:04:52 PM UTC-5, Gerald wrote: It would need to go out the HDMI port. HDMI has and audio channel embedded in it. Gerald On Tue, Dec 31, 2013 at 6:46 PM, James Yeo jpas...@gmail.com wrote: I'm a bit unclear - the BBB doesn't have an audio jack, so does this stream the audio, or...? Sorry if I'm being dense. On Sunday, December 15, 2013 7:38:47 PM UTC-6, Michelangelo Guarise wrote: Hi Beagleboard folks!!! I'm really glad to announce that Volumio http://volumio.org has been released! Volumio is the porting of the RaspyFi distro, which you may have seen on Raspberry Pi. But what does Volumio?? Volumio will turn your BeagleBone Black into an headless music player. Just connect the tiny Beagle to your home Network and to a DAC. You will then be able to control the music playback with your phone, tablet or PC. Wirelessly! Volumio has 2 main goals: to sound amazingly good and to be easy and confortable to use. Just download it, flash to SD Card, hit the user button and you're ready. You can then grab your tunes from a NAS (Samba or NFS), from External Drives (a powered hub is suggested) or listen to your favourite Web Radios. You can also use it as an Airport receiver to stream your tunes from compatible devices! Last but not least, with an Android app you can configure several Volumio powered beagles to play simoultaneously to obtain multiroom audio! This project comes with tons of passion and love for music. And thanks to Beagleboard for giving such an amazing board to work with. The performance on Beagleboard Black are really exciting! CURRENT FEATURES: -Ready to play: flash it and you're ready -Audiophile Quality: bit perfect playback -FLAC, WAV, MP3, AAC, ALAC, PLS support -Music libraries on Samba, NFS and USB drives -Webradios support out of the box -Control it via integrated Webui with PC, Smartphone, Tablet -Airplay capability -Ramplay Support -DSD Native Playback -Multiroom Playback via Android App -Output playback device Selection -Audio out via HDMI, USB, Analog Jack, S/PDIF, I2S (depends on platform) -Compatible with all UAC2 compliant USB DACs -Wireless Network configuration -Various resampling options, up to 32bit/384khrtz You can grab it at volumio.org Very eager to know what you guys think of it! -- 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...@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 a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/QBeRpTB8Z7k/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: problems with webcams
Thank you very much for both of your responses. I will take a look at the
code you both suggested.
In response to Matthew, the ODroid so far has proven to be great at almost
everything. I have already turned off auto exposure and auto focus. The
platform I have the camera on moves often near and far from objects as well
as vibrates, so these of course caused issues.
The webcam seems to get the higher frame rate with no issue when I use
external applications, such as Cheese. I even used framegrabber and
another application someone made for the BBB to test and was able to get 30
fps. The problem seems to be directly related to OpenCV and how it uses
v4l. Even if the resolution (in OpenCV) is set to the lowest resolution,
the fps still maxes at 15fps. This rate is found with just image capture,
so no other processing is performed. This seems like a hard limit that
OpenCV is causing specifically on the ODroid setup.
On Wednesday, January 29, 2014 8:41:54 PM UTC-5, Matthew Witherwax wrote:
To piggy back on Mike's response, when we were testing the capture rate of
the BBB, we used a modified version of framegrabber that is attached to
this article
http://blog.lemoneerlabs.com/post/bbb-optimized-opencv-mjpeg-stream
It allows you to set all the parameters the regular framegrabber accepts
but converts each frame to an OpenCV Mat. It is C code and as another word
of warning, I won't say the code is any less sloppy than Mike's :) It was
written for testing purposes.
The article itself details how to compile OpenCV to use NEON and
libjpeg-turbo courtesy of Mike.
I am surprised to hear the ODroid has trouble capturing higher than 15
fps. I recently bought a Wanboard Quad, but the ODroid was on my short
list.
A few things to consider:
Have you tested with framegrabber to see if you can capture the raw frames
at a speed greater than 15 fps? It could be that OpenCV is the bottle neck
and perhaps you should recompile it per Mike's instructions.
Is auto exposure turned off? Even with the frame rate set to 30 fps, in
low light conditions, the camera increases exposure time to compensate
leading to about 15 fps.
Good luck, and as Mike said, if you need help, we will do out best.
On Wed, Jan 29, 2014 at 4:02 PM, Michael Darling
fndrpl...@gmail.comjavascript:
wrote:
All you have to do is adapt the frame grabber code for your needs. I
actually went ahead and rewrote the capture code to be object oriented so
that I could conveniently use it with OpenCV's C++ interface. You might
find some of my code helpful as an example to work from. It is in a public
git repo:
https://github.com/mdarling39/LinuxVision/blob/master/
I think you would primarily be interested in taking a look at CamObj.hpp,
CamObj.cpp, and v4l2Cap.h, v4l2Cap.cpp, and/or v4l2_c.h and v4l2_c.c. As a
word of warning, my code is sloppy and specific for my needs, but it does
what I need it to do. Feel free to borrow from it and modify it to your
heart's content.
I actually don't remember how all of this stuff works anymore, but you
can look at main_threaded.cpp to see how I am using v4l2_c.h to get frames
into a cv::Mat object. If I remember right, I had to abandon the
object-oriented approach for some reason so that later so that I could
implement multi-threading using pthreads. I think the magic you are looking
for is in the function v4l2_process_image(cv::Mat, const void), where the
frame buffer is actually decoded and saved to a cv::Mat object. Once you
have that, you're home free and can just deal with OpenCV.
static void v4l2_process_image(cv::Mat img, const void *p)
{
cv::Mat buff(img.cols, img.rows, CV_8UC3, (void*)p);
img = cv::imdecode(buff,CV_LOAD_IMAGE_COLOR);
}
I hope that helps you to get started. If you need any help, just ask.
I'll do my best to help where I can.
Good luck,
Mike
On Wed, Jan 29, 2014 at 11:52 AM, Learning Opencv
epsilo...@gmail.comjavascript:
wrote:
I am working with the C920 on an ODroid, similar to the BBB. I am also
having a problem capturing more than 15fps in OpenCV, however, I need to
use OpenCV for doing processing on the video. Since I am not just grabbing
frames, I can't do something like framegrabber. Is there anyone who has
done this and have a solution. I have tried changing settings on v4l
before running my code, but have had no luck.
Thanks.
On Monday, November 4, 2013 7:07:58 AM UTC-5, Matthew Witherwax wrote:
Glad to hear our work is helping others. Let us know how your
endeavors go.
-Matthew
On Sun, Nov 3, 2013 at 3:22 PM, josiasina...@gmail.com wrote:
Excellent, excellent thread! I just purchased my BBB yesterday for a
personal project, and I've been reading for many many hours how and what
would be the best way to stream video from the BBB to a PC over WiFi with
the lowest latency as I could get. This thread, including all
[beagleboard] Re: chipsee beaglebone lcd/dvi expansion kernel support
I get the splash screen, but that is all. Any ideas? On Thursday, January 30, 2014 3:43:47 AM UTC-6, xris@googlemail.com wrote: The previous file share expired. File can now be found at: http://www.fileswap.com/dl/pxPvW1nVwM/ On Monday, January 27, 2014 10:28:06 PM UTC+1, crystal@gmail.comwrote: Excellent. thanks. I'll give it a whirl tonight. On Thursday, January 23, 2014 12:12:25 PM UTC-6, xris@googlemail.comwrote: Hey guys, As promised. Ubuntu 12.04 BBB image for the Chipsee 7” 1024x600 LCD touchscreen. Grab it here: http://www.fileswap.com/dl/sdFGPZoIw6/ You should find yourself downloading bbb-ubuntu-12.04-for-community.xzhttp://www.fileswap.com/dl/sdFGPZoIw6/bbb-ubuntu-12.04-for-community.xz.html Just extract and write that to your SD card (4gb expected) with something like: *cat bbb-ubuntu-12.04-for-community.xz | xz -d /dev/sdX* Note it’s a raw sector dump NOT a tarball, so extract straight to your SD card device. (eg. /dev/sdx, NOT /dev/sdx1) Also note this image doesn’t install or boot from MMC so make sure you’ve got the SD card selected on the boot switch thing. Once the extract is complete, simply slap it into the BBB and boot. It should come up with the Chipsee splash screen but then boot into Ubuntu 12.04 after a while. Hope this helps. l8r, Xris. -- 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: debian: test images (2014-01-10)
I was going to do more testing, but an unexpected power outage corrupted my sd card.I will see if I can retrace my steps with a fresh image On Thursday, January 30, 2014 9:11:02 AM UTC-6, RobertCNelson wrote: On Wed, Jan 29, 2014 at 8:38 PM, Louis McCarthy comp...@gmail.comjavascript: wrote: Darn , I was hoping I narrowed it down 800 x 480 is my resolution. Come to think of it, I think the last lock ups were through HDMI, to a 1680 x 1050 monitor. Nope there goes that theory, 480x272.. 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 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 uSD Boot switch
I have created uSD card with Android image from TI-Android. On the BBB I have the stock Angstrom image. I would like to load the TI-android image from uSD card. I held down the uSD boot button, before applying power to the board and released the button after applying power. I was expecting the BBB to boot from the uSD card. Am I correct in my assumptions? Thank you for the feedback. -- 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] [PATCH] beaglebone capes: Added overlays for CBB-Serial cape
Added main overaly for CBB-Serial BeagleBone cape, as well as separate
overlays to mux the AM335x UART2 and UART4 RTS and CTS pins to the 3.8
branch.
Signed-off-by: Alexander Hiam hiamalexan...@gmail.com
---
firmware/Makefile | 6 ++
firmware/capes/BB-UART2-RTSCTS-00A0.dts | 57 +
firmware/capes/BB-UART4-RTSCTS-00A0.dts | 57 +
firmware/capes/cape-CBB-Serial-r01.dts | 106
4 files changed, 226 insertions(+)
create mode 100644 firmware/capes/BB-UART2-RTSCTS-00A0.dts
create mode 100644 firmware/capes/BB-UART4-RTSCTS-00A0.dts
create mode 100644 firmware/capes/cape-CBB-Serial-r01.dts
diff --git a/firmware/Makefile b/firmware/Makefile
index e45d10b..4b59f44 100644
--- a/firmware/Makefile
+++ b/firmware/Makefile
@@ -221,6 +221,12 @@ fw-shipped-$(CONFIG_CAPE_BEAGLEBONE) += \
# the Tester cape (tester-side)
fw-shipped-$(CONFIG_CAPE_BEAGLEBONE) += cape-bone-tester-00A0.dtbo
+# the CBB-Serial cape (tester-side)
+fw-shipped-$(CONFIG_CAPE_BEAGLEBONE) += \
+ cape-CBB-Serial-r01.dtbo \
+ BB-UART2-RTSCTS-00A0.dtbo \
+ BB-UART4-RTSCTS-00A0.dtbo
+
# the virtual peripheral capes for the UARTs
# UART3 is not routed to the connectors, no cape for it
fw-shipped-$(CONFIG_CAPE_BEAGLEBONE) += \
diff --git a/firmware/capes/BB-UART2-RTSCTS-00A0.dts
b/firmware/capes/BB-UART2-RTSCTS-00A0.dts
new file mode 100644
index 000..bef5fff
--- /dev/null
+++ b/firmware/capes/BB-UART2-RTSCTS-00A0.dts
@@ -0,0 +1,57 @@
+/* BB-UART2-RTSCTS-00A0.dts
+ * Written by Alexander Hiam hiamalexan...@gmail.com
+ * for Logic Supply - http://logicsupply.com
+ * Jan 28, 2014
+ *
+ * This overlay enables RTS/CTS flow control for UART2.
+ * HDMI must be disabled before enabling this overlay, see:
+ *
http://www.logicsupply.com/blog/2013/07/18/disabling-the-beaglebone-black-hdmi-cape/
+ *
+ * Copyright (c) 2014 - Logic Supply (http://logicsupply.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/;
+/plugin/;
+
+/{
+ compatible = ti,beaglebone, ti,beaglebone-black;
+
+ part-number = BB-UART2-RTSCTS;
+ version = 00A0;
+
+ exclusive-use =
+ P8.38, /* uart2 rts */
+ P8.37; /* uart2 cts */
+
+ fragment@0 {
+/* Sets pinmux for flow control pins. */
+target = am33xx_pinmux;
+__overlay__ {
+ u2_rtscts_pins: pinmux_u2_rtscts_pins {
+pinctrl-single,pins =
+ 0x0c4 0x0e /* lcd_data9 - pullup | mode 6 (uart2_rtsn) */
+ 0x0c0 0x36 /* lcd_data8 - rx enable | pullup | mode 6 (uart2_ctsn) */
+;
+ };
+};
+ };
+
+ fragment@1 {
+/* Enable pinmux-helper driver for setting mux configuration. */
+target = ocp; /* On-Chip Peripherals */
+__overlay__ {
+ uart2-rtscts-pinmux {
+compatible = bone-pinmux-helper; /* Use the pinmux helper */
+status=okay;
+/* Define custom names for indexes in pinctrl array: */
+pinctrl-names = default;
+/* Set the elements of the pinctrl array to the pinmux overlays
+ defined above: */
+pinctrl-0 = u2_rtscts_pins;
+ };
+};
+ };
+};
diff --git a/firmware/capes/BB-UART4-RTSCTS-00A0.dts
b/firmware/capes/BB-UART4-RTSCTS-00A0.dts
new file mode 100644
index 000..a8f8e98
--- /dev/null
+++ b/firmware/capes/BB-UART4-RTSCTS-00A0.dts
@@ -0,0 +1,57 @@
+/* BB-UART4-RTSCTS-00A0.dts
+ * Written by Alexander Hiam hiamalexan...@gmail.com
+ * for Logic Supply - http://logicsupply.com
+ * Jan 28, 2014
+ *
+ * This overlay enables RTS/CTS flow control for UART4.
+ * HDMI must be disabled before enabling this overlay, see:
+ *
http://www.logicsupply.com/blog/2013/07/18/disabling-the-beaglebone-black-hdmi-cape/
+ *
+ * Copyright (c) 2014 - Logic Supply (http://logicsupply.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/;
+/plugin/;
+
+/{
+ compatible = ti,beaglebone, ti,beaglebone-black;
+
+ part-number = BB-UART4-RTSCTS;
+ version = 00A0;
+
+ exclusive-use =
+ P8.33, /* uart4 rts */
+ P8.35; /* uart4 cts */
+
+ fragment@0 {
+/* Sets pinmux for flow control pins. */
+target = am33xx_pinmux;
+__overlay__ {
+ u4_rtscts_pins: pinmux_u4_rtscts_pins {
+pinctrl-single,pins =
+ 0x0d4 0x0e /* lcd_data13 - pullup | mode 6 (uart4_rtsn) */
+ 0x0d0 0x36 /* lcd_data12 - rx enable | pullup | mode 6 (uart4_ctsn)
*/
+;
+ };
+};
+ };
+
+ fragment@1 {
+/* Enable pinmux-helper driver for setting mux configuration. */
+target = ocp; /* On-Chip Peripherals */
+__overlay__ {
+ uart4-rtscts-pinmux {
+compatible = bone-pinmux-helper; /* Use the pinmux helper */
+status=okay;
+/* Define
[beagleboard] Re: Android running on BBB with Linux 3.8
Hello Rich, I am also trying to boot BBB with 4DCAPE-43T. 1. Can you please share your uEnv.txt? 2. Did you used a pre-built image from TI-Andriodhttp://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_DeveloperGuide or something different? 3. Did you boot off the uSD card? Appreciate your help Mahendra On Monday, December 30, 2013 11:40:53 PM UTC-5, vega...@gmail.com wrote: Andrew: Thank you for this post. I have this image working on my BBB using 4D Systems 4DCAPE-43T Cape by editing the uEnv.txt as: video=48...@56javascript:. I am able to SSH to the device using Android SSH Server on the device and putty on my PC. However, I need to know the root password for this image. I like to avoid using 'adb shell' to get to the root. I really want to root this device. I use Xamarin as a development tool and it works well. However, when I try to access, via code, the /sys/class/leds/beaglebone:green:usr0 to set the trigger to none I get Access Denied. I need root access via my code...I am pulling my hair on that one. any help is appreciated. Kindly Rich On Monday, June 17, 2013 8:00:07 PM UTC-4, Andrew Henderson wrote: Hello all. I posted this information over at the Google+ group for BeagleBoard.org, but I wanted to post it here as well. I have Android running on the BBB using the Jellybean (4.2.2) source from arowboat.organd the Linux 3.8.13 kernel from my BeagleSNES project ( www.beaglesnes.org). I just added the Android drivers (Drivers - Staging Drivers - Android) into the same kernel configuration that I use for BeagleSNES. This kernel is really just a stripped down configuration (a 1.9 meg zImage) using Robert Nelson's 3.8.x kernel source tree. Instead of using the GCC cross-compiler that comes in Rowboat's current prebuilt tools, I use the 3.7 GCC that comes with Robert's kernel tree to build the entire system. I also updated the u-boot to v2013.04. Here is a video of it running: https://www.youtube.com/watch?v=yeSt1Y7FhEs Here is the download of a working Android image that can be written onto a 4GB microSD card using dd: http://icculus.org/~hendersa/BBB_JB_Android_3_8_13.img.bz2 There is no hardware accelerated video in this version, since SGX support isn't ready for the 3.8 kernel. To shut off hardware accelerated video, I pass qemu=1 as a kernel command line argument in uEnv.txt and I add debug.egl.hw=0 to the /system/build.prop file in the root file system. To get rid of that blinking cursor on the framebuffer (which I accidentally left on in the image that I made), add this to the uEnv.txt kernel command line arguments: vt.global_cursor_default=0 This build will be of interest to Android experimenters who want to use HDMI for audio and video output (rather than using an LCD cape) and who want to experiment with using the device tree. My kernel is pretty stripped down, so feel free to fetch Robert's latest kernel source for the 3.8.x branch and rebuild your own kernel to drop into the image that I have supplied. That way, you can include whatever drivers you would like in your kernel. Use a USB mouse (and a keyboard, too, if you want) to interact with the system. Thanks, and enjoy! Andrew -- 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] Re: Bone VDD_3V3EXP Disable Issues
An update: For the A6 (Beaglebone Black) version, I connected U4 pin 1 (enable) back to VDD_3V3AUX (same as A5C). It now shuts down correctly while on battery. This was verified on two A6 BBB. The mystery is what causes the VDD_3V3A to hang up on the A6 version when shutting down while on battery. -- 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] Re: Beaglebone Black aways losing the SSH connectivity
I simply made a cron job that performed something like systemctl start dropbear.socket periodically. You could have the script detect if dropbear.socket is dead, and restart it. -- 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] Heads up: Device tree files compiled with wrong address references?
Yes,the kernel documentation is bedtime reading. Thanks. My example may have been too simple--I have *two* I2C devices, the RTC and a Solomon SSD1306 display at 3C on the same bus. I could not get the RTC to detect until I made that change with the address. The display was detected OK. I take your point, though; This problem would have had to come up long before I brought it up--of course it could be my mistake! I still think it's ambiguous, and I am going to spell out the radix, always. 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/groups/opt_out.
Re: [beagleboard] Heads up: Device tree files compiled with wrong address references?
On 30/01/14 18:09, David M. wrote: Yes,the kernel documentation is bedtime reading. Thanks. :) My example may have been too simple--I have /two/ I2C devices, the RTC and a Solomon SSD1306 display at 3C on the same bus. I have multiple devices as well, three on the current setup one of which is at 0x48 and having dev@48 makes no difference, still works. I still think it's ambiguous, and I am going to spell out the radix, always. Interestingly, if you ever try to get a change accepted in the mainstream kernel that does that in the node name you'll get told to remove it. But either way, it's entirely up to you. Only requirement from the doc is that the names are unique. -- 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: debian: test images (2014-01-29) (resend with correct topic..)
So presumably, this isn't detecting capes via EEPROM; it's effectively the equivalent of doing: echo cape-bone-proto /sys/devices/bone_capemgr.9/slots In a startup script? Yeap. 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 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] BeagleBone Black: v3.8.13-bone37 kernel flash slowly fills up
On Thu, Jan 30, 2014 at 11:14 AM, Craig Mehan craigleeme...@gmail.com wrote: Oops, sorry, I should have mentioned I am a newbie. After some googling: http://paste.debian.net/79272/ http://paste.debian.net/79273/ Ah crap.. i fixed that a year ago! gen_ndis_query_resp: RNDIS_OID_GEN_RCV_NO_BUFFER And then just unfixed it a couple weeks ago.. https://github.com/RobertCNelson/linux-dev/commit/3f61fc35d46cce0ee1a7543b666b2e9a99822b60 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 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: problems with webcams
Okay, so the problem you're having has to do with bugs in OpenCV, itself. Unfortunately, the capture methods in OpenCV do not set the camera properties correctly for video4linux devices. In other words, you may write the line of code to set the frame rate to 30 fps, but the camera isn't actually getting the instruction to change the frame rate. The fix Matthew and I have used is to just use our own video4linux capture code. You might be able to modify the OpenCV source code, but the capture code is difficult to follow since there are so many layers of abstraction. (There are a lot of wrapper classes used to handle v4l2 devices, v4l1 devices, Mac, Windows so that the programmer doesn't have to handle each camera differently depending on his/her system.) Hope that explains some things for you :) - Mike -- 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: [BBB][Angstrom Distribution] [RS485] Applying a custom Patch
Very nice! Thanks for the update. Wasn't too hard to apply, but it's good to get it into the Beaglebone patch library. Zach On Thursday, January 30, 2014 2:41:26 AM UTC-6, Mickae1 wrote: Zachary, For your information, you don't need anymore to patch the kernel :p = https://github.com/RobertCNelson/linux-dev/commit/823fd45781f6e176ee1dc87062c95a010c7af588 On Tue, Jan 28, 2014 at 4:21 PM, Zachary Thorson zacht...@gmail.comjavascript: wrote: Now, I have developed an application which is combination of both send and recv. I mean , after sending one byte on UART from BBB to other host machine, I just wait for input bytes to receive(added receive timepout at 10 sec). Now in this cae, even if I do not send any character from host machine, BBB detects one/two arbitary bytes. Could you clarify what you mean by this? I am assuming you are essentially using one host as a master and one as the slave. Do you mean when neither end is transmitting, you are seeing arbitrary bytes, or that when the master sends a request out, you that same master sees bytes even if nothing is transmitted by either host? If the random bytes are all 0's or all 1's (0x00, 0xFF) that might indicate some problems in what the non-driven state of the line voltage is. If the bytes seem similar to what was being transmitted, you might be getting reflections if the line is not terminated properly. This seems that driver changes GPIO position (from send mode to recv mode) before transmitte buffer gets empty. Is this a guess from the behavior, or did you watch the signal lines, or use printk statements in the patch? Did any one has face this problem? Can you guys please share your thoughts on this? I have not seen this issue and have been using the patch at 38400 baud with an ADM2582 chip for a number of months now. -- 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...@googlegroups.com javascript:. 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] Re: Beaglebone Black aways losing the SSH connectivity
Thanks! I'll try to work with the cronjob first and then I'll try the OpenSSH. Soon as I fix this, I'll post the results. Thanks again, guys! On Thursday, January 23, 2014 4:59:21 PM UTC-2, vi...@iceland2.com wrote: Hi gyus, I'm trying to find a solution for this SSH problem, I already tried to use these solutions: https://groups.google.com/forum/#!topic/beagleboard/Ya2qE4repSY , https://groups.google.com/forum/?fromgroups=#!msg/beagleboard/Ya2qE4repSY/u4lvOjF66JEJ The only way that I'm able to access the command-line on the Beaglebone is using the 'screen' command on Mac OS X. I tried to recover the SSH by using the command-line and tried to clean the configuration of the Dropbear too, but I couldn't make it works. The only solution that I worked for me was to re-flash the Beaglebone's MMC and reinstall everything from the beginning. Is there a way to create a flasher SD image with custom softwares, making easier to reinstall everything? Or is there a way to reinstalls the SSH server on Beaglebone? Thanks in advance, Vitaliano Palmieri Neto Programmer @ Iceland 2nd Nation -- 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: problems with webcams
If you bypass OpenCV and capture directly like we did, you should test to see if you can capture successfully in YUYV format. OpenCV can convert YUYV to a Mat with less than 3% cpu use. If you capture in MJPEG, you will see cpu use of 90% or more to convert the image to a Mat. This isn't so bad on the Wandboard because it only consumes one core, but can be intense on the single core BBB. I can tell you from testing with the Wandboard Quad, it can push 30 fps in YUYV over USB. However, it is only possible to stream from one camera at 30 fps in YUYV. In short it is a tradeoff. You can either saturate the USB and save processing or save bandwidth and increase processing. Something to consider depending on your needs. On Thu, Jan 30, 2014 at 12:53 PM, Michael Darling fndrplaye...@gmail.comwrote: Okay, so the problem you're having has to do with bugs in OpenCV, itself. Unfortunately, the capture methods in OpenCV do not set the camera properties correctly for video4linux devices. In other words, you may write the line of code to set the frame rate to 30 fps, but the camera isn't actually getting the instruction to change the frame rate. The fix Matthew and I have used is to just use our own video4linux capture code. You might be able to modify the OpenCV source code, but the capture code is difficult to follow since there are so many layers of abstraction. (There are a lot of wrapper classes used to handle v4l2 devices, v4l1 devices, Mac, Windows so that the programmer doesn't have to handle each camera differently depending on his/her system.) Hope that explains some things for you :) - 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/G5Xs2JuwD_4/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] BeagleBone Black: v3.8.13-bone37 kernel flash slowly fills up
On Thu, Jan 30, 2014 at 12:42 PM, Robert Nelson robertcnel...@gmail.com wrote: On Thu, Jan 30, 2014 at 11:14 AM, Craig Mehan craigleeme...@gmail.com wrote: Oops, sorry, I should have mentioned I am a newbie. After some googling: http://paste.debian.net/79272/ http://paste.debian.net/79273/ Ah crap.. i fixed that a year ago! gen_ndis_query_resp: RNDIS_OID_GEN_RCV_NO_BUFFER And then just unfixed it a couple weeks ago.. https://github.com/RobertCNelson/linux-dev/commit/3f61fc35d46cce0ee1a7543b666b2e9a99822b60 So the fix is on the way.. (few hours of building..) to fix it now.. cd /opt/scripts/ git pull ./tools/update_kernel.sh --kernel v3.8.13-bone35 Then tomorrow just run: cd /opt/scripts/ ./tools/update_kernel.sh 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 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] [PATCH] beaglebone capes: Added overlays for CBB-Serial cape
On Thu, Jan 30, 2014 at 10:44 AM, Alexander Hiam hiamalexan...@gmail.com wrote: Added main overaly for CBB-Serial BeagleBone cape, as well as separate overlays to mux the AM335x UART2 and UART4 RTS and CTS pins to the 3.8 branch. Signed-off-by: Alexander Hiam hiamalexan...@gmail.com --- firmware/Makefile | 6 ++ firmware/capes/BB-UART2-RTSCTS-00A0.dts | 57 + firmware/capes/BB-UART4-RTSCTS-00A0.dts | 57 + firmware/capes/cape-CBB-Serial-r01.dts | 106 4 files changed, 226 insertions(+) create mode 100644 firmware/capes/BB-UART2-RTSCTS-00A0.dts create mode 100644 firmware/capes/BB-UART4-RTSCTS-00A0.dts create mode 100644 firmware/capes/cape-CBB-Serial-r01.dts Thanks Alexander! pushed to all 3.8 tree's... 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 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] [PATCH] beaglebone capes: Added overlays for CBB-Serial cape
Very cool, thanks! On Thu, Jan 30, 2014 at 3:50 PM, Robert Nelson robertcnel...@gmail.comwrote: On Thu, Jan 30, 2014 at 10:44 AM, Alexander Hiam hiamalexan...@gmail.com wrote: Added main overaly for CBB-Serial BeagleBone cape, as well as separate overlays to mux the AM335x UART2 and UART4 RTS and CTS pins to the 3.8 branch. Signed-off-by: Alexander Hiam hiamalexan...@gmail.com --- firmware/Makefile | 6 ++ firmware/capes/BB-UART2-RTSCTS-00A0.dts | 57 + firmware/capes/BB-UART4-RTSCTS-00A0.dts | 57 + firmware/capes/cape-CBB-Serial-r01.dts | 106 4 files changed, 226 insertions(+) create mode 100644 firmware/capes/BB-UART2-RTSCTS-00A0.dts create mode 100644 firmware/capes/BB-UART4-RTSCTS-00A0.dts create mode 100644 firmware/capes/cape-CBB-Serial-r01.dts Thanks Alexander! pushed to all 3.8 tree's... 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 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] Which version of uboot is recommended for Beagleboard-XM (kernel 3.11.10)?
Hi, I have been using kernel 2.6.32 for years and decided it was time to upgrade to a more recent one so I chose the following as it can run the board safely at 1GHz: https://github.com/RobertCNelson/armv7-multiplatform (v3.11.x branch) I also had to upgrade u-boot as my version (U-Boot SPL 2013.01-00071-g6ad77d8 (Feb 01 2013 - 22:10:08)) does not support zImage (even if I rebuild it with CONFIG_CMD_BOOTZ set it refuses to boot a zImage). So I switched to u-boot-2014.1. Whilst it booted first time the USB ports do not come up (and there are a bunch of errors during boot). I suspect this is a u-boot problem since if I boot my known working 2.6.32 kernel with uboot-2014.1 the usb ports are not working either. (If I go back to old uboot with 2.6.32 everything works fine so I know the board is good). Is there a known stable version of u-boot for beaglexm that can boot a zImage for this kernel? Do I need some patches for uboot? Thanks, Mark Serial output below: U-Boot 2014.01 (Jan 30 2014 - 01:06:48) OMAP3630/3730-GP ES1.1, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 256 MiB MMC: OMAP SD/MMC: 0 Error: Bad compare! failed Error: Bad compare! failed Error: Bad compare! failed NAND read from offset 26 failed -74 *** Warning - readenv() failed, using default environment In:serial Out: serial Err: serial Beagle xM Rev A/B No EEPROM on expansion board Die ID #127400011ff0015739eb0c00d00d Net: usb_ether Hit any key to stop autoboot: 0 mmc0 is current device gpio: pin 173 (gpio 173) value is 0 gpio: pin 4 (gpio 4) value is 0 SD/MMC found on device 0 reading uEnv.txt 8 bytes read in 3 ms (2 KiB/s) Loaded environment from uEnv.txt Importing environment from mmc ... ** File not found /boot/uImage ** Booting from nand ... NAND read: device 0 offset 0x28, size 0x40 4194304 bytes read: OK Wrong Image Format for bootm command ERROR: can't get kernel image! 3810576 bytes read in 264 ms (13.8 MiB/s) 13511 bytes read in 22 ms (599.6 KiB/s) Booting with DT from mmc0 ... Kernel image @ 0x8020 [ 0x00 - 0x3a2510 ] ## Flattened Device Tree blob at 80f8 Booting using the fdt blob at 0x80f8 Using Device Tree in place at 80f8, end 80f864c6 Starting kernel ... [0.00] Booting Linux on physical CPU 0x0 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.11.10-armv7-x14.2 (@xxx) (gcc version 4.8.2 20131014 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.10 - Linaro GCC 2013.10) ) #1 SMP Wed Jan 29 23:51:17 GMT 2014 [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [0.00] Machine: Generic OMAP3-GP (Flattened Device Tree), model: TI OMAP3 BeagleBoard xM [0.00] cma: CMA: reserved 16 MiB at 9e80 [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] CPU: All CPU(s) started in SVC mode. [0.00] OMAP3630 ES1.1 (l2cache iva sgx neon isp 192mhz_clk ) [0.00] PERCPU: Embedded 9 pages/cpu @c138e000 s14080 r8192 d14592 u36864 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129792 [0.00] Kernel command line: console=ttyO2,115200n8 mpurate=auto buddy=none camera=none vram=2M omapfb.mode=dvi:640x480MR-16@60 omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes) [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] allocated 1048576 bytes of page_cgroup [0.00] please try 'cgroup_disable=memory' option if you don't want memory cgroups [0.00] Memory: 488964K/523264K available (7254K kernel code, 627K rwdata, 2864K rodata, 469K init, 1014K bss, 34300K reserved, 0K highmem) [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) [0.00] vmalloc : 0xe080 - 0xff00 ( 488 MB) [0.00] lowmem : 0xc000 - 0xe000 ( 512 MB) [0.00] pkmap : 0xbfe0 - 0xc000 ( 2 MB) [0.00] modules : 0xbf00 - 0xbfe0 ( 14 MB) [0.00] .text : 0xc0008000 - 0xc09e99f4 (10119 kB) [0.00] .init : 0xc09ea000 - 0xc0a5f700 ( 470 kB) [0.00] .data : 0xc0a6 - 0xc0afcea0 ( 628 kB) [0.00].bss : 0xc0afcea0 - 0xc0bfa6b8 (1015 kB) [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [0.00] Hierarchical RCU implementation. [0.00] RCU restricting CPUs from NR_CPUS=4 to
[beagleboard] Connecting BeagleBone to BeagleBone Black
Hey everyone, I'm new to using the BeagleBone. I've done the basics on the BeagleBone Black. For a project I've been working on I want to have BLE functionality on the BeagleBone Black but unfortunately the cape only works on the BeagleBone and not the Black. Is it doable to have the BeagleBone communicate to the BeagleBone Black? If so is there any hardware that is required in order for the BeagleBone Black to receive information or some kind of software configuration I need to have in mind? 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/groups/opt_out.
Re: [beagleboard] Which version of uboot is recommended for Beagleboard-XM (kernel 3.11.10)?
On Thu, Jan 30, 2014 at 2:48 PM, Mark Pupilli mpupi...@gmail.com wrote: Hi, I have been using kernel 2.6.32 for years and decided it was time to upgrade to a more recent one so I chose the following as it can run the board safely at 1GHz: technically it's still not safe see Nishanth's response when i asked him yesterday about it.. https://lkml.org/lkml/2014/1/29/446 https://github.com/RobertCNelson/armv7-multiplatform (v3.11.x branch) btw: v3.11.x/v3.12.x isn't really being testing anymore, care to jump on v3.13.x while it's stable? ;) (plus usb is now built-in with v3.13.x and works when built-in) I also had to upgrade u-boot as my version (U-Boot SPL 2013.01-00071-g6ad77d8 (Feb 01 2013 - 22:10:08)) does not support zImage (even if I rebuild it with CONFIG_CMD_BOOTZ set it refuses to boot a zImage). So I switched to u-boot-2014.1. Whilst it booted first time the USB ports do not come up (and there are a bunch of errors during boot). I suspect this is a u-boot problem since if I boot my known working 2.6.32 kernel with uboot-2014.1 the usb ports are not working either. (If I go back to old uboot with 2.6.32 everything works fine so I know the board is good). Is there a known stable version of u-boot for beaglexm that can boot a zImage for this kernel? Do I need some patches for uboot? Here's my patch against v2014.01 https://github.com/eewiki/u-boot-patches/blob/master/v2014.01/0001-omap3_beagle-uEnv.txt-bootz-n-fixes.patch It's expecting: fat directory: /dev/mmcblk0p1 zImage /dtbs/omap3-beagle-* root: /dev/mmcblk0p2 Thanks, Mark Serial output below: U-Boot 2014.01 (Jan 30 2014 - 01:06:48) OMAP3630/3730-GP ES1.1, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 256 MiB MMC: OMAP SD/MMC: 0 Error: Bad compare! failed Error: Bad compare! failed Error: Bad compare! failed NAND read from offset 26 failed -74 *** Warning - readenv() failed, using default environment In:serial Out: serial Err: serial Beagle xM Rev A/B PS: make it it loads the omap3-beagle-xm-ab.dtb otherwise usb will not work period.. 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 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] Which version of uboot is recommended for Beagleboard-XM (kernel 3.11.10)?
On Thu, Jan 30, 2014 at 3:27 PM, Robert Nelson robertcnel...@gmail.com wrote: On Thu, Jan 30, 2014 at 2:48 PM, Mark Pupilli mpupi...@gmail.com wrote: Hi, I have been using kernel 2.6.32 for years and decided it was time to upgrade to a more recent one so I chose the following as it can run the board safely at 1GHz: technically it's still not safe see Nishanth's response when i asked him yesterday about it.. https://lkml.org/lkml/2014/1/29/446 yep - so it is.. I am more than happy to guide folks if anyone is interested in pitching in as we work with upstream in the parcels needed. in fact, this is not just an OMAP3/beagle only issue - I have had to state precisely the same here: https://bugzilla.kernel.org/show_bug.cgi?id=58541 Regards, Nishanth Menon -- 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: debian: test images (2014-01-10)
I found it! Switching from 16 bit video mode to 24 bit fixes GTK. I added this to /usr/share/X11/xorg.conf.d/10-evdev.conf Section Screen Identifier Builtin Default fbdev Screen 0 Monitor Configured Monitor Device Configured Video Device DefaultDepth 24 EndSection On Thursday, January 30, 2014 10:40:55 AM UTC-6, Louis McCarthy wrote: I was going to do more testing, but an unexpected power outage corrupted my sd card.I will see if I can retrace my steps with a fresh image On Thursday, January 30, 2014 9:11:02 AM UTC-6, RobertCNelson wrote: On Wed, Jan 29, 2014 at 8:38 PM, Louis McCarthy comp...@gmail.com wrote: Darn , I was hoping I narrowed it down 800 x 480 is my resolution. Come to think of it, I think the last lock ups were through HDMI, to a 1680 x 1050 monitor. Nope there goes that theory, 480x272.. 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 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: debian: test images (2014-01-29) (resend with correct topic..)
On Thursday, January 30, 2014 1:29:30 PM UTC-5, RobertCNelson wrote: So presumably, this isn't detecting capes via EEPROM; it's effectively the equivalent of doing: echo cape-bone-proto /sys/devices/bone_capemgr.9/slots In a startup script? Yeap. Ok, so I'm still interested in getting my overlay loaded at boot time via EEPROM. Could you elaborate on your ideas about using initrd.img to store the .dtbo files? 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-10)
On Thu, Jan 30, 2014 at 3:40 PM, Louis McCarthy compeo...@gmail.com wrote: I found it! Switching from 16 bit video mode to 24 bit fixes GTK. I added this to /usr/share/X11/xorg.conf.d/10-evdev.conf Section Screen Identifier Builtin Default fbdev Screen 0 Monitor Configured Monitor Device Configured Video Device DefaultDepth 24 EndSection Nice find!! It's too bad the colors are psychedelic, so it's unusable.. sudo sed -i -e 's:16:24:g' /etc/X11/xorg.conf sudo reboot But the core finally doesn't lock up! 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 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: debian: test images (2014-01-10)
On Thu, Jan 30, 2014 at 3:40 PM, Louis McCarthy compeo...@gmail.com wrote: I found it! Switching from 16 bit video mode to 24 bit fixes GTK. I added this to /usr/share/X11/xorg.conf.d/10-evdev.conf Section Screen Identifier Builtin Default fbdev Screen 0 Monitor Configured Monitor Device Configured Video Device DefaultDepth 24 EndSection Nice find!! It's too bad the colors are psychedelic, so it's unusable.. sudo sed -i -e 's:16:24:g' /etc/X11/xorg.conf sudo reboot But the core finally doesn't lock up! 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 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: Android running on BBB with Linux 3.8
Rich I got Andrew Henderson JB image working, Thanks On Thu, Jan 30, 2014 at 11:54 AM, Mahendra Gunawardena mahengunaward...@gmail.com wrote: Hello Rich, I am also trying to boot BBB with 4DCAPE-43T. 1. Can you please share your uEnv.txt? 2. Did you used a pre-built image from TI-Andriodhttp://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_DeveloperGuide or something different? 3. Did you boot off the uSD card? Appreciate your help Mahendra On Monday, December 30, 2013 11:40:53 PM UTC-5, vega...@gmail.com wrote: Andrew: Thank you for this post. I have this image working on my BBB using 4D Systems 4DCAPE-43T Cape by editing the uEnv.txt as: video=48...@56 . I am able to SSH to the device using Android SSH Server on the device and putty on my PC. However, I need to know the root password for this image. I like to avoid using 'adb shell' to get to the root. I really want to root this device. I use Xamarin as a development tool and it works well. However, when I try to access, via code, the /sys/class/leds/beaglebone: green:usr0 to set the trigger to none I get Access Denied. I need root access via my code...I am pulling my hair on that one. any help is appreciated. Kindly Rich On Monday, June 17, 2013 8:00:07 PM UTC-4, Andrew Henderson wrote: Hello all. I posted this information over at the Google+ group for BeagleBoard.org, but I wanted to post it here as well. I have Android running on the BBB using the Jellybean (4.2.2) source from arowboat.organd the Linux 3.8.13 kernel from my BeagleSNES project ( www.beaglesnes.org). I just added the Android drivers (Drivers - Staging Drivers - Android) into the same kernel configuration that I use for BeagleSNES. This kernel is really just a stripped down configuration (a 1.9 meg zImage) using Robert Nelson's 3.8.x kernel source tree. Instead of using the GCC cross-compiler that comes in Rowboat's current prebuilt tools, I use the 3.7 GCC that comes with Robert's kernel tree to build the entire system. I also updated the u-boot to v2013.04. Here is a video of it running: https://www.youtube.com/watch? v=yeSt1Y7FhEs Here is the download of a working Android image that can be written onto a 4GB microSD card using dd: http://icculus.org/~hendersa/ BBB_JB_Android_3_8_13.img.bz2 There is no hardware accelerated video in this version, since SGX support isn't ready for the 3.8 kernel. To shut off hardware accelerated video, I pass qemu=1 as a kernel command line argument in uEnv.txt and I add debug.egl.hw=0 to the /system/build.prop file in the root file system. To get rid of that blinking cursor on the framebuffer (which I accidentally left on in the image that I made), add this to the uEnv.txt kernel command line arguments: vt.global_cursor_default=0 This build will be of interest to Android experimenters who want to use HDMI for audio and video output (rather than using an LCD cape) and who want to experiment with using the device tree. My kernel is pretty stripped down, so feel free to fetch Robert's latest kernel source for the 3.8.x branch and rebuild your own kernel to drop into the image that I have supplied. That way, you can include whatever drivers you would like in your kernel. Use a USB mouse (and a keyboard, too, if you want) to interact with the system. Thanks, and enjoy! Andrew -- 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/Yc8CdtU5MEs/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: debian: test images (2014-01-29) (resend with correct topic..)
Robert: Sorry to bug you again, but I've been hunting and hunting and can't figure out where two things concerning apache2 in this testing image: 1) where is the very generic default webpage that I see when go to http://my BBB's URL:8080 located in the file system? It's not in /var/www 2) where does the default port for the apache3 server get changed to :8080 from the normal :80? I don't use bone script and would like to have apache2 use port 80 Thanks John On Thursday, January 30, 2014 2:17:52 PM UTC-8, smith.wi...@gmail.com wrote: On Thursday, January 30, 2014 1:29:30 PM UTC-5, RobertCNelson wrote: So presumably, this isn't detecting capes via EEPROM; it's effectively the equivalent of doing: echo cape-bone-proto /sys/devices/bone_capemgr.9/slots In a startup script? Yeap. Ok, so I'm still interested in getting my overlay loaded at boot time via EEPROM. Could you elaborate on your ideas about using initrd.img to store the .dtbo files? 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/groups/opt_out.
[beagleboard] modifying flasher script
Hi, I am trying to create custom flasher image using https://raw.github.com/RobertCNelson/tools/master/scripts/beaglebone-black-make-microSD-flasher-from-eMMC.sh It works fine and flasher is doing its job, but when I try to modify this script to add fstab entry resulting flasher unable to finish flashing with all leds going on and off constantly. I am adding simple /dev/sda1 /data ext4 defaults 0 0 my modify script: wget https://raw.github.com/RobertCNelson/tools/master/scripts/beaglebone-black-make-microSD-flasher-from-eMMC.sh sed -i '/debugfs.*fstab/a \\techo /dev/sda1 /data ext4 defaults 0 0 /tmp/rootfs/etc/fstab' beaglebone-black-make-microSD-flasher-from-eMMC.sh chmod +x beaglebone-black-make-microSD-flasher-from-eMMC.sh ./beaglebone-black-make-microSD-flasher-from-eMMC.sh If I insert this line into /etc/fstab on a flashed device mounting works fine, but I would like it to come from flasher. Is this the right way to modify fstab for flasher? 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
On Thu, Jan 30, 2014 at 6:29 PM, vermins...@gmail.com wrote: Robert: Sorry to bug you again, but I've been hunting and hunting and can't figure out where two things concerning apache2 in this testing image: 1) where is the very generic default webpage that I see when go to http://my BBB's URL:8080 located in the file system? It's not in /var/www It's /var/www in 2014-01-29 2) where does the default port for the apache3 server get changed to :8080 from the normal :80? I don't use bone script and would like to have apache2 use port 80 sudo systemctl disable bonescript.socket sudo sed -i -e 's:8080:80:g' /etc/apache2/ports.conf sudo sed -i -e 's:8080:80:g' /etc/apache2/sites-enabled/000-default sudo /etc/init.d/apache2 restart 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 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] modifying flasher script
On Thu, Jan 30, 2014 at 7:22 PM, Boris Rybalkin ribal...@gmail.com wrote: Hi, I am trying to create custom flasher image using https://raw.github.com/RobertCNelson/tools/master/scripts/beaglebone-black-make-microSD-flasher-from-eMMC.sh It works fine and flasher is doing its job, but when I try to modify this script to add fstab entry resulting flasher unable to finish flashing with all leds going on and off constantly. I am adding simple /dev/sda1 /data ext4 defaults 0 0 my modify script: wget https://raw.github.com/RobertCNelson/tools/master/scripts/beaglebone-black-make-microSD-flasher-from-eMMC.sh sed -i '/debugfs.*fstab/a \\techo /dev/sda1 /data ext4 defaults 0 0 /tmp/rootfs/etc/fstab' beaglebone-black-make-microSD-flasher-from-eMMC.sh chmod +x beaglebone-black-make-microSD-flasher-from-eMMC.sh ./beaglebone-black-make-microSD-flasher-from-eMMC.sh If I insert this line into /etc/fstab on a flashed device mounting works fine, but I would like it to come from flasher. Is this the right way to modify fstab for flasher? Well, that change shouldn't cause the condition you see. Your change is perfectly fine. I'd say it's more random bad luck, maybe an external cape plugged in on the eMMC pins? 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 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] Which version of uboot is recommended for Beagleboard-XM (kernel 3.11.10)?
On Thu, Jan 30, 2014 at 3:38 PM, menon.nisha...@gmail.com menon.nisha...@gmail.com wrote: On Thu, Jan 30, 2014 at 3:27 PM, Robert Nelson robertcnel...@gmail.com wrote: On Thu, Jan 30, 2014 at 2:48 PM, Mark Pupilli mpupi...@gmail.com wrote: Hi, I have been using kernel 2.6.32 for years and decided it was time to upgrade to a more recent one so I chose the following as it can run the board safely at 1GHz: technically it's still not safe see Nishanth's response when i asked him yesterday about it.. https://lkml.org/lkml/2014/1/29/446 yep - so it is.. I am more than happy to guide folks if anyone is interested in pitching in as we work with upstream in the parcels needed. As the default beagleboard kernel patchset wrangler, I can help out where i can. (plus i have lots of beagle-xm generations running for testing) I have those 6 patches you've posted so far, in my v3.14-rc0 tree i'm prepping for users. 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 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] Re: Boot Android (TI-JB) on beaglebone black from SD card
On Thursday, January 30, 2014 7:04:05 PM UTC+5:30, Mahendra Gunawardena wrote: I am trying to boot Android (TI-JB) on to a Beaglebone Black system. I am referencing the TI Android JB-4.2.2http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_DeveloperGuide *Hardware:* - Beaglebond black Rev A5C with Angstrom loaded - 4D system resistive touch LCD cape (4DCAPE-43Thttp://www.4dsystems.com.au/product/22/125/Beagle_Bone_LCD_Capes/4DCAPE_43/ ) I don't think this cape is supported in the TI kernel - 5V power supply - USB connected to Host PC (Ubuntu 12.04 LTS) *Software* - Beaglebone black has the stock Angstrom Linux - uSD card has JB 4.2.2, I have built the kernel *Connections* - 5V power supply - mini-USB connected to Host PC (Ubuntu 12.04 LTS) On boot/power up I held the S2 (uSD boot) button and release the button. I was expecting the system boot from the uSD card with Android. I don't see any of the USERx LED's illuminated. Do I need to make change to the display resolutions? What am I doing wrong? Any suggestions? Attach few pictures of the hardware too . http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/791/7115.IMAG0214.jpghttp://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/791/5164.IMAG0215.jpg I have read the following post toohttp://e2e.ti.com/support/embedded/android/f/509/t/282310.aspx . I have ordered the Serial to USB cable will post the log when available You could try to see if you are able to connect to BBB using ADB. It works for me. Wait 2-3 minutes after booting and then try and open the adb shell. You can refer to the TI user guide for configuring ADB. -Vishveshwar -- 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.
