Huawei E392 firmware crash caused by MM issuing "AT*CNTI=2"

[Aleksander Morgado]

On 18/11/13 23:30, Dan Williams wrote:
> On Mon, 2013-11-18 at 22:44 +0100, Thomas Schäfer wrote:
>> Am Montag, 18. November 2013, 11:21:05 schrieb Dan Williams:
>>> On Mon, 2013-11-18 at 09:55 +0100, Bjørn Mork wrote:
>>
>>>> And sure enough: Trying "AT*CNTI=2" (after enabling the SIM with
>>>> AT+CPIN=....) in minicom makes the firmware crash, every time.
>>>>
>>
>> I did not try the pre condition at+cpin, because I work with disabled PIN
>>
>>>
>>> My E397 and E392 *do* implement CNTI=2 and do not crash, but they fail
>>> to report LTE capabilities in the command.  
>>
>> I can confirm this for the E398.
>>
>> At other devices I get only "error" and "command not support", but no crash.
> 
> For the record, my E392u-92 is running firmware 11.836.13.00.76.  But
> anyway, if CNTI=2 crashes some Huawei devices, and those Huawei devices
> that don't crash lie in their CNTI=2 response like mine and Thomas' do,
> then we should just skip CNTI=2 for Huawei in general.
> 

Great timing! The 'aleksander/huawei-modes' branch upstream that I wrote
during last weeks re-implements Huawei's load_supported_modes() by using
only ^PREFMODE, ^SYSCFG and ^SYSCFGEX; i.e. it won't use parent's
load_supported_modes (and therefore no *CNTI=2 or WS46=?).

Can you guys test with that branch to see if your devices crash or not?


-- 
Aleksander