Jetson Orin CVB - Connecting MGBE Soc Line to a Switch

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
, , ,
1

Hi,

On my CVB, we have a Switch that is connected via XFI to the SoC MGBE.
Switch: 88E6393XA0-BXB2I000 (PORT9 at the switch)

I follow the guide “Jetson AGX Orin Platform Adaptation and Bring-Up”

JetPack 6 (36.4.4)

and set update the DT:

&mgbe0 {
    status = "okay";

    nvidia,mac-addr-idx = <0>;
    nvidia,max-platform-mtu = <16383>;
    nvidia,pause_frames = <1>;

    /* 10G, XFI mode */
    nvidia,uphy-gbe-mode = <1>;       /* 1 = 10G */
    nvidia,phy-iface-mode = <0>;      /* 0 = XFI/10GBASE-R (per NVIDIA docs) */
	
	/* No direct PHY on a MAC<->switch link */
	/delete-property/ phy-handle;
	/delete-property/ nvidia,mdio_addr;
	/delete-property/ nvidia,phy-reset-gpio;
    phy-mode = "xfi";
    fixed-link {
            speed = <10000>;
            full-duplex;

    };
};

What am I missing here?
The switch is configured via HW to use the mode XFI at PORT9

Jetson Switch
Jetson Switch431×261 8.36 KB

[ 21.150837] nvethernet 6800000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS
[ 22.180684] nvethernet 6800000.ethernet: [xpcs_lane_bring_up][470][type:0x4][loga-0x0] Failed to get PCS block lock
[ 23.198835] nvethernet 6800000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS
[ 24.222836] nvethernet 6800000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS
[ 25.248817] nvethernet 6800000.ethernet: [xpcs_lane_bring_up][470][type:0x4][loga-0x0] Failed to get PCS block lock
[ 26.270838] nvethernet 6800000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS
[ 27.295063] nvethernet 6800000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS
[ 28.318841] nvethernet 6800000.ethernet: [xpcs_lane_bring_up][477][type:0x4][loga-0x0] PCS block lock SUCCESS

Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: Not reported
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Auto-negotiation: on
Port: MII
PHYAD: 0
Transceiver: external
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000000 (0)

Link detected: no

dmesg_log.txt (57.8 KB)

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided information, it appears that you are trying to configure a Switch connected via XFI to the SoC MGBE Switch 88E6393XA0BXB2I000 PORT9 on a Jetson AGX Orin platform. You have followed the guide “Jetson AGX Orin Platform Adaptation and BringUp JetPack 6.3.1” and updated the Device Tree (DT). However, you are still experiencing issues with the Switch configuration.

From the provided logs, it seems that there are some errors related to the PCS block lock, which might be causing the issue. Here are some potential steps to troubleshoot and resolve the issue:

  1. Verify the Switch configuration: Double-check that the Switch is configured correctly to use the XFI mode at PORT9. Ensure that the HW configuration is set correctly, and the Switch is not configured to use a different mode.
  2. Check the Device Tree configuration: Verify that the Device Tree configuration is correct and matches the Switch configuration. Ensure that the nvethernet node is configured correctly, and the xpcslanebringup property is set to the correct value (0x4).
  3. Check the kernel logs: Analyze the kernel logs to see if there are any other errors or warnings related to the Switch configuration. You can use the dmesg command to view the kernel logs.
  4. Verify the PHY configuration: Ensure that the PHY (Physical Layer) configuration is correct. You can use the ethtool command to verify the PHY configuration.
  5. Try a different port: If possible, try using a different port on the Switch to see if the issue is specific to PORT9.

In terms of comparing the configuration to other Jetson platforms, the Jetson AGX Orin platform has a different Switch configuration compared to other Jetson platforms. The Jetson AGX Orin platform uses a Marvell 88E6393XA0BXB2I000 Switch, which has a different configuration compared to other Switches used on other Jetson platforms.

Here is a comparison of the Switch configuration on different Jetson platforms:

  • Jetson AGX Orin: Marvell 88E6393XA0BXB2I000 Switch
  • Jetson Xavier NX: Marvell 88E6390XA0BXB2I000 Switch
  • Jetson AGX Xavier: Marvell 88E6390XA0BXB2I000 Switch

The Switch configuration on the Jetson AGX Orin platform is different from other Jetson platforms, so it’s essential to ensure that the configuration is correct and matches the Switch configuration.

In summary, to resolve the issue, you should verify the Switch configuration, check the Device Tree configuration, analyze the kernel logs, verify the PHY configuration, and try a different port if possible. Additionally, ensure that the configuration is correct and matches the Switch configuration on the Jetson AGX Orin platform.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

5

Sorry for the late response.
Is this still an issue to support? Any result can be shared?