Hi all,
After having done prototyping on both BeaglePlay and the TI AM62-LP EVM, we now have our custom board running. U-boot 2023.04, yocto scarthgap, recipe u-boot-ti-staging. It boots up with the default dtb as used on the EVM k3-am62-lp-sk.dtb (or at least that is the one I expect it uses). The conf file is am62x_lpsk_a53_defconfig.
We have two ethernet ports, and we use the clock design as it is on the BeaglePlay board. So, I have taken mainly the clock details from the beagleplay dts and added it to k3-am62x-sk-common.dtsi. I thought that would be it, the dtb is correctly compiled, but no matter what i do, when u-boot starts up, in only looks for one ethernet port (should look for two), and it fails as there is no phy clock configured!
I get this error:
Net: Could not get PHY for ethernet@8000000port@1: addr 0
am65_cpsw_nuss_port ethernet@8000000port@1: phy_connect() failed
No ethernet found.
The .config:
CONFIG_DEFAULT_DEVICE_TREE=“k3-am62-lp-sk”
CONFIG_OF_LIST=“k3-am62-lp-sk”
CONFIG_SPL_OF_LIST=“k3-am62-lp-sk”
Yet, “mkimage -l u-boot.img” indicates another fdt being used?
Image 1 (fdt-0)
Description: k3-am625-sk
Created: Tue Mar 19 21:31:40 2024
Another image is also produced during build, it seems to include my desired dtb. But it still does not get the phy probed.
“mkimage -l u-image-dtb.img”:
Image 1 (fdt-1)
Description: k3-am62-lp-sk
So I am quite confused, as to what dtb is u-boot using during load? and where can i make my customizations for them to take effect?
Help is greatly appreciated!
Thanks,
Lars