Re: BeagleBone Black does not boot -current (DTB incompatibility?)

Mark Millard <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On Jan 9, 2023, at 08:49, Mike Karels <[email protected]> wrote:

> The last couple of snapshots of -current fail to boot on BeagleBone
> Black (armv7 GENERICSD).  I have no idea how long this has been failing.
> (13.1 runs.)
> 
> It appears that a malloc from ti_sysc_attach or ti_sysc_attach_clocks
> is passing a size of 0, which maybe could happen if the FDT has a "clocks"
> node but no clocks are found.  The console output including backtrace is
> below.
> 
> I replaced the dtb directory with the one from 13.1, and the system boots
> and seems to run.  I don't know my way around the armv7 DTS files, but
> I'm happy to investigate if someone can point me in the right direction.
> 
> Mike
> 
> ...
> . . .
> 

I mounted based on:

FreeBSD-13.1-STABLE-arm-armv7-GENERICSD-20230107-1149f0ec2b18-253362.img

doing:

# mount -onoatime -tmsdosfs /dev/da0s1 /mnt
# dtc -o am335x-boneblack-13.1.dts -O dts -I dtb -s /mnt/dtb/am335x-boneblack.dtb

to generate a sorted, overall .dts source.

I then dismounted and did similarly for based on:

FreeBSD-14.0-CURRENT-arm-armv7-GENERICSD-20230107-11b5b9e8a520-259967.img

generating a sorted, overall .dts source via:

# dtc -o am335x-boneblack-main.dts -O dts -I dtb -s /mnt/dtb/am335x-boneblack.dtb

(The -s sorts for making the source produced more useful for
diff activity.)

Then:

# diff -u am335x-boneblack-*.dts | more

but the diff was rather large. So:

# diff -u am335x-boneblack-*.dts | grep "^-" | wc
     933    4250   36379

# diff -u am335x-boneblack-*.dts | grep "^+" | wc
    1318    5774   50377

13.1 (and stable/13) are back at something like linux 5.9 
for .dt* source but main [so: 14] is at linux 6.0 now, the
11th import after 13.1 if I counted right.

===
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.