From owner-freebsd-usb@freebsd.org Tue Sep 19 15:00:58 2017 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5EEAAE17743 for ; Tue, 19 Sep 2017 15:00:58 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 2B6CA830D6 for ; Tue, 19 Sep 2017 15:00:58 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 775392601A9; Tue, 19 Sep 2017 17:00:55 +0200 (CEST) Subject: Re: umodem0, Cisco USB serial console, and quirks To: Mike Andrews , freebsd-usb@freebsd.org References: From: Hans Petter Selasky Message-ID: Date: Tue, 19 Sep 2017 16:58:26 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2017 15:00:58 -0000 On 09/19/17 16:22, Mike Andrews wrote: > I'm trying to get the USB console of a Cisco ASA 5506-X firewall (not > terribly obscure hardware) talking to FreeBSD, and having some trouble. > The relevant dmesg at probe time is: > > umodem0 on uhub7 > umodem0: > on usbus4 > umodem0: data interface 1, has no CM over data, has no break > > ...and /dev/cuaU2 is created, and I can connect to it using cu, but then > nothing happens. As in, hitting enter to get a prompt just sits there. > (cuaU1 and cuaU0 are a separate two-port USB serial adapter and that one > works fine, it's using uftdi instead of umodem...) > > The "has no CM over data" looks worrying. I attempted to add a quirk, > but either it isn't working or I didn't do it right. In > /boot/loader.conf I tried: > Hi, Try using usbdump to figure out what is going on. usbdump -i usbusX -f Y -s 65536 -vvv X and Y are the numbers in ugenX.Y printed in dmesg. It will dump all low level communication with the firewall. Maybe it needs some special character escaping to respond, or maybe it needs to set the RTS CTS bits. --HPS