From owner-freebsd-arm@freebsd.org  Mon Jul  2 23:20:25 2018
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3D703FE379A
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Mon,  2 Jul 2018 23:20:25 +0000 (UTC)
 (envelope-from freebsd-arm@sentry.org)
Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "shadow.sentry.org",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 6689A7F90C
 for <freebsd-arm@freebsd.org>; Mon,  2 Jul 2018 23:20:23 +0000 (UTC)
 (envelope-from freebsd-arm@sentry.org)
Received: from shadow.sentry.org (localhost [127.0.0.1])
 by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id w62NKIuk049397
 for <freebsd-arm@freebsd.org>; Tue, 3 Jul 2018 09:20:18 +1000 (AEST)
 (envelope-from freebsd-arm@sentry.org)
Subject: Re: RPI3B+ does not reboot
To: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
References: <BY2PR16MB0149B3B639A5664E8CAF1870BD430@BY2PR16MB0149.namprd16.prod.outlook.com>
From: Trev <freebsd-arm@sentry.org>
Message-ID: <b52282e0-40cc-bb59-3f54-ca042b63bfd8@sentry.org>
Date: Tue, 3 Jul 2018 09:20:18 +1000
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Firefox/52.0 SeaMonkey/2.49.3
MIME-Version: 1.0
In-Reply-To: <BY2PR16MB0149B3B639A5664E8CAF1870BD430@BY2PR16MB0149.namprd16.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2
 (shadow.sentry.org [0.0.0.0]); Tue, 03 Jul 2018 09:20:18 +1000 (AEST)
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2018 23:20:25 -0000

Wis Macomson wrote on 03/07/2018 00:58:
> Can you disconnect the serial TX data (data to the RPi) and try the reboots?
> 
> It may be that this signal is partially powering the processor through the input ESD 
> protection diode, leading to very awkward internal states. This has been observed on
> the Rock64 (RK3328 SoC) and Rockpro64 (RK3399).
> 
> If you can just break the TX connection, you'll be able to see the boot messages.

I removed Tx and left Rx and Gnd connected but on the first reboot 
attempt I still suffered:

All buffers synced.
Uptime: 11h34m59s
Rebooting...
cpu_reset failed