From: Colin S. <co...@ab...> - 2006-02-15 10:37:40
|
> To: gum...@li... > Date: Tue, 14 Feb 2006 14:50:45 -0500 (EST) > From: Chris Bare <ch...@ba...> > Subject: [Gumstix-users] robostix ISP adapter > Reply-To: gum...@li... > > Hi, I'm an experienced programmer, but new to the microcontroller world. I'm > looking for a capable controller board to use for robotics experiments, and > the robostix seems like a good place to start. > I use linux for my desktop, so I want to be able to code in C and download > to the robostix from a linux PC (not from a gumstix). > I am trying to find a cable/adapter to purchase (not build). > The gumstix site points to: > http://www.digikey.com/scripts/DkSearch/dksus.dll?PName?Name=ATAVRISP-ND > which digikey says is an obsolete item. > > Can anyone recommend a pre-built ISP that works with avrdude and the robostix > board and a vendor that currently sells it? > It can be serial, parallel or usb. My criterial are: known to work, pre-built, > cost. > Try this one, http://www.active-robots.com/products/controllr/avr-downloader.shtml. I've got this cable to work fine with UISP under Linux and it was only GBP 8 (about USD 14). |
From: Kita K. <kah...@ya...> - 2006-02-15 18:10:22
|
Hi Dave, Thank you for your advice. I used "./i2c-load --reset info 0x0b" and I could communicate with the robostix. And then, I tried to use i2c-io, so installed i2c-io.hex to robostix using i2c-load and installed precompiled versions of i2c-io(i2c-io-2.6.11.tar.gz) to gumstix /bin. But when I used the "i2c-io" on gumstix, I got the message "segmentation fault" from gumstix. So I need more settings of gumstix? Or is it better to compile i2c-io from source and use? Thanks, Kahori Kita > 7. Finaly, I did "# ./i2c-load --reset 0x0b info" as > described on "Robostix-i2c-load". > But, I got following error message. > "ERROR:Unrecognized command '0x0b'" Try using ./i2c-load --reset info 0x0b I used to have the arguments in the order "command i2c-addr [command-options]" but I changed them to "i2c-addr command [command-options]" The wiki reflects the latest version in SVN. I *think* I updated the precompiled version of i2c-load for 2.6.11, but it's entirely possible I screwed up, or you may just have an older version. I decided that it made more sense to have the i2c-address first and wanted i2c-io and i2c-load to both use the same order, which is why I switched it (I also went back and forth a few times before I released it the first time too) > I'm confused. Sorry for the confusion. -------------------------------------- GANBARE! NIPPON! Yahoo! JAPAN JOC OFFICIAL INTERNET PORTAL SITE PARTNER http://pr.mail.yahoo.co.jp/ganbare-nippon/ |
From: Dave H. <dhy...@gm...> - 2006-02-15 18:27:11
|
HI Kahori, On 2/15/06, Kita Kahori <kah...@ya...> wrote: > Hi Dave, > > Thank you for your advice. > I used "./i2c-load --reset info 0x0b" and I could > communicate with the robostix. > > And then, I tried to use i2c-io, so installed i2c-io.hex > to robostix using i2c-load and installed precompiled > versions of i2c-io(i2c-io-2.6.11.tar.gz) to gumstix /bin. > But when I used the "i2c-io" on gumstix, I got the message > "segmentation fault" from gumstix. > So I need more settings of gumstix? > Or is it better to compile i2c-io from source and use? Compiling from source should work fine. I still have a 2.6.11 toolchain that I used (or thought I used) to build the 2.6.11 version of i2c-io, but it's possible I screwed it up. I don't currently have a gumstix with 2.6.11 installed on it to test with. When I get home tonight, I'll reload 2.6.11 and test out all of the precompiled binaries to make sure they still work, and update as appropriate. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Dave H. <dhy...@gm...> - 2006-02-16 06:45:11
|
Hi Kita Kahori (apologies from my previous emails - I think I may have just been using your last name - Doh), > > And then, I tried to use i2c-io, so installed i2c-io.hex > > to robostix using i2c-load and installed precompiled > > versions of i2c-io(i2c-io-2.6.11.tar.gz) to gumstix /bin. > > But when I used the "i2c-io" on gumstix, I got the message > > "segmentation fault" from gumstix. > > So I need more settings of gumstix? > > Or is it better to compile i2c-io from source and use? > When I get home tonight, I'll reload 2.6.11 and test out all of the > precompiled binaries to make sure they still work, and update as > appropriate. OK - the 2.6.11 tarballs for i2c-load and i2c-io were screwed up. I figured out what I did wrong, rebuilt, and tested both under 2.6.11. Everything seems to working again. Let me know if you have any more trouble= s. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: surendranath g <sur...@ya...> - 2006-02-16 07:26:17
|
Hi, I have a software example.tar.gz this works on redhat after running a make. I tried to do the same on gumstix by putting in the make folder and recompiled buildroot, but no luck, what are the steps ? I also checked the dl folder too. thanks surendra |
From: Dave H. <dhy...@gm...> - 2006-02-16 07:31:06
|
> I have a software example.tar.gz this works on redhat > after running a make. > I tried to do the same on gumstix by putting in the > make folder and recompiled buildroot, but no luck, > what are the steps ? I also checked the dl folder too. Can you show us the example.tar.gz? Makefiles can do all kinds of weird and wonderful things, and without having the files, it's really hard to help you. Ideally, I'd like to get the tarball, so I can test it and then tell you exactly what to do. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: surendranath g <sur...@ya...> - 2006-02-16 07:41:21
Attachments:
633_linux.tar.gz
|
Thanks a lot Dave for your time, I am attaching the tarball. Sincerely Surendra --- Dave Hylands <dhy...@gm...> wrote: > > I have a software example.tar.gz this works on > redhat > > after running a make. > > I tried to do the same on gumstix by putting in > the > > make folder and recompiled buildroot, but no luck, > > what are the steps ? I also checked the dl folder > too. > > Can you show us the example.tar.gz? > > Makefiles can do all kinds of weird and wonderful > things, and without > having the files, it's really hard to help you. > > Ideally, I'd like to get the tarball, so I can test > it and then tell > you exactly what to do. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > 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?cmd=lnk&kid3432&bid#0486&dat1642 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2006-02-16 15:55:03
|
Hi Surendra, > > > I have a software example.tar.gz this works on > > redhat > > > after running a make. > > > I tried to do the same on gumstix by putting in > > the > > > make folder and recompiled buildroot, but no luck, > > > what are the steps ? I also checked the dl folder > > too. I did the following. 1 - Build the g++ cross compiler: a - Edit gumstix-buildroot/Makefile and set "INSTALL_LIBSTDCPP:=3Dtrue" b - rm -rf gumstix-builroot/toolchain_build_arm_nofpu c - cd gumstix-buildroot d - make 2 - Make sure that gumstix-buildroot/build_arm_nofpu/staging_dir/bin is in your PATH (i.e. if I type arm-linux-g++ on the command line, I should get this error: arm-linux-g++: no input files 3 - Install the root_fs_arm_nofpu onto your gumstix (this makes the libstdc++.so.6 available for C++ programs) 4 - Unpack your tarball (anywhere you like, it doesn't need to be in the buildroot directory). 5 - Edit the Makefile and change: CC =3D g++ to be CC =3D arm-linux-g++ 6 - Type make This will compile and build test633, which you can copy to your gumstix and try to run. I didn't try this last step since I don't have the hardware connected to know that it works properly or not. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: surendranath g <sur...@ya...> - 2006-02-19 00:46:02
|
Hi Dave, It did not work, I did not see anything on the display. Is there another compiler that I should use? thanks surendra --- Dave Hylands <dhy...@gm...> wrote: > Hi Surendra, > > > > I have a software example.tar.gz this works on > > > redhat > > > > after running a make. > > > > I tried to do the same on gumstix by putting > in > > > the > > > > make folder and recompiled buildroot, but no > luck, > > > > what are the steps ? I also checked the dl > folder > > > too. > > I did the following. > > 1 - Build the g++ cross compiler: > a - Edit gumstix-buildroot/Makefile and set > "INSTALL_LIBSTDCPP:=true" > b - rm -rf > gumstix-builroot/toolchain_build_arm_nofpu > c - cd gumstix-buildroot > d - make > > 2 - Make sure that > gumstix-buildroot/build_arm_nofpu/staging_dir/bin > is in your PATH (i.e. if I type arm-linux-g++ on the > command line, I > should get this error: > arm-linux-g++: no input files > > 3 - Install the root_fs_arm_nofpu onto your gumstix > (this makes the > libstdc++.so.6 available for C++ programs) > > 4 - Unpack your tarball (anywhere you like, it > doesn't need to be in > the buildroot directory). > > 5 - Edit the Makefile and change: > CC = g++ > to be > CC = arm-linux-g++ > > 6 - Type make > > This will compile and build test633, which you can > copy to your > gumstix and try to run. I didn't try this last step > since I don't have > the hardware connected to know that it works > properly or not. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > 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?cmd=lnk&kid3432&bid#0486&dat1642 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2006-02-19 03:27:37
|
Hi Surendra, On 2/18/06, surendranath g <sur...@ya...> wrote: > Hi Dave, > > It did not work, I did not see anything on the > display. Is there another compiler that I should use? You didn't see anything on what display? -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: surendranath g <sur...@ya...> - 2006-02-19 18:51:42
|
Hi Dave, Before a couple of days you helped me to compile an opensouce tar ball. ( List of insturctions you sent are given below) After compiling and loading on gumstix, test633 is supposed to talk to an LCD through the serial port on gumstix, on redhat it sends a signal to the display but not on gumstix. I dont know if its an IO issue or a compiler issue or something else. Thanks for your time surendra -------------------------------------------- 1 - Build the g++ cross compiler: a - Edit gumstix-buildroot/Makefile and set "INSTALL_LIBSTDCPP:=true" b - rm -rf gumstix-builroot/toolchain_build_arm_nofpu c - cd gumstix-buildroot d - make 2 - Make sure that gumstix-buildroot/build_arm_nofpu/staging_dir/bin is in your PATH (i.e. if I type arm-linux-g++ on the command line, I should get this error: arm-linux-g++: no input files 3 - Install the root_fs_arm_nofpu onto your gumstix (this makes the libstdc++.so.6 available for C++ programs) 4 - Unpack your tarball (anywhere you like, it doesn't need to be in the buildroot directory). 5 - Edit the Makefile and change: CC = g++ to be CC = arm-linux-g++ 6 - Type make This will compile and build test633, which you can copy to your gumstix and try to run. I didn't try this last step since I don't have the hardware connected to know that it works properly or not. --- Dave Hylands <dhy...@gm...> wrote: > Hi Surendra, > > On 2/18/06, surendranath g <sur...@ya...> > wrote: > > Hi Dave, > > > > It did not work, I did not see anything on the > > display. Is there another compiler that I should > use? > > You didn't see anything on what display? > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > 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?cmd=lnk&kid3432&bid#0486&dat1642 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2006-02-20 05:05:52
|
Hi Surenda, On 2/19/06, surendranath g <sur...@ya...> wrote: > After compiling and loading on gumstix, test633 is > supposed to talk to an LCD through the serial port on > gumstix, on redhat it sends a signal to the display > but not on gumstix. I dont know if its an IO issue or > a compiler issue or something else. I didn't realize that the code was designed to talk to an LCD. I doubt very highly that it's got anything to do with the compiler. Did you configure the appropriate lines to be serial? For /dev/ttyS2 you need to do: modprobe proc_gpio echo "AF2 in" > /proc/gpio/GPIO46 echo "AF1 out" > /dev/gpio/GPIO47 I ran the tes633 program I compiled and I saw this on my terminal program connected to /dev/ttyS2: >This is line 1< >This is line 2< with some control characters before and after each line. How did you connect the LCD to the gumstix (i.e. what exact cables did you = use? -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: surendranath g <sur...@ya...> - 2006-02-20 06:55:52
|
Hi Dave, I connected the LCD to serial port /dev/ttyS0 using a serial null modem cable and a gender changer. ( Normally this is the line i hyperm to, when I load images). Then I did an SSH to the gumstix and ran the following program. ./test633 /dev/ttyS0 19200 does not display anything on the LCD. But may be I should a different serial port thanks a lot. Surendra --- Dave Hylands <dhy...@gm...> wrote: > Hi Surenda, > > On 2/19/06, surendranath g <sur...@ya...> > wrote: > > > After compiling and loading on gumstix, test633 is > > supposed to talk to an LCD through the serial port > on > > gumstix, on redhat it sends a signal to the > display > > but not on gumstix. I dont know if its an IO issue > or > > a compiler issue or something else. > > I didn't realize that the code was designed to talk > to an LCD. > > I doubt very highly that it's got anything to do > with the compiler. > > Did you configure the appropriate lines to be > serial? > > For /dev/ttyS2 you need to do: > > modprobe proc_gpio > echo "AF2 in" > /proc/gpio/GPIO46 > echo "AF1 out" > /dev/gpio/GPIO47 > > I ran the tes633 program I compiled and I saw this > on my terminal > program connected to /dev/ttyS2: > > >This is line 1< > >This is line 2< > > with some control characters before and after each > line. > > How did you connect the LCD to the gumstix (i.e. > what exact cables did you use? > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > 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?cmd=lnk&kid3432&bid#0486&dat1642 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2006-02-20 07:07:48
|
Hi Surendra, > I connected the LCD to serial port /dev/ttyS0 using a > serial null modem cable and a gender changer. ( > Normally this is the line i hyperm to, when I load > images). > Then I did an SSH to the gumstix and ran the following > program. > ./test633 /dev/ttyS0 19200 > does not display anything on the LCD. > But may be I should a different serial port /dev/ttyS0 is the system console, so you may be confusing the LCD. When you did this under linux, you probably connected the LCD directly into the PC right? If this is the case, then the LCD was acting like a DCE device and the PC is a DTE device. You can connect DTE devices directly to DCE devices, but connecting DCE to DCE or DTE to DTE requires the use of a null modem. The gumstix looks like a DTE device, and the null-modem cable turns it into a DCE device, so you can plug it directly into a PC to make it work. To connect your LCD (DCE) to the gumstix (DTE), you'll either need a cable without the null modem, or you'll need to add a null-modem cable (effectively cancelling the null modem built into the cable). Just using a gender changer won't be enough. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: surendranath g <sur...@ya...> - 2006-02-21 05:52:21
|
Hi Dave, Thank you very much. I appreciate it. You were right again. sincerely surendra --- Dave Hylands <dhy...@gm...> wrote: > Hi Surendra, > > > I connected the LCD to serial port /dev/ttyS0 > using a > > serial null modem cable and a gender changer. ( > > Normally this is the line i hyperm to, when I load > > images). > > Then I did an SSH to the gumstix and ran the > following > > program. > > ./test633 /dev/ttyS0 19200 > > does not display anything on the LCD. > > But may be I should a different serial port > > /dev/ttyS0 is the system console, so you may be > confusing the LCD. > > When you did this under linux, you probably > connected the LCD directly > into the PC right? > If this is the case, then the LCD was acting like a > DCE device and the > PC is a DTE device. You can connect DTE devices > directly to DCE > devices, but connecting DCE to DCE or DTE to DTE > requires the use of a > null modem. > > The gumstix looks like a DTE device, and the > null-modem cable turns it > into a DCE device, so you can plug it directly into > a PC to make it > work. > > To connect your LCD (DCE) to the gumstix (DTE), > you'll either need a > cable without the null modem, or you'll need to add > a null-modem cable > (effectively cancelling the null modem built into > the cable). Just > using a gender changer won't be enough. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > 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?cmd=lnk&kid3432&bid#0486&dat1642 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2006-02-15 14:37:18
|
Hi Colin > > Can anyone recommend a pre-built ISP that works with avrdude and the ro= bostix > > board and a vendor that currently sells it? > > It can be serial, parallel or usb. My criterial are: known to work, pre= -built, > > cost. > > > Try this one, > http://www.active-robots.com/products/controllr/avr-downloader.shtml. > > I've got this cable to work fine with UISP under Linux and it was only > GBP 8 (about USD 14). avrdude should work with any of the parallel style programmers. In the worst case, it would need a new config entry. I figured I'd mention that since the original poster specifically wanted avrdude). -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |