Hello, i just bought a BPI-R3, and discovered that my MA5671 doesn’t work in SFP1 or SFP2. While it works in a Mikrotik RB4011. My MA5671 was flashed with a modded firmware in order to work with my ISP. Some people reported the MA5671 works with original firmware and rooted.
Can you please report here what brand/model or firmware hack you are successfuly using in the BPI-R3 Please ?
Hy. I have the fs sfp gpon onu. It works very well (2.5gbps down for 800 UP).
https://www.fs.com/fr/products/133619.html
You Can change serial number and/or the slid.
Thanks for your feedback !
@frank-w when i boot with my SFP ONT in the cage i have this error :
once i remove and reinsert the SFP ONT, looks like it is finaly recognized
but there is still a problem as it says “persistent fault”
sorry if i copy/paste the logs all the text go in line, i can’t figure out how to fix this with this forum ?!
i have this probem with a Alcatel G-010S-P
with GPON-ONU i guess you need the 3W setting i posted to ML and daniel has in his tree…default is 1W as you see in your logs
i only have 2 different SFP…one fibre and one copper…no gpon, so i can only guess
i installed the debian image, the one in the wiki, and the sfp ont is working here ! I succeded to compile an image from @dangowrt tree, with all the latest patch, but the SFP ONT is still not working… i’d like to use Openwrt not debian…
could you share your bootlog from latest openwrt?
that’s all i have…since i’m with debian now…
root@OpenWrt:/# logread | grep 'sfp'
Sat Aug 26 06:56:05 2023 kern.info kernel: [ 13.366155] sfp sfp-1: Host maximum power 3.0W
Sat Aug 26 06:56:05 2023 kern.info kernel: [ 13.371283] sfp sfp-2: Host maximum power 3.0W
Sat Aug 26 06:56:06 2023 kern.info kernel: [ 20.138821] mt7530-mdio mdio-bus:1f sfp2: configuring for inband/2500base-x link mode
Sat Aug 26 06:56:06 2023 kern.info kernel: [ 20.148459] br-lan: port 5(sfp2) entered blocking state
Sat Aug 26 06:56:06 2023 kern.info kernel: [ 20.153758] br-lan: port 5(sfp2) entered disabled state
Sat Aug 26 06:56:06 2023 kern.info kernel: [ 20.161209] device sfp2 entered promiscuous mode
Sat Aug 26 06:57:02 2023 kern.info kernel: [ 75.799638] sfp sfp-1: module ALCATELLUCENT G010SP rev 10 sn ALCLFAB44018 dc 161205
Sat Aug 26 06:57:02 2023 kern.err kernel: [ 75.873995] sfp sfp-1: module transmit fault indicated
Sat Aug 26 06:57:07 2023 kern.info kernel: [ 81.121230] sfp sfp-1: module transmit fault recovered
Sat Aug 26 06:57:07 2023 kern.err kernel: [ 81.126396] sfp sfp-1: module persistently indicates fault, disabling
I notice that with debian, the ONT is much cooler than with Openwrt
Looks like the TX_FAULT pin is used for something else, maybe a serial port. Hence we will need to add a quirk for this SFP indicating that. This can also be because the external (xPON/fiber) link does not come up yet because you did not configure the MAC address and key in the module.
Unfortunately there is currently no way to temporarily ignore the TX_FAULT indication in order to be able to access the system running inside the ONT and configure it despite the external link not being up. This is a shortcoming which will have to be addressed in Linux at some point, hopefully…
With SinoVoip’s image it’s working because they just configure both SFP slots to work in 2500Base-X mode fixed without caring about any the SFP’s signals other than the SerDes lanes.
maybe he can simply disable the tx pin in dts (or patch out the possible tx-fault-requirement/handling in his codebase)? to use it for uart or anything else?
Hi thank you for your help, i’ve seen in this page something interesting : https://hack-gpon.org/ont-fs-com-gpon-onu-stick-with-mac/
Maybe this can be fixed from the ONT itself with these commands ?
basicly daniel is right here…
text says it will disable TX-Fault (i guess on the ONT) and serial, but r3 will still try to read tx-fault gpio…so what state will the pin have when it is disabled?
fw_setenv is for setting an variable in uboot environment. i am sure openwrts uboot does not call the preboot-var, so this will do nothing. also the gpio numbers will not match bpi-r3. so i guess you need to enter the system on the gpon-stick…maybe it uses uboot too and here the gpio are correct and preboot is called…make sure you can enter the falcon-bootloader before do the gpio command…
Yes, this is the U-Boot environment of the embedded Lantiq Falcon system running on the ONT stick.
well, I don’t understand these controls, so I prefer not to touch them at the risk of bricking the ONT.
If you can login to the ONT somehow via SSH or Telnet and use fw_setenv asc0 1 only without seeting or modifying preboot. If you are afraid to break things, dump the env first with fw_printenv and lets discuss here.
looks like it fixed the problem as i can’t see any errors now
root@OpenWrt:/# logread | grep 'sfp'
Sat Aug 19 14:01:10 2023 kern.info kernel: [ 11.683303] sfp sfp-1: Host maximum power 1.0W
Sat Aug 19 14:01:10 2023 kern.info kernel: [ 11.688496] sfp sfp-2: Host maximum power 1.0W
Sat Aug 19 14:01:10 2023 kern.info kernel: [ 12.019752] sfp sfp-1: module ALCATELLUCENT G010SP rev 10 sn ALCLFAB44018 dc 161205
Sat Aug 19 14:01:10 2023 kern.info kernel: [ 12.059671] sfp sfp-2: module TP-LINK TL-SM410U rev 2.0 sn 122C304001372 dc 221228
Sat Aug 19 14:01:13 2023 kern.info kernel: [ 19.273990] mt7530-mdio mdio-bus:1f sfp2: configuring for inband/2500base-x link mode
Sat Aug 19 14:01:13 2023 kern.info kernel: [ 19.283870] br-lan: port 5(sfp2) entered blocking state
Sat Aug 19 14:01:13 2023 kern.info kernel: [ 19.289098] br-lan: port 5(sfp2) entered disabled state
Sat Aug 19 14:01:13 2023 kern.info kernel: [ 19.296781] device sfp2 entered promiscuous mode
root@OpenWrt:/#
root@OpenWrt:/# logread | grep 'eth1'
Sat Aug 19 14:01:10 2023 kern.info kernel: [ 1.181362] mtk_soc_eth 15100000.ethernet eth1: mediatek frame engine at 0xffffffc009780000, irq 136
Sat Aug 19 14:01:13 2023 kern.info kernel: [ 19.305501] mtk_soc_eth 15100000.ethernet eth1: configuring for inband/2500base-x link mode
Sat Aug 19 14:01:13 2023 kern.info kernel: [ 19.315595] br-wan: port 1(eth1) entered blocking state
Sat Aug 19 14:01:13 2023 kern.info kernel: [ 19.320850] br-wan: port 1(eth1) entered disabled state
Sat Aug 19 14:01:13 2023 kern.info kernel: [ 19.326233] device eth1 entered promiscuous mode
Sat Aug 19 14:01:13 2023 kern.info kernel: [ 19.332371] br-wan: port 1(eth1) entered blocking state
Sat Aug 19 14:01:13 2023 kern.info kernel: [ 19.337600] br-wan: port 1(eth1) entered forwarding state
Sat Aug 19 14:01:14 2023 kern.info kernel: [ 20.151135] br-wan: port 1(eth1) entered disabled state
root@OpenWrt:/#
But it keeps going into disabled state so i still can’t acces the onu on it’s ip address at 192.168.20.10
OMG ! i can’t access my ONT anymore with ssh with debian now…
root@bpi-r3:/# ping 192.168.20.10
PING 192.168.20.10 (192.168.20.10) 56(84) bytes of data.
64 bytes from 192.168.20.10: icmp_seq=1 ttl=64 time=0.306 ms
64 bytes from 192.168.20.10: icmp_seq=2 ttl=64 time=0.273 ms
64 bytes from 192.168.20.10: icmp_seq=3 ttl=64 time=0.318 ms
64 bytes from 192.168.20.10: icmp_seq=4 ttl=64 time=0.262 ms
root@bpi-r3:/# ssh [email protected]
ssh: connect to host 162.168.20.10 port 22: No route to host
root@bpi-r3:/#
i can’t revert to fw_setenv asc0 0 
EDIT: Fortunately i could revert the setting using a mediaconverter (TP-LINK MC220L) But i’m still getting that route error…I must have a configuration problem somewhere
You have a typo in ip address 
THANKS !!!
some of you having a snapshot working with your ONT SFP, please share a link so we can test it with our equipment ! Thanks a lot !