I solved the problem by creating a new fimage with the kernel 2.6.15, using the Phrozen SDK.
Ciao, Giovanni Giovanni <[EMAIL PROTECTED]> wrote: Hello, I'm building a device, which needs to receive bytes from a serial port. This device is connected to a PL-2303 USB/serial converter, which is connected to a USB port of the Fox. I use the kernel 2.4.31. The dmesg says: usb.c: registered new driver serial usbserial.c: USB Serial support registered for Generic usbserial.c: USB Serial Driver core v1.4 usbserial.c: USB Serial support registered for FTDI SIO usbserial.c: USB Serial support registered for FTDI 8U232AM Compatible usbserial.c: USB Serial support registered for FTDI FT232BM Compatible usbserial.c: USB Serial support registered for USB-UIRT Infrared Tranceiver usbserial.c: USB Serial support registered for Home-Electronics TIRA-1 IR Transceiver ftdi_sio.c: v1.3.5:USB FTDI Serial Converters Driver usbserial.c: USB Serial support registered for PL-2303 pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.10.1 ... usbserial.c: PL-2303 converter detected usbserial.c: PL-2303 converter now attached to ttyUSB0 (or usb/tts/0 for devfs) I have the following setup of the /dev/ttyUSB0: [EMAIL PROTECTED] /root]1717# stty -F /dev/ttyUSB0 -a speed 9600 baud; rows 0; columns 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxbel opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke I use the following command to send hexadecimal values to the serial port: [EMAIL PROTECTED] /root]111# printf \x20 > /dev/ttyUSB0 (sending 20 hexadecimal to the serial port) By using the above commands, the Fox is completely frozen, sometimes after the first printf, sometimes after two or three, etc. printf commands and sometimes after the stty -F /dev/ttyUSB0 -a command. Does anyone know why is this happening and how to solve this problem ? Best regards, Giovanni PS: I tried the above commands on my Slackware computer and it is working perfectly; one difference is that there is no USB/serial adapter on the Slackware computer and the kernel is 2.6.17.13. ------------------------------------------------ Resources are limited, Imagination is unlimited. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com [Non-text portions of this message have been removed] ------------------------------------------------ Resources are limited, Imagination is unlimited. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com [Non-text portions of this message have been removed]
