Qualcomm Gobi 2000 Modem Issues

Qualcomm Gobi 2000 Modem Issues

[Kai Scharwies]

[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]

Hi everyone.

I ran into two issues trying to setup a data connection with a Gobi 2000 card.
The first one seems to be an error regarding simcard onlocking. After
enabling the modem test/list-modems shows the following, despite the
simcard is inserted correctly:

[ /gobi0 ]
    Features = sim
    Emergency = 0
    Powered = 1
    Lockdown = 0
    Interfaces = org.ofono.SimManager
    Online = 0
    Model = Qualcomm Gobi 2000
    Revision = D1025-STUTABGD-3600  1  [Jan 14 2010 14:00:00]
    Serial = 353093033460401
    Manufacturer = Qualcomm Incorporated
    [ org.ofono.SimManager ]
        Present = 0

Our current workaround is quitting ofono and using minicom to unlock
the sim directly, then restarting ofono.
> at+cpin?
+CPIN: SIM PIN
OK

> at+cpin="1234"
OK
$QCSIMSTAT: 1 SIM INIT COMPLETED

The second issue is not being able to activate an internet context:
(Network registration and attachment is alright)

test/enable-modem
Connecting modem /gobi0...
test/online-modem
Setting modem /gobi0 online...
test/list-contexts
[ /gobi0 ]
    [ /gobi0/context1 ]
        Username =
        Protocol = ip
        Name = Internet
        Settings = { }
        IPv6.Settings = { }
        Active = 0
        AccessPointName = internet.t-mobile
        Password =
        Type = internet

test/activate-context
Error activating /gobi0/context1: org.ofono.Error.NotImplemented:
Implementation not provided

If you could give me a little assisting on where to look, maybe I
would be able to contribute patches, too.

Best regards,
Kai

RE: Qualcomm Gobi 2000 Modem Issues

[Aygon, Bertrand]

[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]

Hi,

>test/activate-context
>Error activating /gobi0/context1: org.ofono.Error.NotImplemented:
>Implementation not provided
>
>If you could give me a little assisting on where to look, maybe I
>would be able to contribute patches, too.

This second issue looks like an issue reported a couple of days ago.

Can you please check in oFono logs if there is not something like this:

ofonod[2329]: drivers/atmodem/gprs-context.c:at_gprs_context_probe()
ofonod[2329]: Missing support for TUN/TAP devices

And if so, it means that your kernel doesn't have support for TUN enabled.

Regards,

Bertrand.
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Re: Qualcomm Gobi 2000 Modem Issues

[Marcel Holtmann]

[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]

Hi Kai,

> I ran into two issues trying to setup a data connection with a Gobi 2000 card.
> The first one seems to be an error regarding simcard onlocking. After
> enabling the modem test/list-modems shows the following, despite the
> simcard is inserted correctly:
> 
> [ /gobi0 ]
>     Features = sim
>     Emergency = 0
>     Powered = 1
>     Lockdown = 0
>     Interfaces = org.ofono.SimManager
>     Online = 0
>     Model = Qualcomm Gobi 2000
>     Revision = D1025-STUTABGD-3600  1  [Jan 14 2010 14:00:00]
>     Serial = 353093033460401
>     Manufacturer = Qualcomm Incorporated
>     [ org.ofono.SimManager ]
>         Present = 0
> 
> Our current workaround is quitting ofono and using minicom to unlock
> the sim directly, then restarting ofono.
> > at+cpin?
> +CPIN: SIM PIN
> OK
> 
> > at+cpin="1234"
> OK
> $QCSIMSTAT: 1 SIM INIT COMPLETED

this is weird since the PIN unlocking should just work fine. Have you
tried to use the test/enter-pin script?

> The second issue is not being able to activate an internet context:
> (Network registration and attachment is alright)
> 
> test/enable-modem
> Connecting modem /gobi0...
> test/online-modem
> Setting modem /gobi0 online...
> test/list-contexts
> [ /gobi0 ]
>     [ /gobi0/context1 ]
>         Username =
>         Protocol = ip
>         Name = Internet
>         Settings = { }
>         IPv6.Settings = { }
>         Active = 0
>         AccessPointName = internet.t-mobile
>         Password =
>         Type = internet
> 
> test/activate-context
> Error activating /gobi0/context1: org.ofono.Error.NotImplemented:
> Implementation not provided
> 
> If you could give me a little assisting on where to look, maybe I
> would be able to contribute patches, too.

Of course this does not work. Check doc/hardware-support.txt for
supported modem and supported capabilities.

Until Qualcomm gives us the chance to implement QMI properly, we are a
bit out of luck with just one AT command channel. You need at least two
AT command channel to run oFono properly.

Regards

Marcel

Re: Qualcomm Gobi 2000 Modem Issues

[Kai Scharwies]

[-- Attachment #1: Type: text/plain, Size: 6272 bytes --]

2011/4/7 Marcel Holtmann <marcel@holtmann.org>:
> Hi Kai,
>
>> I ran into two issues trying to setup a data connection with a Gobi 2000 card.
>> The first one seems to be an error regarding simcard onlocking. After
>> enabling the modem test/list-modems shows the following, despite the
>> simcard is inserted correctly:
>>
>> [ /gobi0 ]
>>     Features = sim
>>     Emergency = 0
>>     Powered = 1
>>     Lockdown = 0
>>     Interfaces = org.ofono.SimManager
>>     Online = 0
>>     Model = Qualcomm Gobi 2000
>>     Revision = D1025-STUTABGD-3600  1  [Jan 14 2010 14:00:00]
>>     Serial = 353093033460401
>>     Manufacturer = Qualcomm Incorporated
>>     [ org.ofono.SimManager ]
>>         Present = 0
>>
>> Our current workaround is quitting ofono and using minicom to unlock
>> the sim directly, then restarting ofono.
>> > at+cpin?
>> +CPIN: SIM PIN
>> OK
>>
>> > at+cpin="1234"
>> OK
>> $QCSIMSTAT: 1 SIM INIT COMPLETED
>
> this is weird since the PIN unlocking should just work fine. Have you
> tried to use the test/enter-pin script?

Yes, I tried the enter-pin script. Using it without the optional PATH
this is the error:
dbus.exceptions.DBusException: org.ofono.Error.InvalidFormat: Argument
format is not recognized

Entering 'test/enter-pin /generic pin 1234' resultis in:
dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.UnknownMethod: Method "EnterPin" with
signature "ss" on interface "org.ofono.SimManager" doesn't exist

The problem is ofono not detecting the sim card properly since
'list-modems' shows:
    [ org.ofono.SimManager ]
        Present = 0

What it should look like is this (Output after unlocking via AT
commands, described above):
    [ org.ofono.SimManager ]
        Retries =
        MobileCountryCode = 262
        FixedDialing = 0
        SubscriberNumbers =
        PreferredLanguages = de en
        BarredDialing = 0
        CardIdentifier = 89490200000622126220
        LockedPins =
        MobileNetworkCode = 01
        SubscriberIdentity = 262019038101028
        Present = 1
        PinRequired = none

PinRequired should of course read "pin" before unlocking.
Anymore logs I could deliver to solve this issue?

>
>> The second issue is not being able to activate an internet context:
>> (Network registration and attachment is alright)
>>
>> test/enable-modem
>> Connecting modem /gobi0...
>> test/online-modem
>> Setting modem /gobi0 online...
>> test/list-contexts
>> [ /gobi0 ]
>>     [ /gobi0/context1 ]
>>         Username =
>>         Protocol = ip
>>         Name = Internet
>>         Settings = { }
>>         IPv6.Settings = { }
>>         Active = 0
>>         AccessPointName = internet.t-mobile
>>         Password =
>>         Type = internet
>>
>> test/activate-context
>> Error activating /gobi0/context1: org.ofono.Error.NotImplemented:
>> Implementation not provided
>>
>> If you could give me a little assisting on where to look, maybe I
>> would be able to contribute patches, too.
>
> Of course this does not work. Check doc/hardware-support.txt for
> supported modem and supported capabilities.
>
> Until Qualcomm gives us the chance to implement QMI properly, we are a
> bit out of luck with just one AT command channel. You need at least two
> AT command channel to run oFono properly.
>

I missed reading that document.
However I don't understand why you would need QMI for setting up a PPP
connection, since there are infact three AT command channels, not one,
if I understand the log correctly:

ofonod[2844]: src/modem.c:ofono_modem_create() name: (null), type: gobi
ofonod[2844]: src/modem.c:set_modem_property() modem 0x8dcb268 property Path
ofonod[2844]: src/modem.c:set_modem_property() modem 0x8dcb268
property Registered
ofonod[2844]: plugins/udev.c:add_modem()
/devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.1/ttyUSB3/tty/ttyUSB3
(gobi)
ofonod[2844]: plugins/udev.c:add_gobi() modem 0x8dcb268
ofonod[2844]: src/modem.c:get_modem_property() modem 0x8dcb268 property Path
ofonod[2844]: plugins/udev.c:add_modem()
/devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.2/ttyUSB4/tty/ttyUSB4
(gobi)
ofonod[2844]: plugins/udev.c:add_gobi() modem 0x8dcb268
ofonod[2844]: src/modem.c:set_modem_property() modem 0x8dcb268 property Device
ofonod[2844]: plugins/gobi.c:gobi_probe() 0x8dcb268
ofonod[2844]: plugins/hfp_ag.c:modem_watch() modem: 0x8dcb268, added: 1
ofonod[2844]: plugins/dun_gw.c:modem_watch() modem: 0x8dcb268, added: 1
ofonod[2844]: plugins/smart-messaging.c:modem_watch() modem: 0x8dcb268, added: 1
ofonod[2844]: plugins/push-notification.c:modem_watch() modem:
0x8dcb268, added: 1
ofonod[2844]: src/modem.c:get_modem_property() modem 0x8dcb268 property Path
ofonod[2844]: plugins/udev.c:add_modem()
/devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.3/ttyUSB5/tty/ttyUSB5
(gobi)
ofonod[2844]: plugins/udev.c:add_gobi() modem 0x8dcb268
ofonod[2844]: plugins/gobi.c:gobi_enable() 0x8dcb268
ofonod[2844]: src/modem.c:get_modem_property() modem 0x8dcb268 property Device
ofonod[2844]: plugins/gobi.c:open_device() Device /dev/ttyUSB4
ofonod[2844]: plugins/gobi.c:cfun_enable()
ofonod[2844]: src/modem.c:modem_change_state() old state: 0, new state: 1
ofonod[2844]: plugins/gobi.c:gobi_pre_sim() 0x8dcb268
ofonod[2844]: src/modem.c:modem_change_state() old state: 1, new state: 2
ofonod[2844]: plugins/gobi.c:gobi_post_sim() 0x8dcb268
ofonod[2844]: src/sim.c:ofono_sim_add_state_watch() 0x8dc8900
ofonod[2844]: src/sim.c:ofono_sim_add_state_watch() 0x8dc8900
ofonod[2844]: Phonebook not supported by this modem.  If this is in
error please submit patches to support this hardware
ofonod[2844]: src/phonebook.c:phonebook_remove() atom: 0x8dc5498
ofonod[2844]: SMS not supported by this modem.  If this is in error
please submit patches to support this hardware
ofonod[2844]: src/sms.c:sms_remove() atom: 0x8dca430
ofonod[2844]: plugins/gobi.c:simstat_notify() state UNKNOWN

The other hint looking for missing TUN/TAP support is not an issue.
Using e.g. OpenVPN I definetly have the support enabled and the logs
didn't mention the error.

Best regards,
Kai

Re: Qualcomm Gobi 2000 Modem Issues

[Marcel Holtmann]

[-- Attachment #1: Type: text/plain, Size: 5062 bytes --]

Hi Kai,

> >> I ran into two issues trying to setup a data connection with a Gobi 2000 card.
> >> The first one seems to be an error regarding simcard onlocking. After
> >> enabling the modem test/list-modems shows the following, despite the
> >> simcard is inserted correctly:
> >>
> >> [ /gobi0 ]
> >>     Features = sim
> >>     Emergency = 0
> >>     Powered = 1
> >>     Lockdown = 0
> >>     Interfaces = org.ofono.SimManager
> >>     Online = 0
> >>     Model = Qualcomm Gobi 2000
> >>     Revision = D1025-STUTABGD-3600  1  [Jan 14 2010 14:00:00]
> >>     Serial = 353093033460401
> >>     Manufacturer = Qualcomm Incorporated
> >>     [ org.ofono.SimManager ]
> >>         Present = 0
> >>
> >> Our current workaround is quitting ofono and using minicom to unlock
> >> the sim directly, then restarting ofono.
> >> > at+cpin?
> >> +CPIN: SIM PIN
> >> OK
> >>
> >> > at+cpin="1234"
> >> OK
> >> $QCSIMSTAT: 1 SIM INIT COMPLETED
> >
> > this is weird since the PIN unlocking should just work fine. Have you
> > tried to use the test/enter-pin script?
> 
> Yes, I tried the enter-pin script. Using it without the optional PATH
> this is the error:
> dbus.exceptions.DBusException: org.ofono.Error.InvalidFormat: Argument
> format is not recognized
> 
> Entering 'test/enter-pin /generic pin 1234' resultis in:
> dbus.exceptions.DBusException:
> org.freedesktop.DBus.Error.UnknownMethod: Method "EnterPin" with
> signature "ss" on interface "org.ofono.SimManager" doesn't exist
> 
> The problem is ofono not detecting the sim card properly since
> 'list-modems' shows:
>     [ org.ofono.SimManager ]
>         Present = 0

this is clearly a bug in the Gobi plugin then. It does not detect the
SIM card properly. So you need to dig a bit into plugins/gobi.c and
figure out how to fix it.

> >> The second issue is not being able to activate an internet context:
> >> (Network registration and attachment is alright)
> >>
> >> test/enable-modem
> >> Connecting modem /gobi0...
> >> test/online-modem
> >> Setting modem /gobi0 online...
> >> test/list-contexts
> >> [ /gobi0 ]
> >>     [ /gobi0/context1 ]
> >>         Username =
> >>         Protocol = ip
> >>         Name = Internet
> >>         Settings = { }
> >>         IPv6.Settings = { }
> >>         Active = 0
> >>         AccessPointName = internet.t-mobile
> >>         Password =
> >>         Type = internet
> >>
> >> test/activate-context
> >> Error activating /gobi0/context1: org.ofono.Error.NotImplemented:
> >> Implementation not provided
> >>
> >> If you could give me a little assisting on where to look, maybe I
> >> would be able to contribute patches, too.
> >
> > Of course this does not work. Check doc/hardware-support.txt for
> > supported modem and supported capabilities.
> >
> > Until Qualcomm gives us the chance to implement QMI properly, we are a
> > bit out of luck with just one AT command channel. You need at least two
> > AT command channel to run oFono properly.
> >
> 
> I missed reading that document.
> However I don't understand why you would need QMI for setting up a PPP
> connection, since there are infact three AT command channels, not one,
> if I understand the log correctly:
> 
> ofonod[2844]: src/modem.c:ofono_modem_create() name: (null), type: gobi
> ofonod[2844]: src/modem.c:set_modem_property() modem 0x8dcb268 property Path
> ofonod[2844]: src/modem.c:set_modem_property() modem 0x8dcb268
> property Registered
> ofonod[2844]: plugins/udev.c:add_modem()
> /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.1/ttyUSB3/tty/ttyUSB3
> (gobi)
> ofonod[2844]: plugins/udev.c:add_gobi() modem 0x8dcb268
> ofonod[2844]: src/modem.c:get_modem_property() modem 0x8dcb268 property Path
> ofonod[2844]: plugins/udev.c:add_modem()
> /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.2/ttyUSB4/tty/ttyUSB4
> (gobi)
> ofonod[2844]: plugins/udev.c:add_gobi() modem 0x8dcb268
> ofonod[2844]: src/modem.c:set_modem_property() modem 0x8dcb268 property Device
> ofonod[2844]: plugins/gobi.c:gobi_probe() 0x8dcb268
> ofonod[2844]: plugins/hfp_ag.c:modem_watch() modem: 0x8dcb268, added: 1
> ofonod[2844]: plugins/dun_gw.c:modem_watch() modem: 0x8dcb268, added: 1
> ofonod[2844]: plugins/smart-messaging.c:modem_watch() modem: 0x8dcb268, added: 1
> ofonod[2844]: plugins/push-notification.c:modem_watch() modem:
> 0x8dcb268, added: 1
> ofonod[2844]: src/modem.c:get_modem_property() modem 0x8dcb268 property Path
> ofonod[2844]: plugins/udev.c:add_modem()
> /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.3/ttyUSB5/tty/ttyUSB5
> (gobi)

This means that there are 3 TTYs exposed by the Gobi card. This does not
mean that these are all AT modem capable ports. In fact they are not.
Check /proc/bus/usb/devices and see what driver got loaded for what USB
interface. All the qcaux bound interfaces are not really helpful.

But if you by accident have a Gobi firmware that exposes 2 real AT
command ports, I like to hear about it.

Regards

Marcel

Re: Qualcomm Gobi 2000 Modem Issues

[Kai Scharwies]

[-- Attachment #1: Type: text/plain, Size: 6054 bytes --]

2011/4/8 Marcel Holtmann <marcel@holtmann.org>:
> Hi Kai,
>
>> >> I ran into two issues trying to setup a data connection with a Gobi 2000 card.
>> >> The first one seems to be an error regarding simcard onlocking. After
>> >> enabling the modem test/list-modems shows the following, despite the
>> >> simcard is inserted correctly:
>> >>
>> >> [ /gobi0 ]
>> >>     Features = sim
>> >>     Emergency = 0
>> >>     Powered = 1
>> >>     Lockdown = 0
>> >>     Interfaces = org.ofono.SimManager
>> >>     Online = 0
>> >>     Model = Qualcomm Gobi 2000
>> >>     Revision = D1025-STUTABGD-3600  1  [Jan 14 2010 14:00:00]
>> >>     Serial = 353093033460401
>> >>     Manufacturer = Qualcomm Incorporated
>> >>     [ org.ofono.SimManager ]
>> >>         Present = 0
>> >>
>> >> Our current workaround is quitting ofono and using minicom to unlock
>> >> the sim directly, then restarting ofono.
>> >> > at+cpin?
>> >> +CPIN: SIM PIN
>> >> OK
>> >>
>> >> > at+cpin="1234"
>> >> OK
>> >> $QCSIMSTAT: 1 SIM INIT COMPLETED
>> >
>> > this is weird since the PIN unlocking should just work fine. Have you
>> > tried to use the test/enter-pin script?
>>
>> Yes, I tried the enter-pin script. Using it without the optional PATH
>> this is the error:
>> dbus.exceptions.DBusException: org.ofono.Error.InvalidFormat: Argument
>> format is not recognized
>>
>> Entering 'test/enter-pin /generic pin 1234' resultis in:
>> dbus.exceptions.DBusException:
>> org.freedesktop.DBus.Error.UnknownMethod: Method "EnterPin" with
>> signature "ss" on interface "org.ofono.SimManager" doesn't exist
>>
>> The problem is ofono not detecting the sim card properly since
>> 'list-modems' shows:
>>     [ org.ofono.SimManager ]
>>         Present = 0
>
> this is clearly a bug in the Gobi plugin then. It does not detect the
> SIM card properly. So you need to dig a bit into plugins/gobi.c and
> figure out how to fix it.
>

I would like to do that, but having trouble with the code, especially
because I couldn't find any documentation on AT$QCSIMSTAT and
code-documentation in gobi.c is virtually not present.
Maybe someone can help here.

Again, the problem is, that the modem responds "$QCSIMSTAT: 1,UNKNOWN"
instead of "$QCSIMSTAT: 1 SIM INIT COMPLETED" when "AT$QCSIMSTAT?" is
sent.

>> >> The second issue is not being able to activate an internet context:
>> >> (Network registration and attachment is alright)
>> >>
>> >> test/enable-modem
>> >> Connecting modem /gobi0...
>> >> test/online-modem
>> >> Setting modem /gobi0 online...
>> >> test/list-contexts
>> >> [ /gobi0 ]
>> >>     [ /gobi0/context1 ]
>> >>         Username =
>> >>         Protocol = ip
>> >>         Name = Internet
>> >>         Settings = { }
>> >>         IPv6.Settings = { }
>> >>         Active = 0
>> >>         AccessPointName = internet.t-mobile
>> >>         Password =
>> >>         Type = internet
>> >>
>> >> test/activate-context
>> >> Error activating /gobi0/context1: org.ofono.Error.NotImplemented:
>> >> Implementation not provided
>> >>
>> >> If you could give me a little assisting on where to look, maybe I
>> >> would be able to contribute patches, too.
>> >
>> > Of course this does not work. Check doc/hardware-support.txt for
>> > supported modem and supported capabilities.
>> >
>> > Until Qualcomm gives us the chance to implement QMI properly, we are a
>> > bit out of luck with just one AT command channel. You need at least two
>> > AT command channel to run oFono properly.
>> >
>>
>> I missed reading that document.
>> However I don't understand why you would need QMI for setting up a PPP
>> connection, since there are infact three AT command channels, not one,
>> if I understand the log correctly:
>>
>> ofonod[2844]: src/modem.c:ofono_modem_create() name: (null), type: gobi
>> ofonod[2844]: src/modem.c:set_modem_property() modem 0x8dcb268 property Path
>> ofonod[2844]: src/modem.c:set_modem_property() modem 0x8dcb268
>> property Registered
>> ofonod[2844]: plugins/udev.c:add_modem()
>> /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.1/ttyUSB3/tty/ttyUSB3
>> (gobi)
>> ofonod[2844]: plugins/udev.c:add_gobi() modem 0x8dcb268
>> ofonod[2844]: src/modem.c:get_modem_property() modem 0x8dcb268 property Path
>> ofonod[2844]: plugins/udev.c:add_modem()
>> /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.2/ttyUSB4/tty/ttyUSB4
>> (gobi)
>> ofonod[2844]: plugins/udev.c:add_gobi() modem 0x8dcb268
>> ofonod[2844]: src/modem.c:set_modem_property() modem 0x8dcb268 property Device
>> ofonod[2844]: plugins/gobi.c:gobi_probe() 0x8dcb268
>> ofonod[2844]: plugins/hfp_ag.c:modem_watch() modem: 0x8dcb268, added: 1
>> ofonod[2844]: plugins/dun_gw.c:modem_watch() modem: 0x8dcb268, added: 1
>> ofonod[2844]: plugins/smart-messaging.c:modem_watch() modem: 0x8dcb268, added: 1
>> ofonod[2844]: plugins/push-notification.c:modem_watch() modem:
>> 0x8dcb268, added: 1
>> ofonod[2844]: src/modem.c:get_modem_property() modem 0x8dcb268 property Path
>> ofonod[2844]: plugins/udev.c:add_modem()
>> /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.3/ttyUSB5/tty/ttyUSB5
>> (gobi)
>
> This means that there are 3 TTYs exposed by the Gobi card. This does not
> mean that these are all AT modem capable ports. In fact they are not.
> Check /proc/bus/usb/devices and see what driver got loaded for what USB
> interface. All the qcaux bound interfaces are not really helpful.
>
> But if you by accident have a Gobi firmware that exposes 2 real AT
> command ports, I like to hear about it.

Can you please explain to me why a second command port is needed? I
tried setting up a data connection with said modem using modem-manager
and it just uses the one existing port for setting up a
ppp-connection.

>
> Regards
>
> Marcel
>
>
> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org
> http://lists.ofono.org/listinfo/ofono
>

Re: Qualcomm Gobi 2000 Modem Issues

[Marcel Holtmann]

[-- Attachment #1: Type: text/plain, Size: 6903 bytes --]

Hi Kai,

> >> >> I ran into two issues trying to setup a data connection with a Gobi 2000 card.
> >> >> The first one seems to be an error regarding simcard onlocking. After
> >> >> enabling the modem test/list-modems shows the following, despite the
> >> >> simcard is inserted correctly:
> >> >>
> >> >> [ /gobi0 ]
> >> >>     Features = sim
> >> >>     Emergency = 0
> >> >>     Powered = 1
> >> >>     Lockdown = 0
> >> >>     Interfaces = org.ofono.SimManager
> >> >>     Online = 0
> >> >>     Model = Qualcomm Gobi 2000
> >> >>     Revision = D1025-STUTABGD-3600  1  [Jan 14 2010 14:00:00]
> >> >>     Serial = 353093033460401
> >> >>     Manufacturer = Qualcomm Incorporated
> >> >>     [ org.ofono.SimManager ]
> >> >>         Present = 0
> >> >>
> >> >> Our current workaround is quitting ofono and using minicom to unlock
> >> >> the sim directly, then restarting ofono.
> >> >> > at+cpin?
> >> >> +CPIN: SIM PIN
> >> >> OK
> >> >>
> >> >> > at+cpin="1234"
> >> >> OK
> >> >> $QCSIMSTAT: 1 SIM INIT COMPLETED
> >> >
> >> > this is weird since the PIN unlocking should just work fine. Have you
> >> > tried to use the test/enter-pin script?
> >>
> >> Yes, I tried the enter-pin script. Using it without the optional PATH
> >> this is the error:
> >> dbus.exceptions.DBusException: org.ofono.Error.InvalidFormat: Argument
> >> format is not recognized
> >>
> >> Entering 'test/enter-pin /generic pin 1234' resultis in:
> >> dbus.exceptions.DBusException:
> >> org.freedesktop.DBus.Error.UnknownMethod: Method "EnterPin" with
> >> signature "ss" on interface "org.ofono.SimManager" doesn't exist
> >>
> >> The problem is ofono not detecting the sim card properly since
> >> 'list-modems' shows:
> >>     [ org.ofono.SimManager ]
> >>         Present = 0
> >
> > this is clearly a bug in the Gobi plugin then. It does not detect the
> > SIM card properly. So you need to dig a bit into plugins/gobi.c and
> > figure out how to fix it.
> >
> 
> I would like to do that, but having trouble with the code, especially
> because I couldn't find any documentation on AT$QCSIMSTAT and
> code-documentation in gobi.c is virtually not present.
> Maybe someone can help here.
> 
> Again, the problem is, that the modem responds "$QCSIMSTAT: 1,UNKNOWN"
> instead of "$QCSIMSTAT: 1 SIM INIT COMPLETED" when "AT$QCSIMSTAT?" is
> sent.

I have no official documentation for Gobi cards either. The current work
has been done by locking on how the card responds. So you need to dig
into this and try to figure this out.

Or you just disable the PIN code of that SIM card and then it should
work just fine.

> >> >> The second issue is not being able to activate an internet context:
> >> >> (Network registration and attachment is alright)
> >> >>
> >> >> test/enable-modem
> >> >> Connecting modem /gobi0...
> >> >> test/online-modem
> >> >> Setting modem /gobi0 online...
> >> >> test/list-contexts
> >> >> [ /gobi0 ]
> >> >>     [ /gobi0/context1 ]
> >> >>         Username =
> >> >>         Protocol = ip
> >> >>         Name = Internet
> >> >>         Settings = { }
> >> >>         IPv6.Settings = { }
> >> >>         Active = 0
> >> >>         AccessPointName = internet.t-mobile
> >> >>         Password =
> >> >>         Type = internet
> >> >>
> >> >> test/activate-context
> >> >> Error activating /gobi0/context1: org.ofono.Error.NotImplemented:
> >> >> Implementation not provided
> >> >>
> >> >> If you could give me a little assisting on where to look, maybe I
> >> >> would be able to contribute patches, too.
> >> >
> >> > Of course this does not work. Check doc/hardware-support.txt for
> >> > supported modem and supported capabilities.
> >> >
> >> > Until Qualcomm gives us the chance to implement QMI properly, we are a
> >> > bit out of luck with just one AT command channel. You need at least two
> >> > AT command channel to run oFono properly.
> >> >
> >>
> >> I missed reading that document.
> >> However I don't understand why you would need QMI for setting up a PPP
> >> connection, since there are infact three AT command channels, not one,
> >> if I understand the log correctly:
> >>
> >> ofonod[2844]: src/modem.c:ofono_modem_create() name: (null), type: gobi
> >> ofonod[2844]: src/modem.c:set_modem_property() modem 0x8dcb268 property Path
> >> ofonod[2844]: src/modem.c:set_modem_property() modem 0x8dcb268
> >> property Registered
> >> ofonod[2844]: plugins/udev.c:add_modem()
> >> /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.1/ttyUSB3/tty/ttyUSB3
> >> (gobi)
> >> ofonod[2844]: plugins/udev.c:add_gobi() modem 0x8dcb268
> >> ofonod[2844]: src/modem.c:get_modem_property() modem 0x8dcb268 property Path
> >> ofonod[2844]: plugins/udev.c:add_modem()
> >> /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.2/ttyUSB4/tty/ttyUSB4
> >> (gobi)
> >> ofonod[2844]: plugins/udev.c:add_gobi() modem 0x8dcb268
> >> ofonod[2844]: src/modem.c:set_modem_property() modem 0x8dcb268 property Device
> >> ofonod[2844]: plugins/gobi.c:gobi_probe() 0x8dcb268
> >> ofonod[2844]: plugins/hfp_ag.c:modem_watch() modem: 0x8dcb268, added: 1
> >> ofonod[2844]: plugins/dun_gw.c:modem_watch() modem: 0x8dcb268, added: 1
> >> ofonod[2844]: plugins/smart-messaging.c:modem_watch() modem: 0x8dcb268, added: 1
> >> ofonod[2844]: plugins/push-notification.c:modem_watch() modem:
> >> 0x8dcb268, added: 1
> >> ofonod[2844]: src/modem.c:get_modem_property() modem 0x8dcb268 property Path
> >> ofonod[2844]: plugins/udev.c:add_modem()
> >> /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.3/ttyUSB5/tty/ttyUSB5
> >> (gobi)
> >
> > This means that there are 3 TTYs exposed by the Gobi card. This does not
> > mean that these are all AT modem capable ports. In fact they are not.
> > Check /proc/bus/usb/devices and see what driver got loaded for what USB
> > interface. All the qcaux bound interfaces are not really helpful.
> >
> > But if you by accident have a Gobi firmware that exposes 2 real AT
> > command ports, I like to hear about it.
> 
> Can you please explain to me why a second command port is needed? I
> tried setting up a data connection with said modem using modem-manager
> and it just uses the one existing port for setting up a
> ppp-connection.

Actually ModemManager is lazy here. Once it enters PPP mode it ignores
everything else. It prays that everything works out, but that is risky
actually.

ModemManager is just a fancy way for chat + pppd while oFono is a proper
telephony stack. For a telephony stack you need to monitor things like
incoming SMS, USSD and also network registration, signal strength and
cell changes. Once your TTY is stuck in PPP (aka online mode) you are
lost here.

The proper way for driving a Gobi card is Qualcomm's QMI protocol, but
they are keeping that one a secret :(

Regards

Marcel