I would like to ask the same question that klemenz is asking. Does cloud9 provide a framework to run i2c slaves with js or python?
On Wednesday, March 7, 2012 at 10:44:32 PM UTC+13, [email protected] wrote: > > Hi Dan, > > Is there an i2c support within cloud9ide environment or more precisely > within bonescript custom .js? > > thanks > > Dne sobota, 31. december 2011 22:07:43 UTC+1 je oseba Dan napisala: >> >> Stan, >> Thanks for the info. I was able to get i2cdetect to work with a 3.3V >> device, and will give the level shifter a shot (when I have one) for >> the 5V device. >> Poking around further, I'm guessing the /sys/class/i2c-adapter >> approach mentioned in my question #4 works only if there is a kernel >> module for the device. For example, there is a kernel-module-bmp085 >> for the BMP085 barometric sensor. >> For everything else, there is the i2cget and i2cset approach that you >> recommended. >> Thanks, >> Dan. >> On Dec 30, 9:55 pm, Stan Seibert <[email protected]> wrote: >> > On Dec 30, 4:50 pm, Dan <[email protected]> wrote: >> > >> > > 1. Should the pullup resistors always be connected to 3.3V (as >> opposed >> > > to some other voltage) on the Beaglebone? I used 5K resistors - is >> > > that close enough? (the SRM says 5.5K). >> > >> > 5k resistors should be fine (I used 4.7k with my device), and since >> > the I/O voltage on the board is 3.3V, you should only connect the pull- >> > ups to that. (Pin 3 or 4 on P9) >> > >> > > 2. Are pins 19 and 20 connected to i2c2 or i2c3? The SRM manual says >> > > i2c2, but based on the results of i2cdetect and other posts I think >> > > it's i2c3. Is there an i2c2 on the Beaglebone? >> > >> > The numbering in the OS seems to be different than the numbering in >> > the SRM. Pins 19 and 20 are on i2c2 in the hardware numbering scheme, >> > but in Linux, the device name is /dev/i2c-3. >> > >> > > 3. Should i2cdetect automatically find thei2cdevice at the correct >> > > address if everything is hooked up correctly? >> > >> > That depends on your device and whether it will respond to the read >> > probes that i2cdetect uses, but in general, yes. >> > >> > > 4. Do I always need to enter a command similar to the one in Koen's >> > > article: "echo bmp085 0x77 > /sys/class/i2c-adapter/i2c-3/ >> > > new_device"? Is the "bmp085" part just a label that I choose, or >> does >> > > it need to precisely match some setting in the device? >> > >> > I just interact with my device using the i2cget and i2cset command >> > line tools, following the data sheet for my device to know what data >> > addresses on the device to set and get. >> > >> > > 5.Is a 5V device like theBlinkMsupported by the BeagleboneI2C? If >> > > so, is the process for configuring it any different from the process >> > > described in Koen's blog post? (This is the device I tried to get >> > > working, and I'm guessing it's not supported). >> > >> > I've never tried using a 3.3V master and a 5VI2Cdevice, but I have >> > used this level shifter for the other direction with an Arduino (5V >> > master and 3.3V device): >> > >> > http://www.sparkfun.com/products/8745 >> > >> > (The description and comments were kind of confusing for this board. >> > I used the TX on channel 1 and 2 for theI2CSDA and SCL.) > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/4ed9a05f-3c26-4a9f-8894-a1690b735de1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
