On 2017-11-23, Paul B. Henson <hen...@acm.org> wrote: > SIM not initialized PIN required
>From my post at https://www.mail-archive.com/tech@openbsd.org/msg32396.html, : The description in the spec for the state which triggers this : message is, : : "The operation failed because the device is : in the process of initializing. Retry the : operation after the ReadyState of the device : changes to MBIMSubscriberReadyStateInitialized." > Under linux, the serial control interfaces were available as USB devices > so you could poke at the card with AT commands, I don't see any listed > booted under openbsd. The umb driver doesn't support accessing the card > directly for debugging and diagnostics? Correct, you can't get at those from OpenBSD atm. On 2017-11-23, Paul B. Henson <hen...@acm.org> wrote: > Looking at the source code, I see that there's an workaround for the > EM7455 card, something about requiring an "FCC Authentication" command? > From what I understand the MC7455 is the same as the EM7455 other than > form factor, so I added it to the list for that workaround and also > turned on debugging in the driver. Here's what it has to say now: > > Jul 23 18:12:41 maggie /bsd: umb0 at uhub2 port 3 configuration 1 > interface 12 "Sierra Wireless, Inc > orporated Sierra Wireless MC7455 Qualcomm\M-. Snapdragon? X7 LTE-A" rev > 2.10/0.06 addr 3 > Jul 23 18:12:41 maggie /bsd: umb0: ctrl_len=4096, maxpktlen=1422, > cap=0x20 > Jul 23 18:12:41 maggie /bsd: umb0: ctrl-ifno#12: ep-ctrl=5, > data-ifno#13: ep-rx=4, ep-tx=3 > Jul 23 18:12:41 maggie /bsd: umb0: rx/tx size 16384/16384 > Jul 23 18:12:41 maggie /bsd: umb0: -> snd MBIM_OPEN_MSG (tid 1) > Jul 23 18:12:41 maggie /bsd: umb0: sent MBIM_OPEN_MSG (tid 1) > Jul 23 18:12:41 maggie /bsd: 0: 01 00 00 00 10 00 00 00 01 00 00 00 > 00 10 00 00 > Jul 23 18:12:41 maggie /bsd: umb0: vers 1.0 > Jul 23 18:12:41 maggie /bsd: ugen0 at uhub2 port 3 configuration 1 > "Sierra Wireless, Incorporated Si > erra Wireless MC7455 Qualcomm\M-. Snapdragon? X7 LTE-A" rev 2.10/0.06 > addr 3 > > > Jul 23 18:13:31 maggie /bsd: umb0: stop: reached state DOWN > Jul 23 18:13:59 maggie /bsd: umb0: init: opening ... > Jul 23 18:13:59 maggie /bsd: umb0: -> snd MBIM_OPEN_MSG (tid 2) > Jul 23 18:13:59 maggie /bsd: umb0: sent MBIM_OPEN_MSG (tid 2) > Jul 23 18:13:59 maggie /bsd: 0: 01 00 00 00 10 00 00 00 02 00 00 00 > 00 10 00 00 > Jul 23 18:14:29 maggie /bsd: umb0: state change timeout > Jul 23 18:14:29 maggie /bsd: umb0: init: opening ... > Jul 23 18:14:29 maggie /bsd: umb0: -> snd MBIM_OPEN_MSG (tid 3) > Jul 23 18:14:29 maggie /bsd: umb0: sent MBIM_OPEN_MSG (tid 3) > Jul 23 18:14:29 maggie /bsd: 0: 01 00 00 00 10 00 00 00 03 00 00 00 > 00 10 00 00 > Jul 23 18:14:59 maggie /bsd: umb0: state change timeout > > Not sure where to go from here. I don't have it handy to check now, but IIRC that's similar to what I see on MC8805 after adding the ID for fcc auth.
