Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Feb 2021 13:21:05 +0200
From:      Andriy Gapon <avg@FreeBSD.org>
To:        KOT MATPOCKuH <matpockuh@gmail.com>, Ian FREISLICH <ian.freislich@capeaugusta.com>
Cc:        freebsd-usb@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org>, freebsd-stable List <freebsd-stable@freebsd.org>
Subject:   Re: uchcom update
Message-ID:  <592ff8c3-a47f-30c2-4e09-1a11152715c8@FreeBSD.org>
In-Reply-To: <CALmdT0XEvbnRW99H3JRp1iN7Zbr1S7EyEiLFSUMOpN6kvykPtQ@mail.gmail.com>
References:  <eb56d9bc-a915-fa56-d1c2-b24cc30c8aa2@FreeBSD.org> <83f7a6dd-5d7e-cfd2-e580-4db0c7134220@capeaugusta.com> <CALmdT0XEvbnRW99H3JRp1iN7Zbr1S7EyEiLFSUMOpN6kvykPtQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 28/02/2021 11:03, KOT MATPOCKuH wrote:
> Hello!
> 
> I'm using FreeBSD 12.2-STABLE r368656 and got usb-to-rs232 with this
> controller.
> I see /dev/cuaU0 after plugging in adapter, I can attach to serial line
> using cu, but after sending any symbol to device I have device reconnection:
> uchcom0 on uhub0
> uchcom0: <vendor 0x1a86 USB2.0-Ser, rev 1.10/2.54, addr 17> on usbus0
> uchcom0: CH340 detected
> uchcom0: at uhub0, port 9, addr 17 (disconnected)
> uchcom0: detached
> uchcom0 on uhub0
> uchcom0: <vendor 0x1a86 USB2.0-Ser, rev 1.10/2.54, addr 17> on usbus0
> uchcom0: CH340 detected

I have this in my loader.conf:

# Ignore result of "clear stall" (clearing halt on endpoints)
# CH340 USB<->RS232 requires this
# and it seems that Linux and Windows do this by default
hw.usb.no_cs_fail=1

I recall that without that tuning I had a similar problem.

> вт, 5 июн. 2018 г. в 15:05, Ian FREISLICH <ian.freislich@capeaugusta.com>:
> 
>> On 05/22/2018 09:44 AM, Andriy Gapon wrote:
>>> Yesterday I committed some changes to uchcom (so far, only in CURRENT).
>>> Commits are r333997 - r334002.
>>>
>>> If you have a CH340/341 based USB<->RS232 adapter and it works for you,
>> could
>>> you please test that it still does?
>>> If you tried your adapter in the past and it did not work, there is a
>> chance it
>>> might start working now.  Could you please test that as well?
>>
>> ugen5.4: <vendor 0x1a86 USB2.0-Serial> at usbus5, cfg=0 md=HOST spd=FULL
>> (12Mbps) pwr=ON (96mA)
>> ugen5.4.0: uchcom0: <vendor 0x1a86 USB2.0-Serial, rev 1.10/2.54, addr 3>
>>
>> It's not made it any worse.  I'm not using this adapter by choice - it's
>> a USB to Maxim (Dallas) one-wire bus adapter.  The manual used to state
>> that these are possibly the worst chips ever.  Is that still the
>> prevailing opinion?


-- 
Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?592ff8c3-a47f-30c2-4e09-1a11152715c8>