From: Marcel G. <mar...@gm...> - 2010-02-14 01:23:46
|
A while back I purchased a 1 x waysmall 400xm-bt (with 5v US power adapter and duck antenna ). This wasn't cheap, I paid about 200 bucks for it. It has never worked. I've tried to connect to it using, kermit, minicom, screen, and usbnet. The only indication that this piece of crap even works is that the green led lights up. Does any body know how I can reset it back to the factory default. Or should I just toss it into the trash. |
From: Jaya K. <jay...@gm...> - 2010-02-14 04:54:52
|
On Sun, Feb 14, 2010 at 9:23 AM, Marcel Grenier <mar...@gm...> wrote: > A while back I purchased a 1 x waysmall 400xm-bt (with 5v US power adapter > and duck antenna ). This wasn't cheap, I paid about 200 bucks for it. It > has never worked. I've tried to connect to it using, kermit, minicom, > screen, and usbnet. > The only indication that this piece of crap even works is that the green led > lights up. Does any body know how I can reset it back to the factory > default. Or should I just toss it into the trash. > Hi Marcel, Don't toss it in the trash as it would then crap up the planet. :-) I had bought a basix 400xm-bt too and if you don't get the uboot console in minicom at 115200-8-n-1 then it is probably bricked which means you'll need to send it back to Gumstix and pay them 10 gazillion dollars to get it reflashed with a bootloader. I don't know if there is something like tweener that you can use to get JTAG access on your own. If it had never ever worked, then might also be a hardware fault though. Best regards, jaya |
From: Dave H. <dhy...@gm...> - 2010-02-14 04:55:41
|
HI Marcel, On Sat, Feb 13, 2010 at 5:23 PM, Marcel Grenier <mar...@gm...> wrote: > A while back I purchased a 1 x waysmall 400xm-bt (with 5v US power adapter > and duck antenna ). This wasn't cheap, I paid about 200 bucks for it. It > has never worked. I've tried to connect to it using, kermit, minicom, > screen, and usbnet. usbnet won't work out of the box. Are you sure you've disabled hardware flow control? That's the number 1 reason for not receiving any response? What type of connector are you using? What baud rate/settings are you using? Was this purchased new or used? (it's possible the previous owner changed the settings). Have you verified that serial loopback works? (i.e. unplug the serial cable from the gumstix and short Tx and Rx. You should be able to type and see the characters typed echoed back. If you remove the short, you should type and not see any characters echoed back. If you can't get get that working, then you have a problem with your PC or cable. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: Mark S. <ms...@ta...> - 2010-02-18 21:55:36
|
I am writing data over a usb serial link. I've set up the USB link using: modprobe usbserial ... and the device shows up as \dev\ttyUSB0. That's all fine. In my software, I open the port, no problem. The problem is that when I write data, "\n", 0x0a, gets converted to "\r", 0x0d. I am using the write function to write to the USB device. write(fd, str, nb); It seems that either the write function or the usbserial driver is replacing "\n" with "\r". The API to the usb device requires "\n". Does anyone have a clue as to what's happening here? Any info would be helpful. Thanks, -- Mark Sompel Principal Firmware Engineer Tagent 67 E. Evelyn Ave. Mountain View, CA 94041 |
From: Miner, J. W (US SSA) <jon...@ba...> - 2010-02-18 22:03:56
|
MArk - Look at setting the mode of the serial line. Something like what they do here in the tty_raw() function: http://www.cs.uleth.ca/~holzmann/C/system/ttyraw.c ________________________________________ From: Mark Sompel [ms...@ta...] Sent: Thursday, February 18, 2010 16:55 To: gum...@li... Subject: [Gumstix-users] usbserial problem I am writing data over a usb serial link. I've set up the USB link using: modprobe usbserial ... and the device shows up as \dev\ttyUSB0. That's all fine. In my software, I open the port, no problem. The problem is that when I write data, "\n", 0x0a, gets converted to "\r", 0x0d. I am using the write function to write to the USB device. write(fd, str, nb); It seems that either the write function or the usbserial driver is replacing "\n" with "\r". The API to the usb device requires "\n". Does anyone have a clue as to what's happening here? Any info would be helpful. Thanks, -- Mark Sompel Principal Firmware Engineer Tagent 67 E. Evelyn Ave. Mountain View, CA 94041 ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Mark S. <ms...@ta...> - 2010-02-19 00:05:58
|
OK. I figured it out. You need to run stty and change a few of the settings that replace "\n" with "\r". stty -F /dev/ttyUSB0 -onlret On 02/18/2010 01:55 PM, Mark Sompel wrote: > I am writing data over a usb serial link. I've set up the USB link using: > modprobe usbserial ... > and the device shows up as \dev\ttyUSB0. > > That's all fine. > > In my software, I open the port, no problem. > > The problem is that when I write data, > "\n", 0x0a, gets converted to "\r", 0x0d. > I am using the write function to write to the USB device. > > write(fd, str, nb); > > It seems that either the write function or the usbserial > driver is replacing "\n" with "\r". > > The API to the usb device requires "\n". > > Does anyone have a clue as to what's happening here? > Any info would be helpful. > > Thanks, > > -- Mark Sompel Principal Firmware Engineer Tagent 67 E. Evelyn Ave. Mountain View, CA 94041 |
From: Dave H. <dhy...@gm...> - 2010-02-19 00:49:32
|
Hi Mark, On Thu, Feb 18, 2010 at 4:05 PM, Mark Sompel <ms...@ta...> wrote: > OK. I figured it out. > > You need to run stty and change a few of the settings that replace > "\n" with "\r". > > stty -F /dev/ttyUSB0 -onlret You probably want stty -F /dev/ttyUSB0 raw The serial ports are in "cooked" mode by default. Raw mode changes a bunch of stuff and essentially gets you a raw pipe. And it's best if you do it from within your program (do the appropriate ioctl calls yourself). See: <http://tldp.org/HOWTO/Serial-Programming-HOWTO/> -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |