Hello everyone,
Two of my Sara-R10M8S-00B-01 modules have their NVM reseting after every reboot. They both are running the 02.06,A00.01 firmware version.
Here are the commands through M-center, directly after boot. Please note that the results are the same whether I initialize the module or not.
The devices work as expected, however anything related to the NVM has been reset: APN, GPIO config, etc.
Does anyone have any clue on what could be causing this ?
Thanks,
Kilian
The AppNotes for that mention what/how to configure NVM storage here https://cdn.sparkfun.com/assets/f/c/7/3 … 09652_.pdf starting on page 8, and a bit scattered throughout - see if sending the suggested AT commands allow them to persist?
Thanks for the answer, however we were using these at commands from the beginning, I’ll post them again here:
AT+UPSV=1
AT+UPSV=1
OK
AT&W
AT&W
OK
AT&V
AT&V
ACTIVE PROFILE:
&C1, &D1, &K3, &S1, E1, Q0, V1, S2:043, S3:013, S4:010, S5:008,
+ICF:3,1, +IFC:2,2, +IPR:0,
+CMGF:0, +CNMI:1,0,0,0,0, +COPS:0,0,FFFFF, +UPSV:1,2000, +USTS:0
STORED PROFILE 0:
&C1, &D1, &K3, &S1, E1, Q0, V1, S2:043, S3:013, S4:010, S5:008,
+ICF:3,1, +IFC:2,2, +IPR:0,
+CMGF:0, +CNMI:1,0,0,0,0, +COPS:0,0,FFFFF, +UPSV:1,2000, +USTS:0
STORED PROFILE 1:
&C1, &D1, &K3, &S1, E1, Q0, V1, S2:043, S3:013, S4:010, S5:008,
+ICF:3,1, +IFC:2,2, +IPR:0,
+CMGF:0, +CNMI:1,0,0,0,0, +COPS:0,0,FFFFF, +UPSV:0, +USTS:0
OK
AT+CFUN=16
AT+CFUN=16
OK
AT&V
AT&V
ACTIVE PROFILE:
&C1, &D1, &K3, &S1, E1, Q0, V1, S2:043, S3:013, S4:010, S5:008,
+ICF:3,1, +IFC:2,2, +IPR:0,
+CMGF:0, +CNMI:1,0,0,0,0, +COPS:0,0,FFFFF, +UPSV:0, +USTS:0
STORED PROFILE 0:
&C1, &D1, &K3, &S1, E1, Q0, V1, S2:043, S3:013, S4:010, S5:008,
+ICF:3,1, +IFC:2,2, +IPR:0,
+CMGF:0, +CNMI:1,0,0,0,0, +COPS:0,0,FFFFF, +UPSV:0, +USTS:0
STORED PROFILE 1:
&C1, &D1, &K3, &S1, E1, Q0, V1, S2:043, S3:013, S4:010, S5:008,
+ICF:3,1, +IFC:2,2, +IPR:0,
+CMGF:0, +CNMI:1,0,0,0,0, +COPS:0,0,FFFFF, +UPSV:0, +USTS:0
OK
As you can see, it’s pretty clear that the NVM was erased at reboot, the power saving setting +UPSV:1,2000 in profile 0 is back to +UPSV:0.
We’ve tested this on our other working modules and as it should, the settings stored in profile 0 are still there, and the profile is active.