From owner-freebsd-arm@freebsd.org Fri Jul 15 21:57:01 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 A6DF8B9A6B3 for ; Fri, 15 Jul 2016 21:57:01 +0000 (UTC) (envelope-from hmurray@megapathdsl.net) Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by mx1.freebsd.org (Postfix) with ESMTP id BEEC917F5 for ; Fri, 15 Jul 2016 21:56:57 +0000 (UTC) (envelope-from hmurray@megapathdsl.net) Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 1E399406063; Fri, 15 Jul 2016 14:47:52 -0700 (PDT) X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: Russell Haley cc: freebsd-arm , hmurray@megapathdsl.net From: Hal Murray Subject: Re: Bizarre clone attempt failures on Raspberry Pi2... In-Reply-To: Message from Russell Haley of "Fri, 15 Jul 2016 13:09:18 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Jul 2016 14:47:52 -0700 Message-Id: <20160715214752.1E399406063@ip-64-139-1-69.sjc.megapath.net> X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2016 21:57:01 -0000 russ.haley@gmail.com said: > Isn't putting an non-functioning embedded system on a serial console to > debug standard procedure with ALL operating systems? My two cents... I have several Pi-s and I didn't use the serial port to get any of them going. I think the answer to your question probably depends on the maturity of the system and the hardware available. If a system supports a keyboard and display, that's what I would try first since I usually have one handy. I have a 4 port KVM box. The 4th port moves to the current project as needed. I have adapters handy so it connects to almost anything... After I get the network going, I just ssh in. (after a while, the KVM cable moves on to the next project) I think work to get early console output on the display and input from the keyboard will be an important step in making a user-friendly environment. I have the hardware gizmo for a serial console on the Pi. I'd get it out to debug something if the documentation (or email) clearly stated that was the right approach. I probably wouldn't think to try it without a reminder. I've don't plenty of low-level debugging. The serial port just wouldn't occur to me when working on a system that supports a keyboard and display. -- These are my opinions. I hate spam.