Rm551e-gl latest firmware

Ati
Quectel
RM551E-GL
Revision: RM551EGL00AAR02A02M8G

Plz share latest firmware

I have sent the latest firmware to your email, pls check

Hi @herbert.pan-Q can you send to me as well. I have the same version.

I have sent the latest firmware to your email, pls check

Plz share latest firmware

Is RM551EGL00AAR02A02M8G the latest engineering/production firmware for RM551E-GL, or is there any newer branch (like A03/A04) available for 5G SA UL-CA stability?"

I have this question, too. I’ve experienced extreme instability with RM551EGL00AAR02A02M8G for some time, both in QMI and ECM mode. Sometimes after an hour, or sometimes even within minutes, wwan0 or usb0 (depending on mode) stops receiving any data, and errors continue to increment. A usbreset of the device will restore it without a full tower reconnect, so it seems it is something within the modem itself. Is there a newer version of the R02 firmware that specifically targets this condition? If not, is it possible to downgrade to R02A01? Thanks in advance!

Dear @Michael_Pudelko
Currently, no newer version than RM551EGL00AAR02A02M8G .
With R02A01, do you have the same issue?

Hi Sylvia,

Thank you confirming that I am on the most current firmware. While I can’t remember whether I ever had the same issue with that prior version, I also can’t remember why I updated it. That was earlier this year when I was using it with a Verizon-based plan. This current issue began when I recently switched to an AT&T-based US plan after many months of a pause in service, so it’s difficult to draw any conclusions with respect to whether this behavior was firmware- or carrier-specific.

All this said, I believe I figured it out today (along with a lot of help from Claude Code). It was apparently due to a 1420 mtu on the qmi_wwan host interface (wwan0/wan1). When I explicitly set that back to to 1500 along with outbound uplink path MTU of 1430 (or 1420) the blowouts seem to have stopped. This is in combination with mss clamping set to 1390 and 1380, respectively, also using OpenWRT’s mtu_fix on the adapter.

Here’s where I’m at since the fixes were applied, so I think I’m good:
wwan0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.65.204.160 P-t-P:10.65.204.160 Mask:255.255.255.192
inet6 addr: fe80::12cc:c9ac:2b46:5b09/64 Scope:Link
inet6 addr: 2600:382:3a93:76e9:e1df:76a:c459:dacd/128 Scope:Global
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:3048249 errors:0 dropped:0 overruns:0 frame:0
TX packets:1273810 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3698235523 (3.4 GiB) TX bytes:209401911 (199.7 MiB)

If I ever do feel another need to rule out a particular firmware version, can you confirm whether it is possible to roll back to a prior version? I know it’s not safe to ever go from any R02 to R01 or vice-versa, but so long as I stay within the same R revision, can I go from R02A02 back to R02A01?

Unrelated to above, do you have any roadmap plans to ever offer an x85 M.2 module?

Regards,
Mike

Dear @Michael_Pudelko
From the debug, the issue is related with MTU on the qmi_wwan, right?
If solved your issue, you don’t need to downupgrade to A01.

Hello again, silvia,

Yes, that’s correct. I am good on A02. Rock-solid.