Re: Qualcomm Gobi 2000 Modem Issues

[Marcel Holtmann <marcel@holtmann.org>]

[-- 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