From owner-freebsd-arm@freebsd.org Fri Nov 25 16:42:51 2016 Return-Path: Delivered-To: freebsd-arm@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 ED621C557B6 for ; Fri, 25 Nov 2016 16:42:51 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AB96F900 for ; Fri, 25 Nov 2016 16:42:50 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id uAPGgUoR022075; Fri, 25 Nov 2016 08:42:36 -0800 (PST) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id uAPGgJmX022074; Fri, 25 Nov 2016 08:42:19 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201611251642.uAPGgJmX022074@pdx.rh.CN85.dnsmgr.net> Subject: Re: Can't get 11.0-RELEASE to boot on Banana PI M3 In-Reply-To: <20161125105751.8F15A406061@ip-64-139-1-69.sjc.megapath.net> To: Hal Murray Date: Fri, 25 Nov 2016 08:42:19 -0800 (PST) CC: Michael Sperber , freebsd-arm@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2016 16:42:52 -0000 > > sperber@deinprogramm.de said: > > Ah, thanks ... but that's not standard RS232, right? (BPI homepages says > > "TTL".) If it isn't, what kind of hardware connects to that? > > The normal setup for RS232 is that the transmit and receive signals come out > of a big chip (SOC, or PCI UART, or USB UART, or ...) and then go through a > level converter which is typically a MAX-232 or one of many clones or > variants. The "TTL" is telling you that it doesn't have that level converter > chip. > > You can either add a level converter chip and then plug it into a real RS-232 > port, or find some setup that also doesn't have the level converter and > speaks TTL levels. Adafruit and probably many others sell a USB UART without > the level converter for applications like this. > https://www.adafruit.com/product/954 > > Sometimes, TTL means 3V CMOS levels and 5V from real TTL/CMOS will fry your > expensive chip. Best to check carefully. The above part says 3V. It also > has an extra power wire that you get to ignore. Be SURE to ignore that extra power wire! If your USB/Serial adapter also has a power wire DO NOT CONNECT IT. Many of these embeded boards provide a power pin with the serial interface that can be used to power something external, like a level shifter, and many of the USB/Serial adapters also bring out the USB 5V rail on a wire. DO NOT CONNECT THE TWO! That being said, there are many aftermarket USB/Serial cables avaliable, usually a 3.3V version of these well work everywhere as long as it has 5V tolerent inputs, which most of the newer ones do, check the specs from the vendor. 3.3V outputs well satisfy the input requirements of a 5V TTL/CMOS circuit and not cause it problems, the opposite is not always true. Watch your lead length and wire sizes if you need to do anything funny to get this connected, capacitive loading of any kind on this type of signal can cause character loss, especially at speeds above 9600 baud. -- Rod Grimes rgrimes@freebsd.org