Re: clock problems with BeagleBone Black on 12.2BETA2

On Thu, 24 Sep 2020 at 12:31, Ian Lepore <[email protected]> wrote:
>
> It was mentioned on irc a few days ago when someone noticed the BBB in
> the CI setup was failing...
>
> <emaste> hrm, looks like BBB has been broken since end of July
> <emaste> panic: Duplicated clock registration: clk@4_0
> <emaste> ah, mmel r363700
> <strejda> emaste: im sorry, but this is (unfortunately) expected
> collateral damage. im aware of this problem but right solution is not
> trivial and it needs more time.
>
> (strejda == mmel@)
>
> Then it was mentioned a while later that that BBB is using a very old
> u-boot, so maybe that has something to do with it.

I've updated uboot on eMMC on the the CI system's BBB to:
U-Boot SPL 2020.07 (Sep 24 2020 - 04:58:48 +0000)^M

however it's still failing the same way:

clk_fixed7: <Fixed factor clock> on ofw_clkbus0^M
clk_fixed7: Cannot FDT parameters.^M
device_attach: clk_fixed7 attach returned 6^M
clk_fixed7: <Fixed factor clock> on ofw_clkbus0^M
clk_fixed7: Cannot FDT parameters.^M
device_attach: clk_fixed7 attach returned 6^M
ti_clkctrl0: <TI clkctrl> mem 0x14-0x14f on ti_omap4_cm0^M
ti_clkctrl1: <TI clkctrl> mem 0x4-0xd7 on ti_omap4_cm1^M
ti_clkctrl2: <TI clkctrl> mem 0x4-0x7 on ti_omap4_cm2^M
panic: Duplicated clock registration: clk@4_0^M
^M
cpuid = 0^M
time = 1^M

phk@ reported success booting 13-CURRENT snapshots though, so I'm not
really sure what's going on.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[email protected]"