From: Jonathan S. <agg...@gm...> - 2006-04-13 03:37:57
|
I have the i2c working on the robostix. now how do i find out the address of my device? also how can i make sure that the robostix driver is loaded automatically? Jonathan |
From: Dave H. <dhy...@gm...> - 2006-04-13 03:47:10
|
Hi Jonathan, On 4/12/06, Jonathan Stewart <agg...@gm...> wrote: > I have the i2c working on the robostix. now how do i find out the > address of my device? i2c-io prints it's i2c address to UART0, so if you connect up the jumpers as you would for programming via uisp and run serial-log& robostix reset pulse then you should see the output of i2c-io printed in green text. > also how can i make sure that the robostix driver is loaded automatically= ? There is a script called S10robostix which can be found here: <http://websvn.gumstix.com/listing.php?repname=3DBuildroot&path=3D%2Fbranch= es%2Fprojects%2Frobostix%2Fgumstix%2F&rev=3D0&sc=3D0> You can copy that into /etc/init.d on the gumstix. You can also follow the information on this page: http://gumstix.org/tikiwiki/tiki-index.php?page=3DRobostix-uboot -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Dave H. <dhy...@gm...> - 2006-04-13 05:02:52
|
Hi Jonathan, On 4/12/06, Dave Hylands <dhy...@gm...> wrote: > Hi Jonathan, > > On 4/12/06, Jonathan Stewart <agg...@gm...> wrote: > > I have the i2c working on the robostix. now how do i find out the > > address of my device? > > i2c-io prints it's i2c address to UART0, so if you connect up the > jumpers as you would for programming via uisp and run > > serial-log& > robostix reset pulse > > then you should see the output of i2c-io printed in green text. Well that would work fine if the logging is enabled - Doh. You can do this: uisp --segment=3Deeprom --download of=3Deeprom.srec tail -5 eeprom.srec On my robostix, I get this: S1130FD0FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF1D S1130FE0FFFFFFFFFFFFFFFFFFFFFFFF5465737469 S1130FF0000000000000000000000000FFFFFF14DC S5030100FB S9030000FC We're interested in the last line that starts with S1. I've added spaces to the line to break out the various fields. The last byte (0xDC in this case) is a checksum. The 0x14 is the structure size. If it's uninitialized it will be 0xFF. The byte before that is the i2c address. If it's set to 0xFF, then it uses the default i2c address of 0x0B. S1 13 0FF0 000000000000000000000000FFFFFF14 DC The i2c address should be in the range 0x02 thru 0x7F. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Dave H. <dhy...@gm...> - 2006-04-13 05:56:06
|
Hi Jonathan, You asked me off list how to reset the i2c address. I added a file to SVN called eeprom-init.hex <http://websvn.gumstix.com/listing.php?repname=3DBuildroot&path=3D%2Fbranch= es%2Fprojects%2Frobostix%2Fi2c-BootLoader%2F&rev=3D0&sc=3D0> You can use the following command: uisp --segment=3Deeprom --upload if=3Deeprom-init.hex to reset the portion of the EEPROM used by the bootloader back to the default erased state. The i2c address will then be 0x0b -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Erik D. R. <eri...@ce...> - 2006-06-22 15:27:49
|
Dave: =20 I noticed you are demonstrating serial-log via running with the & = argument. Reading the code for that program, I dont see the & argument = being handled. You mentioned some time before this message (Below) that = the & will cause the program to become TSR (NEP, or run in background... = terminology depends on what platform you are used to working on...). Is = & a Linux handled command, or did I miss something in your code? =20 Also, with the Signal() command, is there a good resource to identify = Linux generated signals? ________________________________ From: gum...@li... on behalf of Dave = Hylands Sent: Wed 4/12/2006 11:47 PM To: gum...@li... Subject: Re: [Gumstix-users] i2c addresses when using robostix Hi Jonathan, On 4/12/06, Jonathan Stewart <agg...@gm...> wrote: > I have the i2c working on the robostix. now how do i find out the > address of my device? i2c-io prints it's i2c address to UART0, so if you connect up the jumpers as you would for programming via uisp and run serial-log& robostix reset pulse then you should see the output of i2c-io printed in green text. > also how can i make sure that the robostix driver is loaded = automatically? There is a script called S10robostix which can be found here: <http://websvn.gumstix.com/listing.php?repname=3DBuildroot&path=3D%2Fbran= ches%2Fprojects%2Frobostix%2Fgumstix%2F&rev=3D0&sc=3D0> You can copy that into /etc/init.d on the gumstix. You can also follow the information on this page: http://gumstix.org/tikiwiki/tiki-index.php?page=3DRobostix-uboot -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting = language that extends applications into web and mobile media. Attend the live = webcast and join the prime developer group breaking into this new coding = territory! http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=121642 _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Dave H. <dhy...@gm...> - 2006-06-22 16:51:28
|
HI Erik, > I noticed you are demonstrating serial-log via running with the & argument. Reading the code for that program, I dont see the & argument being handled. You mentioned some time before this message (Below) that the & will cause the program to become TSR (NEP, or run in background... terminology depends on what platform you are used to working on...). Is & a Linux handled command, or did I miss something in your code? The & is handled by the shell. So the program never sees it on the command line. Similarly, redirection, piping, and wildcard expansion are also handled by the shell. Here's some background information: http://www.tech-geeks.org/contrib/mdrone/LinuxWorkshop/newbie-linux-manual/sections/job.html http://linuxcommand.org/lts0080.php Actually, the contents link from the tech-geeks site looks like a pretty good introduction to linux: http://www.tech-geeks.org/contrib/mdrone/LinuxWorkshop/newbie-linux-manual/contents.html Just keep in mind that the busybox version of the commands used on the gumstix are typically stripped down versions of the ones you normally find on linux distributions. You can get some documentation about the busybox versions here: http://www.busybox.net/downloads/BusyBox.html Also keep in mind that not all buybox commands are enabled. Typiing 'busybox --help' on the gumstix will show you the functions that busybox is currently configured to support, and typiing help will show you the shells builtin commands. > Also, with the Signal() command, is there a good resource to identify Linux generated signals? Here's a man page for signals, also obtainable using the command: man 7 signal if the appropriate stuff has been installed on your host machine. http://www.die.net/doc/linux/man/man7/signal.7.html -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |