Date: Mon, 9 Jul 2018 07:44:13 -0700 From: bob prohaska <fbsd@www.zefox.net> To: freebsd-arm@freebsd.org Subject: Re: RPI3B+ does not reboot Message-ID: <20180709144413.GA84647@www.zefox.net> In-Reply-To: <2b1d5d6a-602e-4d53-12a5-0f23c3569101@sentry.org> References: <BY2PR16MB0149B3B639A5664E8CAF1870BD430@BY2PR16MB0149.namprd16.prod.outlook.com> <20180703002249.GA57112@www.zefox.net> <2b1d5d6a-602e-4d53-12a5-0f23c3569101@sentry.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 03, 2018 at 10:38:15AM +1000, Trev wrote: > bob prohaska wrote on 03/07/2018 10:22: > > On Mon, Jul 02, 2018 at 02:58:30PM +0000, Wis Macomson wrote: > >> 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. > >> > > > > Updating from the June 28 snapshot (which did it twice) to r335835 seems to make > > the problem go away. > > r335854 compiled Mon Jul 2 16:03:04 AEST 2018 and I still have the > "cpu_reset failed" issue :( Still seeing this at r336118. On initial startup reboot worked correctly, but after running a day the problem returned. Thanks for reading, bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180709144413.GA84647>