Issue with the FM350-GL firmware tutorial

[twwn]

Thank you for supporting these modems.

The FM350-GL's FWupgrade.md could probably use a mention to uncheck the vendor-supplied DEV_OTA, as that file is not present and (by 4pda discussion) gets wiped otherwise. I found out too late.

I'm still trying to get my HP-branded card to work (BPI-R4, kernel 6.6). fm350_fcc_unlock.sh on ttyUSB{1,3} says it already is unlocked and AT+GTUSBMODE? on ttyUSB3 returns 41, so I tried to set ttyUSB6 in the interface, but nothing happens. On ttyUSB3 it at least reads "Unknown error (PINerror)" (It's a Vodafone MVNO that afaik shouldn't need more than APN "internet" and the PIN, at least that's also what Android auto-configures & then just works fine with.)

I also tried the neatly abstracted modemfeed package but it just causes the modem to perpetually reset itself, cycling through none, ttyUSB*, and ttyACM0. Also, if I don't disable &pcie2/SIM1 as by here, the modem seems to make it malfunction with a very audible buzzing noise and no tty* at all.

echo 0e8d 7127 > /sys/bus/usb-serial/drivers/option1/new_id is similar, ttyUSB7 and ttyACM0 briefly appears, buzzing, restart.

In the forum a user remarked…

For the FM350-GL there is a AT command which allows you to ignore the SIM-detection signal, then it works on the R4 as PCIe device

… but +MSMPD=0 has no effect, either.

[mrhaav]

Hi
Sorry to hear that I missed this about the DEV_OTA file. I will add that.

In cat /sys/kernel/debug/usb/devices it´s the sixth interface that you should use, if you have AT+GTUSBMODE=41.
Look in syslog which tty is connected to USB interface 6.

If you get answer to AT+GTUSBMODE? with /dev/ttyUSB3, then you have the correct device.

With kernel 6.6 you don´t need to run echo 0e8d 7127 > /sys/bus/usb-serial/drivers/option1/new_id.

BPI-R4 has support for both PCIe and USB interfaces in the M.2 KEY-B slot. You need to disable PCIe interface, as you mentioned.

I have seen other uses that have had issues with the SIM-detection on BPI-R4.
Use Picocom, picocom /dev/ttyUSB3 and check manually SIM status, AT+CPIN?.

T:  Bus=03 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  7 Spd=480  MxCh= 0
D:  Ver= 2.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0e8d ProdID=7127 Rev= 0.01
S:  Manufacturer=Fibocom Wireless Inc.
S:  Product=FM350-GL
C:* #Ifs=10 Cfg#= 1 Atr=a0 MxPwr=500mA
A:  FirstIf#= 0 IfCount= 2 Cls=e0(wlcon) Sub=01 Prot=03
I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=ff Driver=rndis_host
E:  Ad=82(I) Atr=03(Int.) MxPS=  64 Ivl=125us
I:* If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=rndis_host
E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
E:  Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 6 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option -> (dev/ttyUSB3)
E:  Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 7 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=07(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 8 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=89(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=08(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 9 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=8a(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=09(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms

[twwn]

Thank you for the reply. I've edited my original comment with a bit more info.

it´s the sixth interface that you should use, if you have AT+GTUSBMODE=41

Yes, AT+GTUSBMODE? replies on ttyUSB3 with 41. I'm not sure how to use that 6th interface though, do you mean selecting /dev/ttyUSB6 for Modem device in a AT commands interface? I'm afraid with that nothing happens at all. logread -f then only shows

daemon.notice netifd: Interface 'modem0' is setting up now
daemon.notice netifd: modem0 (5655): Initiate modem with interface eth1

daemon.notice netifd: modem0 (5655): sh: running: unknown operand

Look in syslog which tty is connected to USB interface 6.

Do you mean this from dmesg?

option 2-1.1:1.9: GSM modem (1-port) converter detected
usb 2-1.1: GSM modem (1-port) converter now attached to ttyUSB6

You need to disable PCIe interface, as you mentioned.

(It's really weird how loud the whistling is if I leave it enabled.)

I have seen other uses that have had issues with the SIM-detection on BPI-R4.

I really hope I don't have a defective R4 board. Sinovoip themselves warn how brittle their simcard ports are.

manually SIM status, AT+CPIN?

With minicom -D /dev/ttyUSB3:

AT+CPIN?
+CPIN: EMPTY_EUICC

OK

From cat /sys/kernel/debug/usb/devices, several differences stand out:

• Dev#= 4 Spd=5000 (yours: Dev#= 7 Spd=480, which I guess is just the board & mine using USB3)
• Ver 3.00 (yours 2.10), MxPS 9 (64)
• MxPS=1024 (512)
• your Driver=option -> (dev/ttyUSB3) where mine has no such reference

T:  Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  4 Spd=5000 MxCh= 0
D:  Ver= 3.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs=  1
P:  Vendor=0e8d ProdID=7127 Rev= 0.01
S:  Manufacturer=Fibocom Wireless Inc.
S:  Product=FM350-GL
C:* #Ifs=10 Cfg#= 1 Atr=a0 MxPwr=896mA
A:  FirstIf#= 0 IfCount= 2 Cls=e0(wlcon) Sub=01 Prot=03
I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=ff Driver=rndis_host
E:  Ad=82(I) Atr=03(Int.) MxPS=  64 Ivl=125us
I:* If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=rndis_host
E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=83(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=84(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=85(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
E:  Ad=86(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=05(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 6 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=87(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=06(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 7 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=88(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=07(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 8 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=89(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=08(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 9 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=8a(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=09(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms

[mrhaav]

This is USB interface 6: I:* If#= 6 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
It was me who added -> (dev/ttyUSB3) in an attempt to make it clear :)
In your case you shall us /dev/ttyUSB3.

Maybe your modem is trying to use eSIM?

+SIMTYPE, Read Current SIM Type AT+SIMTYPE?
0: USIM
1: ESIM

+GTDUALSIM, for Dual SIM Switch AT+GTDUALSIM=<sim_app>
AT+GTDUALSIM? -> +GTDUALSIM:<sim_app>,<sub_app>,<sys_mode>]
AT+GTDUALSIM=? -> +GTDUALSIM:(list of support <sim_app>)

Defined Values
<sim_app>: integer type; operate sim card id, Parameter range is (0,1).
0 SIM1(default)
1 SIM2
<sub_app>: string type; display the subscribe app id.
SUB1 subscribe id 1
SUB2 subscribe id 2
<sys_mode>: string type, display the current system mode.
No Service no service
N NR service*
L LTE service
W WCDMA service

[twwn]

Well, that was wild.

It was me who added -> (dev/ttyUSB3) in an attempt to make it clear :)

Oh. :) Though to be honest I don't understand how that /sys/kernel/debug/usb/devices line shows it's ttyUSB3 — I just went with whichever replied to AT in minicom.

Maybe your modem is trying to use eSIM?

I failed to look into eSIM as I was under the impression that these hardware variants were visibly marked so on their metal shield, and this one isn't.

AT+SIMTYPE? indeed returned 1/eSIM. AT+GTDUALSIM? accordingly +GTDUALSIM : 1, "SUB2", "NO SERVICE"

So I set AT+GTDUALSIM=0 and cut power, and without AT commands interface preoccupying the tty the modem responds now responds with SIMTYPE=0. It seems to now correctly recognize whether the SIM is physically present.

With the AT commands interface, the tty then first shown locked into a 2s loop of

AT+CPIN?
+CPIN: SIM PIN

OK

I tried various Authentication Type & PDP Type combinations (half-heartedly as I know there are no other creds and when I used the SIM in a phone, it got IPv4 only). Eventually it then switched to…

+CPIN: READY

… so I guess the delay was just my MVNO provisioning things.

Luci now reports the interface as properly receiving its IPv4/connectivity and all it then took was adding it to WAN zone to use it.

So thank you very much for this repo and your prompt support!

(BTW, is there a better way to disable &pcie2 than having to manually edit mt7988a-bananapi-bpi-r4.dtsi on every OpenWrt compilation?)

edit: Regarding the firmware tutorial's mention of v2306.7, there's a 2306.8 package on the MS Update Catalog. But given the tutorial was published after it, I'm assuming the choice of .7 was deliberate.

[mrhaav]

With the AT commands interface, the tty then first shown locked into a 2s loop of

Are you running minicom in parallel with atc? It is not recommended. atc is listening to all AT command responses.
If you choose Debug = All then the AT commands and responses are visible in syslog. You can use logread -f to view in real time.

What modem firmware version did you get with 2306.8 package?

[twwn]

Are you running minicom in parallel with atc? It is not recommended. atc is listening to all AT command responses.

Just listening with it. It would show the back & forth between atc and the modem.

What modem firmware version did you get with 2306.8 package?

I didn't actually flash it as the modem wasn't working yet and I wanted to go with a proven version rather than potentially break more. Right now I can't upgrade as I had to borrow a laptop for it.

[twwn]

Okay, I found another way. So with 3500.5003.2306.8 (there's also a 3500.5033.2306.4 but it's two months older), only the preloader_k6880v1_mdot2_datacard.bin shows a different hash.

The various AT info commands:

ATI
Manufacturer: Fibocom Wireless Inc.
Model: FM350-GL
Revision: 81600.0000.00.29.23.06
SVN: 09

IMEI: {###…}

OK
AT+GTAPPVER
FM350.F09

OK
AT+GTBASELINEVER
gem-mp-1907-mp1
               _gem-mp-1907-mp1.V1.30.1
MOLY.NR15.R3.MD700.TC35.SP.V110.5.P14

OK
AT+GTPKGVER
81600.0000.00.29.23.06_5000.0002.018.302.011_F09

OK
AT+GTMCFWVER
81600.0000.00.29.23.06

OK
AT+GTCUSTPACKVER
302.011

OK
AT+GTCFGELEMVER
5000.0002.018

OK
AT+GTCUSTDATAVER
ERROR
AT+GTCUSTDATAVER?
+GTCUSTDATAVER: ""

OK

Did I forget any command? Any difference to your output?

edit: The modem is working fine, ofc.

One note for the tutorial: Device Guard needs to be disabled in UEFI for Windows/the flasher to recognize the modem (and one better has the Bitlocker recovery key at hand if that too is enabled).

edit2: Have you thought about merging your repo with modemfeed? That'd make it much easier to integrate atc into a build/to upgrade. (That feed also has a fm350-modem package, but I couldn't get it to work.)

[mrhaav]

I have the same information except for AT+GTCUSTDATAVER? +GTCUSTDATAVER: "5001.0001.0000_Default_001.000.000.014".

No, I have not thought about merging with modemfeed. Why would that be easier?
You can add my repo, src-git mrhaav https://github.com/mrhaav/openwrt-packages.git, to feeds.conf.default when you build you own firmware.
All source code are available at: https://github.com/mrhaav/openwrt-packages

[twwn]

Oops, I didn't see this other repo. I'll indeed just be using that then. (The modemfeed packages don't seem to work with the modem, anyway.)

except for AT+GTCUSTDATAVER?

Is yours branded, by chance? There's no info at all in the manual as to what section is actually good for, just that this "dev_image" is the "device parameters image version." I guess it's what I wiped along the DEV_OTA, elsewhere referred to as having "vendor configurtions."

[mrhaav]

Hi. sorry for late response.
No, my modem is not branded, not what I know. I bought from AliExpress.
It´s working fine.