ftdi-usb-sio-devel

[Ftdi-usb-sio-devel] AT91SAM9263 USB Serial hang?

[Timo TH <ti...@po...>]

Anyone seen this kind of a problem?

Environment : ARM9 SAM9263ek, gprs modem on usb, (pppd 2.4.4)

With Linux 2.6.27.34 and ftdi_sio 1.4.3, everything worked OK.
Upgraded to Linux 2.6.31.6, which brought ftdi_sio 1.5.0 and now
everything works upto point where
data connection should be made.
Something wrong with handling of DTR or DCD or what?


# modprobe ftdi_sio
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
USB Serial support registered for FTDI USB Serial Device
ftdi_sio 1-2.2:1.0: usb_probe_interface
ftdi_sio 1-2.2:1.0: usb_probe_interface - got id
ftdi_sio 1-2.2:1.0: FTDI USB Serial Device converter detected
usb 1-2.2: Detected FT2232C
usb 1-2.2: Number of endpoints 2
usb 1-2.2: Endpoint 1 MaxPacketSize 64
usb 1-2.2: Endpoint 2 MaxPacketSize 64
usb 1-2.2: Setting MaxPacketSize 64
usb 1-2.2: FTDI USB Serial Device converter now attached to ttyUSB0
ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver

# microcom /dev/ttyUSB0
AT
OK
AT+CPIN=0000
OK
AT+CREG?
+CREG: 0,1
ATD*98#
//// No reply of any kind

With 2.6.27.34, everything above is same
and there ATD gets reply
CONNECT

Strange detail, If instead of microcom doing
# cat < /dev/ttyUSB0 in one terminal, and just echo in the AT commands
in another terminal, then the cat displays CONNECT

But this is no help for my goal, since I'm trying to use pppd and it
only gets timeout to its ATD command.




Greatly appreciating any help and hints already..
- Timmy

Re: [Ftdi-usb-sio-devel] AT91SAM9263 USB Serial hang?

[Bill R. <bil...@gm...>]

Are able to try minicom instead of microcom?

If that actually works can you get an strace of both of them? I'm curious to
see how they setup the serial port.

To get the detail it would need to be something like:

strace -f -w /tmp/microcom.strace -tt -T -v microcom whatever arguments

I like the -tt -T for timing reasons. The important thing is the -v and
maybe the -f. But the -v is necessary to get the full ioctl/termios
settings.

And you could be right  - there may be some kind of flow control setting
getting in the way.

Re: [Ftdi-usb-sio-devel] AT91SAM9263 USB Serial hang?

[Timo TH <ti...@po...>]

You were correct, using minicom things worked,
attached both straces,

On 11 February 2010 20:46, Bill Ryder <bil...@gm...> wrote:
> Are able to try minicom instead of microcom?
>
> If that actually works can you get an strace of both of them? I'm curious to
> see how they setup the serial port.
>
> To get the detail it would need to be something like:
>
> strace -f -w /tmp/microcom.strace -tt -T -v microcom whatever arguments
>
> I like the -tt -T for timing reasons. The important thing is the -v and
> maybe the -f. But the -v is necessary to get the full ioctl/termios
> settings.
>
> And you could be right  - there may be some kind of flow control setting
> getting in the way.
>
>
>
>

Re: [Ftdi-usb-sio-devel] AT91SAM9263 USB Serial hang?

[Timo TH <ti...@po...>]

Did the strace reveal something interesting? about why the microcom
and pppd hang.

On 12 February 2010 12:17, Timo TH <ti...@po...> wrote:
> You were correct, using minicom things worked,
> attached both straces,
>
> On 11 February 2010 20:46, Bill Ryder <bil...@gm...> wrote:
>> Are able to try minicom instead of microcom?
>>
>> If that actually works can you get an strace of both of them? I'm curious to
>> see how they setup the serial port.
>>
>> To get the detail it would need to be something like:
>>
>> strace -f -w /tmp/microcom.strace -tt -T -v microcom whatever arguments
>>
>> I like the -tt -T for timing reasons. The important thing is the -v and
>> maybe the -f. But the -v is necessary to get the full ioctl/termios
>> settings.
>>
>> And you could be right  - there may be some kind of flow control setting
>> getting in the way.
>>
>>
>>
>>

Re: [Ftdi-usb-sio-devel] AT91SAM9263 USB Serial hang?

[Bill R. <bil...@gm...>]

Hi there,

minicom uses the TIOCMGET and TIOCMSET calls which are properly implemented.

microcom does not.

Which is possibly why minicom was working and microcom was not.

The flow control was set properly by minicom

1044  10:12:29.685847 ioctl(3, TIOCMGET, [TIOCM_CTS|TIOCM_DSR]) = 0
<0.000875>
1044  10:12:29.688026 ioctl(3, TIOCMSET, [TIOCM_RTS|TIOCM_CTS|TIOCM_DSR]) =
0 <0.000802>

Also minicom was quite careful about checking the stats of the various
flowcontrol/status lines and microcom does not.

Bill


On Wed, Feb 17, 2010 at 8:22 AM, Timo TH <ti...@po...> wrote:

> Did the strace reveal something interesting? about why the microcom
> and pppd hang.
>
> On 12 February 2010 12:17, Timo TH <ti...@po...> wrote:
> > You were correct, using minicom things worked,
> > attached both straces,
> >
> > On 11 February 2010 20:46, Bill Ryder <bil...@gm...> wrote:
> >> Are able to try minicom instead of microcom?
> >>
> >> If that actually works can you get an strace of both of them? I'm
> curious to
> >> see how they setup the serial port.
> >>
> >> To get the detail it would need to be something like:
> >>
> >> strace -f -w /tmp/microcom.strace -tt -T -v microcom whatever arguments
> >>
> >> I like the -tt -T for timing reasons. The important thing is the -v and
> >> maybe the -f. But the -v is necessary to get the full ioctl/termios
> >> settings.
> >>
> >> And you could be right  - there may be some kind of flow control setting
> >> getting in the way.
> >>
> >>
> >>
> >>
>