From: Peter D. <pda...@pc...> - 2006-02-21 22:03:10
|
hello, I am setting up the i2c between the gumstix and robo. Do I need to mknod the /dev/robostix manually or is modprobe i2c-dev & i2c-pxa supposed to handle that device file creation or something? I notice that running those modprobes doesn't produce any output to the console, but do show in dmesg. I seem to recall seeing output earlier that reflects the wiki i2c quickstart (which I followed). Since I build the fs image (but downloaded the modules) do I need to tweak something in the buildroot to make i2c work? Thanks, Peter -- Peter Darling pda...@pc... |
From: Dave H. <dhy...@gm...> - 2006-02-21 22:34:17
|
Hi Peter, > I am setting up the i2c between the gumstix and robo. Do I need to > mknod the /dev/robostix manually or is modprobe i2c-dev & i2c-pxa > supposed to handle that device file creation or something? I notice > that running those modprobes doesn't produce any output to the > console, but do show in dmesg. I seem to recall seeing output earlier > that reflects the wiki i2c quickstart (which I followed). Since I > build the fs image (but downloaded the modules) do I need to tweak > something in the buildroot to make i2c work? Are you also insmod'ing robostix_drv.ko? I wrote the remainder of this email and re-read your email, and realized that you mentioned loading the i2c modules, but not the robostix_drv module. It depends on which software you're using. On 2.6.11 and earlier, the /dev/robostix needs to be created manually (although I think in the more recent 2.6.11's this was being done in the buildroot automatically). Under 2.6.15, in revision 806, I updated robostix_drv.c so that it now does whats required to register with udev automatically. When you insmod robostix_drv.ko, if you see something like this printed: Robostix Driver: 0.01 Compiled: Jul 27 2005 at 18:49:14 Hello World then you have the old version. If you see something like this printed: Robostix Driver: SVN: 806 Compiled: Feb 11 2006 at 00:00:00 (notice the SVN and lack of Hello World), then you should have the new vers= ion. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Peter D. <pda...@pc...> - 2006-02-21 23:02:21
|
Dave, Indeed I had not insmod robostix_drv.ko, figured that was for uisp only. I see no console output from that command though, however, dmesg indicates I have the new version. It appears I'm still not doing something right: # i2c-load --reset 0x0b info ERROR: I2cTransfer: CRC failed: Rcvd: 0x00, expecting: 0xc5 ERROR: I2cReadBlock failed ERROR: Unable to retrieve boot information from i2c address 0x0b Thanks again for your time, Peter On 2/21/06, Dave Hylands <dhy...@gm...> wrote: > Hi Peter, > > > I am setting up the i2c between the gumstix and robo. Do I need to > > mknod the /dev/robostix manually or is modprobe i2c-dev & i2c-pxa > > supposed to handle that device file creation or something? I notice > > that running those modprobes doesn't produce any output to the > > console, but do show in dmesg. I seem to recall seeing output earlier > > that reflects the wiki i2c quickstart (which I followed). Since I > > build the fs image (but downloaded the modules) do I need to tweak > > something in the buildroot to make i2c work? > > Are you also insmod'ing robostix_drv.ko? I wrote the remainder of this > email and re-read your email, and realized that you mentioned loading > the i2c modules, but not the robostix_drv module. > > It depends on which software you're using. On 2.6.11 and earlier, the > /dev/robostix needs to be created manually (although I think in the > more recent 2.6.11's this was being done in the buildroot > automatically). > > Under 2.6.15, in revision 806, I updated robostix_drv.c so that it now > does whats required to register with udev automatically. > > When you insmod robostix_drv.ko, if you see something like this printed: > > Robostix Driver: 0.01 Compiled: Jul 27 2005 at 18:49:14 > Hello World > > then you have the old version. If you see something like this printed: > > Robostix Driver: SVN: 806 Compiled: Feb 11 2006 at 00:00:00 > > (notice the SVN and lack of Hello World), then you should have the new ve= rsion. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmdlnk&kid=103432&bid#0486&dat=121642 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > -- Peter Darling pda...@pc... |
From: Dave H. <dhy...@gm...> - 2006-02-21 23:17:59
|
Hi Peter, > Indeed I had not insmod robostix_drv.ko, figured that was for uisp > only. Yeah - I'm using an ioctl to reset the robostix in response to the --reset option on i2c-load. > I see no console output from that command though, however, Hmm. You should see output to the console (not necessarily stdout). Same as modprobe for the i2c-dev and i2c-pxa. Modules normally use printk, which gets routed to the console. > dmesg indicates I have the new version. It appears I'm still not > doing something right: > > # i2c-load --reset 0x0b info > ERROR: I2cTransfer: CRC failed: Rcvd: 0x00, expecting: 0xc5 > ERROR: I2cReadBlock failed > ERROR: Unable to retrieve boot information from i2c address 0x0b Hmm. I'll have to play around when I get home. Did you download a recent bootloader to the robostix? If you have the bootloader that you downloaded around can you send it back to me, along with the i2c-load? Also, it would be good to see the output of: i2c-load --debug --reset 0x0b info I think I'm going to have to be more diligent about putting SVN version numbers on things so I can figure out what's what :) -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Peter D. <pda...@pc...> - 2006-02-21 23:41:06
|
Dave, Maybe my bluetooth console doesn't want to show the output, I dunno.=20 Letsee, it was a fairly recent bootloader I put to the 128.. maybe from friday? I'll post the files (and debug output) when I get home in a half-hour or so. -Peter On 2/21/06, Dave Hylands <dhy...@gm...> wrote: > Hi Peter, > > > Indeed I had not insmod robostix_drv.ko, figured that was for uisp > > only. > > Yeah - I'm using an ioctl to reset the robostix in response to the > --reset option on i2c-load. > > > I see no console output from that command though, however, > > Hmm. You should see output to the console (not necessarily stdout). > Same as modprobe for the i2c-dev and i2c-pxa. Modules normally use > printk, which gets routed to the console. > > > dmesg indicates I have the new version. It appears I'm still not > > doing something right: > > > > # i2c-load --reset 0x0b info > > ERROR: I2cTransfer: CRC failed: Rcvd: 0x00, expecting: 0xc5 > > ERROR: I2cReadBlock failed > > ERROR: Unable to retrieve boot information from i2c address 0x0b > > Hmm. I'll have to play around when I get home. Did you download a > recent bootloader to the robostix? If you have the bootloader that you > downloaded around can you send it back to me, along with the i2c-load? > > Also, it would be good to see the output of: > > i2c-load --debug --reset 0x0b info > > I think I'm going to have to be more diligent about putting SVN > version numbers on things so I can figure out what's what :) > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmdlnk&kid=103432&bid#0486&dat=121642 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > -- Peter Darling pda...@pc... |
From: Dave H. <dhy...@gm...> - 2006-02-22 00:00:38
|
Hi Peter, > Maybe my bluetooth console doesn't want to show the output, I dunno. > Letsee, it was a fairly recent bootloader I put to the 128.. maybe > from friday? I'll post the files (and debug output) when I get home > in a half-hour or so. OK - I checked in the most recent set of changes of any significance (I think) about 10 days ago, so that should put you in the "most recent" category. You might as well send the files to me off-list (dhylands-at-gmail-dot-com) so that we don't waste bandwidth :) -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Dave H. <dhy...@gm...> - 2006-02-22 04:08:28
|
Hi everyone, This is to follow up with Peter's problem onlist. Peter was having troubles problems programming the i2c-BootLoader using PonyProg2000. Since Peter has a gumstix, I suggested he try using uisp instead and everything worked fine. If somebody who is familiar with AVR programming using PonyProg2000 could figure out what steps are necessary to download and use the i2c-BootLoader, I'll add the instructions to the Wiki page. I'll probably pick up one of the PG1B programmers the next time I order from SparkFun, but I figured I'd ask in case someboy else knows the right steps to take. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |