Re: Configure Serial Adapter
On 2022/05/11 22:06, Rin Okuyama wrote: Alternatively, you can buy a well-supported product. I'm using one from CableCreation with uftdi(4) driver. This is sold worldwide, e.g.: https://www.amazon.com/dp/B075YHFMC7 Robert tells me that CableCreation has PL2303 models besides FTDI ones, which I meant in the previous message. If you want to use uftdi(4) driver, you have to choose the latter. Thanks, rin
Re: Configure Serial Adapter
On 2022/05/11 20:36, Robert Nestor wrote: First, I was mistaken about this Prolific PL2303 USB Serial Adapter cable being a null modem. It’s just a straight turn cable but I have a null modem dongle attached to it on the DB-9 end. As for the USB port on the system it’s attached to, this port has been used for various other devices (disks, geek sticks, weather station) without any issues. Rebooting the system with and without the DB-9 end connected always gives the same NOMEM results though. Your device seems to be supported by OpenBSD's uplcom(4). Probably, this commit does trick: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/uplcom.c#rev1.76 See also this one: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/uplcom.c#rev1.78 Alternatively, you can buy a well-supported product. I'm using one from CableCreation with uftdi(4) driver. This is sold worldwide, e.g.: https://www.amazon.com/dp/B075YHFMC7 Thanks, rin
Re: Configure Serial Adapter
First, I was mistaken about this Prolific PL2303 USB Serial Adapter cable being a null modem. It’s just a straight turn cable but I have a null modem dongle attached to it on the DB-9 end. As for the USB port on the system it’s attached to, this port has been used for various other devices (disks, geek sticks, weather station) without any issues. Rebooting the system with and without the DB-9 end connected always gives the same NOMEM results though.
Re: Configure Serial Adapter
rnes...@mac.com (Robert Nestor) writes:
>Following Michael=92s advice I added this line to sys/dev/usb/usbdevs =
>where other Prolific devices were defined:
> product PROLIFIC PL2303Y 0x23c3 PL2303 Serial adapter (Null =
>modem)
I've now added a few models to usbdevs...
>I regenerated the header files and added these lines to the device table =
>in sys/dev/usb/uplcom.c:
>/* Prolific USB to serial null modem cable */
>{ USB_VENDOR_PROLIFIC, USB_PRODUCT_PROLIFIC_PL2303Y },
>Rebuilt the GENERIC kernel and copied to to / and rebooted my system. I =
>get this result:
>[ 4.235870] uplcom0 at uhub1 port 1
>[ 4.235870] uplcom0: Prolific Technology Inc. (0x67b) USB-Serial =
>Controller (0x23c3), rev 2.00/3.05, addr 1
>[ 4.245877] uplcom0: autoconfiguration error: reset failed, NOMEM
>Did I miss something that is leading to this error?=20
No. A failed reset suggests that the chip isn't compatible to an old
PL2303. But NOMEM suggests, that this is a generic issue in the stack.
Does any other USB device work on that port ? Maybe a reboot helps.
Re: Configure Serial Adapter
The USB Serial cable I’m trying to use came from Amazon. According to their
description it uses the PL2303 chipset, so ...
Following Michael’s advice I added this line to sys/dev/usb/usbdevs where other
Prolific devices were defined:
product PROLIFIC PL2303Y 0x23c3 PL2303 Serial adapter (Null modem)
I regenerated the header files and added these lines to the device table in
sys/dev/usb/uplcom.c:
/* Prolific USB to serial null modem cable */
{ USB_VENDOR_PROLIFIC, USB_PRODUCT_PROLIFIC_PL2303Y },
Rebuilt the GENERIC kernel and copied to to / and rebooted my system. I get
this result:
[ 4.235870] uplcom0 at uhub1 port 1
[ 4.235870] uplcom0: Prolific Technology Inc. (0x67b) USB-Serial Controller
(0x23c3), rev 2.00/3.05, addr 1
[ 4.245877] uplcom0: autoconfiguration error: reset failed, NOMEM
Did I miss something that is leading to this error?
-bob
Re: Configure Serial Adapter
rnes...@mac.com (Robert Nestor) writes: >capture system). The USB-Serial device shows up on boot on the capture = >system as: >ugen0: Prolific Technology Inc. (0x67b) USB-Serial Controller (0x23c3), = >rev 2.00/3.05, addr 1 Means, it doesn't really show up. >I=92m thinking I need to build a new kernel to get it to show up as a = >com device before I can capture the serial input. Can someone give me = >the lines that need to be include in the GENERIC config file to = >accomplish this? The driver has a vendor/product list builtin, and that device doesn't match anything in that list. You should - add this to sys/dev/usb/usbdevs - Regen the header files with 'make -f Makefile.usbdevs TOOL_AWK=awk' - add the device to the table in sys/dev/usb/uplcom.c >And since I=92ve never done this before can someone tell me what I need = >to do on the test system to direct console output over the serial and = >what need to do on the capture system to get the results? That depends a bit on the system. For a traditional PC booting with BIOS you'd use 'fdisk -c /usr/mdec/mbr_com0' to install a bootblock for serial console. Greetings,
Configure Serial Adapter
Working on getting the console output from a system that consistently fails to boot amd64 -current (it boots and runs 9.2 without any issues). I’ve got a serial (null modem) cable, but I need to go from a serial port (on the test system) to a USB-Serial converted port (on the capture system). The USB-Serial device shows up on boot on the capture system as: ugen0: Prolific Technology Inc. (0x67b) USB-Serial Controller (0x23c3), rev 2.00/3.05, addr 1 I’m thinking I need to build a new kernel to get it to show up as a com device before I can capture the serial input. Can someone give me the lines that need to be include in the GENERIC config file to accomplish this? And since I’ve never done this before can someone tell me what I need to do on the test system to direct console output over the serial and what need to do on the capture system to get the results? Hoping to try and get some useful data here before the 10.0 release as I’m pretty sure I won’t be the only one with this particular problem. Thanks, -bob
