From: areichow <are...@gm...> - 2009-09-25 18:51:42
|
Ahoy, all! I have a Connex 200xm (and netcf) that has been on the shelf, just waiting for me to have some time. What boards do you sell that are still compatible with the Connex Gumstix modules? From what I can tell, my options are: - tweener - robostix - robostix-TH - console-st Is that correct? I'm hoping to find some way to get easy access to pins for GPIO; failing that, a serial connection for interfacing with a device that can take care of the GPIO. Thanks in advance! Regards, Aaron -- View this message in context: http://www.nabble.com/Expansion-boards-for-the-Connex-200xm--tp25617284p25617284.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2009-09-25 19:22:47
|
Hi Aaron, On Fri, Sep 25, 2009 at 11:51 AM, areichow <are...@gm...> wrote: > > Ahoy, all! > > I have a Connex 200xm (and netcf) that has been on the shelf, just waiting > for me to have some time. > > What boards do you sell that are still compatible with the Connex Gumstix > modules? From what I can tell, my options are: > > - tweener > - robostix > - robostix-TH > - console-st > > Is that correct? There's also the gpsstix, audiostix2, and roboaudio-TH, and you could probably use the breakout-vx. Some of the pin mappings will be slightly different (because the connex has HWUART and the verdex doesn't). > I'm hoping to find some way to get easy access to pins for GPIO; failing > that, a serial connection for interfacing with a device that can take care > of the GPIO. Pretty much any of the daugtercards will give you access to some GPIOs. What's important is making sure that you put appropriate voltage converters/drivers on the GPIOs. For most of the boards, the GPIOs are 3.3v, and can only drive a few mA. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: areichow <are...@gm...> - 2009-09-25 21:08:00
|
Dave, Dave Hylands wrote: > > There's also the gpsstix, audiostix2, and roboaudio-TH, and you could > probably use the breakout-vx. Some of the pin mappings will be > slightly different (because the connex has HWUART and the verdex > doesn't). > Good to know! Didn't even notice the roboaudio. Dave Hylands wrote: > > Pretty much any of the daugtercards will give you access to some > GPIOs. What's important is making sure that you put appropriate > voltage converters/drivers on the GPIOs. For most of the boards, the > GPIOs are 3.3v, and can only drive a few mA. > ...and that certainly helps explain why the Robostix has an Atmega128 on it. I've not looked into example source yet, but I was hesitant to go with the Robostix simply because I didn't want to have to write code for both the AVR and within Linux- at least not as a requirement to bring a pin high or low. I'd be interfacing with I2C and SPI devices that are able to do a bit more. I've some experience with PIC and AVR MCUs, though a current favorite is the Propeller. Still is limited in terms of language and RAM, and so I've been interested again in a Linux-based board. With the Robostix, will I have the ability to directly control GPIO? Or will I need to write AVR programs to handle all the IO? As an aside- I don't suppose you're related to Jon Hylands? I plan on (or, hope to) run Squeak on this Gumstix once I access to some I/O. Thanks! Regards, Aaron -- View this message in context: http://www.nabble.com/Expansion-boards-for-the-Connex-200xm--tp25617284p25619314.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2009-09-26 02:16:47
|
Hi Aaron, > Dave Hylands wrote: >> >> There's also the gpsstix, audiostix2, and roboaudio-TH, and you could >> probably use the breakout-vx. Some of the pin mappings will be >> slightly different (because the connex has HWUART and the verdex >> doesn't). >> > > Good to know! Didn't even notice the roboaudio. > > > Dave Hylands wrote: >> >> Pretty much any of the daugtercards will give you access to some >> GPIOs. What's important is making sure that you put appropriate >> voltage converters/drivers on the GPIOs. For most of the boards, the >> GPIOs are 3.3v, and can only drive a few mA. >> > > ...and that certainly helps explain why the Robostix has an Atmega128 on it. > I've not looked into example source yet, but I was hesitant to go with the > Robostix simply because I didn't want to have to write code for both the AVR > and within Linux- at least not as a requirement to bring a pin high or low. For just toggling a GPIO, the robostix is probably overkill. The real advantage of the robostix is that it has six PWM channels (for driving motors or servos), 8 ADC channels, and lots of other things, which can allow I/O to be offloaded from the gumstix. > I'd be interfacing with I2C and SPI devices that are able to do a bit more. > I've some experience with PIC and AVR MCUs, though a current favorite is the > Propeller. Still is limited in terms of language and RAM, and so I've been > interested again in a Linux-based board. Both i2c and spi devices can be interfaced directly to the gumstix, perhaps requiring voltage conversion. > With the Robostix, will I have the ability to directly control GPIO? Or will > I need to write AVR programs to handle all the IO? With the robostix, pretty much all of the GPIO pins come from the ATMega128. There are a few pins that can be controlled directly from the gumstix (or UCB1400 in the case of the roboaudiostix). I've written quite a bit of sample code for the robostix. Included in that is a program called i2c-io which allows the gumstix to send commands to the robostix to control GPIOs, and read/write all of the registers on the robostix. This works for simple I/O. More complex I/O requires adding more code to i2c-io, or replacing it entirely. > As an aside- I don't suppose you're related to Jon Hylands? I plan on (or, > hope to) run Squeak on this Gumstix once I access to some I/O. Jon is my brother. I've ported Squeak to the gumstix. I'll have to dig around and see where I put it. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |