From: clairm <cla...@ho...> - 2007-06-20 19:38:18
|
I'm trying to follow the directions on http://docwiki.gumstix.org/I2C_on_the_Gumstix in order to get i2c-io to work between my gumstix and robostix. It has a troubling section: Configuring the kernel for master/slave Be sure CONFIG_I2C_PXA_SLAVE is set correctly in your buildroot's linux.config (set to 'n' if your Gumstix will be the master). If this changes, you will need to rebuild the kernel. I'm running the factory 1161 kernel. So, by default is this set correctly? Do I need to rebuild the kernel in order to get I2C going? I went ahead and tried to install the precompiled modules, but it doesn't seem to be working: # modprobe i2c-dev FATAL: Module i2c_dev not found. # modprobe i2c-pxa FATAL: Module i2c_pxa not found. Any ideas? Clair -- View this message in context: http://www.nabble.com/Module-i2c_dev-not-found-tf3954660.html#a11220734 Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2007-06-20 20:24:02
|
HI Clair, > I'm running the factory 1161 kernel. So, by default is this set correctly? > Do I need to rebuild the kernel in order to get I2C going? The factory image doesn't include i2c support. You can use the precompiled versions on the "I2C on the gumstix" page. For 1161 you'll want the i2c-modules-2.6.18-1143.tar.gz tarball (for 1143 to 1184). and then follow the directions about installing the precompiled modules. > I went ahead and tried to install the precompiled modules, but it doesn't > seem to be working: > > # modprobe i2c-dev > FATAL: Module i2c_dev not found. > # modprobe i2c-pxa > FATAL: Module i2c_pxa not found. Were you in / when you expanded the tarball? You can manually check if the precompiled stuff was installed properly by looking in: /lib/modules/2.6.18gum/kernel/drivers/i2c and you should see the i2c-dev.ko file. You can also check the /lib/modules/2.6.18gum/modules.dep file and you should see entries for i2c-dev.ko and i2c-pxa.ko at the very end. If either of the above two steps don't check out, then it means you didn't follow the steps properly to install the precompiled modules. For the 1161 revision, then the steps will be (on the gumstix) cd / tar xzf /tmp/i2c-modules-2.6.18-1143.tar.gz cd lib/modules/2.6.18gum cp modules.symbols modules.symbols.org cp modules.dep modules.dep.org cat mod.sym >> modules.symbols cat mod.dep >> modules.dep assuming that you copied the i2c-modules-2.6.18-1143.tar.gz tarball into /tmp -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: clairm <cla...@ho...> - 2007-06-20 21:48:12
|
I had expanded the tarball from /mnt/mmc/i2c. I redid it from / and I now see /lib/modules/2.6.18gum/kernel/drivers/i2c/i2c-dev.ko. I added: # I2C i2c-dev i2c-pxa to /etc/modules, and rebooted. Now I can't get it to come up and attach to the Bluetooth console any more. I guess it's time to add the pull-up resistor between GUMSTIX pins 3 & 4. Was I just getting lucky before? Dave Hylands wrote: > > HI Clair, > >> I'm running the factory 1161 kernel. So, by default is this set >> correctly? >> Do I need to rebuild the kernel in order to get I2C going? > > The factory image doesn't include i2c support. > > You can use the precompiled versions on the "I2C on the gumstix" page. > For 1161 you'll want the i2c-modules-2.6.18-1143.tar.gz tarball (for > 1143 to 1184). > > and then follow the directions about installing the precompiled modules. > >> I went ahead and tried to install the precompiled modules, but it doesn't >> seem to be working: >> >> # modprobe i2c-dev >> FATAL: Module i2c_dev not found. >> # modprobe i2c-pxa >> FATAL: Module i2c_pxa not found. > > Were you in / when you expanded the tarball? > > You can manually check if the precompiled stuff was installed properly > by looking in: > > /lib/modules/2.6.18gum/kernel/drivers/i2c > > and you should see the i2c-dev.ko file. > > You can also check the /lib/modules/2.6.18gum/modules.dep file and you > should see entries for i2c-dev.ko and i2c-pxa.ko at the very end. > > If either of the above two steps don't check out, then it means you > didn't follow the steps properly to install the precompiled modules. > > For the 1161 revision, then the steps will be (on the gumstix) > > cd / > tar xzf /tmp/i2c-modules-2.6.18-1143.tar.gz > cd lib/modules/2.6.18gum > cp modules.symbols modules.symbols.org > cp modules.dep modules.dep.org > cat mod.sym >> modules.symbols > cat mod.dep >> modules.dep > > assuming that you copied the i2c-modules-2.6.18-1143.tar.gz tarball into > /tmp > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Module-i2c_dev-not-found-tf3954660.html#a11222885 Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2007-06-20 21:57:33
|
Hi Clair, > I had expanded the tarball from /mnt/mmc/i2c. I redid it from / and I now see > /lib/modules/2.6.18gum/kernel/drivers/i2c/i2c-dev.ko. I added: > > # I2C > i2c-dev > i2c-pxa > > to /etc/modules, and rebooted. Now I can't get it to come up and attach to > the Bluetooth console any more. I guess it's time to add the pull-up > resistor between GUMSTIX pins 3 & 4. Was I just getting lucky before? I've you're using a robostix, and have nothing plugged into the GUMSTIX connector, then yes, it's just luck. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: clairm <cla...@ho...> - 2007-06-20 22:25:24
|
OK, I got i2c-io loaded and can turn the LEDs on and off. How do I set or read one of the ADC ports? I've tried every combination of: i2c-io 0x0b getdir ad0 i2c-io 0x0b getdir adc.0 i2c-io 0x0b getdir ADC.0 etc. ...but I always get ERROR: Unrecognized port: 'xxx.x' Dave Hylands wrote: > > Hi Clair, > >> I had expanded the tarball from /mnt/mmc/i2c. I redid it from / and I now >> see >> /lib/modules/2.6.18gum/kernel/drivers/i2c/i2c-dev.ko. I added: >> >> # I2C >> i2c-dev >> i2c-pxa >> >> to /etc/modules, and rebooted. Now I can't get it to come up and attach >> to >> the Bluetooth console any more. I guess it's time to add the pull-up >> resistor between GUMSTIX pins 3 & 4. Was I just getting lucky before? > > I've you're using a robostix, and have nothing plugged into the > GUMSTIX connector, then yes, it's just luck. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Module-i2c_dev-not-found-tf3954660.html#a11223410 Sent from the Gumstix mailing list archive at Nabble.com. |
From: clairm <cla...@ho...> - 2007-06-20 22:35:44
|
OH, i guess you can't set the direction. I have no trouble getting the values. clairm wrote: > > OK, I got i2c-io loaded and can turn the LEDs on and off. How do I set or > read one of the ADC ports? I've tried every combination of: > > i2c-io 0x0b getdir ad0 > i2c-io 0x0b getdir adc.0 > i2c-io 0x0b getdir ADC.0 > etc. > > ...but I always get ERROR: Unrecognized port: 'xxx.x' > > > Dave Hylands wrote: >> >> Hi Clair, >> >>> I had expanded the tarball from /mnt/mmc/i2c. I redid it from / and I >>> now see >>> /lib/modules/2.6.18gum/kernel/drivers/i2c/i2c-dev.ko. I added: >>> >>> # I2C >>> i2c-dev >>> i2c-pxa >>> >>> to /etc/modules, and rebooted. Now I can't get it to come up and attach >>> to >>> the Bluetooth console any more. I guess it's time to add the pull-up >>> resistor between GUMSTIX pins 3 & 4. Was I just getting lucky before? >> >> I've you're using a robostix, and have nothing plugged into the >> GUMSTIX connector, then yes, it's just luck. >> >> -- >> Dave Hylands >> Vancouver, BC, Canada >> http://www.DaveHylands.com/ >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- View this message in context: http://www.nabble.com/Module-i2c_dev-not-found-tf3954660.html#a11223535 Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2007-06-21 06:38:40
|
Hi Clari, On 6/20/07, clairm <cla...@ho...> wrote: > > OH, i guess you can't set the direction. I have no trouble getting the > values. I see you figured it out. You can set the direction for GPIO pins, but ADC are read-only. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |