Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive
Synopsis: uplcom USB To COM Device doesn't transmit data, only receive State-Changed-From-To: open->closed State-Changed-By: eadler State-Changed-When: Sat Aug 6 21:43:28 UTC 2011 State-Changed-Why: Submitted reported that a new copy of the same hardware works. Old one was likely defective. http://www.freebsd.org/cgi/query-pr.cgi?pr=158650 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive
The following reply was made to PR usb/158650; it has been noted by GNATS. From: Wayne Sierke To: Hans Petter Selasky Cc: Renato Tambellini , freebsd-gnats-sub...@freebsd.org, freebsd-usb@freebsd.org Subject: Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive Date: Fri, 08 Jul 2011 12:40:19 +0930 On Wed, 2011-07-06 at 21:35 +0200, Hans Petter Selasky wrote: > I have an uplcom adapter here and I cannot reproduce except if I do the > following: > > cu -l /dev/cuaU0 > > Unplug uplcom. Then type something: > > cu -l /dev/cuaU0 > Connected > write: Device not configured > write: Device not configured > > Then I need to "killall -KILL cu" to get back to normal. Just a note that in my experience it has always been sufficient in this circumstance (as far as I can recall) to simply exit normally from cu/tip; I don't recall ever having to KILL it. Typing the following has worked: ~. i.e. carriage-return, tilde, then a period (or control-d) (assuming the default "~" escape character). I don't recall off-hand whether I've done this on 8.x, but certainly it has worked up to 7.4. Wayne ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive
On Wed, 2011-07-06 at 21:35 +0200, Hans Petter Selasky wrote: > I have an uplcom adapter here and I cannot reproduce except if I do the > following: > > cu -l /dev/cuaU0 > > Unplug uplcom. Then type something: > > cu -l /dev/cuaU0 > Connected > write: Device not configured > write: Device not configured > > Then I need to "killall -KILL cu" to get back to normal. Just a note that in my experience it has always been sufficient in this circumstance (as far as I can recall) to simply exit normally from cu/tip; I don't recall ever having to KILL it. Typing the following has worked: ~. i.e. carriage-return, tilde, then a period (or control-d) (assuming the default "~" escape character). I don't recall off-hand whether I've done this on 8.x, but certainly it has worked up to 7.4. Wayne ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive
The following reply was made to PR usb/158650; it has been noted by GNATS. From: Hans Petter Selasky To: Renato Tambellini Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@freebsd.org Subject: Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive Date: Wed, 6 Jul 2011 21:35:18 +0200 On Wednesday 06 July 2011 17:37:53 Renato Tambellini wrote: > Hi Hans, > > Follow the logs of my application and cu(1) trying to access my > another BSD machine. > > The files .dump are stdout of usbdump and .log are the logs of debug from > cons. > > In cu, I get the "login: " and a write error when I try to send the > chars to the remote console: > > # cu -l /dev/ttyU0 > Connected > ]Jj > > login: write: Device not configured >write: Device not configured > ... > > The kernel reconnects the device on error and the speed are set > correctly, 19200 for my app and 9600 to access the remote console from > cu. > Hi, What are the values of the following sysctls? sysctl hw.usb.ucom.cons_unit sysctl hw.usb.ucom.cons_baud Could you set: sysctl hw.usb.ucom.debug=15 Then type something on the cu terminal and see if you get something through. I have an uplcom adapter here and I cannot reproduce except if I do the following: cu -l /dev/cuaU0 Unplug uplcom. Then type something: cu -l /dev/cuaU0 Connected write: Device not configured write: Device not configured Then I need to "killall -KILL cu" to get back to normal. NOTE: If applications opening a USB TTY device does not close on error, then the USB stack will wait until that happens before it can enumerate more devices. This is a TTY stack problem. You can try to remove the force_short_xfer=1 flag in sys/dev/usb/serial/uplcom.c for the BULK TX transfer. I'm not sure if it helps. Really strange if your uplcom crashes on a ZLP! --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive
On Wednesday 06 July 2011 17:37:53 Renato Tambellini wrote: > Hi Hans, > > Follow the logs of my application and cu(1) trying to access my > another BSD machine. > > The files .dump are stdout of usbdump and .log are the logs of debug from > cons. > > In cu, I get the "login: " and a write error when I try to send the > chars to the remote console: > > # cu -l /dev/ttyU0 > Connected > ]Jj > > login: write: Device not configured >write: Device not configured > ... > > The kernel reconnects the device on error and the speed are set > correctly, 19200 for my app and 9600 to access the remote console from > cu. > Hi, What are the values of the following sysctls? sysctl hw.usb.ucom.cons_unit sysctl hw.usb.ucom.cons_baud Could you set: sysctl hw.usb.ucom.debug=15 Then type something on the cu terminal and see if you get something through. I have an uplcom adapter here and I cannot reproduce except if I do the following: cu -l /dev/cuaU0 Unplug uplcom. Then type something: cu -l /dev/cuaU0 Connected write: Device not configured write: Device not configured Then I need to "killall -KILL cu" to get back to normal. NOTE: If applications opening a USB TTY device does not close on error, then the USB stack will wait until that happens before it can enumerate more devices. This is a TTY stack problem. You can try to remove the force_short_xfer=1 flag in sys/dev/usb/serial/uplcom.c for the BULK TX transfer. I'm not sure if it helps. Really strange if your uplcom crashes on a ZLP! --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive
The following reply was made to PR usb/158650; it has been noted by GNATS. From: Hans Petter Selasky To: Renato Tambellini Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@freebsd.org Subject: Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive Date: Wed, 6 Jul 2011 08:59:58 +0200 On Tuesday 05 July 2011 17:31:36 Renato Tambellini wrote: > Hi Hans, > > I'm trying to transmit data to an serial console on another machine > and nothing happens > when I send data, the same occur when I use fldigi to control my > amateur radio transceiver and use a serial mouse attached to the USB > to COM serial port. > > In my old machine that was a FreeBSD 6, the device worked normally via > ucom driver. After sent this PR, I update my kernel to the latest > source with csup and the problem has worsened. Now when the program > wait a response of the radio, the device is disconnected by kernel. > > Lots of messages generated by kernel: > > uplcom0: at uhub3, port 2, addr 5 (disconnected) > uplcom0: rev 1.10/3.00, addr 5> on usbus1 > > This usbdump.txt was recorded when I use fldigi to get the radio > transceiver frequency. Hi, It looks like your application is only opening and closing the comport. Try also to enable ucom debugging: sysctl hw.usb.ucom.debug=15 --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive
On Tuesday 05 July 2011 17:31:36 Renato Tambellini wrote: > Hi Hans, > > I'm trying to transmit data to an serial console on another machine > and nothing happens > when I send data, the same occur when I use fldigi to control my > amateur radio transceiver and use a serial mouse attached to the USB > to COM serial port. > > In my old machine that was a FreeBSD 6, the device worked normally via > ucom driver. After sent this PR, I update my kernel to the latest > source with csup and the problem has worsened. Now when the program > wait a response of the radio, the device is disconnected by kernel. > > Lots of messages generated by kernel: > > uplcom0: at uhub3, port 2, addr 5 (disconnected) > uplcom0: rev 1.10/3.00, addr 5> on usbus1 > > This usbdump.txt was recorded when I use fldigi to get the radio > transceiver frequency. Hi, It looks like your application is only opening and closing the comport. Try also to enable ucom debugging: sysctl hw.usb.ucom.debug=15 --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive
The following reply was made to PR usb/158650; it has been noted by GNATS. From: Hans Petter Selasky To: freebsd-usb@freebsd.org Cc: Renato Tambellini , freebsd-gnats-sub...@freebsd.org Subject: Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive Date: Tue, 5 Jul 2011 09:06:17 +0200 On Tuesday 05 July 2011 02:37:49 Renato Tambellini wrote: > >Number: 158650 > >Category: usb > >Synopsis: uplcom USB To COM Device doesn't transmit data, only > >receive Confidential: no > >Severity: non-critical > >Priority: low > >Responsible:freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Tue Jul 05 00:40:09 UTC 2011 > >Closed-Date: > >Last-Modified: > >Originator: Renato Tambellini > >Release:8.2-STABLE > >Organization: > > >Environment: > FreeBSD devilbox.homeunix.net 8.2-STABLE FreeBSD 8.2-STABLE #0: Wed Jun 1 > 05:48:46 BRT 2011 > r...@devilbox.homeunix.net:/usr/obj/usr/src/sys/GENERIC amd64 > > >Description: > The USB To COM Device Prolific PL-2303 doesn't transmit data, only receive. > > # dmesg | grep Prolific > ugen1.4: at usbus1 > uplcom0: rev 1.10/3.00, addr 4> on usbus1 > > # usbconfig -d 1.4 dump_device_desc > ugen1.4: at usbus1, > cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0110 > bDeviceClass = 0x > bDeviceSubClass = 0x > bDeviceProtocol = 0x > bMaxPacketSize0 = 0x0040 > idVendor = 0x067b > idProduct = 0x2303 > bcdDevice = 0x0300 > iManufacturer = 0x0001 > iProduct = 0x0002 > iSerialNumber = 0x > bNumConfigurations = 0x0001 > > >How-To-Repeat: > 1) Plug the DB9 to serial console on another box using a null-modem cable. > 2) Plug the device to USB port. > 3) Try to access the console: > > cu -l /dev/cuaU0 -s 9600 > > 4) The terminal only receive data, not transmit. > Hi, Can you run usbdump and show what happens when you try to transmit data? Are you sure the baudrate is correct? usbdump -i usbus1 - -s 4096 ugen1.4 -> usbus1 ugen2.4 -> usbus2 ... --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive
On Tuesday 05 July 2011 02:37:49 Renato Tambellini wrote: > >Number: 158650 > >Category: usb > >Synopsis: uplcom USB To COM Device doesn't transmit data, only > >receive Confidential: no > >Severity: non-critical > >Priority: low > >Responsible:freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Tue Jul 05 00:40:09 UTC 2011 > >Closed-Date: > >Last-Modified: > >Originator: Renato Tambellini > >Release:8.2-STABLE > >Organization: > > >Environment: > FreeBSD devilbox.homeunix.net 8.2-STABLE FreeBSD 8.2-STABLE #0: Wed Jun 1 > 05:48:46 BRT 2011 > r...@devilbox.homeunix.net:/usr/obj/usr/src/sys/GENERIC amd64 > > >Description: > The USB To COM Device Prolific PL-2303 doesn't transmit data, only receive. > > # dmesg | grep Prolific > ugen1.4: at usbus1 > uplcom0: rev 1.10/3.00, addr 4> on usbus1 > > # usbconfig -d 1.4 dump_device_desc > ugen1.4: at usbus1, > cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0110 > bDeviceClass = 0x > bDeviceSubClass = 0x > bDeviceProtocol = 0x > bMaxPacketSize0 = 0x0040 > idVendor = 0x067b > idProduct = 0x2303 > bcdDevice = 0x0300 > iManufacturer = 0x0001 > iProduct = 0x0002 > iSerialNumber = 0x > bNumConfigurations = 0x0001 > > >How-To-Repeat: > 1) Plug the DB9 to serial console on another box using a null-modem cable. > 2) Plug the device to USB port. > 3) Try to access the console: > > cu -l /dev/cuaU0 -s 9600 > > 4) The terminal only receive data, not transmit. > Hi, Can you run usbdump and show what happens when you try to transmit data? Are you sure the baudrate is correct? usbdump -i usbus1 - -s 4096 ugen1.4 -> usbus1 ugen2.4 -> usbus2 ... --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
usb/158650: uplcom USB To COM Device doesn't transmit data, only receive
>Number: 158650 >Category: usb >Synopsis: uplcom USB To COM Device doesn't transmit data, only receive >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 05 00:40:09 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Renato Tambellini >Release:8.2-STABLE >Organization: >Environment: FreeBSD devilbox.homeunix.net 8.2-STABLE FreeBSD 8.2-STABLE #0: Wed Jun 1 05:48:46 BRT 2011 r...@devilbox.homeunix.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: The USB To COM Device Prolific PL-2303 doesn't transmit data, only receive. # dmesg | grep Prolific ugen1.4: at usbus1 uplcom0: on usbus1 # usbconfig -d 1.4 dump_device_desc ugen1.4: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x067b idProduct = 0x2303 bcdDevice = 0x0300 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x bNumConfigurations = 0x0001 >How-To-Repeat: 1) Plug the DB9 to serial console on another box using a null-modem cable. 2) Plug the device to USB port. 3) Try to access the console: cu -l /dev/cuaU0 -s 9600 4) The terminal only receive data, not transmit. >Fix: >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
