Hi there,
New issue during boot of a JAO64GB on a custom carrier board (JP6.2.2, L4T36.5, Ubuntu 22.04). I have enabled GBE in .common.conf, because we our carrier board does support MGBE and 10GBE, not sure if this could be the issue.
All camera pins arent connected currently.
Here’s the log:
dump (2).txt (75.4 KB)
FATAL ERROR [FILE=platform/drivers/uphy/uphy-tegra234-dt.c, ERR_UID=2203]: invalid gbe0-enable-10g
Error log is from this. Not sure what does that mean from your comment.
So do you have MGBE in use or not?
I meant what is the exact items you did here?
The current ODMDATA is: ODMDATA=“gbe-uphy-config-22,hsstp-lane-map-3,hsio-uphy-config-16,nvhs-uphy-config-0,gbe0-enable-10g”;
This is based on the following:
- we have 1 RGMI intended for 1GB Ethernet
- we have 1 UPHY intended for the 10GB Ethernet (separate from the 1GB)
im trying to follow the ethernet setup as per the L4T 36.5, but i cant find where to edit the files to make adjustmenets.
For instance:
“For RGMII
Prerequisites
Ensure that PHY comes out of reset mode and is in a ready state when the PHY reset GPIO is toggled.
-
The read PHY ID should use the mdio tool to ensure that PHY is out of the reset mode.
-
Ensure that the PHY driver is available.
-
Ensure that the PIN mux settings are correct in the RGMII interface.
-
Ensure that PHY comes out of reset and supplies the Rx clock to EQOS.
Here are the DT entries that are necessary to connect the 1G MAC to the third-party ethernet PHY:pinmux:
phy-mode = "rgmii-id";
phy-handle = <$phy>;
nvidia,phy-reset-gpio = <$tegra_main_gpio TEGRA234_MAIN_GPIO(G, 5) 0>
mdio {
compatible = "nvidia,eqos-mdio";
#address-cells = <1>;
#size-cells = <0>;
phy: phy@1 {
reg = <1>;
nvidia,phy-rst-pdelay-msec = <224>; /* msec */
nvidia,phy-rst-duration-usec = <10000>; /* usec */
interrupt-parent = <$tegra_main_gpio>;
interrupts = <TEGRA234_MAIN_GPIO(G, 4) IRQ_TYPE_LEVEL_LOW>;
};
};
I have not a single clue where this file is. Ive checked the pinmix.dts files, and nothing. Tried to do a grep search, it turned up compiled files. They havent given any file names that ive seen.
The MGBE and RGMII are separate items.
The boot error happened here has nothing to do with RGMII but only with MGBE.
My question here is what did you do here to trigger this error in boot?
I meant you didn’t have this error in previous post boot log. Now it comes up. What configuration did you do to trigger this?
The reason im trying to setup both etherenets is so i can fully configure both, and then start chasing errors. Otherwise im just wasting time configuring based on errors.
The change I made was to enable the 10gb ethernet in the .conf file as part of ODMDATA
So previously you didn’t enable gbe-uphy-config-22 and gbe0-enable-10g in the config? I meant the situation that you were even able to flash and boot yesterday.