Re: Boot image for a Pi4 ?

On Jul 5, 2024, at 11:28, bob prohaska <fbsd@www.zefox.net> wrote:

> On Thu, Jul 04, 2024 at 09:36:22PM -0700, Mark Millard wrote:
>> On Jul 4, 2024, at 18:22, bob prohaska <fbsd@www.zefox.net> wrote:
>> 
>>> Can anybody suggest a -release  image to run on a Pi4, 8GB?
>> 
>> RPi4B Rev. 1.4? Rev. 1.5?
>> 
> 
> It's marked Raspberry Pi 4 Model B, no rev that I can find.
> The copyrwight date is 2018, so it's older than expected.

That Copyright date does not tell you the vintage:

The RPi4B Rev 1.5 "C0T" wtih 8 GiBytes also lists 2018.

Capture the early serial console output from the
RPi* bootloader and firmware and look for lines
that contain one of (showing a 8 GiByte Rev 1.5
example: d03115):

boardrev d03115
0x00d03115
RPI 4 Model B (0xd03115)

That last is actually from U-Boot.
The first was toward the end of the "BOOTMODE:" line.
The middle was the line after the "Read fixup4.dat bytes" line.

By contrast a 4GiByte Rev 1.1 has for those lines:

boardrev c03111
0x00c03111
RPI 4 Model B (0xc03111)

>> Using a Rev 1.5 (so: "C0T", not "B0T") . . .
>> 
> Guess my Pi4 is likely "BOT", given the age. 
> 
> After a lot of hair-pulling it turns out I didn't
> connect the usb-serial ground wire..... 
> Now the machine boots
> FreeBSD-14.1-RELEASE-arm64-aarch64-RPI.img
> with no problem.
> 
> I think the original problem was likely a bungled
> dd operation. When the card was put back in RasPiOS,
> config.text was reported "non-ascii", likely some
> kind of corruption. The image that boots was written
> with the Raspberry Pi Imager, which seems to verify
> after writing. In any case, all seems well now.
> 
> Thanks for writing, and apologies for the noise!





===
Mark Millard
marklmi at yahoo.com