From owner-freebsd-stable@freebsd.org Sun Feb 28 11:21:11 2021 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 494005683D4; Sun, 28 Feb 2021 11:21:11 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from relay9-d.mail.gandi.net (relay9-d.mail.gandi.net [217.70.183.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DpLYf4ntkz3jP9; Sun, 28 Feb 2021 11:21:10 +0000 (UTC) (envelope-from avg@FreeBSD.org) X-Originating-IP: 195.64.148.76 Received: from [192.168.0.88] (unknown [195.64.148.76]) (Authenticated sender: andriy.gapon@uabsd.com) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id 31CD3FF807; Sun, 28 Feb 2021 11:21:06 +0000 (UTC) Subject: Re: uchcom update To: KOT MATPOCKuH , Ian FREISLICH Cc: freebsd-usb@freebsd.org, FreeBSD Current , freebsd-stable List References: <83f7a6dd-5d7e-cfd2-e580-4db0c7134220@capeaugusta.com> From: Andriy Gapon Message-ID: <592ff8c3-a47f-30c2-4e09-1a11152715c8@FreeBSD.org> Date: Sun, 28 Feb 2021 13:21:05 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4DpLYf4ntkz3jP9 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:29169, ipnet:217.70.176.0/20, country:FR]; local_wl_from(0.00)[FreeBSD.org] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Feb 2021 11:21:11 -0000 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: on usbus0 > uchcom0: CH340 detected > uchcom0: at uhub0, port 9, addr 17 (disconnected) > uchcom0: detached > uchcom0 on uhub0 > uchcom0: 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 : > >> 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: at usbus5, cfg=0 md=HOST spd=FULL >> (12Mbps) pwr=ON (96mA) >> ugen5.4.0: uchcom0: >> >> 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