[url]U-Boot Customization https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%2520Linux%2520Driver%2520Package%2520Development%2520Guide%2Fuboot_guide.html%23[/url]
is this online U-Boot document fit for xavier?
Applies to: NVIDIA® Jetson Nano™, NVIDIA® Jetson™ TX2, and NVIDIA® Jetson™ TX2i devices.
U-Boot is the default bootloader for NVIDIA® Tegra® Linux Driver Package (L4T) on Jetson Nano, Jetson TX2, and Jetson TX2i devices.
There is no u-boot on xavier release anymore. why do you need it?
use u-boot “mii” and “mdio” tools to debug PHY chip on our xavier custom board.
then CBoot has tools like that?
and more: where can i get CBoot source code?
Please download source from here.
Why do you need to debug PHY chip in bootloader? I was thinking that this can be done in kernel too.
Sorry in advance for this question. I am not actively working on porting PHY.
OK, thanks for CBoot Source code.
PHY debug tools in kernel, like mdio-tool, mii-tool, phytool, are based on socket “eth0”, but in my system, only “ifconfig -a” can show the “eth0” device.
and operations on “eth0”, it will be in errors:
xavier@EAXV100:~$ sudo /sbin/ifconfig eth0 up
[sudo] password for xavier:
[ 9632.855260] -->eqos_init_phy
[ 9632.855364] eth0: Could not attach to PHY
[ 9632.855468] net eth0: eqos_open: Cannot attach to PHY (error: -19)
SIOCSIFFLAGS: No such device
xavier@EAXV100:~/mdio-tools$ sudo sudo ./mdio-tool r eth0 2
SIOCGMIIPHY on ‘eth0’ failed: Invalid argument
Would you mind looking into kernel:
/kernel/nvidia/drivers/net/ethernet/nvidia/eqos/mdio.c#424
and see which line is causing this error?
Does your design work with eqos controller now?