ZTE 403ZT supported ?

[Nir Fuchs]

I remember dealing with it a few months back. ( I wish I had those lsusb and debug logs saved somewhere. )

As far as I remember it is identified as 19d2:1282, mode switch is done automatically by the device itself.

By default, option driver has this device ID with the following configuration:

{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, 0x1282, 0xff, 0xff, 0xff) },

However, that line exposes ttyUSBx interfaces that don't respond to AT commands. ( Probably debug / diagnostics interfaces )

What you should do is to have to have this line of configuration instead:

{ USB_DEVICE(ZTE_VENDOR_ID, 0x1282) },

which will expose those ttyUSBx interfaces that you can use for PPP. If I recall correctly then interface #1 is ZTE UI AT interface and interface #2 is ZTE Proprietary USB Modem.

As Bjorn already pointed-out no QMI interfaces are exposed by this device.

I hope this helps,
Nir Fuchs. 
________________________________________
From: libqmi-devel <libqmi-devel-bounces at lists.freedesktop.org> on behalf of Gopakumar Choorakkot Edakkunni <gopakumar.c.e at gmail.com>
Sent: Wednesday, September 9, 2015 03:11
To: Bjørn Mork
Cc: libqmi (development)
Subject: Re: ZTE 403ZT supported ?

Thanks Bjorn. I will try fiddling around with it and report if I have success

Rgds,
Gopa.

On Mon, Sep 7, 2015 at 1:12 AM, Bjørn Mork <bjorn at mork.no> wrote:
> Gopakumar Choorakkot Edakkunni <gopakumar.c.e at gmail.com> writes:
>
>> Hi modem experts,
>>
>> Is the latest and greatest ZTE 403ZT modem supported by qmi or linux
>> serial ? I tried plugging it in, it does create ttyUSB0/1 interfaces,
>> but no wwan interfaces. The ttyUSB doesn't respond to AT commands
>> either
>
> You can safely assume that any new ZTE modems are unsupported.  They do
> their best to prevent any generic support.
>
> Each ZTE device has a unique function layout, with no hints whatsoever.
> So the support depends on someone with the actual device figuring out
> what the different functions are.  The easiest way is usually inspecting
> the Windows driver package.  The *.inf files describe the relationship
> between Windows drivers and USB pid/vid/interfaces.  Most of the time
> you can guess the function based on the Windows driver name.  But it's
> best to verify the guesswork, which can only be done with someone having
> access to the device.
>
> So:
> 1) dig up the Windows *.inf file for your modem
> 2) run "lsusb -v" on Linux and try to match the output against the *,inf
> 3) start testing existing Linux drivers based on the above
> 4) report your findings
>
> Reports in the form of patches against the drivers are preferred, but
> any form will do.  Just make sure to include a description of your
> device and testing, so that we know how you came to the conclusion in
> case some question shows up later.
>
>
> Bjørn
_______________________________________________
libqmi-devel mailing list
libqmi-devel at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libqmi-devel