Date: Wed, 3 Jan 2018 23:08:06 -0800 From: Mark Millard <markmi@dsl-only.net> To: bob prohaska <fbsd@www.zefox.net> Cc: Freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: RPI2 boot hangs with red light on Message-ID: <802335D5-A961-4ABB-91D8-97B108106BEB@dsl-only.net> In-Reply-To: <20180104054236.GA15764@www.zefox.net> References: <20180102222730.GB10596@www.zefox.net> <3EE68320-8359-495D-AFCE-098A2220C6AE@dsl-only.net> <20180104023257.GA15177@www.zefox.net> <1515039689.1759.27.camel@freebsd.org> <20180104054236.GA15764@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-Jan-3, at 9:42 PM, bob prohaska <fbsd at www.zefox.net> wrote: > On Wed, Jan 03, 2018 at 09:21:29PM -0700, Ian Lepore wrote: >> >> There are no architectural differences between ubldr built for armv6 vs >> armv7, and either version could load either flavor of kernel. ?There >> have been some bugfixes applied to ubldr in the past few months. >> >> -- Ian > > It seems the problems lie elsewhere. I've updated the contents of > /boot/msdos to > -rwxr-xr-x 1 root wheel 1494 Jan 3 20:45 LICENCE.broadcom > -rwxr-xr-x 1 root wheel 50248 Jan 3 20:45 bootcode.bin > -rwxr-xr-x 1 root wheel 75 Jan 3 20:45 config.txt > -rwxr-xr-x 1 root wheel 6551 Jan 3 20:45 fixup.dat > -rwxr-xr-x 1 root wheel 2578 Jan 3 20:45 fixup_cd.dat > -rwxr-xr-x 1 root wheel 9694 Jan 3 20:45 fixup_db.dat > -rwxr-xr-x 1 root wheel 9694 Jan 3 20:45 fixup_x.dat > -rwxr-xr-x 1 root wheel 13419 Jun 26 2017 rpi2.dtb > -rwxr-xr-x 1 root wheel 2820196 Jan 3 20:45 start.elf > -rwxr-xr-x 1 root wheel 667460 Jan 3 20:45 start_cd.elf > -rwxr-xr-x 1 root wheel 4956676 Jan 3 20:45 start_db.elf > -rwxr-xr-x 1 root wheel 3904228 Jan 3 20:45 start_x.elf > -rwxr-xr-x 1 root wheel 380264 Jan 3 20:33 u-boot.bin > -rwxr-xr-x 1 root wheel 892172 Jan 3 20:48 ubldr > -rwxr-xr-x 1 root wheel 232112 Jan 3 20:48 ubldr.bin > (yes, rpi2.dtb is stale, but it seems not to matter) . . . I do not have ubldr, just ubldr.bin. Other than that, the sizes of the files listed above all match the sizes on the msdosfs partition that I use for the rpi2. (My dates are all Dec 22 but the rpi2's time may not have had a good combination of accuracy and precision.) "unable to get device descriptor (error=-22)" is from u-boot/blob/master/common/usb.c and its usb_new_device routine from what I can tell. It's cause and consequences might have contributed to the "Timeout poll on interrupt endpoint" messages from u-boot. May be eliminating all the usb devices that you can might sidestep some issue? (Also avoid from -r326347 through -r327484 for head: before or after as far as the kernel goes.) === Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?802335D5-A961-4ABB-91D8-97B108106BEB>