nah i haven't figured out on how to configure it but I'm seeing many tutorials on the 4pda forum
has anyone the same ping/latency problem?
[ 1303.326621] mtk_t7xx 0000:01:00.0: assign IRQ: got 130
[ 1303.331798] mtk_t7xx 0000:01:00.0: enabling bus mastering
[ 1303.339283] mtk-pcie-gen3 11280000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11280c00 data 1
[ 1303.347843] mtk-pcie-gen3 11280000.pcie: msi#0x2 address_hi 0x0 address_lo 0x11280c00 data 2
[ 1303.356304] mtk-pcie-gen3 11280000.pcie: msi#0x3 address_hi 0x0 address_lo 0x11280c00 data 3
[ 1303.364747] mtk-pcie-gen3 11280000.pcie: msi#0x4 address_hi 0x0 address_lo 0x11280c00 data 4
[ 1303.373191] mtk-pcie-gen3 11280000.pcie: msi#0x5 address_hi 0x0 address_lo 0x11280c00 data 5
[ 1303.381631] mtk-pcie-gen3 11280000.pcie: msi#0x6 address_hi 0x0 address_lo 0x11280c00 data 6
[ 1303.390071] mtk-pcie-gen3 11280000.pcie: msi#0x7 address_hi 0x0 address_lo 0x11280c00 data 7
[ 1303.398503] mtk-pcie-gen3 11280000.pcie: msi#0x8 address_hi 0x0 address_lo 0x11280c00 data 8
[ 1364.969575] mtk_t7xx 0000:01:00.0: MD handshake timeout
[ 1364.974806] mtk_t7xx 0000:01:00.0: Boot Handshake failure
How to solve this problem, the device is Bpi r3
have you random reboots?
I have created a script and a luci-proto app to the FM350-GL.
It support dual stack and, I think, authentication works as well. The script re-connects on network disconnections. Received SMS are stored in /tmp/sms/rx folder.
Fell free to try.
More info and the script: https://github.com/mrhaav/openwrt/tree/master/atc/fib-fm350_gl
luci-proto-atc: https://github.com/mrhaav/openwrt/tree/master/atc
Edit: The hotplug script for the Option, or Generic, USB driver didnĀ“t work as expected. Now itĀ“s corrected.
4 Likes
No random reboots
i have tryed the sierra serial driver and its detect and displayed in modemmanager/mmcli but only with 4g mode and if i try to connect i got "connection error message: Unknown error" and the device crash after some time
@mrhaav run the usb dive on your tests stable?
its look like the modem-control requests on usb interface 2,3,4 and 5 crash the card
if i add the card to the option driver and disable modem-control requests with NCTRL
the driver load without crash
but modemmanager not detect the modem
1 Like
I have noticed the same thing, if I use some of the other ports than the AT-command port the modem crashes.
When I have AT+GTUSBMODE=40 (0e8d:7126) I have the AT-command port at ttyUSB2 and if I have AT+GTUSBMODE=41 (0e8d:7127) I have the AT-command port at ttyUSB4, and there is only one AT-command port.
It is generally not a good idea to refer to /dev/ttyUSBx at all.
For PID 7126 the "AT Port" is USB interface 04
For PID 7127 the "AT Port" is USB interface 06
They may appear as ttyUSB2 and ttyUSB4, but not necessarily.
1 Like
if i see it right
the option driver can only block the first 8 (0-7) interfaces for attach with RSVD? so the AT+GTUSBMODE=41 (0e8d:7127) is a bad idea an its better to use AT+GTUSBMODE=40 (0e8d:7126) ?
for the detection in modemmanager i need to do some changes in modemmonitor source. but i cant change openwrt overide the folder at compiling
anyone know how to change code on modemmanager? Prevent openwrt do override modemmanager on compiling - For Developers - OpenWrt Forum
Does anyone know how to upgrade FM350-GL firmware under Linux? My upgrade failed under Windows
Manufacturer: Fibocom Wireless Inc.
Model: FM350-GL
Revision: 81600.0000.00.09.06.29
SVN: 01
it seems stuck in windows 10 when using pcie mode.
i have found only one solution over the usb interface with the SP Flash Tool.
@0x5826 if u use your card in pcie mode under linux have you some high pings with your card?
I have only used USB mode before, there seems to be something wrong about PCIE mode
under windows the card works fine under pcie.
have use ipv6 in usb mode? i try to recive a ipv6 address an get the ipv6 only in decimal not hex even after the execution of AT+CGPIAF=1,1,1,0
IPv6 also needs to be set manually because the generated network card does not fill in the gateway address and dns of IPv6.
yes but i get the ipv6 in decimal not hex and its start with 0.0.0.0.0... i think this is not right. 
I went through the same steps as you did and it still won't unlock. May I ask how you did it and can you be more detailed? Thanks
I've made many attempts to do this but it didn't work, can you show more detailed steps? Thank you very much.