EM9191 lost its band mask configuration

Hi,

I have an EM9191 module that doesn’t connect to network. Problem is that it has lost its band mask configuration:

ati
Manufacturer: Sierra Wireless, Incorporated
Model: EM9191
Revision: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23
IMEI: 355890347570397
IMEI SV: 27
FSN: 784484958601B1
+GCAP: +CGSM

OK

at!band=?
Index, Name

Available:

OK

at!band?
Unknown band mask. Use AT!BAND to set band.
0 - GW: 0000000000000000
1 - LTE: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
3 - NRNSA: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000
4 - NRSA: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000

OK

I have tried to redefine band masks by hand, but all commands return error. PCINFO indicates RFC_INIT error:

AT!PCINFO?
State: Offline
LPM voters - Temp:0, Volt:0, User:0, W_DISABLE:0, IMSWITCH:0, BIOS:0, LWM2M:0, OMADM:0, FOTA:0, NVCRIT:0, RFCAL:0, MMWCAL:0, RFC_INIT:1
LPM persistence - None

OK

I have tried rmareset=1 and also tried to update firmware, but no help. How can I recover that module to working state again?

what is the return of “AT!RFDEVSTATUS?”

AT!RFDEVSTATUS?

RFC init failure
instance,manufacture id,product id,device status
0 ,0x217 ,0xfed ,PRESENT
1 ,0x217 ,0x35 ,PRESENT
2 ,0x217 ,0x1c3 ,PRESENT
3 ,0x217 ,0x412 ,PRESENT
4 ,0x217 ,0x35 ,PRESENT
5 ,0x217 ,0x1a8 ,PRESENT
6 ,0x217 ,0x418 ,PRESENT
7 ,0x217 ,0x337 ,PRESENT
8 ,0x217 ,0x1ad ,PRESENT
9 ,0x217 ,0x338 ,PRESENT
10 ,0x217 ,0x1ac ,FATAL
11 ,0x217 ,0x338 ,PRESENT
12 ,0x217 ,0x142 ,PRESENT
13 ,0x217 ,0x417 ,PRESENT
14 ,0x217 ,0x338 ,PRESENT
15 ,0x217 ,0x26f ,PRESENT
16 ,0x217 ,0x26f ,PRESENT
17 ,0x217 ,0x26e ,PRESENT
18 ,0x217 ,0x4d0 ,PRESENT
19 ,0x217 ,0x26e ,PRESENT
20 ,0x217 ,0x4d0 ,PRESENT
21 ,0x217 ,0x253 ,PRESENT
22 ,0x217 ,0x253 ,PRESENT
23 ,0x217 ,0x263 ,PRESENT
24 ,0x217 ,0x254 ,PRESENT
25 ,0x217 ,0x254 ,PRESENT
26 ,0x217 ,0x260 ,PRESENT
27 ,0x217 ,0x255 ,PRESENT
28 ,0x217 ,0x26e ,PRESENT
29 ,0x217 ,0x4d0 ,PRESENT
30 ,0x217 ,0x253 ,PRESENT
31 ,0x217 ,0x263 ,PRESENT
32 ,0x217 ,0x254 ,PRESENT
33 ,0x217 ,0x253 ,PRESENT
34 ,0x217 ,0x254 ,PRESENT
35 ,0x134 ,0x17 ,PRESENT
36 ,0x134 ,0x14 ,PRESENT
37 ,0x134 ,0x15 ,PRESENT

OK

It seems this is qualcomm chipset problem
You need to contact distributor and see if rma is accepted if module still within warranty period

Hi again,

We have had several similar issues in the field now. Replacing the module is extremely difficult and should be avoided as much as possible. So, is there any way to get these modules fixed other than replacing it? Previous answer was bit a vague, it said that it “seems” to be Qualcomm chipset problem. But is it for sure? If it is, is there some errata from Qualcomm? Have they fixed this problem on some newer revision of the chipset? Does this same problem apply to other modems too? For example EM9291?

br, Sami

Have you contacted distributor?

You need to contact distributor and see if rma is accepted if module still within warranty period

If you want to know the root cause, you also need to contact distributor to arrange for failure analysis.

BTW, I have checked IMEI of the faulty module, its warranty period has been expired…

Maybe I can help. I have been following this.

I checked the latest release notes and there is a known issue that looks like the problem you are having.

Release notes say - RFC init failure. Some modules are found in offline mode due to RFC failure.

FERRARI-3600 is the Sierra Wireless ID number for this problem.

Sami, I suggest following what jyijyi said. Contact the module distributor. The disti will get a Sierra Wireless support person involved and he/she will help get you to the best ending possible.

Yes, i guess it is the same issue

Hi,

Yes, it is probably the same thing. Unfortunately it is still listed for latest FW version, so there is no hope that upgrading FW would prevent this from happening.

We have been in contact with our distributor but replacing the module isn’t really a solution that we would like to have.

I remember this issue might be identified by downloading a test build to it according to its serial number.
You can follow up with distributor

Ok, I’ll ask from our distributor about that..

Is there some way to access more detailed information about this FERRARI-3600 issue?

as said before, you need to contact distributor to identify the issue