Re: rpi4b main-n245392-8423f5d4c12 won't boot due to microsd timeout [FIXED]

tech-lists <[email protected]> Sun, 14 Mar 2021 01:29:36 +0000
Newsgroups	gmane.os.freebsd.devel.arm
Message-ID	<[email protected]>
Hi,

(in my reply below I'm using md5 to differentiate btwn files with
identical names)

On Sat, Mar 13, 2021 at 01:04:01PM -0800, Mark Millard wrote:

>If I gather correctly, it works but so does the one found in
>FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20210311-15565e0a217-257277.img
>? In other words, the material from
>fbsd-rpi4-u-boot2021-04-klaus/files/u-boot.bin/download
>works but is not required to make the RPi4B work?

I didn't even think about the u-boot already on the image! I just
followed the notes i made in
https://cloud.zyxst.net/~john/FreeBSD/current/rpi4b/installing.txt
which installed u-boot.bin dated Oct 5 and has md5 of
d208763206d50d3ec40b04cc81685b29 and that worked.

The one provided with
FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20210311-15565e0a217-257277.img
has md5 967c3a667af11512bafd2525ef97af5f and is dated 11th March. I've
not tried this one, as I overwrote it before booting it for the first
time. 

I got the latest u-boot.bin when Klaus kindly offered it (md5
1b868cc0550df026e1a4e7baf2cca223 dated 13th March)

>Be very careful with referencing "latest" start4.elf and
>the like because folks could easily interpret such to be
>something like (using start4.elf as an example):
>
>https://github.com/raspberrypi/firmware/blob/master/boot/start4.elf
>
>that can change on a regular basis and is far from guaranteed
>to be a version that works for FreeBSD use. (In recent months
>such usually has not worked. Even tagged versions need not
>work for FreeBSD use, as was true for FreeBSD tried to use
>some in the range 1.20210104 through 1.20210201 .)

My reference was:
https://github.com/raspberrypi/firmware/raw/master/boot/fixup4.dat
https://github.com/raspberrypi/firmware/raw/master/boot/start4.elf

from my notes but yeah, point taken. I am still trying to get my head 
around git, after using svn and cvs for years.

>My guess here is that you are referring to materials from the
>most recent sysutils/rpi-firmware port. Those are (for now)
>based on somewhat older RPi* materials. Using start4.elf as
>an example, sysutils/rpi-firmware is based on, in part,
>
>https://github.com/raspberrypi/firmware/blob/1.20210303/boot/start4.elf

I'd not installed the port at any stage. The md5 for the start4.elf 
above is 1a13569ce69f758c87a71dba78750f0d and the md5 of the one I downloaded
is 741c0a91981196e2bc01b0b25f458045 (dated 10th March).

>If one does find materials in master that work and wants to
>refer to them, it is best to find what master translates to
>at the time and refer to that specifically, for example:
>
>https://github.com/raspberrypi/firmware/tree/0591568b29a724de406aa737fc8e13f68c423f3f
>
>(One has to look at the commits history to figure out
>such an absolute untagged reference.)

OK. So in my example, in this case start4.elf (of 10th March), the absolute URL would be 
https://github.com/raspberrypi/firmware/raw/0591568b29a724de406aa737fc8e13f68c423f3f/boot/start4.elf
?

...and that's a stable URL? just making sure

thanks,
-- 
J.
signature.asc (application/pgp-signature, 833 B)