Using the Turris RTROM01-RTSF-10G SFP with Turris Omnia

Omnia hardware Omnia HW help
1

Dear Members,

I recently bought a Turris RTROM01-RTSF-10G type SFP for use with my Turris Omnia, because I read that it was supported out of the box on my Omnia.
I currently have TurrisOS 5.3.10 installed.

When I plug the SFP into the slot and unplug the Ethernet cable from the WAN port and plug it into the SFP (the device on the other side is 1G capable currently), and reboot Omnia, ethtool will say that there is no link on eth2 and that the port type is still MII.
Then if I unplug the Ethernet cable from the SFP, and put it back to WAN, then ethtool will report a link on eth2, but I can’t get an address over DHCP as long as the SFP is in its slot.
Is there perhaps something I need to do in order to activate the SFP properly? I read that it’s supposed to work out of the box and that only a reboot is necessary. Well I did reboot the Omnia several times, but no luck.
I also tried modifying the port type of eth2 to TP with ethtool, but it doesn’t seem to do anything. It doesn’t return an error, but nothing happens.
Is there any log message that I should look for in dmesg? Btw. I did not find any message saying anything about the SFP being plugged in.

I would appreciate any suggestions in order to make the SFP work properly.

2

Autodetection of SFP in U-Boot currently doesnt work. You have to link /boot/dbt to the correct file in /boot. If you show ls /boot I will tell you the exact command

3

root@router:~# ln -sf /boot/armada-385-turris-omnia-sfp.dtb /boot/dtb

After that and reboot your SFP should work

1 Like
4

There was a typo in your command (dtb instead of dbt). It should have been:

ln -sf /boot/armada-385-turris-omnia-sfp.dtb /boot/dtb

However even that doesn’t solve the problem by itself. After a reboot with the correct dtb I was greeted by this:

root@omnia:~# ethtool eth2
Settings for eth2:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: no
root@omnia:~# dmesg | fgrep -i eth2
[    4.467538] mvneta f1034000.ethernet eth2: Using hardware mac address d8:58:d7:00:3e:6e
[   19.836832] mvneta f1034000.ethernet eth2: configuring for inband/sgmii link mode
[   51.723326] mvneta f1034000.ethernet eth2: PHY [i2c:sfp:16] driver [mv88x3310]
root@omnia:~# dmesg | fgrep -i sfp
[   13.909149] sfp sfp: module Turris           RTSFP-10G        rev A    sn 2109150017       dc 15-09-21
[   13.918516] sfp sfp:   unknown connector, encoding 64b66b, nominal bitrate 10.3Gbps +0% -0%
[   13.926914] sfp sfp:   1000BaseSX- 1000BaseLX- 1000BaseCX- 1000BaseT- 100BaseTLX- 1000BaseFX- BaseBX10- BasePX-
[   13.937046] sfp sfp:   10GBaseSR+ 10GBaseLR- 10GBaseLRM- 10GBaseER-
[   13.943350] sfp sfp:   Copper length: unsupported/unspecified
[   13.949121] sfp sfp:   Options: txdisable, txfault, los+
[   13.954462] sfp sfp:   Diagnostics: ddm, intcal, rxpwravg
[   51.712236] mv88x3310 i2c:sfp:16: PHY supports (18000,000070ea) more modes than phylib supports, some modes not supported.
[   51.723326] mvneta f1034000.ethernet eth2: PHY [i2c:sfp:16] driver [mv88x3310]
root@omnia:~# ethtool -s eth2 port tp
root@omnia:~# ethtool eth2
Settings for eth2:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Full 
                                100baseT/Full 
                                1000baseT/Full 
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Full 
                                100baseT/Full 
                                1000baseT/Full 
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: Unknown!
        Duplex: Unknown! (255)
        Port: MII
        PHYAD: 22
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes
root@omnia:~# ls -l /boot
-rw-r--r--    1 root     root         18834 May 25 21:00 armada-385-turris-omnia-phy.dtb
-rw-r--r--    1 root     root         18870 May 25 21:00 armada-385-turris-omnia-sfp.dtb
-rw-r--r--    1 root     root          1199 Dec 10  2021 boot.scr
lrwxrwxrwx    1 root     root            37 Jul 10 20:29 dtb -> /boot/armada-385-turris-omnia-sfp.dtb
-rwxr-xr-x    1 root     root       3379416 May 25 21:00 zImage
root@omnia:~#
1 Like
5

I have to correct myself.
A reboot is enough. It just needs some more time (~60 seconds) for the link to come up.
No need for the ethtool -s eth2 port tp command.

1 Like
6

And it seems I almost forgot the most important part: Thank you for your help!

1 Like
7

Update your u-boot forever!

8

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.