Is this only happening to particular network operator?
Will there be any crash if no data channel establishment?
Will there be any crash if using mbim instead rmnet interface in at!usbcomp?
Do you see crash in linux pc?
Is this only happening to particular network operator?
Will there be any crash if no data channel establishment?
Will there be any crash if using mbim instead rmnet interface in at!usbcomp?
Do you see crash in linux pc?
Is this only happening to particular network operator?
we tested with three operators and all gave the some results
Will there be any crash if no data channel establishment?
I will check that
Will there be any crash if using mbim instead rmnet interface in at!usbcomp?
Do you see crash in linux pc?
No we didn’t test it in linux pc and we use qmi and never tried mbim
hello
I switched to mbim mode and there are a lot of firmware crashes
root@test201:~# atexecute ttyUSB2 “AT!GCDUMP”
AT!GCDUMP
Src: FatalError
File: sys_m_smsm_mpss.c
Line: 285
Str: APPS force stop
00000000 00000000 00000000 00000000
Prc: MPSS
Task: AMSS
Time: 0024362C
R0: 00000000 R1: C0046130 R2: EB102000 R3: 281E91A0 R4: 000000FE
R5: C3772C74 R6: 00000001 R7: 00000001 R8: C00A8770 R9: 018F0045
R10: 00000000 R11: C0110960 R12: C51B5000 R13: 281E91A0 R14: 9BD61E8D
R15: 00000186 R16: C51C61B2 R17: 00000000 R18: 00000000 R19: 00000000
R20: C004601C R21: 0000005A R22: 0000007F R23: 00000000 R24: 00000000
R25: 00000000 R26: 281E91A0 R27: C15697BC R28: 281A3430 SP: 281E8B98
FP: 281E8BA0 LR: C009F27C
PC: 4C92D40F
CPSR: 00000000
Mod: Unknown
TOS
281E8BC0 4C92D53B C0791580 0000005A 00000002 C49F9E28 C51C61B2
C51BC2B8 281E8BD0 4C92D40F C51C6194 C51BC2B8 281E8BF0 4CE23077
00000000 00000001 00000000 C49F9E28 C213CF84 FFFFFFFF 281E8C98
4DAA5B0B 00000000 0631340D C213CF68 00000000 C213CF84 FFFFFFFF
00000000 C49F9E28 C0791580 0000005A
BOS
App ver: SWI9X50C_01.14.13.00
Src: FatalError
Str: Recursive fault!
00000000 00000000 00000000 00000000
Prc: APSS
Task: C5170000
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: C516FEBC R12: 00000000 R13: C516FE90 R14: C0011DC4
PC: C001483C
CPSR: 00000000
Mod: Unknown
TOS
C0011DC4 0982D74D C001F1E8 00000023 C07BF984 C0E124F8 C0A1D204
00000000 001190D8 C516FF88 C001F298 00000000 00000023 C0A18DB4
C07BF984 00000001 C1067DF8 00000000 C07DD134 C516FF88 00000001
C0E9508C C65FB100 00000001 C013A994 C516FF88 001190D8 00000002
00000002 00000002 C50FEA80 001190D8
BOS
OK
but mbimcli respond without any issue (without stress test)
is it possible to connect to linux machine or windows machine?
is it possible to connect to linux machine or windows machine?
No and We need it to work with openwrt platform,
Now I work with mbim mode and the module never crashes until now, but
1- there are always firmware crashes (see below)
2- I saw that I can run qmi command while the module is in mbim mode is this normal behavior
AT!GCDUMP
Src: FatalError
File: sys_m_smsm_mpss.c
Line: 285
Str: APPQ force stO0
00000000 00000000 00000000 00000000
Prc: Unknown
Task: AMSS
Time: 000503A8
R0: 00000000 R1: C0046130 R2: EB102000 R3: C97E9120 R4: 0000007E
R5: C3772C74 R6: 00000001 R7: 00000000 R8: 400A8770 R9: 018F0045
R10: 00000000 R11: C0110960 R12: C11B5000 R13: CB7E91A0 R14: 78050471
R15: 00000086 R16: C51C41B2 R17: 00000000 R18: 00000000 R19: 00000000
R20: C004601C R21: 0000005A R22: 0000007F R23: 00000000 R24: 00000000
R25: 00000000 R26: CB7E90A0 R27: C15697BC R28: CB723410 SP: CB7E8B98
FP: CB7E8BA0 LR: C009F27C
PC: 1D780776
CPSR: 00000000
Mod: Unknown
TOS
CB7E8BC0 1C788640 C0791580 0000005A 00000002 C49F9E28 C51C61B2
C51BC298 C37E8BD0 1D788576 C51C6194 C51BC2B8 CB768BF0 1D08630E
00000000 00000001 00000000 C49F9E28 C213CF84 FFFFFFFF CB3E8C98
1C400872 00000000 0631340D C213CF68 00000000 C013CF84 DFFFEFFD
00000000 C49F9E08 C0791500 0000005A
BOS
App ver: SWI9X5C[ 1.14.!3.00
OK
yes, qmi message can run over mbim interface
I understand you need to work with openwrt, but if you can run in linux or windows, at least we can isolate if problem only exists in operwrt