EM9191 4x4 MIMO

IoT Modules MC/EM Series
1

Hi,

I have an EM9191 module with all four antennas connected. My rfcid setting is 1008 (2x2 MIMO) and I get solid 5G NSA connection on band n78. Then I try to change the rfcid setting to 1007 (4x4 MIMO) to utilize all four connected antennas. After that the throughput of the modem degrades substantially. I also see lots of NAS_SS_INFO_IND from modem. I tried to study what they are about and it seem that CS and PS domain attach states constantly toggles between attached and detached states.

Any idea why that is happening? 4x4 MIMO should be valid setting wit four antennas, right? Below is some info about my module:

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

br, Sami

2

Wht is the return of the following?

At!impref?
At!gstatus?
At!sdpref?
At!band?
At!selrat?

Can you also lock to n78 in NSA mode with at!band command to see if there is improvement?

3

Hi,

Here is the output of the at-command you requested. I’ll try that band locking…

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

OK
At!impref?
!IMPREF:
preferred fw version: 03.14.10.04
preferred carrier name: GENERIC
preferred config name: GENERIC_030.094_000
preferred subpri index: 000
current fw version: 03.14.10.04
current carrier name: GENERIC
current config name: GENERIC_030.094_000
current subpri index: 000

OK
At!gstatus?
!GSTATUS:
Current Time: 312 Temperature: 39
Thermal Mitigation Level: 0
Reset Counter: 1 Mode: ONLINE
System mode: LTE PS state: Attached
LTE band: No band LTE bw: 1.4 MHz
LTE Rx chan: — LTE Tx chan: —
EMM state: Registered No Cell
RRC state: RRC Connected
IMS reg state: NOT REGISTERED IMS mode: Normal
IMS Srv State: UNKNOWN SMS,UNKNOWN VoIP

PCC Rx0 RSSI: — PCC Rx0 RSRP: —
PCC Rx1 RSSI: — PCC Rx1 RSRP: —
PCC Rx2 RSSI: — PCC Rx2 RSRP: —
PCC Rx3 RSSI: — PCC Rx3 RSRP: —
PCC Tx Power: — TAC: —
RSRQ (dB): — Cell ID: —
SINR (dB): 0

NR5G band: — NR5G bw: —
NR5G Tx Power: — NR5G Tx chan: —
NR5G Rx chan: — NR5G RSRP (dBm): —
NR5G RSRQ (dB): — NR5G SINR (dB): —

OK
At!sdpref?
RATs : WCDMA,LTE,NR5G
GWC : B1,B2,B4,B5,B6,B8,B9,B19
LTE : B1,B2,B3,B4,B5,B7,B8,B12,B13,B14,B17,B18,B19,B20,B25,B26,B28,B29,B30,B32,B34,B38,B39,B40,B41,B42,B43,B46,B48,B66,B71
TDS :
NRSA : n1,n2,n3,n5,n7,n8,n12,n20,n25,n28,n38,n40,n41,n48,n66,n71,n77,n78,n79
NRNSA: n1,n2,n3,n5,n7,n8,n12,n20,n25,n28,n38,n40,n41,n48,n66,n71,n77,n78,n79

OK
At!band?
Index, Name
00, All bands,
0 - GW: 100600000FC00000
1 - LTE: 0000A7E2BB0F38DF 0000000000000042
3 - NRNSA: 000081A0090808D7 0000000000007042
4 - NRSA: 000081A0090808D7 0000000000007042

OK
At!selrat?
!SELRAT: 00, Automatic

OK

4

I changed 5G band masks so that only n78 should be allowed. Behaviour is the same.

at!band?
Index, Name
0D, LTE 5G ALL,
0 - GW: 0000000000000000
1 - LTE: 0000A7E2BB0F38DF 0000000000000042
3 - NRNSA: 0000000000000000 0000000000002000
4 - NRSA: 0000000000000000 0000000000002000

OK
At!gstatus?
!GSTATUS:
Current Time: 189 Temperature: 40
Thermal Mitigation Level: 0
Reset Counter: 1 Mode: ONLINE
System mode: LTE PS state: Attached
LTE band: No band LTE bw: 1.4 MHz
LTE Rx chan: — LTE Tx chan: —
EMM state: Registered No Cell
RRC state: RRC Connected
IMS reg state: NOT REGISTERED IMS mode: Normal
IMS Srv State: UNKNOWN SMS,UNKNOWN VoIP

PCC Rx0 RSSI: — PCC Rx0 RSRP: —
PCC Rx1 RSSI: — PCC Rx1 RSRP: —
PCC Rx2 RSSI: — PCC Rx2 RSRP: —
PCC Rx3 RSSI: — PCC Rx3 RSRP: —
PCC Tx Power: — TAC: —
RSRQ (dB): — Cell ID: —
SINR (dB): 0

NR5G band: — NR5G bw: —
NR5G Tx Power: — NR5G Tx chan: —
NR5G Rx chan: — NR5G RSRP (dBm): —
NR5G RSRQ (dB): — NR5G SINR (dB): —

OK
At!sdpref?
RATs : WCDMA,LTE,NR5G
GWC : B1,B2,B4,B5,B6,B8,B9,B19
LTE : B1,B2,B3,B4,B5,B7,B8,B12,B13,B14,B17,B18,B19,B20,B25,B26,B28,B29,B30,B32,B34,B38,B39,B40,B41,B42,B43,B46,B48,B66,B71
TDS :
NRSA : n1,n2,n3,n5,n7,n8,n12,n20,n25,n28,n38,n40,n41,n48,n66,n71,n77,n78,n79
NRNSA: n1,n2,n3,n5,n7,n8,n12,n20,n25,n28,n38,n40,n41,n48,n66,n71,n77,n78,n79

OK
At!selrat?
!SELRAT: 00, Automatic

OK

5

Why there is no signal strength RSRP in at!gstatus?

And from at!gstatus?, LTE shows there is no band

6

That I don’t know. But with 2x2 MIMO gstatus has signal information:

At!gstatus?
!GSTATUS:
Current Time: 149 Temperature: 36
Thermal Mitigation Level: 0
Reset Counter: 1 Mode: ONLINE
System mode: ENDC PS state: Attached
LTE band: B3 LTE bw: 20 MHz
LTE Rx chan: 1825 LTE Tx chan: 19825
EMM state: Registered Normal Service
RRC state: RRC Connected
IMS reg state: NOT REGISTERED IMS mode: Normal
IMS Srv State: UNKNOWN SMS,UNKNOWN VoIP

PCC Rx0 RSSI: -61 PCC Rx0 RSRP: -94
PCC Rx1 RSSI: -63 PCC Rx1 RSRP: -97
PCC Tx Power: -1 TAC: 7154 (29012)
RSRQ (dB): -13.2 Cell ID: 000d6a11 (879121)
SINR (dB): 7.6

SCC1 NR5G band: n78 SCC1 NR5G bw: 100 MHz
SCC1 NR5G Tx Power: 19 SCC1 NR5G Tx chan: 641332
SCC1 NR5G Rx chan: 641332
NR5G RSRP (dBm): -100 NR5G RSRQ (dB): -12
NR5G SINR (dB): 6.0

OK

So, it seems that there is something wrong with 4x4 MIMO.

7

what are the return of the followings?

AT!RATCA?
AT!RFCID?
AT!RFCMBNSCAN?
AT!RFDEVSTATUS?

8

Hmm… Today I’m at the different location, about 30km from the original. 4x4 MIMO seems to be working here. How can that be? Could this be related to base station that the device is connecting to? Or what? Below are the outputs you requested. Not sure if they are of any interest now that 4x4 MIMO is working at the moment.

AT!RATCA?
!RATCA:
CA: 0
ENDC: 1
SA: 1

OK
AT!RFCID?
!RFCID:
CMW_HWID: 1007
CMW_BID : 0
MMW_HWID: 0
MMW_BID : 0

OK
AT!RFCMBNSCAN?

1003_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:77
1004_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:76
1007_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:77
1008_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:77
1090_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:74
1091_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:76
1100_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:77
1101_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:78
1102_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:77
1103_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:77
1104_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:78
1105_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:77
1200_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:68
1201_0_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:68
1500_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:1
1501_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:1
1502_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:1
1503_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:2
1504_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:1
1505_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:3
1506_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:3
1507_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:3
1508_0.mbn: SWIX55C_03.14.10.04 25b6d9 jenkins 2024/02/29 17:20:23 rfctag: rfcver:3
2000_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:3
2050_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2051_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2100_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:4
2101_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:2
2102_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2103_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2150_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2200_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2201_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:2
2202_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2250_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2300_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2350_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2400_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2450_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2451_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1
2500_0.mbn: SWIX55C_03.14.10.04 1972b0 jenkins 2024/03/01 08:05:19 rfctag:001 rfcver:1

OK
AT!RFDEVSTATUS?

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 ,PRESENT
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
at!gstatus?
!GSTATUS:
Current Time: 143 Temperature: 33
Thermal Mitigation Level: 0
Reset Counter: 1 Mode: ONLINE
System mode: ENDC PS state: Attached
LTE band: B3 LTE bw: 20 MHz
LTE Rx chan: 1825 LTE Tx chan: 19825
EMM state: Registered Normal Service
RRC state: RRC Connected
IMS reg state: NOT REGISTERED IMS mode: Normal
IMS Srv State: UNKNOWN SMS,UNKNOWN VoIP

PCC Rx0 RSSI: -57 PCC Rx0 RSRP: -80
PCC Rx1 RSSI: — PCC Rx1 RSRP: —
PCC Rx2 RSSI: — PCC Rx2 RSRP: —
PCC Rx3 RSSI: — PCC Rx3 RSRP: —
PCC Tx Power: -17 TAC: 71c1 (29121)
RSRQ (dB): -3.1 Cell ID: 0018a702 (1615618)
SINR (dB): 22.6

SCC1 NR5G band: n78 SCC1 NR5G bw: 100 MHz
SCC1 NR5G Tx Power: 19 SCC1 NR5G Tx chan: 639332
SCC1 NR5G Rx chan: 639332
NR5G RSRP (dBm): -99 NR5G RSRQ (dB): -11
NR5G SINR (dB): 16.5

OK

9

you can also try if enabling CA in AT!RATCA can have improvement

10

Hi. I’m back at the original location and 4x4 MIMO problem persist. I then enabled CA with AT!RATCA to see if it helps. And it did! I would like to understand why, because it worked even without CA at the other location. Should 4x4 MIMO usage always require enabling of CA?

at!gstatus?
!GSTATUS:
Current Time: 312 Temperature: 40
Thermal Mitigation Level: 0
Reset Counter: 1 Mode: ONLINE
System mode: ENDC PS state: Attached
LTE band: B3 LTE bw: 20 MHz
LTE Rx chan: 1825 LTE Tx chan: 19825
LTE SCC1 state:INACTIVE LTE SCC1 band: B1
LTE SCC1 bw : 20 MHz LTE SCC1 Rx chan: 100
LTE SCC1 UL Configured: FALSE LTE SCC1 Tx chan: 0
LTE SCC3 state:INACTIVE LTE SCC3 band: B20
LTE SCC3 bw : 10 MHz LTE SCC3 Rx chan: 6400
LTE SCC3 UL Configured: FALSE LTE SCC3 Tx chan: 0
EMM state: Registered Normal Service
RRC state: RRC Connected
IMS reg state: NOT REGISTERED IMS mode: Normal
IMS Srv State: UNKNOWN SMS,UNKNOWN VoIP

PCC Rx0 RSSI: -65 PCC Rx0 RSRP: -100
PCC Rx1 RSSI: -66 PCC Rx1 RSRP: -100
PCC Rx2 RSSI: — PCC Rx2 RSRP: —
PCC Rx3 RSSI: — PCC Rx3 RSRP: —
SCC1 Rx0 RSSI: -78 SCC1 Rx0 RSRP: -104
SCC1 Rx1 RSSI: -77 SCC1 Rx1 RSRP: -105
SCC1 Rx2 RSSI: — SCC1 Rx2 RSRP: —
SCC1 Rx3 RSSI: — SCC1 Rx3 RSRP: —
SCC3 Rx0 RSSI: -62 SCC3 Rx0 RSRP: -94
SCC3 Rx1 RSSI: -65 SCC3 Rx1 RSRP: -96
PCC Tx Power: -2 TAC: 7154 (29012)
SCC1 Tx Power: —
SCC3 Tx Power: —
RSRQ (dB): -13.5 Cell ID: 000d6a11 (879121)
SINR (dB): 5.2

SCC1 NR5G band: n78 SCC1 NR5G bw: 100 MHz
SCC1 NR5G Tx Power: 23 SCC1 NR5G Tx chan: 641332
SCC1 NR5G Rx chan: 641332
NR5G RSRP (dBm): -97 NR5G RSRQ (dB): -11
NR5G SINR (dB): 11.5

OK

11

can you type AT!PRIID? and AT!PACKAGE?
It is quite strange that the CA is not enabled by default.

I believe yes, because if you type AT!RFCOMBOS? , it shows all the combo in ENDC mode.
If CA is not enabled, some of the combo cannot be used.

12

AT!PRIID?
PRI Part Number: 9910604
Revision: 001.001
Customer: Generic

Carrier PRI: 9999999_9909621_SWIX55C_03.14.10.04_01_GENERIC_030.094_000

OK
AT!PACKAGE?
1104903_9910604_EM9191_03.09.06.00_01_Generic_001.001_000

OK

I believe yes, because if you type AT!RFCOMBOS? , it shows all the combo in ENDC mode.
If CA is not enabled, some of the combo cannot be used.

But I don’t get why it worked without CA in other location. If it would be due to missing combo, wouldn’t that combo be missing no matter where the device is?

13

Seems your module is quite an old one…
You need to apply the following to change the CA setting:

AT!ENTERCND="A710"
AT!RATCA=1,1,1
AT!NVBACKUP=2
AT!RESET

I have no idea, maybe in some NOK location, it does not support single LTE B3 + 5G n78.
Anyway, you still need to enable the CA setting for normal usage.

14

I’ve made some configuration changes between 4x4 and 2x2 MIMO. After a while I wasn’t able to set 2x2 MIMO again. Modem seems to be in reset loop. I checked the crash dump on modem and it looked like this:

at!gcdump

Src: FatalError
File: nr5g_ml1_rfmgr_proc.c
Line: 2158
Str: Assert nr_mode != NR5G_FR_SUB6 || carrier_def->sub6.bwps.rx_tx_
00000000 00000000 00000000 00000000
Prc: MPSS
Task: NONE
Time: 0000C482
R0: 00000000 R1: 00000000 R2: 00000000 R3: 00000000 R4: 00000000
R5: 00000000 R6: 00000000 R7: 00000000 R8: 00000000 R9: 00000000
R10: 00000000 R11: 00000000 R12: 00000000 R13: 00000000 R14: 00000000
R15: 00000000 R16: 00000000 R17: 00000000 R18: 00000000 R19: 00000000
R20: 00000000 R21: 00000000 R22: 00000000 R23: 00000000 R24: 00000000
R25: 00000000 R26: 00000000 R27: 00000000 R28: 00000000 SP: C9464C38
FP: C9464D50 LR: D9447830
PC: C888B728
CPSR: 00000000
Mod: Unknown
Ctr: ARM, IRQ dis,FIQ dis

TOS
C9464DB8 C8894C4C 00001019 5A86A940 00000000 5A86A944 00000CB8
F4F1CDC8 F4F1B728 F4F1AC48 5B2239C4 F4F1B6E0 F4F1B6D0 D1453558
5B2239C0 5B223738 00000440 00000280 C40E3430 0000000C F4F21280
C40980DD 5B2232C8 5B093C78 5B093C70 F4F12238 C9464DD8 C888B728
D944FB00 C40980DD 5B2232C8 00000000
BOS

Src: FatalError
Str: Internal error:
00000000 00000000 00000000 00000000
Prc: APSS
Task:
Time: 00000000
R0: 00000000 R1: 00000000 R2: 00000000 R3: 00000000 R4: 00000000
R5: 00000000 R6: 00000000 R7: 00000000 R8: 00000000 R9: 00000000
R10: 00000000 R11: 00000000 R12: 00000000 R13: 00000000 R14: 00000000
PC: 00000000
CPSR: 00000000
Mod: Unknown
Ctr: ARM, IRQ dis,FIQ dis

TOS
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
BOS
ending QMI_IPA_INIT_MODEM_DRIVER_REQ_V01
<6>[ 15.638305] ipa-wan ipa3_handle_indication_req:154 not send indication
<3>[ 15.648607] ipa ipa3_uc_wdi_event_log_info_handler:357 WDI protocol missing 0x21
<3>[ 15.648648] ipa ipa3_uc_ntn_event_log_info_handler:33 NTN stats sz invalid exp=224 is=112
<6>[ 15.656886] QMI_IPA_INIT_MODEM_DRIVER_REQ_V01 response received
<5>[ 17.347120] audit: type=1325 audit(1732536094.711:2): table=mangle family=2 entries=6
<5>[ 17.385419] audit: type=1325 audit(1732536094.751:3): table=mangle family=2 entries=8
<5>[ 17.423777] audit: type=1325 audit(1732536094.791:4): table=mangle family=2 entries=9
<5>[ 17.437989] audit: type=1325 audit(1732536094.801:5): table=mangle family=2 entries=11
<3>[ 17.642444] ipa-wan ipa3_wwan_ioctl:2045 dev(rmnet_data0) register to IPA
<12>[ 19.590701] power_config: Starting powerconfig for SDX55:
<6>[ 19.686730] zram0: detected capacity change from 0 to 104857600
<6>[ 20.132709] Adding 102396k swap on /dev/zram0. Priority:-2 extents:1 across:102396k SS
<12>[ 20.133403] ++++ /etc/initscripts/power_config → ENABLE-FTRACE START
<6>[ 20.252183] coresight-tmc 6048000.tmc: TMC-ETR enabled
<6>[ 20.252365] coresight-dynamic-funnel 6b08000.funnel: FUNNEL inport 7 enabled
<6>[ 20.252388] coresight-dynamic-funnel 6045000.funnel: FUNNEL inport 0 enabled
<6>[ 20.252411] coresight-dynamic-funnel 6041000.funnel: FUNNEL inport 7 enabled
<6>[ 20.252493] coresight-stm 6002000.stm: STM tracing enabled
<12>[ 20.254963] ++++ /etc/initscripts/power_config → ENABLE-FTRACE END
<12>[ 20.255064] ++++ /etc/initscripts/power_config → ENABLE-DCC START
<3>[ 20.256689] msm-dcc 10a2000.dcc_v2: DCC list passed 2
<6>[ 20.256725] msm-dcc 10a2000.dcc_v2: All values written to enable
<12>[ 20.256828] ++++ /etc/initscripts/power_config → ENABLE-DCC END
<12>[ 20.256922] power_config: done
<12>[ 20.315286] syslog: Starting syslogd/klogd:
<12>[ 21.411447] syslog: done
<4>[ 22.482997] swi_netlink_data_ready: receive user pid:881, msg_cached:0
<3>[ 48.232573] Fatal error on modem!
<3>[ 48.232790] modem subsystem failure reason: nr5g_ml1_rfmgr_proc.c:2158:Assert nr_mode != NR5G_FR_SUB6 || carrier_def->sub6.bwps.rx_tx_arr[NR5G_ML1_RFMGR_RX_IDX].num_bwps failed: RFM_DEV::TUNE:PREP: No RX BWPs specified for carrier 0 in SUB6 mode.
<6>[ 48.235057] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = SYSTEM.
<3>[ 48.235419] Ramdump(ramdump_microdump_modem): No consumers. Aborting…
<6>[ 48.262894] microdump_modem_notifier_nb: do_ramdump() failed
<0>[ 48.370780] Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.
<4>[ 48.370902] CPU: 0 PID: 14 Comm: kworker/0:1 Tainted: G W 4.14.206 #1
<4>[ 48.378003] Hardware name: Qualcomm Technologies, Inc. SDXPRAIRIE (Flattened Device Tree)
<4>[ 48.385603] Workqueue: events device_restart_work_hdlr
<4>[ 48.393836] [] (unwind_backtrace) from [] (show_stack+0x1c/0x20)
<4>[ 48.398869] [] (show_stack) from [] (dump_stack+0x20/0x24)
<4>[ 48.406767] [] (dump_stack) from [] (panic+0x18c/0x3cc)
<4>[ 48.413795] [] (panic) from [] (subsys_remove_restart_order+0x0/0x88)
<4>[ 48.420664] [] (subsys_remove_restart_order) from [] (process_one_work+0x1a8/0x47c)
<4>[ 48.428996] [] (process_one_work) from [] (worker_thread+0x384/0x4f0)
<4>[ 48.438190] [] (worker_thread) from [] (kthread+0x158/0x160)
<4>[ 48.446521] [] (kthread) from [] (ret_from_fork+0x14/0x20)
<3>[ 48.462553] ipa ipa3_active_clients_panic_notifier:300
<3>[ 48.462553] ---- Active Clients Table ----
<3>[ 48.462553] FREEZE_VOTE 1 SPECIAL
<3>[ 48.462553] USB 1 SPECIAL
<3>[ 48.462553] TAG_PROCESS -1 SPECIAL
<3>[ 48.462553]
<3>[ 48.462553] Total active clients count: 2
<3>[ 48.462553]

OK

This is EM9190 module with older FW:

ati
Manufacturer: Sierra Wireless, Incorporated
Model: EM9190
Revision: SWIX55C_03.09.06.00 340b2d jenkins 2022/03/16 00:37:53
IMEI: 351735110105505
IMEI SV: 21
FSN: 4H0252003102AG
+GCAP: +CGSM

OK

Is this some known bug related to this older FW version or is this some general problem? If I return MIMO setting to 4x4, modem stops resetting itself.

15

Do you mean old FW 3.9.6.0 has problem and newer FW can switch between 2x2 and 4x4 mode?
BTW, why do you need to continuously switch between 2x2 and 4x4 mode?

16

Well, not really. I have made couple of switches between 2x2 and 4x4 with devices with both FW versions. Haven’t really counted how many times I have changed the configuration, maybe 4 or 5. But suddenly this device with older FW stopped accepting 2x2 mode.

I’m testing this because our customers are having varying amount of antennas in use. Just wanted to make sure that MIMO change works. If someone could verify that using 4x4 MIMO is preferred even when only two antennas are connected, then there wouldn’t be a need for changing MIMO mode at all. We could always go with 4x4 setting.

17

you may see if the newest FW still has this problem

18

I updated to version SWIX55C_03.14.10.04 and it seemed to solve the problem. I made several changes between 2x2 and 4x4 MIMO without problems.

We have been told by Sierra through our distributor that RFCID shouldn’t be changed on the field. But we haven’t got an explanation that why it shouldn’t be done. Is this problem with older FW version reason for not recommending it?

19

I guess product in the field will not frequently change number of antenna

20

No, it doesn’t. But when we deliver our product to our customer, we don’t know how many antennas will be used. And therefore we would like to have an option to configure MIMO accordingly on field.