Wireless Joint

I've been using my EM7565 with the ZBT WE1326 for a few months now, on the default generic firmware that came with the modem. Today I tried to flash the latest carrier-specific firmware version out (for me it was Verizon), using the M.2 to USB adapter I also have. I flashed it, and used putty to verify using AT! commands that it was on the new firmware. When I put the modem back into my WE1326, it would not connect. I finally thought to myself, oh I'll do a reset (AT!RMARESET=1), thinking it would wipe all of my custom configuration and start fresh with the new firmware I flashed (like a phone remains on it's newest firmware when you perform a factory reset). Well that was wrong, and after the AT!RMARESET=1 command it went back to the older Generic firmware that was previously on it.

My questions are:

1) is there a known issue with running the carrier specific firmware?
2) Does issuing the AT!RMARESET=1 always reset the modem back to the original firmware the modem shipped with? That seems strange to me.
3) Any pointers for how I could re-address this, assuming I did something wrong?

Old/shipped firmware: 01.08.04.00/002.011_000
Current Verizon firmware: 01.08.04.00/002.015_001

Thanks!

a-townie wrote: Sun Apr 07, 2019 11:09 pm 1) is there a known issue with running the carrier specific firmware?

I have not heard of an issue running a particular carrier firmware other than possibly provisioning issues. I am not familiar with the Verizon firmware, or if it requires the IMEI to be tied to a particular plan and SIM Card--much like Sprint does when running its firmware. Most find the Generic firmware best to avoid these type of complications.

2) Does issuing the AT!RMARESET=1 always reset the modem back to the original firmware the modem shipped with? That seems strange to me.

Yes, I have seen this happen on the EM7565 as well as the MC7455 and MC7354. In certain situations it is useful to resort to the OEM firmware--but certainly an annoyance at other times.

3) Any pointers for how I could re-address this, assuming I did something wrong?

I do not believe you have done anything abnormal.

When flashing the EM7565 behind a Windows machine, never allow Windows to manage or attempt to connect the modem with the carrier network. Windows can and will change the composition of a modem.

I would reflash the modem to the latest Generic firmware following a RMARSET.

I would then reflash the modem a second time with the same firmware. The EM7565 at one point would go into low power mode if not flashed the second go around. While perhaps not necessary with the newer firmware, I generally reflash them twice nonetheless.

Thanks for the thorough reply, @JimHelms. I will try to flash the latest Generic firmware later this week. I'm only one small update behind on that (I think the PRI for Generic is up to PRI 002.012_000 as of the time of this writing).

I had been having issues where the EM7565 on the WE1326 was getting stuck on a particular Verizon band and no longer performing Carrier Aggregation correctly. I was hoping that flashing the latest Verizon firmware would fix this bug. The only ways I've found to work around that issue are to reboot the router once a day, or to lock it to a single band. I live far enough out in the country that I don't get great CA anyways... it makes a negligible difference in speed for me it seems (usually running on B66 and using CA to add B13 on occasions).

I flashed the latest Generic firmware hoping it'd resolve my issue of getting stuck on a particular band - no luck. Back to locking down to a specific band. I'll wait for another new Verizon or Generic firmware and try again next time around.