gobi 3000 mc8355 error: couldn't set FCC auth

ITwrx Info info at itwrx.org
Wed Aug 17 15:46:42 UTC 2016



On 08/17/2016 10:08 AM, Bjørn Mork wrote:
> "ITwrx.org" <info at itwrx.org> writes:
>
>> my MM debug log is here:  http://pastebin.com/ev8TGi8J
>
> OK, so that detects the sw radio off state and runs the FCC auth logic
> as it is supposed to.  But the result indicates this is not the issue:
>
> ModemManager[1109]: [/dev/cdc-wdm0] Received MBIM message
> ModemManager[1109]: [/dev/cdc-wdm0] Received message...
>>>>>>> RAW:
>>>>>>>    length = 20
>>>>>>>    data   = 01:13:00:80:02:04:02:01:00:5F:55:07:00:02:04:00:01:00:1A:00
> ModemManager[1109]: [/dev/cdc-wdm0] Received message (translated)...
>>>>>>> QMUX:
>>>>>>>    length  = 19
>>>>>>>    flags   = 0x80
>>>>>>>    service = "dms"
>>>>>>>    client  = 4
>>>>>>> QMI:
>>>>>>>    flags       = "response"
>>>>>>>    transaction = 1
>>>>>>>    tlv_length  = 7
>>>>>>>    message     = "Set FCC Authentication" (0x555F)
>>>>>>> TLV:
>>>>>>>    type       = "Result" (0x02)
>>>>>>>    length     = 4
>>>>>>>    value      = 01:00:1A:00
>>>>>>>    translated = FAILURE: NoEffect
> ModemManager[1109]: error: couldn't set FCC auth: QMI protocol error (26): 'NoEffect'
my reading of the log is that it tried to set the fcc auth but failed. 
to me that doesn't necessarily mean it's not the issue, but i don't 
know. that's just my reading of it from a layman's perspective.
>
>
> Are you sure your modem requires FCC auth?
no.
> Are you sure there aren't
> enywhting else keeping it in radio off state?
no. there very well may be but i don't know what.
> Typically that would a
> "missing" firmware image, as required by your operator settings.
this was the only guess i had too. i don't know what firmware i may need 
or where to get it or how to load it. gobi-loader and gobi-firmware were 
the only things i found but they appear to be for gobi 2000 and 1000.
>
> Hmm, you don't have any AT command port enabled, do you?
not that i'm aware of.
> A look at the
> "AT!PCINFO?" output would be most useful...  Not to mention the
> "AT!PCFCCAUTH?" I've just learned about.
>
> But failing that, could you try this:
those commands failed to produce any results.
>
>   qmicli -p -d /dev/cdc-wdm0 --device-open-mbim  --dms-list-stored-images
[/dev/cdc-wdm0] Device list of stored images retrieved:

     [0] Type:    'modem'
         Maximum: '6'

         >>>>>>>>>> [CURRENT] <<<<<<<<<<
         [modem0]
         Unique ID: '8A:6F:98:CD:F2:68:3A:45:97:E0:E8:F2:90:03:1B:F1'
         Build ID:      'D3200-SCAUTNZ-331425XN02'
         Storage index: '0'
         Failure count: '0'

>
>
> Maybe we can guess the issue... Or maybe I'm completely lost as usual...
>
>
>
> Bjørn
>
not as lost as me. :) thanks


More information about the ModemManager-devel mailing list