AM69 USXGMII Configuration

Hello Support Team,

I’m working on configuring my Aquila AM69 to support 2x 10Gb interfaces using SFP+ connections. I’ve configured serdes2 lane 2 and 3 for USXGMII operation and tried to setup the appropriate nodes in the device tree for the SFP connections.

In the boot log I see this error, though I’m not sure what mode to use instead: [ 4.418906] phy-gmii-sel 104044.phy: port2: unsupported mode: “10gbase-r”

I am building my image using Yocto 7.5.0.

I have attached my device tree file. Any help would be appreciated. Thanks!

device_tree.dts (32.5 KB)

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.


I’d be glad to help with your USXGMII configuration! To provide the most accurate guidance for your Aquila AM69 setup, could you let me know which OS and version you are running on the device?(1)

You mentioned you’re building with Yocto 7.5.0, but I’d like to confirm the specific Torizon OS version or BSP version you’re targeting. You can use the tdx-info command on your device to get detailed information about your current setup - see the tdx-info documentation for more details.(1)

Common platforms to clarify:

  • Hardware: Aquila AM69, Verdin i.MX8M Plus, Verdin AM62, Apalis i.MX8QP, Colibri i.MX8X
  • OS: Torizon OS 6, Torizon OS 7.2.0-build.13, BSP 7, BSP 6, Yocto 7.2.0
  • Integration: Device tree overlays, ethernet configuration, serdes configuration

The error you’re seeing with “unsupported mode: ‘10gbase-r’” suggests there may be a configuration mismatch in your device tree setup. Once I know your exact platform details, I can provide specific guidance for configuring the USXGMII interfaces and SFP+ connections properly.(1)(2)

Best regards, Toradex AI Assistant.


Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

@ToradexAI Here is the output of tdx-info

root@aquila-am69-12594727:~# tdx-info

Software summary

Bootloader:               U-Boot
Kernel version:           6.6.119-7.5.0-devel #1 SMP PREEMPT Fri Dec 12 14:50:07 UTC 2025
Kernel command line:      root=PARTUUID=2e9ce3b5-02 ro rootwait console=tty1 console=ttyS2,115200
Distro name:              NAME=“TDX Wayland with XWayland”
Distro version:           VERSION_ID=7.5.0-devel-20260409180022-build.0
Distro variant:           -
Hostname:                 aquila-am69-12594727

Hardware info

HW model:                 Toradex Aquila AM69 on SLAC TILES V3 Carrier R0 Board
Toradex version:          0211 V1.1A
Serial number:            12594727
Processor arch:           aarch64

root@aquila-am69-12594727:~#

Thank you for providing the tdx-info output! I can see you’re running BSP 7.5.0-devel on an Aquila AM69 with kernel 6.6.119 (1).

For USXGMII configuration on the Aquila AM69, I can see from the available documentation that the Aquila AM69 is supported in BSP 7.x with various overlays (2). However, the specific USXGMII/10GbE configuration details you need aren’t fully covered in the available documentation sources.

Key Points for Your Configuration:

The error phy-gmii-sel 104044.phy: port2: unsupported mode: "10gbase-r" suggests that the phy-gmii-sel driver doesn’t recognize the “10gbase-r” mode for that particular port configuration.

Available Resources:

Based on the documentation, the Aquila AM69 supports various overlays including SPI and camera configurations (2), but I don’t have specific guidance for USXGMII/10GbE ethernet configuration in the available sources.

Recommendation:

For this specific USXGMII configuration issue, I’d recommend checking these potentially useful sources:

Would you like me to try to provide a general answer based on my knowledge instead? The specific USXGMII configuration for dual 10Gb interfaces on the Aquila AM69 may require consulting the TI documentation or working with Toradex support for platform-specific guidance.

Best regards, Toradex AI Assistant.


Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

@ToradexAI I resolved the previous error message by changing 10gbase-r to usxgmii, which seems appropriate here.

However, neither of my two SFP connections are recognized. I don’t see any relevant errors in the boot log. How can I troubleshoot this further?

Good progress on resolving the 10gbase-r to usxgmii mode issue! For troubleshooting SFP connections that aren’t being recognized, here are several steps you can take:

Network Interface Verification

First, check if the network interfaces are being created:

ip link show

Look for interfaces that correspond to your USXGMII configuration (typically named like eth2, eth3, or similar).

Device Tree and GPIO Status

Verify your SFP GPIO configurations are working:

# Check if SFP detect/present GPIOs are configured correctly
cat /sys/kernel/debug/gpio
# Look for your SFP detect pins and their current state

Module Detection

Check if the SFP modules are being detected at the hardware level:

# Check for any SFP-related messages
dmesg | grep -i sfp
dmesg | grep -i phy
dmesg | grep -i ethernet

# Check network interface statistics
cat /proc/net/dev

I2C Communication

If your SFPs use I2C for module identification, verify I2C communication:

# List I2C buses
i2cdetect -l

# Scan for devices on relevant I2C buses (replace X with bus number)
i2cdetect -y X

SerDes and PHY Status

Check if the SerDes lanes are properly configured:

# Look for SerDes-related messages in boot log
dmesg | grep -i serdes
dmesg | grep -i lane

# Check if PHY devices are detected
ls /sys/class/net/

Manual Interface Bring-up

Try manually bringing up the interfaces:

# Replace ethX with your actual interface names
ip link set ethX up
ethtool ethX  # Check link status and supported modes

Device Tree Verification

Ensure your device tree has proper SFP node configuration with:

  • Correct GPIO specifications for detect/LOS/tx-disable pins
  • Proper I2C bus references for module identification
  • SerDes lane assignments matching your hardware

Since you’re working with a custom carrier board configuration, double-check that your hardware connections match your device tree GPIO assignments and that the SFP+ modules are properly seated and compatible.

Best regards, Toradex AI Assistant.


Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

This request was closed and merged into request #65157 “Configuring USXGMII and SGMII in…”.