**** BEGIN LOGGING AT Fri Jan 03 02:59:59 2014 Jan 03 03:06:51 hi Jan 03 05:46:15 hai guys need some help i have a GY-521 (MPU6050 Module) and i am not able to read the values of x,y,z of accelerometer or x,y,z of gyroscope .... whenever i move the module to see if the register values are changing ,it is still same..... Jan 03 05:46:36 i am running Angstrom OS in my BBB Jan 03 05:47:24 and i used the command "i2cdump -y 1 0x68 Jan 03 05:53:38 any hints as to why the latest Anstrom/Beagebone bone image doesn't include VNC/web-based shell? just 22,80 and 3000 are open. (BeagleBone Black, latest Angstrom) Jan 03 07:24:05 hi.. is that the device tree is fully associated with beaglebone cape? Jan 03 10:06:09 How are you controlling gpio pins from a webinterface? I have looked at PyBBIO but that does not yet support 3.8 kernel. What other alternatives are there? Jan 03 10:06:20 besides coding my own Jan 03 13:21:49 :) Jan 03 13:24:01 https://www.google.com/patents/US6830455 Jan 03 14:44:14 silly patents. Jan 03 16:34:17 [kernel] RobertCNelson pushed 1 new commit to 3.12: http://git.io/Y1Ib6g Jan 03 16:34:17 kernel/3.12 5acc45a Robert Nelson: 3.12: update to v3.12.6... Jan 03 16:39:23 (cast)(cast)struct->member Jan 03 16:39:25 gaaah Jan 03 16:39:54 if that's within 10 lines of the file, should I keep reading ? Jan 03 16:41:25 heh Jan 03 17:00:00 [kernel] RobertCNelson pushed 1 new commit to 3.8: http://git.io/tH4WRQ Jan 03 17:00:00 kernel/3.8 9a349c4 Robert Nelson: 3.8: add network fix from: https://groups.google.com/d/msg/beagleboard/mfQwHdfHyoo/SA9EnjpXoAsJ... Jan 03 17:05:02 Hi all.. Jan 03 17:05:56 can anyone give me some hints on the TI lcdc module? Jan 03 17:06:07 think I need to change some kernel parameters around Jan 03 17:06:08 I am using RS232 cape for BBB, when i connect it to board and boot it. at boot time my slots are enabled Jan 03 17:06:33 flow control ?! :) Jan 03 17:06:55 i have ensured that clock and pin mux for UART2 (ttyO2) is correct but i can not commnucaicate using a loo-back Jan 03 17:07:01 *loopback Jan 03 17:07:22 Checked that as well, no HW Flow control is enabled Jan 03 17:07:23 how are you connecting to the port? Jan 03 17:07:29 any other thought? Jan 03 17:07:54 if you're accessing it direct .. did you stty to set it up? do you have correct permissions to access the port? Jan 03 17:08:45 yes, i am root. Actually i have done a loopback on BBB's Header and tried i loopback, it works but when i mount cape.then it doesn't work Jan 03 17:09:13 the board header or the cape? Jan 03 17:09:20 using a wire Jan 03 17:09:49 which port - the beagle debug header or the cape port? Jan 03 17:09:55 not accessing directly, using minicom Jan 03 17:11:04 restarted minicom to affect the port change? Jan 03 17:11:11 (its weird like that) Jan 03 17:11:27 cape RS232 doesn't work, w/o cape BBB's P9.21 & P9.22 that wors Jan 03 17:11:34 *works Jan 03 17:11:56 The Cape doesn't work!! Jan 03 17:12:04 d'oh Jan 03 17:12:09 so the uart is fine .. Jan 03 17:12:17 Yes. Jan 03 17:12:38 I can assure that!! Jan 03 17:12:42 checkde cape jumpers :) Jan 03 17:12:51 Yes, UART2 Jan 03 17:13:08 why restart minicom by the way?? Jan 03 17:13:23 would that really matter? Jan 03 17:13:38 I find because it initialises the port on startup .. I'm not convinced it closes/re-opens the ports Jan 03 17:13:55 I always specify them manually on the command-line now ... minicom -d /dev/tty??? Jan 03 17:14:29 but then minicom has HW Flow control enabled by default. Jan 03 17:14:41 Change is seperately?? Jan 03 17:14:46 ah I must have fudged that too :) Jan 03 17:15:14 but if you've proved the uart out fine .. its something ont he board itself Jan 03 17:15:44 you mean cape?? Jan 03 17:15:53 yes Jan 03 17:16:42 I have tried UART4 on that as well but that didn't work as well. Jan 03 17:16:56 Any chance that trying UART1 might work?? Jan 03 17:17:17 I think uart1 is the debug port .. so you can try that .. Jan 03 17:17:43 probably won't be able to get full access to it though Jan 03 17:17:57 Nope. I mean ttyO1, debug port is ttyO0!! right? Jan 03 17:18:10 anybody has an Angstrom image that can be flashed directly on the eMMC ? Jan 03 17:18:39 http://beagleboard.org/latest-images Jan 03 17:18:57 hmm .. let me refresh ..t oo many uarts on that board Jan 03 17:19:09 yeah. :) Jan 03 17:19:15 i don't want the eMMC flasher Jan 03 17:19:16 I'm using uart4 :D Jan 03 17:19:27 an image that can be directly flashed on the BBB without the uSD Jan 03 17:19:42 how do you propose getting it onto the emmc?? :) Jan 03 17:19:47 usb boot Jan 03 17:19:47 without a uSD? Jan 03 17:19:51 serial boot Jan 03 17:19:52 https://github.com/ungureanuvladvictor/BBBlfs Jan 03 17:19:53 and Jan 03 17:19:55 magic Jan 03 17:20:07 heh magic .. I'm clean outta that. Jan 03 17:20:09 vvu|Log: you still limited by ramdisk size? Jan 03 17:20:13 yep Jan 03 17:20:18 did not do more work on the project Jan 03 17:20:23 well, the stock images take like 2gb, no? Jan 03 17:20:28 or 4 Jan 03 17:20:41 so even if you had one for emmc, how would you flash it? Jan 03 17:20:47 in .xz format is less than 512mb Jan 03 17:20:52 oh Jan 03 17:20:54 ok Jan 03 17:20:55 i think koen gave me one Jan 03 17:21:07 lemme search for the link, had it in the BeagleDroid sources Jan 03 17:21:19 @ You mean UART4 on cape?? Jan 03 17:21:39 which device node /ttyO4?? Jan 03 17:22:00 on the pins .. we have an external TTL->RS232 converter chip .. like the cape Jan 03 17:22:04 found it! http://dominion.thruhere.net/koen/angstrom/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.09.10.eMMC.img.xz Jan 03 17:22:29 wooops .. sorry Prat .. yes mine is using UART2 Jan 03 17:22:57 I have a kernel option to manually force the cape 'on' Jan 03 17:23:05 err .. Load the cape Jan 03 17:23:07 vvu|Log: that is ancient Jan 03 17:23:10 :) Jan 03 17:23:21 yeah i know...but i need one just to access some pwms and stuff Jan 03 17:23:24 embedded development frequently is. Jan 03 17:23:25 nothin fancy Jan 03 17:23:31 Ancient, that is Jan 03 17:23:34 do you use uEnv.txt for that?? Jan 03 17:23:37 yes Jan 03 17:23:48 givin me a headache with HDMI/LVDS currently Jan 03 17:24:20 Prat: if you do a 'dmesg' you should see it identify and load the pinmux for the UART by the cape-manager Jan 03 17:24:39 that proves the EEPROM on the cape works Jan 03 17:24:42 yes, it does. Jan 03 17:25:09 there is no error. My slot#1 is okay, as it has to be for BB-BONE_SERL-03 Jan 03 17:25:48 kernel wouldn't load it unless it detected cape on board!! Am i right? Jan 03 17:26:12 not strictly true :) Jan 03 17:26:31 can't show the dmesg o/p. do not have cape on or BBB up. Jan 03 17:26:53 Then what do you suggest? Jan 03 17:27:10 sounds a bit like toasted cape .. but I find that hard to believe Jan 03 17:27:17 to ensure that EEPROM on cape works.. Jan 03 17:28:12 Infact i tried two different capes. both of them do not work. that is why i doubt, its SM wrong with firmware. Jan 03 17:28:59 if the uart signals are present fine on the P8/9 header .. Jan 03 17:29:11 you're just linking through pins 2/3 on the serial port, yes? Jan 03 17:29:19 the DB9 connector? Jan 03 17:29:22 yes Jan 03 17:29:27 that is correct. Jan 03 17:30:15 it works with a jumper from P8#21-22 Jan 03 17:30:44 nope ..its P9#21-22 Jan 03 17:31:06 oops my bad Jan 03 17:31:20 :) Jan 03 17:31:31 yeah those are the pins I'm using fine Jan 03 17:32:13 the only difference between the cape and my board .. is the physical chip :) Jan 03 17:33:20 I remember there are two switches on Cape, i think those are used for addressing EEPROM on I2C bus. Jan 03 17:33:39 yes - to avoid conflicts when you stack capes Jan 03 17:33:57 Can that be problem? Jan 03 17:34:26 when multiple peripherals try to access the same pins/resources, yes .. but more-so if two EEPROMs try to reply when configured :) Jan 03 17:34:41 but as far as i understand the concept of capes, it is just two load the overlay automatically, otherwise no other SW configuration is needed for it. Jan 03 17:34:44 am i right? Jan 03 17:35:26 the cape manager manages the pin multiplexes .. and takes away user configuration Jan 03 17:35:33 thats the principle Jan 03 17:35:51 i mean for UART2 to work, no other SW configuration is needed. Jan 03 17:36:19 no. But you've proven the port works with a link on P9 Jan 03 17:36:31 so, Any suggestions?? :) Jan 03 17:36:41 yes that is correct. Jan 03 17:37:07 if you can see a signal (voltmeter or oscilloscope) on the P9 pins with the cape plugged in .. and signals on the output ... Jan 03 17:37:15 somehow your signal is getting "lost" Jan 03 17:38:02 you mean the RS232?? Jan 03 17:38:04 DB9 Jan 03 17:38:05 I'm inclined to say its an electrical problem rather than a software one Jan 03 17:38:19 hmmm. Jan 03 17:38:48 Yeah let me use a scope and see the output. Jan 03 17:38:58 Thanks for the help.. :) Jan 03 17:39:02 welcome Jan 03 17:39:23 @ Jan 03 17:58:57 I am have trouble getting gpsd to recognize my Adafruit GPS Breakout. It is connected to my BBB through UART1 (cat /dev/ttyO1 and minicom both work and so does gpsmon /dev/ttyO1) Jan 03 18:06:48 this is what happens when i run gpsd http://pastie.org/8597750 Jan 03 18:07:39 everything seems to work except for the test client cgps (i run it in a separate terminal window so i dont need to end the gpsd process) Jan 03 18:07:53 does the gpsd have permissions to access the serial port? Jan 03 18:08:15 and nothing else is trying to acccess the port at the same time .. eg. minicom/cat/etc Jan 03 18:08:21 yeah i think so, im running everything as root Jan 03 18:08:33 yuk, but ok :) Jan 03 18:09:17 when i use the -n option on gpsd to query without waiting for client calls (a suggestion ive seen else where) gpsd does seem to spit out the proper information Jan 03 18:09:57 but no matter what i've done cgps hasn't been able to pick up on it... i'm trying to get this to work before writing my own client Jan 03 18:10:15 ah yes .. it looks like cgps can't get to the gpsd .. problem with the listening port .. Jan 03 18:11:38 I'm not really sure how else to test it since the other test clients (xgps) are GUI and i'm just ssh'ing into the BBB Jan 03 18:12:02 you're using a stock version of BBB angstrom? Jan 03 18:12:12 you should be able to tunned the X-session using ssh -X :) Jan 03 18:12:16 tunnel* Jan 03 18:12:16 yeah, just how it shipped Jan 03 18:13:44 whenever i've tried that i get this error http://pastie.org/8597774 Jan 03 18:14:04 ah you'll probabyl need to enable it in the sshd_config Jan 03 18:14:22 ok yikes .. yeah thats bad Jan 03 18:14:52 do i not have the packages/x setup on my BBB? Jan 03 18:15:24 it can't find gtk for some reason .. I woulda thought that would be in the stock distro Jan 03 18:16:37 i hasn't really presented much of a problem for me (except this) since i haven't needed any of that. I recently ordered the stuff i need to use the bbb standalone (microHDMI etc) and i might try reinstalling angstrom or another distro Jan 03 18:17:27 on line 7 of the gpsd log http://pastie.org/8597750#7 it says that gpsd is stashing /dev/ttyO1 Jan 03 18:18:55 I looked on the troubleshooting page of http://www.catb.org/gpsd/troubleshooting.html#firsttry and the page says that gpsd cannot find the device? but that may just be for usb gps's? Jan 03 18:18:57 yeah I saw that Jan 03 18:20:21 ok so .. you can see serial data on the port ok Jan 03 18:20:46 do you have gpsmon ? Jan 03 18:21:33 yeah gpsmon /dev/ttyO1 works just fine Jan 03 18:24:24 did you do the two steps before .. killall gpsd and remove the lockfile? Jan 03 18:24:54 yeah killall gpsd and rm /var/run/gpsd.sock? Jan 03 18:25:25 yup Jan 03 18:26:02 I'm suspicious of Line 3 .. http://pastie.org/8597750#3 Jan 03 18:27:00 yeah im not quite sure where that comes from, I was suspicious of the way i was connecting to the internet on the BBB (through usb to my computer) but it has the same error before i set up the connection as well Jan 03 18:28:32 hmm .. did you install from source or a package? Jan 03 18:29:33 i think i just used the package Jan 03 18:29:38 opkg install gpsd Jan 03 18:35:33 bunsen: do you recall whether angstrom downloaded any additional packages? Jan 03 18:35:53 I'm seeing three/four related packages available Jan 03 18:36:22 i dont think so? i have tried installing other packages and uninstalled them (ntp) but i dont think gpsd installed others Jan 03 18:36:49 oh yeah, i installed the python-pygpsd package.. or soemthing like that Jan 03 18:37:21 just looking at http://pandorawiki.org/GPS Jan 03 18:38:38 it should be possible to telnet to the gpsd .. thats where I think one of the problem(s) lie(s) Jan 03 18:39:49 yeah i tried the telnet instructions from http://www.catb.org/gpsd/troubleshooting.html#telnet but i didnt get anything. Give me a second ill try again and post the result Jan 03 18:41:59 http://pastie.org/8597843# Jan 03 18:43:17 ah that looks about right Jan 03 18:44:47 so i guess theres nothing coming on the ip4 port that gpsd clients are looking for? Jan 03 18:45:12 the gpsd is like a server .. it makes gps data available to anything that connects to it Jan 03 18:45:45 at the moment .. it doesn't seem to 'see' a gps receiver by the looks of things Jan 03 18:47:50 well when i run gpsd with -n there is gps data parsed and spit out onto te console screen, but none of it seems to make it to the clients? could this stem from the problem with http://pastie.org/8597750#3 ? Jan 03 18:48:20 besides, cgps .. what other clients are you using? Jan 03 18:48:27 and this is over the usbnet connection, yes? Jan 03 18:48:43 im not quite sure what that means Jan 03 18:49:05 ive been just ssh'ing into the BBB and trying to get cgps to work Jan 03 18:49:17 ok grand. Good starting place. Jan 03 18:49:27 so cgps is failing .. currently? Jan 03 18:49:32 im trying to get this to work before i start working on my own client haha Jan 03 18:49:36 yeah and telnet Jan 03 18:49:56 gpsmon and cat/minicom'ing to /dev/ttyO1 works just fine Jan 03 18:50:25 ok so that proves the serial connection to the GPS device is ok Jan 03 18:50:30 Hi All.... I am looking at beaglebone to learn linux porting and driver development.... having easy jtag debugging is essential for me. In this regard I need your advice on selecting beaglebone or BBB Jan 03 18:51:55 rkc: I think you'll find most embedded devices have JTAG connections for factory test/debug Jan 03 18:52:17 the only difference will be whats accessible and supported by the community at large Jan 03 18:52:23 stt_michael yeah thats what was confusing me, it seems like everything works except for gpsd's "server"-things. I've even gotten small clients that connect to the GPS with serial to work (just parsing raw data) but i wanted to use gpsd for more... good-ness Jan 03 18:52:44 sure .. I can see an application I would find useful for gpsd .. and a usb gps dongle :) Jan 03 18:53:39 is that the issue im having? UART rather than USB? Jan 03 18:54:17 it should work with either .. but there are catches because of usb hotplugging Jan 03 18:55:01 stt_michael: I earlier had mini2440 and made it work with openocd... but i read about beaglebone having inbuilt jtag over usb... i am unable to understand what does that mean... is it full fledged jtag or some kind of client server mechanism like adb in android ? Jan 03 18:55:31 stt_michael: yeah i was just following along this guide since it is the right gps chip http://learn.adafruit.com/adafruit-ultimate-gps-on-the-raspberry-pi Jan 03 18:55:43 rkc: wouldn't personally recommend jtag-over-usb .. thats not gonna be native by definition :) let me look at a bbb board sec. Jan 03 18:55:57 basically my requirement is i should be able to debug starting from uboot till kernel and module level... Jan 03 18:56:32 yeah you'll be fine on the debug serial port :) Jan 03 18:56:54 there's a 5pin header on the BBB baseboard .. you'll need a TTL converter .. think the BBB is 3v3 for reference Jan 03 18:58:00 bunsen: I'm reminded of a known fact of GPS modules .. they often take a LONG time to start up Jan 03 18:58:45 rkc: if you can handle linux debugging .. the serial port/console should be adequate for most purposes. U-boot gives you a blob of text on boot. Jan 03 18:59:03 Then you get kernel messages, etc as per usual Jan 03 18:59:20 you can then interact with a serial console as you would connected directly. Jan 03 19:00:17 bunsen: have you left gpsd running, tried cgps and gone to make a hot drink/etc ?! Jan 03 19:00:55 michael: but i need a full fledged JTAG where I can check for register dumps... I am not used to putting printk's in sources :-) Jan 03 19:01:28 well i've left cgps running and it just times out. the gps board has an led on it and i know that it has locked on a signal and warmed up so that shouldn't be the issue Jan 03 19:01:45 rkc: yes, would love to learn how to do that properly some day Jan 03 19:02:09 rkc: from http://www.elinux.org/Beagleboard:BeagleBoneBlack#Optional_JTAG - To install the JTAG header, all you have to do is install P2 on the back of the board. Jan 03 19:02:09 P2 is a Samtec FTR-110-03-G-D-06 connector and can be purchased from Samtec or any of their distributors. Jan 03 19:04:03 rkc: http://beagleboard.org/static/beaglebone/a3/Docs/ccs-jtag-simple.htm - maybe applicable Jan 03 19:04:26 yes... i just read through... thats why I wanted to understand the difference between jtag over USb and the one given by BBB. They seem to have saved some cost by removing FTDI on BBB Jan 03 19:04:54 yeah ftdi chips are expensive :( Jan 03 19:05:07 although ftdi are making some cheaper cut-down versions Jan 03 19:05:55 But for me ease of use is the key... even if its costlier I would go with beaglebone instaed of BBB... but want to take an educated decision after understanding what this jtag over usb means.... Jan 03 19:05:57 for our debugging purposes we use a FTDI usb breakout board or http://www.robotshop.com/en/parallax-prop-plug-usb-to-serial-converter.html Jan 03 19:06:28 bunsen: hmm Jan 03 19:06:43 bunsen: whats your GPS? Jan 03 19:06:59 Thttp://www.adafruit.com/products/746 Jan 03 19:07:30 bunsen: aha, its all starting to fit together ... :) Jan 03 19:08:11 do you think its an issue with the port being locked up or whatnot haha? Jan 03 19:10:10 bunsen: nope .. just made an oversight in configuration somewhere :) Jan 03 19:11:04 bunsen: the limitation with the Pi is it only has a couple of serial ports, and not very accessible Jan 03 19:11:27 but BBB shouldn't have this issue? Jan 03 19:11:32 newp Jan 03 19:15:12 i just did a sanity check and it still doesn't work Jan 03 19:15:14 http://pastie.org/8597952 Jan 03 19:15:38 hrm Jan 03 19:15:51 I'm trying to look up angstrom packages, but the damn website is down Jan 03 19:16:30 can you run "gpsd -Nn -D3 " and paste the results please? Jan 03 19:16:46 or even D4 Jan 03 19:16:52 something just isn't quite right Jan 03 19:17:06 sure one sec Jan 03 19:18:28 i just stopped it after a while because otherwise it would go on forever haha Jan 03 19:18:34 sure np Jan 03 19:21:32 http://pastie.org/8597973 Jan 03 19:23:12 ok .. it definitely gets data.. from what I'm reading the "-n" switch is necessary Jan 03 19:23:37 yeah but that still doesnt help with cgps haha Jan 03 19:24:11 ive tried pointing cgps to the right port too with cgps localhost 2947 and i still get the same error(s) Jan 03 19:29:30 element14.com says the BBB has two ethernet ports---is that right???! Jan 03 19:29:42 no lol Jan 03 19:29:48 just one Jan 03 19:29:52 not as standard! Jan 03 19:30:44 hehe Jan 03 19:30:56 I don't think I've seen a .. cheap .. development platform with more than one ethernet Jan 03 19:31:11 hehe Jan 03 19:31:20 is it just me or are they manufacturing BBBs out of hen's teeth? Jan 03 19:31:22 to have one with many platforms is even a bonus Jan 03 19:31:30 http://www.adafruit.com/products/1278#Technical_Details hmm this is a little confused too Jan 03 19:31:56 i guess 2 -ethernet means two led indicators heh Jan 03 19:31:59 Indicators 1-Power, 2-Ethernet, 4-User Controllable LEDs Jan 03 19:32:12 one LED for power, One LEd for Ethernet, 4 LEDs for user control Jan 03 19:32:22 in fact .. there's the standard 2 LEDs on the ethernet socket Jan 03 19:32:23 2 LEDs for ethernet, link and activity Jan 03 19:32:26 one for link .. one for speed Jan 03 19:32:32 correct .. my bad Jan 03 19:32:39 soekris.com has some nice boards with multiple ethernets though they're outside the bbb price range Jan 03 19:33:01 it depends what you're looking to achieve wiht your system :) Jan 03 19:34:20 currently I would like to achieve "in my hands" =) Jan 03 19:34:46 but computer at farnell says no. at least not until the 7th feb Jan 03 19:34:51 lee: there should be a number of vendors with stock .. Jan 03 19:35:00 try RS ? Jan 03 19:35:04 [RS components] Jan 03 19:35:08 RS is april Jan 03 19:35:16 also, they're RS-holes Jan 03 19:35:31 hmph .. they've grossly underestimated demand .. Again. Jan 03 19:35:43 only other one in the UK is RoboSavvy, which doesn't even have an estimated date Jan 03 19:36:11 kids these days... tsktsk haha Jan 03 19:36:12 I got 21/1 from RS - http://uk.rs-online.com/web/p/processor-microcontroller-development-kits/7753805/ Jan 03 19:36:48 ohh Jan 03 19:37:00 well that's changed since yesterday when it was 3/4/2014 Jan 03 19:37:33 looks like CircuitCo doin another production batch Jan 03 19:38:01 alright stt_michael i've got to go... still mostly clueless on how to solve this issue... i might just reinstall angstrom and start over later, see if that helps Jan 03 19:38:06 sucks .. none in the US - http://www.digikey.co.uk/product-detail/en/BB-BBLK-000/BB-BBLK-000-ND/3884456 Jan 03 19:38:18 bunsen: yeah sorry about that .. attention wandering Jan 03 19:38:27 might wanna try debian if you're gonna scratch it Jan 03 19:38:40 I'm waiting for some LED panels to arrive, should be around mid january at a guess, apparently the pi can't handle the timings but the BBB's PRU can Jan 03 19:38:42 what I'm doing most of my embedded development on beagle/imx6 chips Jan 03 19:38:43 do i lose anything with debian? Jan 03 19:38:56 much better packaging system :) imho! Jan 03 19:39:06 alright thanks for the help! Jan 03 19:39:10 good luck Jan 03 19:40:03 beagle is far superior board to the Pi Jan 03 19:40:39 in all but graphics acceleration/hdmi . but thats what the Broadcom chip was designed for Jan 03 19:40:40 certainly seems to be for this use Jan 03 19:40:57 I still can't believe the Pi's ethernet is via a USB hub chip Jan 03 19:41:06 -puke- Jan 03 19:43:49 and on that happy note .. I need to get home! .. catchya laters! Jan 03 19:44:35 oh btw if you want a really funky embedded board .. with wifi .. check out http://www.wandboard.org/ Jan 03 19:44:52 only downside is no eMMC Jan 03 19:44:52 nah I just want what I'm told will work with the hardware and libraries Jan 03 19:45:10 and I figure idling in here will give me plenty to read when I can't figure out the basics Jan 03 19:45:16 gotta get our 'spare' board RMA'd :/ heh. Jan 03 19:45:35 wish I'd known there was a supply problem last month though, I would have ordered a couple then Jan 03 19:46:00 I foolishly assumed they were widespread, like the pi Jan 03 19:46:39 even the pi has been out-of-stock at times .. the difference is Eben/etc have stepped up production. Bigtime. Jan 03 19:46:44 stt_michael: i got a wandboard in a couple of weeks ago. Jan 03 19:46:55 pretty cool bit of kit. Jan 03 19:47:20 my dual is sittin serving on the bookshelf at home .. its got a project involving the wifi and audio waiting Jan 03 19:47:20 yeah, the pi has had issues, but nowadays they're easy to get hold of Jan 03 19:47:31 pi is cheap. nuff said. Jan 03 19:47:33 mrpackethead: does it suppor~t pxe boot, do you know? Jan 03 19:47:48 anything with ethernet should support netbooting Jan 03 19:48:07 lee, dont' know. Ive only just fired it up with debian, and done a very limited amount of testing. Jan 03 19:48:53 lee: think it should work through uboot Jan 03 19:49:22 ok going going gone .. bbl :p Jan 03 19:49:27 cya Jan 03 21:47:34 hi all Jan 03 21:47:50 anyone know if i can use a BMP085 pressure sensor with a beagleboard rev c4? Jan 03 21:48:42 it's i2c right? Jan 03 21:48:45 then yeah Jan 03 21:49:14 yep, it's i2c Jan 03 21:49:38 do i need to connect this to the expansion header on the board? Jan 03 21:50:52 check derek molloy's spreadsheets for which pins are the SDA and SCL for the different i2c busses. Jan 03 21:50:55 https://github.com/derekmolloy/boneDeviceTree/tree/master/docs Jan 03 21:51:44 this is for the bone and not the rev c4 board that i have. will the pins still be the same? Jan 03 21:51:53 I don't know. Jan 03 21:52:22 Sorry, I didn't read that you were using the beagleboard XD Jan 03 21:53:03 al3xclarke: have a look at the schematic for the trainer board, that has the pins for the i2c interface on the expansion header Jan 03 21:53:06 no problem. i see lots of information using this type of sensor with the bone, but not the earlier beagleboards. Jan 03 21:54:36 prpplague: silly question, but where do i find the schematics? Jan 03 21:55:00 al3xclarke: http://elinux.org/BeagleBoard_Trainer Jan 03 21:58:37 thanks for the advice. i'm guessing i cannot wire the sensor directly into the beagleboard and must go via the trainer board then? Jan 03 22:00:31 *coming from someone who hasn't worked with the beagleboard c4* do you have a male header on the expansion port? couldn't you just put some jumpers between it and a breadboard? Jan 03 22:07:37 i'd need to install the header (as the board comes without it) Jan 03 22:07:54 ok Jan 03 22:11:03 just checked the manual and the pins on the expansion header (when installed) should allow me to connect the sensor. i was under the impression that i required something to work inbetween the sensor and board. Jan 03 22:13:07 nah, most devices support i2c Jan 03 22:18:43 cool, thanks for the help. Jan 03 22:23:18 np Jan 04 01:21:35 anyone running one of the bsds on their bbb? **** ENDING LOGGING AT Sat Jan 04 02:59:58 2014