From owner-freebsd-hackers@freebsd.org Wed Nov 22 08:36:12 2017 Return-Path: Delivered-To: freebsd-hackers@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 5E63DDE4D8E for ; Wed, 22 Nov 2017 08:36:12 +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 281647235C; Wed, 22 Nov 2017 08:36:11 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 498512602ED; Wed, 22 Nov 2017 09:36:04 +0100 (CET) Subject: Re: Is ddb(4) over a USB-to-Serial port possible? To: Julian Elischer , Farhan Khan , freebsd-hackers@freebsd.org References: <11ce9826-f768-3ea0-547d-2d182d1552f0@gmail.com> <36165883-5cb7-aabc-c81e-cb5458029803@freebsd.org> From: Hans Petter Selasky Message-ID: <5c6da274-102c-33c6-50f0-20597cf8e7ef@selasky.org> Date: Wed, 22 Nov 2017 09:33:22 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <36165883-5cb7-aabc-c81e-cb5458029803@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2017 08:36:12 -0000 On 11/22/17 08:40, Julian Elischer wrote: > On 22/11/17 3:08 pm, Farhan Khan wrote: >> Hi all >> >> I am reading here in section "10.5, On-Line Kernel Debugging User >> Remote GDB" that you can run ddb(4) over a serial cable. I am >> interested in setting this up. >> >> My development box does not have a serial port (however, I do see a >> uart0 device in the kernel messages), so I attached a USB serial port >> attached to a machine with a serial port. The device uses the >> uslcom(4) driver and is listed as "Silicon Labs CP2102 USB to UART >> Bridge Controller". When I enter ddb and enter "gdb" I receive the >> error "The remote GDB backend could not be selected." >> >> The hint.uart.0.port in /boot/device.hints is still set to 0x3F8, >> which corresponds to the aforementioned kernel messages. I am not >> certain if this is the same port as the USB-based serial port. Does >> this feature work over USB? >> >> Thanks, >> Farhan Khan >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to >> "freebsd-hackers-unsubscribe@freebsd.org" >> > generally speaking the answer is no, unless the device is emulated using > SMI or some other mechanism that is independent of FreeBSD. > > uart0 is not the device on the USB but a hardware device at 3F8, > regardless of whether it actually exists. Since the USB stack is not > really functional when in the debugger, it can not be used to > communicate with the debugger. > > I find a better answer is to fire up the test machine under bhyve, in > which case its console is accessible through any stream session. (e.g. > ssh).. > Hi, There is another setting for this: Try setting cons_baud and cons_unit below. USB serial supports polling from the debugger after panic. hw.usb.ucom.cons_baud: 9600 hw.usb.ucom.cons_subunit: 0 hw.usb.ucom.cons_unit: -1 hw.usb.ucom.debug: 0 hw.usb.ucom.pps_mode: 0 --HPS