Mike Frysinger wrote: > On Sunday 14 October 2007, Jason wrote: >> So what kind of wiring error would cause CTRL-C (0x03) and <CR> 0x0d to >> not get passed correctly, but [a-zA-Z0-9] to go through okay? > > i dont think they are getting passed through ... i think your device is > operating in loop back ... but i'm not an ee guy at all, i'm just posting > some of my experience ... > -mike
I think I found the problem. I enabled debug in the ftdi_sio driver and saw that it is echoing back what I type. It's status flags seems to be jive with what I found on the net as being okay. But this guy [1] mentions that the exact problem I'm having (subset: CTRL-C not making it to RedBoot) is caused by flow control being enabled and the gw2348-4 doesn't use it. So it looks like the FTDI cable either doesn't support disabling flow control, or ftdi_sio isn't setting the flow control to none properly... However, this is mostly academic since I found a neat hack [2] to probe for the board's ip, then telnet into Redboot and send CTRL-C within a 2 second window. Between this and tftp, I should be able to do everything I need to do. Jason [1] - http://www.me2000.net/wiki/index.php/Gateworks_Notes [2] - http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot "C program using Berkeley Sockets" -- [EMAIL PROTECTED] mailing list
