Modem device with qualcomm MDM9200 chipset stop responding on windows 7

NTDEV
1

hello dear all,

Is there any difference in xp, vista and windows 7 operating systems regarding. control requests over control pipe.? we have developed drivers for ndis port miniport NDIS driver.

its working fine with LTE network in XP and vista. but in case of windows 7 operating systems. when we send control request to stop network to device, we are not getting response from device. we have observed Lecroys usb analyzer logs. we are not getting response. even though we its device side problem. why this issue is not happening in xp and vista.
we have two applications for sending control requests to device for starting network.

  1. company application.
  2. mobile broad band Microsoft provided default application .

this issue happens only with company application. we have compared data in requests send by cm and mobile broadband but no difference… please guide us its an urgent issue

Anybody working with WDM NDIS device drivers for the NDIS interface on Qualcomm MDM 9200 device???

Please let me know… i have queries…

please anybody have experience with WDS, NAS, CTL services on qualcomm also please respond me

2

xxxxx@lge.com wrote:

Is there any difference in xp, vista and windows 7 operating systems regarding. control requests over control pipe.?

No.

we have developed drivers for ndis port miniport NDIS driver. its working fine with LTE network in XP and vista. but in case of windows 7 operating systems. when we send control request to stop network to device, we are not getting response from device. we have observed Lecroys usb analyzer logs. we are not getting response. even though we its device side problem. why this issue is not happening in xp and vista.

We can’t answer that. If the logs are the same, then it’s hard to blame
the host side for this. You might check to see if the order of
operations is somehow different. Is there an extra SET_INTERFACE
request? Was the timing different? Perhaps your device’s firmware
makes assumptions that aren’t actually valid.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

On 2/2/2012 6:58 AM, xxxxx@lge.com wrote:

Is there any difference in xp, vista and windows 7 operating systems
regarding. control requests over control pipe.?

Yes, Win7 tolerates slightly different errors than WinXP and Vista.

[Of course it could actually be that Windows7 has a bug in the USB stack
that your application triggers. But this is not likely, specifically if
“this issue happens only with company application” and not with the
“Microsoft provided default application”.]

We had similar questions before in this forum. “My device does not work
with Vista, but worked well with Win2K and WinXP. Is Vista broken?”.
(Turned out they had implemented a faulty descriptor. In the device.)

Sometimes developers - as opposed to take the time and effort to
actually read, design and test against a protocol spec - code solely
against a specific OS, and stop “when it works”, e.g. with Windows.

In the short term, this strategy looks like a win for everyone: for the
developer, their manager, and even for the end users. OK, you don’t
fulfill the spec, but - hey, it works!! So what do you want any more
testing for? [The current version of Windows gracefully overlooks the
fault and everyone is happy.]

In the long term, this strategy is dangerous: the next version of
Windows might actually need to check more rigorously, e.g. because a new
USB standard requires it, because they detected problems in the past. Or
someone else took over module maintenance and just improved the error
handling. Now the newer Windows version checks for the specific error
condition you introduced. And rejects your device, or an application
protocol frame. If you are lucky, you get an error message.

So what can you do? Please check if your device and driver are really
standards compliant. “It works on Windows from X to Y.” is not the same
as “USB standards compliant.”.

If you ask me, this looks like an application error (e.g. security, or
some DPC handling, etc.). If it works with an MS default app, but not
with your application, you need to analyze the calls your app sends to
the system and compare that with the calls the MS default does.

4

> this issue happens only with company application.

Fix your buggy app, no need in a bus analyzer. Just make your app using MS’s standard APIs and it will work the same way as the MS’s standard thing works.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

5

@ Shatskih Thanks for your answer. we cant use Microsoft provided APIs, as it is qualcomm Chiset. there is set sequence of requests send to device for activating network on device side and deactivate the network. even Microsoft provided MB service we are using for connecting to network. when we receive OID_WWAN_CONNECT like commands according sequence we will change that to Qualcomm requests and in response will fill the OID request and complete the OID.

6

Thanks for all replies
@Hagen Patzke

Yes, Win7 tolerates slightly different errors than WinXP and Vista can you explain this point??

we are developing only NDIS drivers. CM and firmware is developed by third party company.

one suspect point issue happens only in windows 7 64bit on LTE network.

i am wondering

  1. why issue happens only in windows 7 64bit on LTE network not with 3G network?
  2. why issue does not happen with Microsoft WMB application either 3G or LTE in all OS?
  3. i compared packets for Company CM and WMB same data we are passing to device for connecting?

is it a timing issue ?
or device is going wrong with LTE network if so why in windows 7 64bit only.