IPQ9574 SFP port how to use wifi7

horasjey · January 16, 2025, 7:41am

Hallo,
i have device wifi7 800be Celling, and have port ETH and SFP,

i have problem , how to use port SFP ?

in my log dmsg

~ # dmesg |grep sfp
[   14.421627] of_get_named_gpiod_flags: can't parse 'sfp_rx_los_pin' property of node '/soc/ess-instance/ess-switch@3a000000/qcom,port_phyinfo/port@4[0]'[   14.421631] of_get_named_gpiod_flags: can't parse 'sfp_tx_dis_pin' property of node '/soc/ess-instance/ess-switch@3a000000/qcom,port_phyinfo/port@4[0]'[   14.421634] of_get_named_gpiod_flags: can't parse 'sfp_mod_present_pin' property of node '/soc/ess-instance/ess-switch@3a000000/qcom,port_phyinfo/port@4[0]'
[   14.421638] of_get_named_gpiod_flags: can't parse 'sfp_medium_pin' property of node '/soc/ess-instance/ess-switch@3a000000/qcom,port_phyinfo/port@4[0]'[   14.427803] sfp_phy_init[412]:INFO:qca probe sfp phy driver succeeded!
~ #

and why in ip -a dont have interface SFP?

~ # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 92:6d:cd:fa:d2:46 brd ff:ff:ff:ff:ff:ff
3: miireg: <> mtu 0 qdisc noop state DOWN group default qlen 1000
    link/netrom
4: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-lan state UP group default qlen 1000
    link/ether 00:01:23:20:14:b0 brd ff:ff:ff:ff:ff:ff
5: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-lan state DOWN group default qlen 1000
    link/ether 00:01:23:20:14:b1 brd ff:ff:ff:ff:ff:ff
6: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:01:23:20:14:b2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.2/24 brd 192.168.11.255 scope global eth2
       valid_lft forever preferred_lft forever
    inet6 fe80::201:23ff:fe20:14b2/64 scope link
       valid_lft forever preferred_lft forever
7: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1000
    link/tunnel6 :: brd ::
8: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
9: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1000
    link/gre 0.0.0.0 brd 0.0.0.0
10: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
11: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
12: ip6gre0@NONE: <NOARP> mtu 1448 qdisc noop state DOWN group default qlen 1000
    link/gre6 :: brd ::
13: teql0: <NOARP> mtu 1500 qdisc noop state DOWN group default qlen 100
    link/void
14: br-lan: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 00:01:23:20:14:b0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.12.1/24 brd 192.168.12.255 scope global br-lan
       valid_lft forever preferred_lft forever
    inet6 fda9:f6f8:53c1::1/60 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::201:23ff:fe20:14b0/64 scope link
       valid_lft forever preferred_lft forever
15: wifi0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 2699
    link/ieee802.11 00:01:23:20:14:b3 brd ff:ff:ff:ff:ff:ff
16: soc0: <> mtu 0 qdisc noop state DOWN group default qlen 1000
    link/ieee802.11
17: mld-wifi0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
18: wifi1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 2699
    link/ieee802.11 00:01:23:20:14:b4 brd ff:ff:ff:ff:ff:ff
19: wifi2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 2699
    link/ieee802.11 00:01:23:20:14:b5 brd ff:ff:ff:ff:ff:ff
20: soc1: <> mtu 0 qdisc noop state DOWN group default qlen 1000
    link/ieee802.11
21: mld0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue master br-lan state DOWN group default qlen 1000
    link/ether 3a:83:67:1b:b7:9e brd ff:ff:ff:ff:ff:ff
22: ath2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 00:01:23:20:14:b5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.2/24 brd 192.168.1.255 scope global ath2
       valid_lft forever preferred_lft forever
    inet6 fe80::201:23ff:fe20:14b5/64 scope link
       valid_lft forever preferred_lft forever

please anyone , how to use port sfp in my device, i use SFP bidi and led on in my device

img my device led

brada4 · January 16, 2025, 7:50am

What is shown in

ubus call system board

horasjey · January 16, 2025, 8:49am

hi @brada4 ,
this result for command

~ # ubus call system board
{
        "kernel": "5.4.213",
        "hostname": "OpenWrt",
        "system": "ARMv7 Processor rev 0 (v7l)",
        "model": "Qualcomm Technologies, Inc. IPQ9574/AP-AL02-C6",
        "board_name": "qcom,ipq9574-ap-al02-c6",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "23.05-SNAPSHOT",
                "revision": "r0+24213-a132865f62cc",
                "target": "ipq95xx/ipq95xx_32",
                "description": "OpenWrt 23.05-SNAPSHOT r0+24213-a132865f62cc"        }
}
~ #

frollic · January 16, 2025, 8:56am

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

horasjey · January 16, 2025, 9:57am

From the results of the Ubus call system board, is this really my device's firmware?
https://firmware-selector.openwrt.org/?version=SNAPSHOT&target=armsr%2Farmv7&id=generic

frollic · January 16, 2025, 10:38am

I wouldn't try to find out, by flashing it ...

You're running a vendor SDK.

Read about ipq95xx in Can Xiaomi Router BE3600 (RD16) be supported? This version seems to have 512MB of memory - #3 by slh

horasjey · January 16, 2025, 10:44am

hmmmmmmmmmmmmmmmmmmm

brada4 · January 16, 2025, 10:46am

If you have two devices and plenty of time you can try porting real OpenWRT, ath12k and wifi7 is a very unexplored territory and probably will turn into lot of time consumed.

system · March 20, 2025, 6:56am

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