From my window

PnP and Power Management Scenarios in UMDF

Nazan Kurt — Thu, 06 Dec 2012 06:38:15 GMT

If you are implementing a UMDF driver for GPS, Sensors or another device, the following additions to MSDN on PnP and Power Management Scenarios in UMDF are very helpful:

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560452%28v=vs.85%29.aspx

Mapping your location

Nazan Kurt — Tue, 20 Nov 2012 20:04:00 GMT

Would like to quickly map your location in your Windows 8 app? Take a look at this "One Dev Minute" video: Mapping your Location .

Interested in more details? Check out the How-to topic on displaying your location on a Bing Map.

(Please rate so that I know if you'd like to see more/less of such posts - Thanks)

Windows Hardware Testing and Certification Forum

Nazan Kurt — Thu, 04 Oct 2012 23:26:06 GMT

There is a dedicated forum for WHCK now! The forum is used by the community to post testing and certification questions. I thought this is exciting news for many people following the blog.

“Windows Hardware Testing and Certification”

GNSS (GPS) Test Guidence for Windows 8

Nazan Kurt — Sun, 10 Jun 2012 00:58:00 GMT

I have been working on GNSS for last few months. If you are interested in developing GNSS solutions on Windows platform, hope you find my whitepaper on the topic useful: http://msdn.microsoft.com/en-US/library/windows/hardware/hh975385

Where can I see the list of Logo'ed Mobile Bradband Drivers for Windows 7?

NazanK — Fri, 16 Apr 2010 07:23:00 GMT

You can find the list at Winqual website.

Where to get the home provider name?

NazanK — Mon, 05 Apr 2010 18:26:00 GMT

The home provider name should be read from the SIM. EFSPN is one of the most common places this information is available. What if the SIM is not SPN (Service Provider Name) provisioned? EONS (Enhanced Operator Name String) could be another option or doing a partial match based on the MCC-MNC from the IMSI to the network name. The operator providing the SIM can tell the alternative ways to get the home provider info.

You'll see a failure similar to below if the driver does not provide the home provider info to the OS:

Querying OID_WWAN_HOME_PROVIDER failed:
NDIS_STATUS: NDIS_STATUS_SUCCESS
WWAN_STATUS: WWAN_STATUS_READ_FAILURE

SMS tests for CDMA SevenBitAscii encoding - Who is responsible for encoding/decoding the data?

NazanK — Sat, 03 Apr 2010 00:48:00 GMT

Logo tests for CDMA devices those support SMS SevenBitAscii encoding send the UTF-8 encoded unpacked data to the driver and expects the driver to do the encoding to 7BitASCII. On the receive also, the tests expects the driver to give the unpacked data up to the OS. For Unicode encoding also, the data is data is sent in UTF-8 encoding.

A failure similar to below can be seen if the driver does not comply with this expectation:

SMS received is not that sent:
- Sent: 443935425600915599 : length 18
- Received: 4439354256009155 : length 16

You get a failure in NDISTest log. Now what?

NazanK — Tue, 23 Mar 2010 19:39:00 GMT

1- Make sure you read the ndistest html log very carefully.

2- Check the test source code for the failing test. Test source code can be found at \ControllerName\Tests\x86fre\NTTest \nettest \ndis \ndistest.net\sdk\src\wwan. Reading the source code along with the log helps.

3- Try with another network to see if it’s a network/SIM related issue.

4- If you believe it’s an infrastructure or test issue, try with another device to verify.

5- Check for known issues. Please see my earlier blogposts on erratas.

6- Attach a debugger to the test machine and enable verbose debugger prints from NDISTest GUI, View/Options window. NDISTest might have dbg-printed info that can help with root causing.

7- Use WWANDriverTestApp which is available in WDK i.e. to query the failing OIDs individually. It's located @ WDKPath\tools\Networking\i386\WwanDriverTestApp.exe.

Before starting Mobile Broadband Logo testing

NazanK — Tue, 23 Mar 2010 19:15:00 GMT

1- Make sure you download latest QFEs applicable to WLK you are using. QFE packages can be found @ Microsoft Connect download page.You can find the instructions @ http://www.microsoft.com/whdc/winlogo/WLK/WLKQFE.mspx

2- Make sure you check my blogpost about the applicable erratas to Mobile Broadband tests. All erratas can be found @ https://winqual.microsoft.com/EC .

3- Make sure you have all the SIMs required for Logo testing. Please see my blogpost about the SIMs required for Logo testing.

4- Make sure that the PIN for your home SIM and roaming SIM are same.

5- Testing with the fastest network available is recommended.

6- Make sure you delete all SMSes on the SIM/Device before running the SMS tests.

7- You can use standalone NDISTest and make sure you can pass all tests before starting the logo pass from DTM. Running NDISTest standalone gives you the flexibility to re-run a particular test or a set of tests without running everything. You can also modify the parameters i.e. APN info, debug output, severity of debug prints, running tests in loop, stop on fail etc. from NDISTest option window. You can also pass custom parameters to the tests (called 'hot parameters') by right clicking on the test name from NDISTest GUI before stating the test run.

Mobile Broadband Logo tests source code

NazanK — Wed, 10 Mar 2010 21:49:00 GMT

You can find the source code for NDISTest test scripts in your DTM installation at:

C:\Program Files\Microsoft Driver Test Manager\Tests\x86fre\nttest\nettest\ndis\ndistest.net\sdk\src\wwan

You can also view the source code of a test by right clicking on the test name from NDISTest GUI before starting the test.

This is not the complete source code for NDISTest, and part of the test logic and some failures are coming from deeper in the code; however, most of the test logic is in these source files. They can help with better understanding what the test is doing and why a failure is happening.

WLK 1.5 Erratas and known issues for Mobile Broadband Logo Program

NazanK — Wed, 10 Mar 2010 00:08:00 GMT

I tried to list the erratas and known issues in Mobile Broadband Logo tests for WLK 1.5 below and give an example of the failure you'll see in the tests.

1- Errata 1754: https://winqual.microsoft.com/EC/ECDetails.aspx?id=2064

ProviderId must be 0 or 5 digits in length for CDMA, ProviderId was 0

2- Errata 1755: https://winqual.microsoft.com/EC/ECDetails.aspx?id=2065

Signal.htm: Device is CDMA and radio is on, but no signal strength indications were received

3- Errata 1863: https://winqual.microsoft.com/EC/ECDetails.aspx?id=2118

Teredo.htm: Teredo Test and 6 to 4 test are no longer required. Logo Requirement Network-0277, Mobile Broadband Devices must support Teredo, 6To4 and VPN tunneling technologies is being retired

4- Errata 1867: https://winqual.microsoft.com/EC/ECDetails.aspx?id=2140

Pin.htm :Test terminated abnormally with an Exception System.ArgumentOutOfRangeException

5- Errata 1877: https://winqual.microsoft.com/EC/ECDetails.aspx?id=2143

Pin.htm: When PIN enable is tried with wrong PIN , the pin state should be same as PINtype in NDIS_WWAN_SET_PIN but the driver reported PIN state as None

6- Errata 1890: https://winqual.microsoft.com/EC/ECDetails.aspx?id=2163

Radio.htm: Turning off the software radio reported success but PacketServiceState is Attached , expected PacketServiceState is WwanPacketServiceStateDetached.

Turning off the software radio reported success but RegisterState is Home , expected RegisterState is WwanRegisterStateDeregistered

7- Errata 1989: https://winqual.microsoft.com/EC/ECDetails.aspx?id=2491

Pin.htm: AttemptsRemaining should decrement by one when wrong PIN of valid length is given Expected attempts: 2 actual attempts:

8- Errata 2136: https://winqual.microsoft.com/EC/ECDetails.aspx?id=2796

Preferred.htm: WWAN_STATUS_INVALID_PARAMETERS is not a valid uStatus for a OID_WWAN_PREFERRED_PROVIDERS set operation

9- Errata 2150: https://winqual.microsoft.com/EC/ECDetails.aspx?id=2851

Sms.htm: There should be only one SMS in the message store after one of two messages was deleted. Message count is 3

'Compatible with Windows' = 'Designed for Windows'

NazanK — Tue, 09 Mar 2010 18:11:00 GMT

Name of the Windows Logo is changed from 'Designed for Windows' to 'Compatible for Windows' for Windows 7.

Running NDISTest from command prompt

NazanK — Wed, 03 Mar 2010 23:56:00 GMT

You can find NDISTest in your DTM installation at c:\Program Files\Microsoft Driver Test Manager\Tests\x86fre\nttest\nettest\ndis\ndistest.net.

A typical way you can launch and auto execute Ndistest from command line is:

ndistest.exe /auto /client /target:miniport /tc:{your test adapter guid} /jobgroup:WHQL\WWanNI

/auto: This will cause the “start” button to be pressed automatically. The tests will run and then NDIS Test will exit. In server mode the server script will keep running until the user stops it.

/client: Selects CLIENT option

/server: Selects SERVER option. This is not relevant to Moblie broadband testing at this moment.

/jobgroup: Selects the group of tests that'll run. WWanNI stands for WWan Non-Interactive tests.

/tc:{GUID}: This is used to select the TEST: device. A GUID or MAC address can be supplied. Here is an example of each:

/tc:{C9F2D762-153C-43B3-8245-E288810B0AC8}

/tc:{00-10-4b-ca-b3-29}

Note that the leading 0 must be supplied. {0-10-4b-ca-b3-29} will not work. Case does not matter.

If you are providing settings from the NDISTest UI through Options window such as APN, you can provide them once and the settings will be saved for the upcoming executions.

Mobile Broadband Logo test SIM card requirements

NazanK — Wed, 03 Mar 2010 22:54:00 GMT

MSDN lists following SIMs as required for Mobile Broadband Logo testing:

· ‘Home’ SIM with data provisioned

· ‘Roaming’ SIM with data provisioned

· ‘Home’ SIM with no data provisioned

· ‘Roaming’ SIM with no data provisioned

· ‘Bad’ SIM

· ‘Inactive’ SIM

Frequent questions around those are: What do these mean? How you can get them? Do you need it for a CDMA device also? What if my device does not support removable SIMs?

'Data provisioned': SIM can be used for data connection. For example, a voice only SIM is not data provisioned.

'Home SIM': You have a SIM from a network which is visible and you can connect to.

'Roaming SIM': You have a SIM from a network which not visible. You can only connect to roaming partners in this case.

'Bad SIM': SIM is not in usable state. You can get a bad SIM by exceeding the PUK retry limit.

'Inactive SIM': Blank SIM with no provider provisioned

If your driver does not report that it supports removable SIM by setting WwanSimClass to WwanSimClassSimRemovable in DeviceCaps, you do not need these SIMs (except a home 'SIM' with data provisioned).

Windows Mobile Broadband driver development and testing resources

NazanK — Sun, 28 Feb 2010 02:33:00 GMT

I'd like to put together a compile of resources available for Windows Mobile Broadband driver developers and testers. I'll keep updating and please feel free to add to the list via comments:

1- Resources listed in Networking Developer Platform Center: http://msdn.microsoft.com/en-us/network/dd579153.aspx. Scroll down the page.

2- There is no Mobile Broadband driver sample in WDK, however, one of the other NDIS driver samples will be helpful, at least for the common NDIS code part. Usbnwifi 6.20 may be a good fit: http://msdn.microsoft.com/en-us/library/dd163318.aspx. You can find it in WDK source tree at src\network\ndis\usbwifi.

3- General info on NDISTest :

- http://www.microsoft.com/whdc/DevTools/tools/NDIStest.mspx

4- Ndis blog. Check out 'How to run NDISTest outside DTM post: http://blogs.msdn.com/ndis/default.aspx

Stay tuned for more and please feel free to add to the list.

How to handle an OID_WWAN_SMS_CONFIGURATION request when ready state is initialized but SMS subsystem is not ready yet?

NazanK — Sat, 27 Feb 2010 15:25:00 GMT

Miniport driver is expected to respond with uStatus WWAN_STATUS_NOT_INITIALIZED in this case. Then when SMS subsystem is ready, it must follow with an unsolicited indication of NDIS_STATUS_WWAN_SMS_CONFIGURATION.

Returning a different status code may result in Logo tests to fail with an error similar to:

"%uStatus code you returned% is not a valid uStatus for this OID_WWAN_SMS_CONFIGURATION query operation"