Re: RPI2 Model B not booting with 13.2 release?

Mark Millard <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On May 30, 2023, at 09:10, Luís Henriques <[email protected]> wrote:

> I'm probably doing something wrong, but I've run out of ideas.
> 
> This is my first attempt to install FreeBSD on my old RPI2.

Which type of RPi2B? (There was a technically confusing
marking-naming used for a significant technical change.)

RPi2B v1.1: a cortex-A7  implementation of armv7, no aarch64 support
RPi2B v1.2: a cortex-a53 implementation of aarch64, plus aarch32/armv7

You did not supply enough information for me to tell
which.

>  So, after
> dd'ing the 13.2 (release) SD image

v1.1 would need:

FreeBSD-13.2-RELEASE-arm-armv7-GENERICSD.img.xz

instead of FreeBSD-13.2-RELEASE-arm64-aarch64-RPI.img.xz

v1.2 would need :

FreeBSD-13.2-RELEASE-arm64-aarch64-RPI.img.xz

instead of: FreeBSD-13.2-RELEASE-arm-armv7-GENERICSD.img.xz

You did not supply enough information for me to tell
which *.img* file you downloaded and tried to use.

FYI:

FreeBSD-13.2-RELEASE-arm-armv7-GENERICSD.img.xz has just
the one .dtb file: bcm2709-rpi-2-b.dtb (the one for the
v1.1 RPi2B). (If it also had bcm2710-rpi-2-b.dtb, then
both variants would boot. Similarly for other
bcm2710-rpi-*.dtb files enabling some other RPi* variants
to boot as armv7 instead of aarch64.)

By conttrast, adding  bcm2709-rpi-2-b.dtb to
FreeBSD-13.2-RELEASE-arm64-aarch64-RPI.img.xz would
not make it work for a RPi2B v1.1 .

> and connecting the serial USB, I got no
> output at all.  From the HDMI interface, I see a colourful screen, but
> nothing else.  The same happens with 13.1.  And only 12.4 seems to boot
> this device:
> 
> # uname -a
> FreeBSD generic 12.4-STABLE FreeBSD 12.4-STABLE r373082 GENERIC  arm
> 
> Is this model not supposed to boot anymore and I just couldn't find any
> information about it?  Or am I doing something wrong?


===
Mark Millard
marklmi at yahoo.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.