FM350-GL and BE14 finally works on BPI-R4

Banana Pi Router design BPI-R4/BPI-R4 Pro(MT7988)
3

BPI-R4 is currently supported on snapshot only.

4

Can you help what should look commant git checkout to give snapshoot with available R4?

5

git should checkout the main branch by default, which is snapshot. Otherwise run git checkout main.

6

In tut is mistake. In actual main that patch is in dtsi file not in dts as mentioned.

And actuali is problem with instalation package fm350

ERROR: unable to select packages: atc-fib-fm350_gl_2024-08-04-0.2_all.ipk (no such package): required by: world[atc-fib-fm350_gl_2024-08-04-0.2_all.ipk] luci-lib-base-24.322.80622~a403707: error: uninstallable arch: all satisfies: luci-lua-runtime-24.322.80622~a403707[luci-lib-base] luci-lib-ipkg-24.322.80622~a403707: error: uninstallable arch: all satisfies: world[luci-lib-ipkg]<

After adding opkg manualy next problem:

root@OpenWrt:~# opkg install luci-proto-atc_20230813-0.2_all.ipk Unknown package ‘luci-proto-atc’. Collected errors:

  • pkg_hash_check_unresolved: cannot find dependency libc for luci-proto-atc
  • pkg_hash_fetch_best_installation_candidate: Packages for luci-proto-atc found, but incompatible with the architectures configured
  • opkg_install_cmd: Cannot install package luci-proto-atc. root@OpenWrt:~#
7

You need to add “all” as a secondary architecture. Edit this file: “/etc/apk/arch” and make sure it reads:

aarch64_cortex-a53
all

The ATC packages will install after that.

8

Now new challange:

ERROR: unable to select packages: https://github.com/mrhaav/openwrt/raw/master/atc/luci-proto-atc_20230813-0.2_all.ipk (no such package): required by: world[https://github.com/mrhaav/openwrt/raw/master/atc/luci-proto-atc_20230813-0.2_all.ipk]

9

I guess you fall into new package issue

10

Hi,

I want to ask do you have any update with this issue?

12

233 firmware is be14, mt7996e are both

14

Thanks again for this tutorial, I’ve now tried to implemented it for my HP-branded FM350-GL. mrhaav’s fm350_fcc_unlock.sh reported the modem as pre-unlocked.

  • Without the &pcie2 to disabled, the card wouldn’t even bring up any tty/go into pcie mode. Instead, it’ll very audibly “whistle.”

  • After “disabled”, six ttyUSB# appear & stay, and ttyUSB3 responds fine. This seems to kernel 6.6’s fixed behavior.

Then at first it seemed to not detect the SIM, with ATC just reporting “Unknown error (PINerror)”. Updating the modem’s firmware to 29.23.06 didn’t change this.

mrhaav then showed me the fix: The modem simply got delivered in ESIM mode and needed a reset with AT+GTDUALSIM=0. Before that, AT+SIMTYPE? returned 1, AT+GTDUALSIM? returned +GTDUALSIM : 1, "SUB2", "NO SERVICE".

Took a few more minutes (probably for my MVNO) and now the card simply works.

15

Hi @twwn,

I have a question, could you share the image with the changed configuration to USB mode? I tried to compile the image myself but after several attempts I was not able to do it.

16

Hi there,

I have a question about using the Fibocom. Is it still needed at latest OpenWRT release(24.10.0) to use it with USBMode? I have installed the stock bananan pi image and it looks like it is getting recognized but i cant use it (register modem error). So now i am not sure if it’s a problem cause i’m running it at PCIe mode oder maybe just an other error (dial up connection / pin problem etc.).

And it looks like i cant send AT commands at PCIe mode but with umbim i can read some stuff from the modem.

To be honest, of course i can compile it for myself but like i said, maybe i don’t have to :slight_smile:

So if someone got it running at PCIe mode at latest OpenWRT release (not snapshot nor rc), please tell me how :slight_smile:

cheers Chris

17

im testing my fm350 pcie mode without kernel panic on 24.10 but im getting lte speed only while usbmode im getting 600+ mbps. how can i force it to 5g mode only?when trying to set preferred mode to 5g only on luci , i got an error and modem wont connet

18

How did you manage to use it in pcie mode without kernel panic?

It is sad, that this is not solved after years of reporting.

19

It depends on a developer having board and module and can reproduce the error…i do not see a kernel panic here or link to issue. But i also have no such module or experience with lte/5g modules.

20

I have two modules. Quectel RG502Q-EA, it has so many quirks, it worked few times, the planetary alignment was right, but it ends up getting in limbo. Some AT commands do not work for some unknown reasons, like preferred network, the datasheet isn’t updated for the latest FW. It works in Mikrotik Chateau, well kinda. That device is another horror story.

And the FM350-GL, mediatek doesn’t work with mediatek in pcie mode, I haven’t tried the USB3 mode, but that kinda defeats the whole charm of the device. If using snapshots, the AT-Proto is no go also. Maybe there is some unknown firmware that fixes stuff, thus why I asked.

21

I had the fm350-gl running in pcie-mode without problems on my bpi-r4 (just the bare r4, no wifi) for a test over a few days like two or so weeks ago.

The key for me was going with SNAPSHOT in the OpenWrt Firmware Selector and I chose the following packets apk-mbedtls base-files ca-bundle dnsmasq dropbear firewall4 fitblk fstools kmod-crypto-hw-safexcel kmod-gpio-button-hotplug kmod-leds-gpio kmod-nft-offload kmod-phy-aquantia libc libgcc libustream-mbedtls logd mtd netifd nftables odhcp6c odhcpd-ipv6only ppp ppp-mod-pppoe procd-ujail uboot-envtools uci uclient-fetch urandom-seed urngd wpad-basic-mbedtls kmod-hwmon-pwmfan kmod-i2c-mux-pca954x kmod-eeprom-at24 kmod-mt7996-firmware kmod-mt7996-233-firmware kmod-rtc-pcf8563 kmod-sfp kmod-usb3 e2fsprogs f2fsck mkf2fs mt7988-wo-firmware luci kmod-mtk-t7xx kmod-wwan kmod-usb-net-rndis kmod-usb-serial kmod-usb-serial-option luci-proto-mbim luci-proto-modemmanager luci-proto-ncm comgt pciutils usbutils

Then I created a device with “Modemmanager” and filled out my provider data. Ran without panics over 2 or 3 days. It had the same kernel version (6.6.92) as my self-compiled 24.10-Master builds which had the panics, but the snapshot comes with Modemmanager 1.24 instead of 1.22.

22

I’m experiencing the same problem problem with FM350-GL in PCI-E mode, it looks like this is specific to only BPi-R4 because I didn’t saw issues opened regarding this problem on kernel bugzilla and t7xx driver is actively maintained, however I have some kernel panic logs, maybe this would help somehow. I’m also willing to test/debug more of this issue.

305 176761 Unable to handle.txt (4,5 KB)

23

For me it looks like a deadlock (spinlock not released) so basicly a driver issue of this specific card

24

ok, thanks for clarification. I will open a bug report in kernel bugzilla then.