RPi4B: modern firmware vs. Device tree loaded to 0x4000 (size 0xbe0c) [fails] vs. to 0x1f0000 (size 0xbd90) [works]?

Mark Millard marklmi at yahoo.com
Sun Oct 11 20:21:19 UTC 2020


On 2020-Oct-11, at 12:46, Klaus Cucinauomo <maciphone2 at googlemail.com> wrote:

> Am 11.10.2020 um 21:37 schrieb Mark Millard <marklmi at yahoo.com>:
>> 
>> MESS:00:00:20.241899:0: brfs: File read: /mfs/sd/armstub8-gic.bin
>> MESS:00:00:20.244930:0: Loading 'armstub8-gic.bin' to 0x0 size 0x1700
> 
> 
> You have to DELETE the armstub from the MSDOS-partition,
> it loads automatically if available.

What I was replying to had nothing to do with investigations of
deleting or otherwise avoiding armstub8-gic.bin .

It was about why something like "device_tree_address=0x4000" is
needed when something like armstub8-gic.bin is in use.

I'm not currently working on your direction of avoiding
armstub8-gic.bin .

By the way, the naming conventions involved in finding armstub*.bin's
allow the file to be renamed in order to not be found, instead of
having to delete the file.


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



More information about the freebsd-arm mailing list