[beagleboard] Controlling power to USB connections
uname -a Linux beaglebone 3.8.13 #1 SMP Thu Sep 12 10:27:06 CEST 2013 armv7l GNU/Linux Is it possible to control the power to the USB port on the board or a HUB from the CLI? My scenario is that I'd like to be able to turn something on\off that is powered from the USB connection. Thanks, -p -- 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/d/optout.
[beagleboard] bmp085-i2c kernel module doesn't detect bmp180
Hello I have a cape with a MPU6000 and a BMP180 both connected to i2c-1 They both show up with i2cdetect -r 1 but nothing happens when i modprobe bmp085-i2c or inv_mpu6050 Im not sure if inv_mpu6050 supports mpu6000 but as far as I can read the bmp085-i2c code it should support bmp180 Do I need to do something else / enable something for these kernel modules to work? Im using ubunbu 13.10 with kernel 3.8.13-bone40 Thanks in advance -- 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/d/optout.
Re: [beagleboard] Re: [beagleboard-gsoc] Re: Here is the BeagleBone Debian (beta + fixes) image you want to test (2014-03-19)
*Debian X11/LDE display problem ?* hello, I was having trouble to debug a problem related with the bootup process and the LDE GUI display. I am just a beginner so I'm not really sure what or why, but in the end it worked for me. *Configuration / Notes:* *BBB: Rev A5C *Power source: Using barrel connector +/- USB connector *Monitor: Samsung S22B300 Sync-master *Debian Build: root@beaglebone:# uname -a = Linux beaglebone 3.8.13-bone41 #1 SMP Tue Mar 4 22:51:47 UTC 2014 armv7l GNU/Linux *uEnv: cat /proc/cmdline = console=ttyO0,115200n8 video=HDMI-A-1:1024x768 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait fixrtc quiet init=/lib/systemd/systemd *Good HDMI cable, validated with stock Angstrom Ubuntu image; GUI works fine with these images *Debian configuration tested on separate TV monitor works fine - boots to GUI *VNC to Debian display GUI - no problem *Observation / Issue* *Boot process looks normal, Linux Penguin displays; proceeds to display *The IP Address for eth0 displays login prompt; auto login continues, screen goes blank and then after about 5 seconds the screen goes into power save mode. *Selecting tty2, the screen exists from power save mode and shows login prompt *Returning to tty7 the screen is blank and then returns to power save mode *echo 0 /sys/class/graphics/fb0/blank has no impact (as root) *Pulled the EDID info following http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI and tried different resolutions with no change in the observations noted above. Finally, after many tests, google-ing, re-flashing, trying to understand the systemd/init.d/start process (still confused about how the boot process works) , I found some hints here; http://archlinuxarm.org/forum/viewtopic.php?f=28t=5780 In the end, I (*waning = I am a beginner so use this at your own risk*) sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup sudo apt-get install xserver-xorg-video-fbdev sudo reboot and I have the LDE desktop !!! I'm noticing some errors in /var/logs/Xorg.0.log related to FBDEV(0): FBIOPUTCMAP: Invalid argument ,but I'll leave that for another day. cheers On 22 March 2014 13:38, selsin...@gmail.com wrote: On 20/03/14 15:56, Robert Nelson wrote: bootup (wicd seems to take a good 5-15 seconds to get a valid ip address over dhcp, conman is slightly faster). You can see the ethernet driver taking it's sweet time over dmesg: [ 29.139188] net eth0: initializing cpsw version 1.12 (0) [ 29.142439] net eth0: phy found : id is : 0x7c0f1 [ 29.142650] libphy: PHY 4a101000.mdio:01 not found [ 29.147705] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 29.164068] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 32.222827] libphy: 4a101000.mdio:00 - Link is Up - 100/Full [ 32.222962] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 34.697540] net eth0: initializing cpsw version 1.12 (0) [ 34.699719] net eth0: phy found : id is : 0x7c0f1 [ 34.699817] libphy: PHY 4a101000.mdio:01 not found [ 34.705082] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 34.715656] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 35.108521] net eth0: initializing cpsw version 1.12 (0) [ 35.110713] net eth0: phy found : id is : 0x7c0f1 [ 35.110812] libphy: PHY 4a101000.mdio:01 not found [ 35.116039] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 35.126630] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 37.102955] libphy: 4a101000.mdio:00 - Link is Up - 100/Full [ 37.103082] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready However, if we enable it in [/etc/network/interfaces], the serial login prompt will not show up till after eth0 gets a valid ip or the 2 minute dhcp time out. So boot times fall from the 12-15 seconds to 30ish. Something is wrong there, it appears that something is bringing the link up/down three times. I think three seconds to get link is a bit long, but I see the same. It's doing it three times that's costing all the extra time. Any possibility of dodgy cable or hardware somewhere ? Regardless, DHCP shouldn't block serial console, it should immediately daemonize and let startup move on. If it doesn't then that's a bug. FWIW I see a single cycle of what's in your dmesg like this: [5.480948] net eth0: initializing cpsw version 1.12 (0) [5.557625] net eth0: phy found : id is : 0x7c0f1 [5.557707] libphy: PHY 4a101000.mdio:01 not found [5.557716] net eth0: phy 4a101000.mdio:01 not found on slave 1 [5.564342] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [8.637383] libphy: 4a101000.mdio:00 - Link is Up - 100/Full [8.637428] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready In context it looks like 13:47:40.543 kernel: [4.948036] NET: Registered protocol family 10 13:47:40.543 kernel: [5.024912] EXT4-fs (mmcblk0p2): re-mounted. Opts:
Re: [beagleboard] BBB no autoboot of uSD
Ah finally got my toolchain to work with these instructions: http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot The u-boot.img I compiled out of there works just fine - so now let's see what happens when I hack it :D On Saturday, March 22, 2014 12:46:51 PM UTC-4, Louis Thiery wrote: Jumping in a little late perhaps but my concern is slightly relevant to the discussion here. Nelson desribes the boot order: bootrom loads MLO from eMMC (if that fails it moves to microSD) MLO loads u-boot.img from eMMC u-boot.img first looks at microSD for uEnv.txt, reads that file in. I'd like to reverse that last step and make it to default to uEnv.txt from the eMMC. But I have no idea how to modify u-boot.img. What should I be reading? Or is there a u-boot.img that exists already that will allow me to boot off of the eMMC even if the flasher uSD is present (which I understand is the HW default)? Thanks, Louis On Friday, March 7, 2014 11:12:13 PM UTC-5, Loren Amelang wrote: My long but successful learning experience is reported in: https://groups.google.com/forum/#!topic/beagleboard/zNtdwtPf2Q8 Definitely not simple, but possible... Without making any changes to the eMMC installation! On Monday, February 17, 2014 10:17:22 PM UTC-8, Loren Amelang wrote: Robert, My BBB absolutely must default to booting from the uSD. I know I could short the boot switch, or move pull-up/down resistors, or create a hardware switch gated from reset, but I don't want to lose hardware compatibility with other BBB boards, or give up the option of manually booting from eMMC occasionally. The code you suggest here sounds perfect - but I'm not positive what to do with it. From the formatting of the text, I suspect it is intended to be compiled into a new u-boot.img and MLO image, but I'm not sure how to do that. Before I spend hours learning how, is there a chance I could just insert the basic ideas into my uEnv.txt as mmcboot=mmc dev 0; if mmc rescan ; then ...? It does look like uEnv.txt is read before the mmcboot command runs... -- 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/d/optout.
Re: [beagleboard] Re: [beagleboard-gsoc] Re: Here is the BeagleBone Debian (beta + fixes) image you want to test (2014-03-19)
Since I saw GPU support on the newer 3.8/3.12 kernels will there be a version that has PVR support? Thanks ~Chris -- 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/d/optout.
[beagleboard] HELP. dead beagleboneblack
Hi. I bought BBB A6A new, 1 month ago. It worked OK out-of-the-box. I power it from the USB from a windows laptop and poke around with a browser. No problems. I soldered on the proper JTAG header very carefully and now it is dead. The Power LED lights up, but nothing else happens. I am handy with electronics, programming and linux. What can I do to troubleshoot the BBB? Is there a DIY procedure? I did not reflash the eMMC or a SDcard. thanksdd -- 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/d/optout.
[beagleboard] Re: Angstrom passwords
Had same problem. Following the Getting Started with Beaglebone book from Make seems to give this result. Was able to get to a console and add a user manually, and get around it. Shouldn't have to do this, though, honestly. This kit is aimed at beginners. Surely this sort of gotcha would have come up in testing... -Michelle On Thursday, September 12, 2013 6:19:27 AM UTC-7, Gabriel L wrote: Hi, I'm new to the Beaglebone Black but didn't have problems trying out several OS's. As Ubuntu was too slow for my taste I switched back to Angstrom. After loading the latest img to eMMC, several days in a row I could do update/upgrade without a problem until the Angstrom logo appeared. The login procedure was changed drastically as the automatic login was gone and replaced by the choice 'mpd', 'xuser' and 'Other'. As other I tried 'root' but nothing worked. I could not login. I couldn't find the correct passwords anywhere. Can someone help? 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/d/optout.
[beagleboard] Makathon Open Source hardware hackathon | Silicon Valley San Carlos | March 28-30
Hardware Hackathon | 28-30 March | Techshop San Carlos Beableboard Community,Hardware hackers, Programmers, Arduino enthusiasts, Roboticists, Here is THE must attend hackathon of the season and here's why:1) COOL THEMES: Social Impact | Improved Wearable | Music makes me happy *2) MENTORSHIP - these experts will be on-call to coach* - Jeff McAlvay | Tempo Automationhttp://makathon.us3.list-manage1.com/track/click?u=c2ff091fee6383866f15d3e8bid=b0db168701e=5822d17a95 | rapid prototyping - Jonathan Palley | Spire Scienceshttp://makathon.us3.list-manage.com/track/click?u=c2ff091fee6383866f15d3e8bid=a8fe787f2de=5822d17a95 | DFM, manufacturing - Laura Kassovic | MBIENTLABhttp://makathon.us3.list-manage.com/track/click?u=c2ff091fee6383866f15d3e8bid=f87501a743e=5822d17a95 | Wearable device hacking - Luke Dahl | CCRMA Stanfordhttp://makathon.us3.list-manage1.com/track/click?u=c2ff091fee6383866f15d3e8bid=e35c5a41d6e=5822d17a95 | Music Technology - G. Carter Stokum | Automata Labshttp://makathon.us3.list-manage.com/track/click?u=c2ff091fee6383866f15d3e8bid=871efd4e9ce=5822d17a95 | Electronics Robotics - Madelynn Martiniere | Spark Plug Labshttp://makathon.us3.list-manage.com/track/click?u=c2ff091fee6383866f15d3e8bid=5b0bb474b8e=5822d17a95 | Growth hacking *3) COMPONENTS PRIZES* - *Electric Imp* will provide a kit per team to connect your device to wifi! - *Voltaic System* will provide a 6 Watt Solar Charger Kit as a prize. - *BITalino* will provide a physiological sensors kit as a prize - *LittleBits* will provide a kit as a prize. - and many more surprises to come! *4) MEET THE JUDGES* - Jonathan Charles, VC Team, *Samsung Catalyst Fund* - Kevin Hale, Partner, *Y Combinator* - Carlos Uranga, Founder, *OpenFuelCell* Join us for an awesome weekend of hardware hacks! Pitch your idea or join a team, meet like-minded people, learn and have fun. We'll provide an arduino board per team with dev kit, workshop and food^^ All level welcome and feel free to bring your beagleboard~ [image: Eventbrite - Makathon SV]http://makathon.us3.list-manage2.com/track/click?u=c2ff091fee6383866f15d3e8bid=af9b549fa5e=5822d17a95 Hope to see you there, if any question, reach out to carole[at]makathon[dot]org -- 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/d/optout.
[beagleboard] Re: Here is the BeagleBone Debian (beta) image you want to test
How can I make the microSD image to not copy the image to the eMMC of my Beaglebone Black? That is, by default, when I insert the SD card with this Debian image, and then power the BBB, it will automatically start flashing the Debian image to the BBB internal disk (eMMC). I notice it because after some time the 4 leds stay lit, meaning it has completed the process. I don't want it to happen because I want to use Debian directly from the bootable SD card, and keep the eMMC intact. (probably I just need to delete the script that flashes the image to the eMMC, but where is it?) Em quarta-feira, 5 de março de 2014 19h51min19s UTC-3, Jason Kridner escreveu: The latest BeagleBone Debian images are now posted at: http://beagleboard.org/latest-images/ If you've upgraded the firmware on your BeagleBone or BeagleBone Black in the past, the experience will be quite similar, but you might find the eMMC flashing times a bit faster (~15 minutes rather than ~45 minutes) due to less post-installation processing. Using the 2GB uSD card image also flashes a bit faster and can be resized to whatever your uSD card size is using some scripts under /opt/scripts/tools. Many, many thanks to Robert Nelson, Rob Rittman, Dave Anders, Cody Lacey, the Cloud9 IDE team and so many others in getting us this far. Please take the time to give a detailed look over this image and report any issues to the bug tracker on elinux.org: http://bugs.elinux.org/projects/debian-image-releases While plugged in over USB, you'll see the familiar BEAGLE_BONE drive with START.htm to tell you how to get the drivers configured if you haven't already done so: [image: Inline image 2] Clicking the link or visiting http://192.168.7.2, you'll see the familiar on-board served documentation: [image: Inline image 1] I've introduced a few bugs to the documentation ( http://github.com/beaglebone/bone101 and http://beagleboard.github.io/bone101), so expect to find a lot of issues there. Patches are welcome as are notes in the bug tracker to make sure I don't miss dotting any i's or crossing any t's. This is your chance to try to get some documentation into the system you'd like to see. I felt it was pretty safe to save the documentation as an in-beta item because it shouldn't impact functionality. One of the biggest new features you'll see is when you click on the Cloud9 IDE link: [image: Inline image 3] This is a pre-open-source-beta-only release of version 3 of their IDE. Down at the bottom of the Cloud9 IDE you'll see a new terminal window that runs a full 'tmux' session. You can open up a bunch of these and it makes logging into the board and executing command-line operations *super* simple. Cloud9 IDE version 3 now includes support for Python and the Adafruit_BBIO library is included in these Debian images. That means you can simply paste in your Python code and hit the run button, without any additional download. I checked this out myself by doing a quick LED blink using the Adafruit tutorial ( http://learn.adafruit.com/blinking-an-led-with-beaglebone-black/writing-a-program ): [image: Inline image 4] You should also note that the /var/lib/cloud9 directory now contains a git clone of that bone101 repo (http://github.com/beagleboard/bone101), so you can start using the Cloud9 IDE to edit the content live. What I recommend is creating your own fork of the repo and sending me pull requests of any changes you'd like to see. You can also edit C/C++ code in the Cloud9 IDE, but no 'builder' or 'runner' plug-ins are provided. You will, however, find the Userspace-Arduino (http://elinux.org/Userspace_Arduino) code in /opt/source/Userspace-Arduino. Here's a quick little exercise you can do to blink LED0: root@beaglebone# cd /opt/source/Userspace-Arduino/arduino-makefile/examples/Blink root@beaglebone# perl -i -pe 's/13/14/g' Blink.ino root@beaglebone# make root@beaglebone# ./build-userspace/Blink.elf For more advanced C/C++ developers, future releases should include https://github.com/jackmitch/libsoc. Those familiar with Linux will also note that the init system is 'systemd', which has been helpful in providing reasonable boot times. If you are looking for the journal, you can explore it using 'systemd-journalctl'. I use a Mac and despite the latest version of HoRNDIS fixing issues with Internet Connection Sharing, getting on the WIFI at home makes getting my BeagleBones on the network much easier, further making grabbing new packages with 'sudo apt-get install' much simpler. Drivers and firmware for many common USB WiFi dongles are included, so be sure to report any that you find missing. These latest images include the drivers for the popular UWN200 adapters provided by Logic Supply. To test it out myself, I uncommented and edited the wlan0 entry in /etc/network/interfaces (including replacing wlan0 with ra0), shutdown,
[beagleboard] how to add a simple kernel module with customized kernel
hai all, i followed this link to compile a kernel for bbb http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-BasicRequirements i try to mount my kernel using sd card, after a series of bugs finally i can able to boot my kernel using the precompiled ubuntu rootfs which was given in the above link. but when i tried to add a hello world module into my bbb . i got the following error i googled it all the possible ways but none of them helped me . *ubuntu@arm:/opt$ sudo insmod hello.ko * *Error: could not insert module hello.ko: Invalid module format* *ubuntu@arm:/opt$ * when i execute modinfo command from the bbb. i got the following log information ubuntu@arm:/opt$ modinfo hello.ko filename: /opt/hello.ko description:A Simple Hello World module author: sivakumar license:GPL srcversion: F545620F75762B1AAE668ED depends: vermagic: 3.8.13 SMP mod_unload modversions ARMv7 p2v8 help me how to insert the module into my beagelobne black kernel. regards siva -- 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/d/optout.
