Re: Pi4 via Crochet?

On 2022-Mar-9, at 11:56, Karl Denninger <karl@denninger.net> wrote:

> Anyone got the necessary magic for it on -HEAD?
> 
> I've tried to build it and the SD card it makes appears to be built correctly.  I copied the Pi3s board config and modified it to get the RPI4 dtb and config.txt files, along with the RPI4 u-boot package.  That *should* work, I'd expect.
> 
> I get nothing on the serial console at all and only a three-blink/pause pattern on the green LED when power is connected so I have no idea where its failing in the boot process.
> 

What you describe is long before FreeBSD is involved. The sequence
for an RPi4 (in use-aarch64 mode) is basically:

RPI4 EEPROM
config.txt (you mentioned this one)
start4.elf (note the "4")
fixup4.dat (note the "4")
bcm2711-rpi-4-b.dtb (you mentioned this one)
(I omit overlays and such steps here.)
armstub8-gic.bin
U-Boot
FreeBSD loader (efi/boot/bootaa64.efi)
FreeBSD kernel (not from the msdos file system)
FreeBSD world  (not from the msdos file system)

But what you report looks like not even the RPi* firmware
got started.

If Crochet has copies of or refers to RPi* firmware to
put in the msdos file system, I see no evidence of
updates after the RPi4 was released. If so, the
materials are possibly way out of date --or track
the development firmware releases (frequently broken).
(It basically takes manual tracking to identify good
RPi* firmware and U-Boot combinations.)

A similar point could go for whatever U-Boot vintage
it is set up to put in place, although you did not
get that far (yet).

There are lots of vintages of the RPi* firmware and
U-Boot around and many combinations do not work well.
You were not explicit about what versions you are
using.

What does your context show for the likes of:

# strings start4.elf | grep "VC_BUILD_ID_"
VC_BUILD_ID_USER: dom
VC_BUILD_ID_TIME: 12:10:40
VC_BUILD_ID_VARIANT: start
VC_BUILD_ID_TIME: Feb 25 2021
VC_BUILD_ID_BRANCH: bcm2711_2
VC_BUILD_ID_HOSTNAME: buildbot
VC_BUILD_ID_PLATFORM: raspberrypi_linux
VC_BUILD_ID_VERSION: 564e5f9b852b23a330b1764bcf0b2d022a20afd0 (clean)

# strings u-boot.bin | grep "U-Boot 20"
U-Boot 2021.07 (Jan 22 2022 - 18:06:42 -0800)

Does the msdos file system have all files:

config.txt (you mentioned this one)
start4.elf (note the "4")
fixup4.dat (note the "4")
bcm2711-rpi-4-b.dtb (you mentioned this one)
(Here, I omit overlay/ content.)
armstub8-gic.bin
u-boot.bin
efi/boot/bootaa64.efi

Note that armstub8-gic.bin is neither RPi* firmware
nor part of U-Boot nor part of FreeBSD. But installing
the port sysutils/rpi-firmware supplies a copy under:

/usr/local/share/rpi-firmware/

with the RPi* firmware.

(I've not been tracking the status of RPi* firmware,
armstub8-gic.bin , or U-Boot for any RPi*s in some
time. Other vintages may be better than what I happen
to have around. There is more modern RPi* hardware
that "my vintage" materials would definitely not
handle. I'm not sure anyone is trying to track what
vintages are good vs. bad, or in what contexts or
in what ways.)

Note: What I have in overlays/ is just:

overlays/disable-bt.dtbo
overlays/miniuart-bt.dtbo
overlays/mmc.dtbo
overlays/pwm.dtbo

===
Mark Millard
marklmi at yahoo.com