RC7620 registration problem

IoT Modules RC76
1

Hi,

I’m facing to a registration problem with a RC7620 module.
The module worked during a pre-production test phase.

Now, it cannot register to network. The response to the command AT+CREG? is +CREG: 0,0 and never goes to +CREG: 0,1.
The CFUN command reports +CFUN: 0 which is the minimum functionnality. It is impossible to set it to 1.

Here are my logs:

AT
AT
OK

AT&F
AT&F
OK

ATE0
ATE0
OK

AT+KSLEEP?
+KSLEEP: 2
OK

AT+CMEE=2
OK

AT+CREG?
+CREG: 0,0
OK

AT+CSQ
+CSQ: 99,99
OK

AT+KSRAT?
+KSRAT: 0
OK

AT+CPIN?
+CPIN: READY
OK

AT+CGMR
SWI9X07H_00.08.24.02 f90cbd jenkins 2022/03/21 03:47:54
OK

AT+CFUN?
+CFUN: 0
OK

AT+CFUN=1,0
+CME ERROR: operation not supported

AT+CFUN=1,1
OK

<< Reboot >>

AT+CFUN?
AT+CFUN?
+CFUN: 0
OK

What should I test now?

Regards,
Befaoim

2

What is the return of the following?

At!entercnd=“A710”
At!pcinfo?
At!impref?

3

Hi,

Sorry, the module works now. I just updated it again with the same firmware version.
Here is the log with the same firmware:

AT
AT
OK

AT&F
AT&F
OK

ATE0
ATE0
OK

AT+KSLEEP?
+KSLEEP: 2
OK

AT+CMEE=2
OK

AT+CREG?
+CREG: 0,1
OK

AT+CSQ
+CSQ: 19,99
OK

AT+KSRAT?
+KSRAT: 0
OK

AT+CPIN?
+CPIN: READY
OK

AT+CGMR
SWI9X07H_00.08.24.02 f90cbd jenkins 2022/03/21 03:47:54
OK

AT+CFUN?
+CFUN: 1
OK

AT+CFUN=1,0
OK

AT+CFUN=1,1
OK

<< Reboot >>

AT+CFUN?
AT+CFUN?
+CFUN: 1
OK

But just before the update, I did the At!pcinfo? command and the IMSWITCH value was ‘1’. Now it is ‘0’.

4

The module is working now but I would like to know how to prevent this state in the future.

5

How to reproduce the issue?

6

I don’t know how to reproduce the issue.
We’ll try to get that state with the previous failed module.

Btw, what is IMSWITCH?

7

Have you checked at!impref?

8

No I didn’t try it before flashing the firmware.

9

I suspect that is the problem

10

And how to avoid that?

11

i don’t know how you made it, so don’t know how to avoid

12

Hi Jyijyi,

I have a second module with the same behavior as explained above.
Here are the results of some AT command I didn’t execute:

AT!ENTERCND=“A710”

OK
At!pcinfo?

State: Low Power Mode
LPM voters - Temp:0, Volt:0, User:0, W_DISABLE:0, IMSWITCH:1, BIOS:0, LWM2M:0, OMADM:0, FOTA:0, RFCAL:0
LPM persistence - None

OK
At!impref?

!IMPREF:
preferred fw version: 00.08.07.00
preferred carrier name: GENERIC
preferred config name: GENERIC_001.081_000
preferred subpri index: 000
current fw version: 00.08.24.02
current carrier name: GENERIC
current config name: GENERIC_001.081_000
current subpri index: 000

fw version mismatch

OK

Do you have other command I can test now?

Best regards,
Befaoim

13

The carrier PRI file is not updated.
You can run the exe to upgrade firmware again

14

Thank you for the reply.

A customer discovered that problem because the GPS was not working.
After few tests, we saw the problem was similar to the previous module. I didn’t test the GPS on the other module before fixing it.

Before sending the product to the customer, the GSM / GPRS and GPS were tested and they were OK.
How it is possible that the carrier PRI is not good now? I suppose it was OK during our tests.

15

Did they do firmware change?

16

No, they don’t have access to the modem itself.

We did the upgrade when the module was entering in the production phase. Before our plan test.
Is it possible to lose or corrupt the carrier PRI?

17

could you type the following and compare with a working module?

AT!entercnd=“A710”
AT!flog?

BTW, do you have a history on what commands have been entered?
e.g. AT!RMARESET?

18

Here are the AT commands we are using:

AT!MUXMODE=1
AT+KSLEEP=2
AT+CMEE=2
AT+CPWROFF
AT!IIC=0…
AT!IIC=1…
AT!GPSAUTOSTART=0
AT!GPSTRACK=1,…
AT!GPSLOC?
AT+KGSN=3
AT+KSRAT=0
AT+COPS?
AT+CGDCONT=1
AT+CGDCONT=1,…
AT+CGATT=1
AT+KPATTERN=…
AT+KCNXCFG=1,…
AT+KCNXTIMER=1,…
AT+KCNXPROFILE=1
AT+CGATT=0
AT+KTCPSTAT=…
AT+KTCPCNX=…
AT+KTCPCFG=1,…
AT+KURCCFG=TCP,0,0
AT+KTCPCLOSE=…
AT+KTCPDEL=…
AT+KTCPSND=…
AT+KTCPRCV=…
AT+KCERTDELETE=…
AT+KCERTSTORE=…

We don’t use special command with password access.

Please find the AT!flog results files for 2 modules.
The module with problem is very slow to print the log. The information are outputted by small amount of text.

RC7620_Bricked_module.txt (8.7 KB)
RC7620_working_module.txt (6.1 KB)

19

In the bricked one, seems there is problem when download to the new firmware

00:00:00.000,H0082402,CRASH=MPSS,FILE=fs_device.c,LINE=401,STR=[-2095636730] Unexpected device read failure,TASK=AMSS,VER=SWI9X07H_00.08.24.02
00000,1980/01/06 00:00:00.000,H0082402,CRASH=Unknown,FILE=,LINE=0,STR=,TASK=,VER=

20

Why did it work?
In the test, we got the module GPS coordinate and the CREG, CSQ…
Now, it doesn’t work anymore.

And the previous module worked well once after firmware update.
After that, it failed until I updated the firmware again.