So far so good, is it possible to permanently disable this “feature”? I have another EM7455 which does not require this procedure, so it is possible somehow.
What is the result of AT!PCOFFEN?. you can see from the AT guide that modem will enter into low power mode when ‘W_DISABLE’ is asserted. Is this the case for you??
what exactly is this command? Even I didn’t hear about this command earlier…
@fs1: Yes… I tried the mentioned steps when my module was in Low power mode with ‘W_DISABLE’. If you succeeded in recovering the module, let me know the steps
Yes, the PRI is irrelevant. The NV setting you are looking for is written as part of the OEM vendor config. If you download the firmware package from whatever OEM vendor you got this modem from and unpack it, then you will find 3 different firmware parts (multiplied by the number of supported operators):
the actual firmware image, for example SWI9X30C_02.08.02.00.cwe
the operator specific NV settings and other operator files (PRI), for example SWI9X30C_02.08.02.00_GENERIC_002.007_000.nvu
the OEM specific NV settings, for example 1102662_9905046_EM7455_02.05.07.00_00_Lenovo-Laptop_001.003_000.nvu
The latter will contain the FCC auth related setting. I have not tried, so I cannot tell you whether the variable can be changed. But I believe it is likely if you know how to create or modify .nvu files. It might also be possible using other NVRAM modification methods. I don’t know…
Note that all three file types mentioned above are containers with an aribtratry number of different files and/or images. The firmware is responsible for unpacking them and interpreting the files within, and e.g. apply specific files as NVRAM variable updates given some condition. Exactly how this is done, the restrictions that apply and other necessary info, is probably only documented internally. Or possibly to OEM vendors as well? Regular end users like us don’t have access to it. But we can always guess
Yes, I believe that is by design. It is Non-Volatile…
You have to actively disable the setting. The regular NVU files won’t do that. And you might also have to replace the OEM NVUP file? That might also be persistent if written to flash before. I don’t know.
Unfortunateley I have no idea on how to do that, I flashed all available files from the source.
You might wonder why I want this, with the FCC I can’t use the modem in MBIM mode. I can’t send the FCC authentication.
Switching from MBIM to QMI, then load the GobiNet driver helps, but I can’t change back to MBIM without resetting the device, which in turn will reactivate the FCC.
It would be great to know whether the tip from Rex_alex works.
But just FYI in case it doesn’t: You can send the QMI FCC auth request in MBIM mode. Look at how it is implemented in ModemManager/libqmi/libmbim. This Just Works with the recently released ModemManager 1.6.
Thank you for this post, I can’t get into the “engenering” mode with at!unlock, I think this may be a challegene-response sequence. As it changes with every at!unlock? command.
AT!OPENLOCK?
6FF19EEBB325DB2D
OK
AT!OPENLOCK="CFE6B46892423A75"
ERROR