**** BEGIN LOGGING AT Thu Oct 23 03:00:00 2014 Oct 23 09:29:46 i have problem using i2cget and i2cset in beaglebone black? anyone have ideas? Oct 23 09:43:15 i have problem using i2cget and i2cset in beaglebone black? anyone have ideas? Oct 23 09:45:41 I think this question strongly discourages any answer, as it's clear that author doesn't care enough to even describe the problem Oct 23 09:52:28 the problem is that when i use i2cget 1 0x50 0x00 it reads correct from 0x00 Oct 23 09:53:00 but when i again read this command from address 0x00 i read from page2 of 24c32 Oct 23 09:55:24 any hints? Oct 23 09:57:11 Not from me, don't know much about i2c, unfortunately Oct 23 09:58:11 oh ok, i have check it very deeply but does not realize the problem :( Oct 23 09:59:27 use bus-pirate or some other I2C capable sniffer and check what actually goes on on the wire Oct 23 10:04:20 'i2cdump 1 0x50 i' dumps the contents correctly from address 0x00 to 0xff. But after i2cget command execution the 'i2cdump 1 0x50 i' shows dump from 0x100. Oct 23 10:06:04 trying to access eeprom? Oct 23 10:06:55 bus addresss is “1”, that does not sound right Oct 23 10:08:55 in any case ou will want to see what the actual I2C commands and data on the wire are Oct 23 10:10:10 if you don’t have a logic analyzer (or even just a bus-pirate) then a decent two-channel DSO will manage, you’ll see at least the first few commands Oct 23 10:10:12 yes i am communicating with 24c32 eeprom, the bus is 1 and device id is 0x50 Oct 23 10:10:39 ah… I was thinking 1 was device address... Oct 23 10:10:51 for some reason... Oct 23 10:11:16 first read is going very good but second read causes the problem of wrong address read Oct 23 10:11:55 and data write i2cset is not writing anything at all Oct 23 10:12:19 well i hadn't luck with it Oct 23 10:12:51 it’s common for chips to increment to register pointer on each read, but " i2cget 1 0x50 0x00” ought to first write 0x0 to the device and only then call read Oct 23 10:13:03 which is the common way to tell which register we want to access. Oct 23 10:14:07 yes you are right, is the bus pirate software can help me to sort out the problem? Oct 23 10:14:35 bus-pirate is a device http://dangerousprototypes.com/docs/Bus_Pirate Oct 23 10:14:54 super handy for testing and debugging stuff like I2C, SPI etc Oct 23 10:15:21 thanks i will try it Oct 23 10:15:28 take care bye Oct 23 10:15:40 this is also very handy: http://dangerousprototypes.com/open-logic-sniffer/ Oct 23 11:08:59 "ping 8.8.8.8" return me "connect: Network is unreachable" and "route add default gw 192.168.7.1" solve it. But how can I cleanly automate it? Oct 23 12:02:42 bricewge: if on debian, man interfaces. you need to specify the gateway there. Oct 23 12:03:21 samael: The gateway is already specified Oct 23 12:07:05 By the way this is fresh install from the last Debian BBB image Oct 23 12:08:35 * KotH just read "french install" and wondered what that is Oct 23 12:10:32 Hi, I've just added a MCP4725 I2C DAC to my Beaglebone. I can see it with i2cdetect -y -r 1 nicely. I can also get some data out of it with i2cget, but how do I use it to get all the registers it has? Oct 23 12:15:47 KotH: If you wonder, yes it has been installed by a french Oct 23 12:15:56 lol Oct 23 12:16:15 Peanut: beside RTFM? Oct 23 12:17:19 KotH: I've been doing a lot of googling, and did read the manpage, of course. Oct 23 12:17:34 I always get the (presumably) first byte out of the thing, for some reason. Oct 23 12:17:54 did you read the mcp4725 datasheet as well? :p Oct 23 12:18:09 Yes, which is why I know that there should be more bytes to get. Oct 23 12:19:19 do you maybe need to initialize it first? Oct 23 12:21:59 When I ask i2cget to get me a 'word', I do get two bytes, but not all 6 bytes. Oct 23 12:31:33 Peanut: have you connected an oscilloscope and checked whether those bytes are actually transfered? Oct 23 12:32:16 Nope, not yet, as I don't even know how to tell i2cget to do this. It might actually be that i2cget simply doesn't support this (yet). Oct 23 12:32:32 * KotH has no idea Oct 23 12:32:36 * KotH never used i2get Oct 23 12:32:51 but i have debugged a lot of software using an oscilloscope Oct 23 12:36:10 <_av500_> +1 Oct 23 14:49:25 Anybody else get this warning when they run apt-get update: http://paste.debian.net/128346/ Oct 23 14:50:15 Looks like there is a mismatch in the packages on rcn's apt server. Oct 23 14:51:42 I have set up my beagle board however my c9 will not load on the UI Oct 23 15:00:32 jbdatko: Yep same here Oct 23 15:02:08 Ok. I'll send an email to the list about it Oct 23 15:38:52 Had anyone here used a pwm driver with their beaglebone yet? Oct 23 15:38:57 s/had/has Oct 23 15:40:10 <_av500_> https://www.google.com/search?q=beaglebone+pwm Oct 23 15:40:26 I know it has PWM, I am thinking more of a driver Oct 23 15:41:02 I want to drive a few more cahnnels than provided by whats built in, Oct 23 15:41:12 Its for an LED light system on an aquarium Oct 23 15:41:35 <_av500_> PRU then Oct 23 15:41:42 PRU? Oct 23 15:41:56 * buzzsaw googles Oct 23 15:48:46 have anyone faced with this error: [ 3.285980] systemd[1]: Failed to mount tmpfs at /sys/fs/cgroup: No such file or directory , when booting to 3.14.20 kernel? Oct 23 15:49:09 buzzsaw: or use I2C or SPI controlled PWM-driver... Oct 23 15:51:22 I picked up a 12 channel http://www.adafruit.com/products/1455 already, jsut have not played around with it yet. Oct 23 15:51:57 buzzsaw: either external pwm controller or pwm software generated, which would be a perfect waste of a nice hardware. Oct 23 15:52:37 I have not worked with SPI or I2C, is one perferable to the other? Oct 23 15:53:09 mostly looking for opensions here Oct 23 15:54:37 both have enough bandwidth. my self, i preffer SPI, due to its pushpull architecture that makes it a bit more noise tolerant Oct 23 15:55:14 I2C uses open drain Oct 23 15:55:22 Guess I get to write a library for the chip I have because it does not have a bbb. Oct 23 15:57:05 most likely, but it comes out to just using prebuild i2c or spi drivers, wraped around the IC's datasheet info Oct 23 15:58:05 Yeah, I started with just my simple light system at home now people are seeing it and asking if I can do the same thing for them but with more channels :-) Oct 23 18:14:11 Well, I ended up writing my own I2C reader application, now I get all the bits out of my DAC just fine. Oct 23 18:48:13 Hi every body Oct 23 23:05:59 Hey, I'm trying to talk to my BBB via serial (pl2303) from Linux, but I'm not getting a lot out of it Oct 23 23:06:13 I get a tiny amount of output when it boots, and no login prompt Oct 23 23:06:53 I'm not sure what I'm doing wrong, because from all my research, it's supposed to Just Work(tm) Oct 23 23:11:45 stty -F /dev/ttyUSBwhatever 9600 raw Oct 23 23:11:50 screen /dev/ttyUSBwhatever 9600 Oct 23 23:11:56 make sure your ground, tx, and rx are connected Oct 23 23:12:01 solidly Oct 23 23:15:46 nyt-: but the getty on the BBB is running at 115200? Oct 23 23:34:01 then 115200 Oct 23 23:34:02 * nyt- forgets Oct 23 23:34:14 might need to change along the way? Dont know what uboot runs at Oct 23 23:34:18 been a while since i had to console one Oct 23 23:46:28 bbb u-boot runs at 115200 **** ENDING LOGGING AT Fri Oct 24 03:00:00 2014