Other Parts Discussed in Thread: AM69
Tool/software:
Hello,
this is how our uEnv.txt looks like.
root@j784s4-evm:/run/media/BOOT-mmcblk1p1# cat uEnv.txt
# This uEnv.txt file can contain additional environment settings that you
# want to set in U-Boot at boot time. This can be simple variables such
# as the serverip or custom variables. The format of this file is:
# variable=value
# NOTE: This file will be evaluated after the bootcmd is run and the
# bootcmd must be set to load this file if it exists (this is the
# default on all newer U-Boot images. This also means that some
# variables such as bootdelay cannot be changed by this file since
# it is not evaluated until the bootcmd is run.
psdk_setup_file=.psdk_setup
check_psdk_setup=load mmc 1:1 ${loadaddr} ${psdk_setup_file}
# Reset to the default environment
do_psdk_setup=env default -f -a; saveenv
# Update the Linux hostname based on board_name
# The SK also requires an additional dtbo to boot. Prepend it to name_overlays depending on board_name
uenvcmd=if test ${boot_fit} -eq 1; then setenv name_overlays $name_overlays_fit; fi; if test "$board_name" = "am69-sk"; then ; setenv args_all $args_all systemd.hostname=am69a-sk ; if test ${boot_fit} -eq 1; then setenv name_overlays ti/k3-am69-sk-ddr-mem-carveout.dtbo $name_overlays; else; setenv name_overlays k3-am69-sk-ddr-mem-carveout.dtbo $name_overlays ; fi; fi
# Setting the right U-Boot environment variables
dorprocboot=1
name_overlays=k3-j784s4-evm-virt-mac-client.dtbo k3-j784s4-vision-apps.dtbo k3-j784s4-edgeai-apps.dtbo
As soon as I add k3-am69-sk-fpdlink-fusion.dtbo or k3-fpdlink-imx390-rcm-0-0.dtbo
we see the following errors and the boot does not complete
ethernet@46000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@46000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@46000000port@1: am65_cpsw_start end error
Retrieving file: pxelinux.cfg/default-arm-k3
am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 2
ethernet@46000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@46000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@46000000port@1: am65_cpsw_start end error
Retrieving file: pxelinux.cfg/default-arm
am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 2
ethernet@46000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@46000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@46000000port@1: am65_cpsw_start end error
Retrieving file: pxelinux.cfg/default
am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 2
ethernet@46000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@46000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@46000000port@1: am65_cpsw_start end error
Config file not found
starting USB...
No working controllers found
am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 2
ethernet@46000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@46000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@46000000port@1: am65_cpsw_start end error
am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 2
ethernet@46000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@46000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@46000000port@1: am65_cpsw_start end error
This is the output of the mdio
=> mdio list
mdio@f00:
ethernet@46000000port@1:
0 - TI DP83867 <--> ethernet@46000000port@1
=> mdio read ethernet@46000000port@1 0x0
Reading from bus ethernet@46000000port@1
PHY at address 0:
0 - 0x1140
=> mdio read ethernet@46000000port@1 0x1
Reading from bus ethernet@46000000port@1
PHY at address 0:
1 - 0x7949
=> mdio read ethernet@46000000port@1 0x2
Reading from bus ethernet@46000000port@1
PHY at address 0:
2 - 0x2000
=>
Any ideas how to fox that? I assume the k3-am69-sk-fpdlink-fusion.dtbo file is not meant to be loaded on a j784s4 board?
