I have a custom carrier board flashed with Jetpack 6.2 and the default rootfs. I customized the kernel and device tree. When I boot I get the following message: Error: Could not detect network connection.
The system boots successfully but I am wondering why there is an error shown in uefi. In the system are two ethernet ports one is connected like on the devkit.
The other is connected through pcie (lan743x). I did not make any device tree changes.
the pcie ethernet appears in nmcli but when I connect a cable nothing happens
when I do not set a default user with the l4t_create_default_user.sh script and flash the device it always wants to start a ipv6 boot even though I adapted the boot order which does not include ipv6/ipv4 boot
Do I need to add/change something in uefi for it to work correctly?
disable the lan743x driver with modprobe → the system freezes
blacklist the lan743x driver → this works. Now the reboot and shutdown issues disappear. Previously when we tried to shutdown it was stuck forever
Now I am not exactly sure how I should proceed. Is it a driver an uefi or an device tree issue?
It is an pcie device therefore it should not be a device tree issue.
For uefi the problem still remains that it tries to do an ip boot even though I customized the boot order where ip boot is not listed.
I found another potential solution. The Microchip Lan7430 is PCIEx1. On our board it is connected on pcie2 (PCIe x1 (C7)). The default devkit configuration is PCIEx2 which is gbe-uphy-config-8 (see here).
Therefore we need to add to our flash config:
ODMDATA+=",gbe-uphy-config-9";
Do I need to do these changes too? Or has this changed inbetween?
Does PCIe x1 (C9) need to be disabled? We do not use it.
Yes, you have to correct the PCIe configuration before porting ethernet controller.
Both gbe-uphy-config-8 and gbe-uphy-config-9 should work for your case since you use only PCIe x1(C7). PCIe x2 (C7) would be compatible with your PCIe x1 (C7). And it should be fine if PCIe x1 (C9) not used in your case.
Do you have some suggestions which pcie settings might need to be changed? I am going to check with the hardware guys that everything is working as it should.
I also reached out to microchip. Maybe it is only a driver issue.
I noticed that the Error: Could not detect network connection happens when I connect an usb to ethernet adapter. When I connect a ethernet cable it tries to start an IPv6 boot which it should not. I think I got that wrong when I first posted this question. I though the error came from the LAN Ports which are on the carrier board.
The ethernet adapter is a rtl8153a:
[ +0.146862] usbcore: registered new device driver r8152-cfgselector
[ +0.085519] r8152-cfgselector 1-3.1: reset high-speed USB device number 8 using tegra-xusb
[ +0.261178] r8152 1-3.1:1.0: load rtl8153a-4 v2 02/07/20 successfully
[ +0.074579] r8152 1-3.1:1.0 eth0: v1.12.13
[ +0.000127] usbcore: registered new interface driver r8152
[ +0.008664] usbcore: registered new interface driver cdc_ether
+ # CONFIG_NETWORKING is not set
+ # CONFIG_NETWORKING_IPV4 is not set
+ # CONFIG_NETWORKING_IPV6 is not set
- CONFIG_NETWORKING_DEVICE_NVIDIA=y
+ # CONFIG_NETWORKING_DEVICE_NVIDIA is not set
- CONFIG_NETWORKING_DEVICE_ASIX=y
+ # CONFIG_NETWORKING_DEVICE_ASIX is not set
- CONFIG_NETWORKING_DEVICE_REALTEK=y
+ # CONFIG_NETWORKING_DEVICE_REALTEK is not set
I changed the parameters and followed the instructions and build it successfully. I used edk2_docker edkrepo clone nvidia-uefi NVIDIA-Platforms r36.4.3-updates.
The only change I made is in the build command. I used edk2_docker edk2-nvidia/Platform/NVIDIA/Jetson/build.sh --init-defconfig edk2-nvidia/Platform/NVIDIA/Tegra/DefConfigs/t23x_general.defconfig.
What do I need to do now?
Do I only need to replace Linux_for_Tegra/bootloader/uefi_jetson.bin with nvidia-uefi/images/uefi_Jetson_RELEASE.bin?
