RaspberryPi 4B 8G model not boot

[Mark Millard]

On 2020-May-29, at 22:49, Klaus Küchemann via freebsd-arm <freebsd-arm at freebsd.org> wrote:

> Am 30.05.2020 um 06:09 schrieb YAMAMOTO Shigeru <shigeru at os-hackers.jp>:
>> 
>> 
>> Hi all,
>> 
>> I buy new RaspberryPi 4B 8Gbyte model.

This model has differences, such as what eeprom has
the VL805 material:

QUOTE ( https://github.com/raspberrypi/rpi-eeprom/tags for v2020.05.28-137ad )
Newer board revisions do not have a dedicated VL805 EEPROM. Instead,
the VL805 firmware is loaded from the bootloader EEPROM.
END QUOTE

None of sysutils/rpi-firmware , sysutils/u-boot-rpi[34] , and/or
FreeBSD's kernel have been updated for such differences.

> my seller isn’t very responsive so I’m still waiting :-)
>> 
>> I make SD card image from current snapshot for RaspberryPi 3.
>> https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-arm64-aarch64-RPI3-20200528-r361567.img.xz
>> 
>> 1. write image to SD card
> 
> O.K.
> 
>> 2. download *.dat, *.elf, bootcode.bin, bcm2711-rpi-4-b.dtb from https://github.com/raspberrypi/firmware
>> 3. replace *.dat, *.elf, bootcode.bin, bcm2711-rpi-4-b.dtb
> 
> You can leave the msdos-partition as it is, those files are already there.

It may be that the files should not be updated. But the content
of the files need not be the same.

https://github.com/raspberrypi/firmware shows the master branch
by default but allows, for example, selecting a tagged build instead.
The original message did not make clear which branch's/tag's material
was used.

FreeBSD's sysutils/rpi-firmware port shows 1.20190925.g20200109 in
its Makefile, which would match tag 1.20190925 . Since then there
has also been more tags added as things were updated:

1.202000114
1.202000205
1.202000210
1.202000212

The master branch is even more updated than those.

It is not necessarily obvious that the sysutils/u-boot-rpi[34]
ports or the FreeBSD kernel would be well matched to the more
recent https://github.com/raspberrypi/firmware/ materials.


>> 4. cp config_rpi4.txt config.txt
> 
> don`t do:  'mv config_rpi4.txt config.txt‘ , leave all as it is ……

# diff -u /mnt/config.txt /mnt/config_rpi4.txt
--- /mnt/config.txt     2020-05-27 22:07:36.000000000 -0700
+++ /mnt/config_rpi4.txt        2020-05-27 22:07:36.000000000 -0700
@@ -1,7 +1,7 @@
 arm_control=0x200
-dtparam=audio=on,i2c_arm=on,spi=on
-dtoverlay=mmc
-dtoverlay=pwm
+arm_64bit=1
 dtoverlay=disable-bt
+dtoverlay=mmc
 device_tree_address=0x4000
 kernel=u-boot.bin
+armstub=armstub8-gic.bin

(Note the different/special armstub for an RPi4.)

Looking at my builds of u-boot.bin for the rpi3 and rpi4:

# ls -ldT /usr/local/share/u-boot/u-boot-rpi[34]/u-boot.bin
-rw-r--r--  1 root  wheel  499824 Apr 25 00:16:54 2020 /usr/local/share/u-boot/u-boot-rpi3/u-boot.bin
-rw-r--r--  1 root  wheel  506360 Apr 25 13:28:34 2020 /usr/local/share/u-boot/u-boot-rpi4/u-boot.bin

they are not even the same size.

It does not appear that testing a rpi3 based configuration is
the same as testing a rpi4 based configuration, even if the rpi4
could run the rpi3 configuration without problems.


> if you’re interested in testing pcie/USB on the 8GB-model just reply here and you will get answer from 
> the author of the pcie-driver(R. Crowston), thanks in advance for testing  his driver  ;-)

I've no clue what configuration(s) R. Crowston is targeting
or testing.

>> 5. cp /usr/local/share/u-boot/u-boot-rpi4/u-boot.bin .
>> 
>> I try to boot from SD card.
>> But u-boot not booting, I can see a color test patter at booting rpi4.
>> 
>> It seems me to update u-boot-rpi4.
>> 





===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)