Test cases for WLAN SDIO interface

TheMSsForum.com: The Microsoft Software Forum

The MSS Forum ‹ Drivers
- Archive
  - Biz
  - MCSE
  - CRM
  - Drivers
  - Framework
  - ADO
  - ASP
  - Compact
  - Forms
  - Dotnet
  - C#
  - VB
  - FontpageGen
  - Excel
  - WorkSheet
  - Exchange
  - Setup
  - Fox
  - Fontpage
  - ASP
  - IIS
  - Entourage
  - Money
  - Messanger
  - PocketPC
  - Powerpoint
  - Project
  - Publisher
  - Excel
  - VB
  - Security
  - Portal
  - Services
  - SQLServerDev
  - SVCS
  - SQLServer
  - VB
  - VC
  - MFC
  - ExcelGen

- Previous
  - 1
    - Sharing COM1 with WinDbg I have an embedded device running XPe with a single serial port (also no 1394). The COM1 port is normally used by applications for other purposes. However, I would really like to be able to use this for kernel debugging as well. I tried using /crashdebug option in boot.ini so that the COM1 port does not disappear. The problem is that this does not let me debug on demand, only when a bug check occurs. Is there a way to enable on demand debugging without reserving the serial port for exclusive use by the debugger? If not, the other option would be to have WinDbg monitor for specific debug messages coming from the other machine. My understanding is that this used to be possible with a .waitforstr command, but that doesn't seem to be implemented any more. Is there a way to monitor messages from within WinDbg? Thanks! Tag: Test cases for WLAN SDIO interface Tag: 105566
  - 2
    - IoCallDriver Bugcheck Hi, I observed a strange behavior with Intelx64 PCs with my virtual COM driver. When I pass an irp to lower driver (using IoCallDriver()) i get an Assertion Failure - code c0000420 exception and when i forcefully continue it i get a bugcheck. I get this exception when i pass the IRP with one of the vendor specific commands. Also, this exception is not happening frequently. It happens for every 3 out of 5 times. I have used an application to test the sequence. By the way this failure is not happening in either Intel x86, AMD x64 or AMD x86 bit machines. In all the PCs i have installed Vista 32-bit OS. I did not see anything pointing in my driver, but i strongly believe that some thing is going wrong in my driver. I have pasted the bugcheck code and wdflog below. Can someone help me find the bug where im going wrong? Here is the bugcheck code: *** Fatal System Error: 0x0000008e (0xC0000420,0x81828671,0x9EF97A3C,0x00000000) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. Connected to Windows Vista 6000 x86 compatible target, ptr64 FALSE Loading Kernel Symbols ............................................................................................................................... Loading User Symbols ........................................................................................ Loading unloaded module list ........Unable to enumerate user-mode unloaded modules, Win32 error 0n30 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 8E, {c0000420, 81828671, 9ef97a3c, 0} Probably caused by : kdcom.dll ( kdcom!KdCompPollByte+14 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 818818d0 cc int 3 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000420, The exception code that was not handled Arg2: 81828671, The address that the exception occurred at Arg3: 9ef97a3c, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000420 - <Unable to get error code text> FAULTING_IP: nt!KeUpdateRunTime+248 81828671 cd2c int 2Ch TRAP_FRAME: 9ef97a3c -- (.trap 0xffffffff9ef97a3c) ErrCode = 00000000 eax=763b38b9 ebx=00000000 ecx=818f622c edx=0000009b esi=818f4820 edi=8bd343f0 eip=81828671 esp=9ef97ab0 ebp=9ef97ac8 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202 nt!KeUpdateRunTime+0x248: 81828671 cd2c int 2Ch Resetting default scope DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: svchost.exe CURRENT_IRQL: 1c LAST_CONTROL_TRANSFER: from 818d87f7 to 818818d0 STACK_TEXT: 9ef971dc 818d87f7 00000003 9ef9c96c 00000000 nt! RtlpBreakWithStatusInstruction 9ef9722c 818d9264 00000003 9ef97a3c 00000000 nt!KiBugCheckDebugBreak +0x1c 9ef975d8 818d8681 0000008e c0000420 81828671 nt!KeBugCheck2+0x5f4 9ef975fc 8182335e 0000008e c0000420 81828671 nt!KeBugCheckEx+0x1e 9ef979cc 8188d66a 9ef979e8 00000000 9ef97a3c nt!KiDispatchException +0x1a9 9ef97a34 8188d606 9ef97ac8 81828673 badb0d00 nt!CommonDispatchException +0x4a 9ef97a48 804c79ac 804c8020 9ef97a8b 00000000 nt!KiExceptionExit+0x16e 9ef97ac8 818906ad 83347e02 000000d1 9ef97b58 kdcom!KdCompPollByte+0x14 9ef97ac8 81ba4dc0 83347e02 000000d1 9ef97b58 nt!KeUpdateSystemTime +0xed 9ef97b48 806d8533 83347e10 83347eec 9ef97b6c hal! KeAcquireSpinLockRaiseToSynch+0x20 9ef97b58 806e0f8c 9ef97b68 8070cf30 83347eec Wdf01000! FxCallbackSpinLock::Lock+0x7f 9ef97b6c 806e3d13 7ccb81e8 7cf8db90 00000001 Wdf01000! FxIoQueueIoRead::Invoke+0x1e 9ef97b94 806e6598 7cf8db90 83072468 83347e10 Wdf01000! FxIoQueue::DispatchRequestToDriver+0x1dc 9ef97bb0 806e7d2c 83347e00 8070d188 83347e10 Wdf01000! FxIoQueue::DispatchEvents+0x485 9ef97bcc 806e8e67 00000000 83112f40 82f27b58 Wdf01000! FxIoQueue::QueueRequest+0x237 9ef97bf0 806d7d9a 8bd3a920 9ef97c14 81827f83 Wdf01000!FxPkgIo::Dispatch +0x377 9ef97bfc 81827f83 82f27b58 8bd3a920 8bd3a920 Wdf01000! FxDevice::Dispatch+0x7f 9ef97c14 8a42d581 831af0e8 83112e88 831af030 nt!IofCallDriver+0x63 9ef97c28 81827f83 83112e88 00d3a920 82f23030 serenum! Serenum_DispatchPassThrough+0x65 9ef97c40 86338027 9ef97c60 81827f83 82f23030 nt!IofCallDriver+0x63 9ef97c48 81827f83 82f23030 8bd3a920 8bd3a920 RootMdm! RootModemPassThrough+0x21 9ef97c60 892bcb1a 8bd410e8 831af030 00000000 nt!IofCallDriver+0x63 9ef97c74 81827f83 8bd3aab0 8bd3a920 8bd3a920 modem!UniRead+0x4a 9ef97c8c 81988f37 8bd3a920 8bd3aab0 8bd410e8 nt!IofCallDriver+0x63 9ef97cac 81993669 831af030 8bd410e8 00000001 nt! IopSynchronousServiceTail+0x1e0 9ef97d38 8188caaa 831af030 8bd3a920 779ed684 nt!NtReadFile+0x646 9ef97d38 77c30f34 831af030 8bd3a920 779ed684 nt!KiFastCallEntry+0x12a 02e3f1cc 77c30080 779ed71d 00000194 00000000 ntdll!KiFastSystemCallRet 02e3f1d0 779ed71d 00000194 00000000 779ed684 ntdll!ZwReadFile+0xc 02e3f210 6ef09ddf 00000194 03176de4 00000001 kernel32!ReadFileEx+0x72 02e3f698 6ef227ba 00000000 00000000 00780830 unimdmat! ReadCompletionHandler+0x7ca 02e3f6ac 77a06c6d 00780830 02e3a40e 02e3f718 uniplat! AsyncProcessingHandler+0x15 02e3f704 77c30dfd 6ef227a5 00780830 00000000 kernel32!BaseDispatchAPC +0x50 02e3fa5c 6ef22934 000006bc ffffffff 00000001 ntdll!KiUserApcDispatcher +0x25 02e3fa70 77a23833 6ef24020 02e3fabc 77c0a9bd uniplat!UmWorkerThread +0x15 02e3fa7c 77c0a9bd 6ef24020 02e37e4f 00000000 kernel32! BaseThreadInitThunk+0xe 02e3fabc 00000000 6ef2291f 6ef24020 00000000 ntdll!_RtlUserThreadStart +0x23 STACK_COMMAND: kb FOLLOWUP_IP: kdcom!KdCompPollByte+14 804c79ac 0fb7c0 movzx eax,ax SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: kdcom!KdCompPollByte+14 FOLLOWUP_NAME: MachineOwner MODULE_NAME: kdcom IMAGE_NAME: kdcom.dll DEBUG_FLR_IMAGE_TIMESTAMP: 4549bd7c FAILURE_BUCKET_ID: 0x8E_kdcom!KdCompPollByte+14 BUCKET_ID: 0x8E_kdcom!KdCompPollByte+14 Followup: MachineOwner --------- I also captured the WDFLOG as mentioned in http://blogs.msdn.com/doronh/archive/2006/07/31/684531.aspx. Here is the wdflog. But i could not find any useful information in it. 0: kd> !load C:\Program Files\Debugging Tools for Windows (x86)\winext \wdfkd.dll 0: kd> !D:\WINDDK\6000\bin\x86\wdfkd.wdftmffile D:\WINDDK\6000\tools \tracing\i386\wdf01005.tmf Set TMF file name is : 'D:\WINDDK\6000\tools\tracing \i386\wdf01005.tmf' 0: kd> !D:\WINDDK\6000\bin\x86\wdfkd.wdflogdump usbcom Trace searchpath is: Trace format prefix is: %7!u!: %!FUNC! - TMF file used for formatting IFR log is: D:\WINDDK\6000\tools\tracing \i386\wdf01005.tmf Log at 83343000 Gather log: Please wait, this may take a moment (reading 4032 bytes). % read so far ... 10, 20, 30, 40, 50, 60, 70, 80, 90, 100 There are 106 log entries --- start of log --- 274: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 275: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 276: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 277: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 278: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 279: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 280: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 281: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 282: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 283: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 284: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 285: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 286: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 287: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 288: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 289: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 290: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 291: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 292: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 293: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 294: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 295: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 296: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 297: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 298: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 299: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 300: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 301: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 302: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 303: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 304: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 305: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 306: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 307: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 308: FxFileObject::GetFileObjectFromWdm - The PFILE_OBJECT 0x8BD460D0 in this request (cleanup/close) is different from the one specified in create request 0x833D3700.This is bad! 309: FxFileObject::GetFileObjectFromWdm - Since this is a serial port device, framework is using a workaround to allow this 310: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD2DFE8 requests cancelled 311: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD2DFE8 312: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 313: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 314: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 315: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 316: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD2DFE8 requests cancelled 317: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD2DFE8 318: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 319: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 320: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 321: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 322: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 323: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleStartTimer from FxIdleDecrementIo 324: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleTimerRunning from FxIdleStartTimer 325: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleCancelTimer from FxIdleTimerRunning 326: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleCheckIoCount from FxIdleCancelTimer 327: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleCheckIoCount 328: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD2DFE8 requests cancelled 329: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD2DFE8 330: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 331: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 332: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 333: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 334: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 335: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 336: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 337: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 338: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 339: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 340: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 341: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 342: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 343: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 344: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 345: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 346: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 347: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 348: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 349: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 350: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 351: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 352: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 353: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 354: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 355: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 356: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 357: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 358: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 359: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 360: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 361: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 362: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 363: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 364: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CC681E8 requests cancelled 365: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CC681E8 366: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 367: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CC681E8 is already held, deferring to dpc or workitem 368: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 369: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 370: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 371: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 372: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD4AFE8 requests cancelled 373: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD4AFE8 374: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 375: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x7CD4AFE8 is already held, deferring to dpc or workitem 376: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 377: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo 378: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleDecrementIo from FxIdleBusy 379: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7CE73D78 ! devobj 0x82F27B58 entering power idle state FxIdleBusy from FxIdleDecrementIo ---- end of log ---- Thanks and Regards, Sushma Tag: Test cases for WLAN SDIO interface Tag: 105563
  - 3
    - IRP Tracker I see many entries in Device Selection Menu. In that \Driver\Disk is a entry which gives the entries for all the disk in the system. My doubt is,say for a disk I see entries and I notice that a particular IOCTL IOCTL_DISK_GET_DRIVE_LAYOUT reaches only \Device\Harddisk2\DR3 in my case. what is that DR3 ,what does that mean. what are all the other entries like \Device\Harddisk2\DP(2)0X8004400 - 0XC800000+7 \Device\Harddisk2\DP(1)0X4400 - 0X8000000 + 6 can anybody explain what entry is that. why that particular IOCTL reaches \Device\Harddisk2\DR3 from the application eventhough I have filter drivers between. Thanks in advance. Hope I havent confused Tag: Test cases for WLAN SDIO interface Tag: 105562
  - 4
    - Porting WDM to WDF Hello All, I am porting a USB WDM driver to WDF. I have some vendor specific commands thats needs to submitted to lower device. I get a bugcheck 0x7E at WdfIoTargetSendInternalIoctlSynchronously(). Can some one help me if im going wrong anywhere in the below code. Here are the WDM and WDF code snippets. WDM -------- NTSTATUS SubmitUSB() { usUrbSize = (USHORT)sizeof(struct _URB_CONTROL_VENDOR_OR_CLASS_REQUEST); pUrb = (PURB)ExAllocatePoolWithTag(NonPagedPool, usUrbSize, 'BSUD'); if (pUrb == NULL) { DbgPrint(1, ("ExAllocatePool Failed.. No Memory\n")); return STATUS_NO_MEMORY; } UsbBuildVendorRequest(pUrb, URB_FUNCTION_VENDOR_DEVICE, usUrbSize, USBD_TRANSFER_DIRECTION_IN | USBD_SHORT_TRANSFER_OK, 0, ucRequest, usValue, usIndex, pBuffer, NULL, ulTransferLen, NULL); KeWaitForSingleObject( &KeSyncSubmitUrb, Executive, KernelMode, FALSE, NULL ); KeInitializeEvent(&kEvent, NotificationEvent, FALSE); // Build an IRP pIrp = IoBuildDeviceIoControlRequest(IOCTL_INTERNAL_USB_SUBMIT_URB, pdoNext, NULL, 0, NULL, 0, TRUE, &kEvent, &ioStatus); if (pIrp == NULL) { DbgPrint(1, ("IoBuildDeviceIoControlRequest() failed!\n")); status = STATUS_INSUFFICIENT_RESOURCES; } else { PIO_STACK_LOCATION pStack = IoGetNextIrpStackLocation(pIrp); pStack->Parameters.Others.Argument1 = pUrb; IoSetCancelRoutine(pIrp, NULL); // Call the USBD status = IoCallDriver(pdoNext, pIrp); if (status == STATUS_PENDING) { LARGE_INTEGER TimeOut = { (ULONG)(-10000 * 1000), -1 }; while ( status != STATUS_SUCCESS ) { // Wait for completion status = KeWaitForSingleObject(&kEvent, Executive, KernelMode, FALSE, &TimeOut); if ( status != STATUS_SUCCESS ) { DbgPrint(1, ("KeWaitForSingleObject failed\n"); if ( status == STATUS_TIMEOUT ) { IoCancelIrp( pIrp ); } } } status = ioStatus.Status; } } KeSetEvent( &KeSyncSubmitUrb, 0, FALSE ); } WDF Equivalent ----------------------- NTSTATUS SubmitURB() { PURB pUrb = NULL; WDFMEMORY urbMemory; WDF_OBJECT_ATTRIBUTES objectAttribs; WDF_MEMORY_DESCRIPTOR memoryDesc; usUrbSize = (USHORT)sizeof(struct _URB_CONTROL_VENDOR_OR_CLASS_REQUEST); WDF_OBJECT_ATTRIBUTES_INIT(&objectAttribs); objectAttribs.ParentObject = Device; status = WdfMemoryCreate( &objectAttribs, NonPagedPool, POOL_TAG, usUrbSize, &urbMemory, (PVOID*) &pUrb); if (!NT_SUCCESS(status)) { DbgPrint(1, ("Failed to alloc mem for urb\n")); status = STATUS_INSUFFICIENT_RESOURCES; return status; } UsbBuildVendorRequest(pUrb, URB_FUNCTION_VENDOR_DEVICE, usUrbSize, USBD_TRANSFER_DIRECTION_IN | USBD_SHORT_TRANSFER_OK, 0, ucRequest, usValue, usIndex, pBuffer, NULL, ulTransferLen, NULL); WDF_MEMORY_DESCRIPTOR_INIT_HANDLE(&memoryDesc, urbMemory, (USHORT)sizeof(URB)); status = WdfIoTargetSendInternalIoctlSynchronously(WdfDeviceGetIoTarget(Device), NULL, IOCTL_INTERNAL_USB_SUBMIT_URB, &memoryDesc, NULL, NULL, NULL); if (!NT_SUCCESS(status)) { DbgPrint(1, ("WdfIoTargetSendInternalIoctlSynchronously Failed with error 0x%x\n",status)); return status; } } Thank You. Regards, uba Tag: Test cases for WLAN SDIO interface Tag: 105561
  - 5
    - IOCTL_DISK_GET_DRIVE_LAYOUT doubt I have a lower filter driver(sits below file system driver) From the application I pass IOCTL_DISK_GET_DRIVE_LAYOUT ioctl. I get error as my partition style is GPT. I am not supporting GPT Partition style for now in my driver.so I wanted to log the error in system logs from the driver if it is GPT. But when I tried to log it I see that the particularIOCTL never reaches my driver. Is it possible that file system driver can return error for this IOCTL. I tried checking with irp tracker .when I select my driver and see for the occurence of the particular IOCTL I am not seeing the IOCTL. when I select the corresponding GPT disk in select disk menu I see the IOCTL that is required. Is it that the IOCTL is returned back with error code by file system driver before even my filter receives it. I also see that the error code is INVALID_DEVICE_REQUEST in IRP Tracker. I believed that disk.sys is responsible for the above IOCTL.so I expected my that IOCTL_DISK_GET_DRIVE_LAYOUT should reach my driver.But I am not sure whether my driver receives the IOCTL. Can anybody help on this. does file system driver have any specific check in it. Tag: Test cases for WLAN SDIO interface Tag: 105560
  - 6
    - about URB_FUNCTION_SELECT_INTERFACE I want to change interface setting, and the code as below: PURB urb; USBD_CONFIGURATION_HANDLE hConfig; PUSB_CONFIGURATION_DESCRIPTOR pcd; USBD_INTERFACE_LIST_ENTRY interfaces[4]; PUSB_INTERFACE_DESCRIPTOR pid; PURB pUrbSelIntf = NULL; ... urb = USBD_CreateConfigurationRequestEx(pcd, interfaces); status = SendUrb (Adapter, selurb); hconfig = selurb->UrbSelectConfiguration.ConfigurationHandle; .. pUrbSelIntf = (PURB)ExAllocatePool(NonPagedPool, GET_SELECT_INTERFACE_REQUEST_SIZE(pid->bNumEndpoints)); UsbBuildSelectInterfaceRequest(pUrbSelIntf, GET_SELECT_INTERFACE_REQUEST_SIZE(pid->bNumEndpoints), hconfig, 0, 1); status = SendUrb (Adapter, pUrbSelIntf); but when I submit the pUrbSelIntf, OS bring blue screen. why? How can I do this? Tks! Tag: Test cases for WLAN SDIO interface Tag: 105559
  - 7
    - How can I send file or data from WinCE to PC by USB connection ? Hi How can I send file or data from WinCE to PC by USB connection ? Can Activesync service or other way do that , is there any document or sample code ? Thank you . Tag: Test cases for WLAN SDIO interface Tag: 105558
  - 8
    - IRQL of HwStorAdapterControl Hi, What is the IRQL HwStorAdapterControl is called at? Thank you, Andrew Tag: Test cases for WLAN SDIO interface Tag: 105557
  - 9
    - USB on Windows XP: Composite Devices and Selective Suspend Hi, I have a requirement to Selectively Suspend a Composite Device on Windows XP Does anyone know if the Common Class Generic Parent driver (usbccgp.sys) supports Selective Suspend under Windows XP? Is there a minimum SP (i.e. SP2 or SP3) needed to support this? TIA Pete Tag: Test cases for WLAN SDIO interface Tag: 105556
  - 10
    - How to unlock system protected file ? Hi I found serial.sys has been locked by system , so I cannot replace it by my sample code built serial.sys . Is there any way to unlock some built-in generic driver in Windows XP and Vista ? Thank you . Tag: Test cases for WLAN SDIO interface Tag: 105555
  - 11
    - about function COM_IOControl in Virtual COM driver hello,everybody! I'm try to create a virtual COM driver. when i applying the function COM_IOControl: DWORD COM_IOControl(DWORD hOpenContext,DWORD dwCode,PBYTE pBufIn,DWORD dwLenIn,PBYTE pBufOut,DWORD dwLenOut,PDWORD pdwActualOut) i've received some values of dwCode parameter,like 0x1B0050 1769552 0x1B0054 1769556 0x1B003C 1769532 0x1B0048 1769544 0x1B0028 1769512 0x1B0044 1769540 but i don't know what these mean. Can you help me ? Thanks! Tag: Test cases for WLAN SDIO interface Tag: 105554
  - 12
    - Collate value in Bitmap virtual Printer Driver I am developing a Bitmap virtual printer driver based on Microsoft Universal Printer Driver(Unidrv) Problem is inside driver i am not getting the value of "dmCollate" member of "DEVMODE" I read in MSDN they specify This member is ignored unless the printer driver indicates support for collation by setting the dmFields member to DM_COLLATE. also try after set dmFields to DM_COLLATE but then also i am not getting the value of dmCollate. I tried using PDEVMODEW pDevMode; pDevMode = (PDEVMODEW)pDevObj->pPublicDM; pDevMode->dmFields = DM_COLLATE; But i am not getting the value of "pDevMode->dmCollate" If any one have idea on this topic then please help me. Thanks in advance Tag: Test cases for WLAN SDIO interface Tag: 105553
  - 13
    - USB packet ? Hi Does USB has negociate protocol , is there any tool to monitor USB packets ? Where can I find the reference documents ? Thank you . Tag: Test cases for WLAN SDIO interface Tag: 105552
  - 14
    - correct forum for Setup & Deployment & driver installation? Hi, Which is the right forum to ask question related to below types? 1) Setup & Deployment 2) Driver installation & uninstallation using DIFx DPINST tools Thanks, Kota Tag: Test cases for WLAN SDIO interface Tag: 105544
  - 15
    - Prevent loading of SCSIAdapter in Safe Mode Hi, Is there any way to prevent my driver from being loaded in safe mode? In my INF, I have Class=SCSIAdapter. Thank you, Andrew Tag: Test cases for WLAN SDIO interface Tag: 105541
  - 16
    - Filter driver question Hi Can Vista use filter driver , any framework change ? Does MSDN Library tell us much about filter driver ? I have question about ComPort Inf section of msports.inf [ComPort.NT.HW] AddReg=ComPort.NT.HW.AddReg [ComPort.NT.HW.AddReg] HKR,,"UpperFilters",0x00010000,"serenum" What does Inf HW section use for, and where will it create registry key ? Thank you . Tag: Test cases for WLAN SDIO interface Tag: 105537
  - 17
    - Visual studio project files for devcon Somebody asked for it, so here it is... Visual Studio 2008 ex. project for the WDK sample program devcon (KB311272). http://w16.easy-share.com/1700307651.html Make a copy of devcon source directory and extract the zip there; the solution file is in vcproj subdir. Enjoy. --PA Tag: Test cases for WLAN SDIO interface Tag: 105535
  - 18
    - IoAllocateMdl Failure- returns NULL 30% in Vista64 but not in othe Hi, I observed that IoAllocateMdl is returning NULL around 30% of the times in Vista64 but not that much in other OS. I am allocating the MDL memory for 16MB. System is AMD 64-bit 2GB RAM and for other OS also, i tested in the same PC. Do i have modify any settings in vista64-PC to increase the success rate of IoAllocateMdl? I have read in an article, when system loads heavily & runs lack of system pages, it happens, but i tried with SystemPages 0 to not limit of the pages allocation in regedit, but the response is same. Thanks, Kota. Tag: Test cases for WLAN SDIO interface Tag: 105523
  - 19
    - PC Restart required after driver unload and before installing agai Hi, I am working on a WDF PCI device driver, driver supports PNP functionality. Problem: when driver uninstalled, i had to restart the system in xp-32 & xp-64 before driver installing again, where as this is not required in vista-32 bit pc. Driver installation: I am currently using DIFX tools DpInst for installing & uninstalling the driver. I also verified that my driver unmaps the resources before uninstalling the driver using MmUnmapIoSpace to unmap the PCI memory resources. Device doesnt support power managment capability, so driver also not supporting any power managment functionality, instead it just registers the callback & wont do anything inside. Since this problem is existing only in xp, do i have to take any extra care to avoid system restart? and also, after uninstall system doesnt prompt for restart also. Thanks, Prafulla Tag: Test cases for WLAN SDIO interface Tag: 105522
  - 20
    - How to refresh attached disk drivers? If there a way to force windows to refresh attached disk devices?. If I change the partition of a unit the system donâ??t refresh the status until disconnect and reconnect it. For this reason I search how to connect and disconnect, but if I can force a refresh I donâ??t need to disconnect the drive. Thanks for your time, and patience! -- Juan Segura www.sd-a.com juan@sd-a.com Tag: Test cases for WLAN SDIO interface Tag: 105521
  - 21
    - IOCTL_VOLUME_ONLINE and IOCTL_VOLUME_OFFLINE Hello: Turning around connect and disconnect disk devices I look at IOCTL_VOLUME_ONLINE and IOCTL_VOLUME_OFFLINE functions. However I donâ??t find any examples jet. I test this (in c#): SafeFileHandle h = CreateFile(â??\\\\.\\Physicaldriver3â??, GENERIC_READ | GENERIC_WRITE, FILE_SHARE_READ | FILE_SHARE_WRITE, IntPtr.Zero, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL | FILE_FLAG_WRITE_THROUGH, new SafeFileHandle(IntPtr.Zero, true)); if (!h.IsInvalid) { long bret = 0; bool ret=DeviceIoControl(h, IOCTL_VOLUME_OFFLINE,IntPtr.Zero,0,IntPtr.Zero,0, out bret, IntPtr.Zero); â?¦ Where IOCTL_VOLUME_OFFLINE is 3, meanwhile IOCTL_VOLUME_ONLINE is 2. The GetLastWin32Error returns 50, I thing â??ERROR_NOT_SUPPORTEDâ??. The Physicaldriver3 is an USB Memory stick dervice. I know others ways for disconnect USB, but my target is to reconnect the USB without human intervention. Thanks for your time! -- Juan Segura www.sd-a.com juan@sd-a.com Tag: Test cases for WLAN SDIO interface Tag: 105520
  - 22
    - sdram configuration,pls help dear all, I know this might be an old question for u guys, but I really met some troubles within it. My platform is: CPU : Xscale pxa255 OS : Windows CE .Net 4.2 Flash : 32MB SDRAM : 128MB (32MBX4) Now I want to set the configuration of 128M SDRAM. following some suggestions,I modified the some files below, but it does not work.. now,I list my main modification: ////////////////////////////////////// config.bib ////////////////////////////////////// MEMORY IF IMGFLASH ! NK 800B8000 02000000 RAMIMAGE RAM 820B8000 05C00000 RAM EDBG 87F8D000 00020000 RESERVED ENDIF AUD_DMA 87CB8000 0000A000 RESERVED SLEEP_SAV 87CC2000 00001000 RESERVED DRV_GLB 87CC3000 00001000 RESERVED CACHE_FLG 87CC4000 0003C000 RESERVED DISPLAY 87D00000 00130000 RESERVED BLOCK_BUF 87E30000 00080000 RESERVED UNUSED_BUF 87EB0000 000DD000 RESERVED whql_sig 00000001 00002000 EXTENSION ZBANK 88000000 00100000 RESERVED CONFIG IF IMGFLASH ! AUTOSIZE=ON ENDIF IF IMGFLASH ! ROMSTART=800B8000 ROMWIDTH=32 ENDIF ROMSIZE=01D00000 ///////////////////////////////// memmap.inc //////////////////////////////// DCD SDRAM_BASE_C_VIRTUAL,SDRAM_BASE_PHYSICAL,128 DCD ZBANK_BASE_C_VIRTUAL, ZBANK_BASE_PHYSICAL, 1 DCD MEMC_BASE_C_VIRTUAL, MEMC_BASE_PHYSICAL, 1 DCD PERIF_BASE_C_VIRTUAL, PERIF_BASE_PHYSICAL,32 DCD PCMCIA_S0_IO_C_VIRTUAL, PCMCIA_S0_IO_PHYSICAL, 32 DCD PCMCIA_S0_ATTR_C_VIRTUAL, PCMCIA_S0_ATTR_PHYSICAL, 32 DCD PCMCIA_S0_CMN_C_VIRTUAL, PCMCIA_S0_CMN_PHYSICAL, 64 DCD PCMCIA_S1_IO_C_VIRTUAL, PCMCIA_S1_IO_PHYSICAL,32 DCD PCMCIA_S1_ATTR_C_VIRTUAL, PCMCIA_S1_ATTR_PHYSICAL, 32 DCD PCMCIA_S1_CMN_C_VIRTUAL, PCMCIA_S1_CMN_PHYSICAL, 64 DCD LCD_BASE_C_VIRTUAL, LCD_BASE_PHYSICAL, 1 DCD BOOT_FLASH_BASE_C_VIRTUAL, BOOT_FLASH_BASE_PHYSICAL, 32 DCD CS8900A_BASE_C_VIRTUAL, CS8900A_BASE_PHYSICAL, 1 DCD XHYPER255B_PERI_C_VIRTUAL, XHYPER255B_PERI_PHYSICAL, 5 DCD CY7C67300_BASE_C_VIRTUAL, CY7C67300_BASE_PHYSICAL, 1 DCD nCS4_BASE_C_VIRTUAL, nCS4_BASE_PHYSICAL, 8 DCD nCS5_BASE_C_VIRTUAL, nCS5_BASE_PHYSICAL, 8 DCD 0x00000000, 0x00000000, 0 then,I changed xsc1.h,xsc1.inc,xsc1bd.h,xsc1bd.inc to be in sync with config.bib and OEMAddressTable, and I checked a lot ,there's no problem with them. /////////////////////////////////////////////////////////////////////// and in memdefs.h, I was a little confused about the codes below: and I modified the two values which I marked to sync. /////////////////////////////////////////////// #ifndef SABINAL // // Cotulla-32 Defs // #define MEM_BASE_PHYSICAL 0xA3CB8000 #define MEM_BASE_C_VIRTUAL 0x87CB8000 //modifed #define EDBG_PHYSICAL_MEMORY_START 0x87F8D000 //modifed #else // // Sabinal Defs //this seems not used,so I do not modify the value #define MEM_BASE_PHYSICAL 0xA1CB8000 #define MEM_BASE_C_VIRTUAL 0x81CB8000 #define EDBG_PHYSICAL_MEMORY_START 0x81F8D000 #endif /////////////////////////////////////////// I also changed the value in xsc1bd.inc MDCNFG_VAL EQU 0x19C319C3 ; Setup default MDCNFG value for 128MB SDRAM /////////////////////////////////////////// in the end,according to K.S.huang's advice,i modified file fwxsc1.s ; enable sdram bank 0 if installed (must do for any populated bank) orr r3, r3, #MDCNFG_DE0 ;4.28 add orr r3, r3, #MDCNFG_DE1 ;add above and also changed some uart address in platform.reg such as: ;------------------------------------------------------------- ; Serial1 : FFUART ;------------------------------------------------------------- ; @CESYSGEN IF CE_MODULES_SERIAL IF BSP_NOSERIAL ! [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial] "Dll"="xsc1bd_serial.Dll" ; "IoBase"=dword:a6300000 ;FFUART_BASE_U_VIRTUAL "IoBase"=dword:a8300000 ;FFUART_BASE_U_VIRTUAL ................ /////////////////////////////////////////////// when all of them had done,I download the NK.bin, and the debug information shows: rom_offset=0x0. Found pTOC signature. ROMHDR at Address 800B8044h RomHdr.ulRAMStart=81C50000h RomHdr.physfirst=800B8000h. Done. Writing 0x80076BD8 to flash address 0xB8340000 (length=0xA40). Sector=0x200 (Length=0x6) Block=0x1 (Length=0x1). Handling non-block aligned data... FlashErase: Unlocking flash block(s) [0x1, 0x1] (please wait): Done. Erasing flash block(s) [0x1, 0x1] (please wait): .Done. Writing to flash (please wait): Done. Got EDBG_CMD_JUMPIMG Got EDBG_CMD_CONFIG, flags:0x00000000 Download successful! Jumping to image at physical 0xA00B9000... Begin ****************************************************** ****************************************************** ****************************************************** ****************************************************** ****************************************************** OEMInitDebugSerial using UART2 Windows CE Kernel for ARM Built on Mar 13 2003 at 22:54:19 ProcessorType=02d0 Revision=6 sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 800b9ef4 as u see,my system hung at last, if normal,sp=ffffc7cc should be printed behind OEMAddressTable = 800b9ef4 but now,system hung there.... and Platform builder printed the word"Kernel debugger is waiting to connect with target." Anybody has experience ? could u give me some advice? I so appreciate it, thank u a lot. Tag: Test cases for WLAN SDIO interface Tag: 105519
  - 23
    - Generating a driver without DDK,... Hi, i have a situation here which is really true. I have a old laptop, running windows 2000 professional and there is no space left for the DDK from Microsoft. I want to write and test some (simple, monolithic) drivers, targeting 2000/XP/Vista which handle a special device over USB. So the situation is that i dont have a lot of space for ddk on my machine and i am looking for a way to write a driver, compile it into a native image and all this WITHOUT the MS DDK. Is there such a way, a minimal package of compilers, headers, not bigger than 200 MB? I already have livekd and WinDbg here, but no compiler so far and no environment. The environment should be as small as possible and the compiler should be capable of inline assembly. Is something like this available somewhere? I am not kidding, i really have no space left here on the machine. This may sound funny but this is really the situation. Regards Kerem -- ----------------------- Beste Grüsse / Best regards / Votre bien devoue Kerem Gümrükcü Microsoft Live Space: http://kerem-g.spaces.live.com/ Latest Open-Source Projects: http://entwicklung.junetz.de ----------------------- "This reply is provided as is, without warranty express or implied." Tag: Test cases for WLAN SDIO interface Tag: 105515
  - 24
    - Can one force a USB disconnect then reconnect? Is there a way to have Windows pretend a USB device has been unplugged, then plugged back in? -- #include <standard.disclaimer> _ Kevin D Quitt USA 91387-4454 96.37% of all statistics are made up Tag: Test cases for WLAN SDIO interface Tag: 105513
  - 25
    - extra WHQL warnings My app calls UpdateDriverForPlugAndPlayDevices and it works. The driver is installed, the device works, everybody is happy. Except... If more than one instance of the model in question is on the bus (it's a USB device), then I get not just one WHQL warning but at least one more. And the pattern is very weird. Let's say the user plugs in one of my devices, and my app calls UpdateDriverForPlugAndPlayDevices, and the user gets a WHQL warning, and she says continue, and everything works. Peachy, right? Now she plugs in a second device and she gets two warnings. Weird! Let's say she says continue two more times and then plugs in a third device. Now she gets three warnings, but the weirdness is just getting started. She plugs in a fourth instance of the device and she gets one warning (expected) but then she plugs in a fifth instance and gets two warnings. Remember, I get the extra warnings even if all but one instance of the device in question already has the driver. But, just to be paranoid, I made sure I was not calling UpdateDriverForPlugAndPlayDevices again due to re-entrant delivery of messages to my window. Of course, I am looking to inhibit the extra WHQL warnings. Any ideas? Pete Gontier http://www.m-audio.com/ pete (at) m-audio (dot) com Tag: Test cases for WLAN SDIO interface Tag: 105510
- Next
  - 1
    - Mount and dismount physicaldriver Hello: I donâ??t know if it is the correct forum, sorry if Iâ??m wrong. I need to mount and dismount physical drives, like \\.\Physicaldrive0 for example, for a backup software. The idea is to dismount the usb drive after the backup for a safe extraction (this is the less problem), and mount it before start the backup. All of this without human intervention. I develop in c#, but I call Kernel32.dll APIs. Some ideas? Thanks, and sorry for my bad English! -- Juan Segura www.sd-a.com juan@sd-a.com Tag: Test cases for WLAN SDIO interface Tag: 105508
  - 2
    - Creating an IP option within a WFP Callout Hello everyone, I am trying to design a driver that will add an IPv4 option to every outbound IPv4 packet. I have developed a WFP callout that allows me to inspect each IP packet as flows through the network layer. At this point I'd like to clone the netbuffer, add the option header and recalculate the appropriate fields. However, I am stuck at one critical area. I need to report to the higher layers that the MTU is reduced by the size of the option header to ensure that the finished packets do not exceed the MTU. Since an outbound network layer callout can not see IP fragments, I am concerned that the packet will then be fragmented, thus invalidating the header that I applied (each option is correlated to the data in the payload). Can any of the forum gurus give me any advice? Thanks! Tag: Test cases for WLAN SDIO interface Tag: 105505
  - 3
    - Access violation when device plugged out I have allocated using ExAllocatePoolWithTag to allocate buffer from non paged pool for reading data through the USB AV streaming device. when the driver is streamng the data from the device, and when device is suddenly removed, I check for the URB's status for NO DEVICE after IoCall driver to the next device object. The data recieved is buffered and processed and sent to the other layer. during this time some time when the device is plugged out suddenly, it gives ACCESS VIOLATION BSOD with 0x7E, I am sure the allocated memory is not freed also, the accessed location is not out of bounds of the allocated memory area. The address is not null. Is there any way to check whether the address is valid. This happens only when the device is plugged out. and during normal operation, it works fine. There are 2 possibilities: Device present: during this time bulk transfer is done to read the data from deivce into the buffer and is further sent to processing. Device is removed: when a bulk transfer is attempted, it is programmed to return STATUS_NO_SUCH_DEVICE such that the call is returned and the buffer pointer is not sent for processing. In both the case, how does it give access violation, as the buffer is allocated and is not freed yet. Can somebody let me know if any thing I am missing.. Thanks.. Tag: Test cases for WLAN SDIO interface Tag: 105495
  - 4
    - WPP Tracing in miniport Hi, How do I use HwStorInitializeTracing in a miniport driver? Would the following be correct: HwStorInitializeTracing(p1,p2) { WPP_INIT_TRACING(p1,p2) } Thank you, Andrew Tag: Test cases for WLAN SDIO interface Tag: 105493
  - 5
    - Windows 95/98 Vxd driver question Hi I might need to study Windows 98 Vxd driver framework , is there any book talk abount it ? Where can I find MSDN online document about Vxd driver ? Thank you . Tag: Test cases for WLAN SDIO interface Tag: 105486
  - 6
    - Bug in usbser.sys when using a high speed hub I have a full speed USB device that I'm developing that uses usbser.sys. I found that if I connect the device directly to my Dell laptop everything works find. If I connect the device through a high speed USB 2.0 hub everything is very flaky. I see hangs when opening the com port, Windows lockups, and other wierd falures. I found a workaround. If I disabled the enhanced USB controller in device manager to force the hub to use full speed everything is rock solid. So this makes me think the problem is either a bug in Windows or a bug with the Intel chipset in my Dell Inspiron laptop. 1. Is this a known bug in usbser.sys or Windows? 2. What do I need to do to report the problem? My operating system is Vista SP1. Tag: Test cases for WLAN SDIO interface Tag: 105484
  - 7
    - Asyc Call Of MiniportProcessSGList If HAL asynchronously completes the request to to create a scatter/gather list through calls to NdisMAllocateNetBufferSGList (i.e., completes the request outside of the context of the NDIS call), can I assume that it serialize the completion of pending requests? For example, if I have two requests, can I assume that request #1 will always be completed before request #2? Thanks! Tag: Test cases for WLAN SDIO interface Tag: 105483
  - 8
    - Deserialized miniport question Hi, I am leveraging a deserialized miniport driver that hooks into the NDIS library. The driver is written in WDM format, not in WDF, and the OS is Windows XP The miniport driver hooks into the Windows TCP/IP stack and uses my hardware driver to send and receive data across the physical medium. The hardware is a PCIe Non-transparent bridge. I have successfully connected on a HARDWARE level, and am able to transfer data back and forth between the processors' exposed memory. Consider: Processor A = Windows XP = miniport Driver. Processor B = other side of the NTB PCIe chip. Processor A boots first, and establishes the connections as far as it can. When Processor B boots, it sends a GRATUITOUS ARP to Processor A through my hardware and miniport driver. 1) From what I can tell, the ARP comes across from B to A, and I can see it in Wireshark when I monitor my adapter. HOWEVER, the ARP information does not get logged into the ARP table, even when I â??preloadâ?? the table with the IP and a bogus Physical Address. I was expecting the Physical Address to get updated with the GRATUITOUS ARP, but it doesnâ??t. 2) Data from the GRATUITOUS ARP is passed up to the Windows stack via a call to NDISMIndicateReceivePacket() in my minport driver, and I can see my MiniportReturnPacket() function get called to release the packet. 3) Next, when I try to â??pingâ?? Processor B from Processor A, I can see the ping request come across into Processor B, and then see B respond back to A. I see the data come through into the miniport driver, but it all hangs when NdisMIndicateReceivePacket() is called. There is no Blue screen of Death, but it might as well, because it all hangs. It BEHAVES as if the system is locked on a spin lock, but I donâ??t think that is it. I can comment in and out the NdisMIndicateReceivePacket( ) to change behavior. The OOB data packet status is set to: NDIS_SET_PACKET_STATUS(RecvPacket, NDIS_STATUS_SUCCESS); Prior to calling NdisMIndicateReceivePacket(). I am looking for ideas on what to look into as possible suspects. Does anyone have any thoughts? Thanks, Jan Tag: Test cases for WLAN SDIO interface Tag: 105480
  - 9
    - Ramdisk with Vista SP1 Hi, I installed the wdk 6.0 6001.18001 on Windows Vista SP1, then I compiled the exmaple of the ramdisk. After I installed the driver, i noticed that the disk are not accessible via the explorer nor the cmd. But if I launch the cmd via the administrator rights, i can access the ramdisk drive. How I can do to get it worked around normal user? Thanx, Pierluigi Tag: Test cases for WLAN SDIO interface Tag: 105479
  - 10
    - Ramdisk example and Vista Hi, I installed the wdk 6.0 6001.18001 on Windows Vista SP1, then I compiled the exmaple of the ramdisk. After I installed the driver, i noticed that the disk are not accessible via the explorer nor the cmd. But if I launch the cmd via the administrator rights, i can access the ramdisk drive. How I can do to get it worked around normal user? Thanx, Pierluigi Tag: Test cases for WLAN SDIO interface Tag: 105478
  - 11
    - USB 2.0 Streaming MPEG - Best way to queue request? We have a USB 2.0 device that outputs small multiples of MPEG2 TS packets(188 bytes), and therefore need to queue up multiple BULK requests to the USB bus driver(USBD) in order to keep the MPEG2 video flowing without dropping packets. Since in BULK mode our requests are not aligned on 512 byte boundaries, submitting a large buffer to the USBD does not help, since in BULK mode a transaction of less than 512 bytes ends the session. So the question is: What is the best way to queue up multiple BULK requests with small buffers in the driver? Are System Work Items a way to go, queue up multiple initially, then requeue in the callback? The DDK docs indicate that the System thread pool is a shared resource and should be used sparingly... Any suggestions would be appreciated. Thanks -decoder Tag: Test cases for WLAN SDIO interface Tag: 105477
  - 12
    - DIFxApp download help I am trying to download DIFxAPP so that I can integrate a driver installation with my application installer. I keep finding myself going in circles trying to find it and would appreciate a URL. I went to the Installer home page and still was able to find the latest version. Thanks, Sid. Tag: Test cases for WLAN SDIO interface Tag: 105471
  - 13
    - DPInst.exe encounters PnP Manager busy With Windows XP SP2, following is my installation experience using DPInsta.exe v2.1.0.0: 1. With deceive attached during installation, the DPInst.log reports, "PnP Manager busy, waiting until it processed the pending install events". And the driver won't be installed if the 'Found New Hardware Wizard' is not dismissed manually. How to fix the issue to allow auto installation without user intervention? 2. After preinstall the device driver, the XP machine still pops up the 'Found New hardware Wizard' for the device which requires user to search for the driver that has been pre-installed in the system. How to avoid the pops up after preinstall? Tag: Test cases for WLAN SDIO interface Tag: 105470
  - 14
    - How to call the kernel API which is not in the DDK document! I can't find that kernel API in the DDK document. But it is exposed by ntoskrnl.exe. What should I do to call it ! Thank you very much! -- å¤©è?¥æ??æ??å¤©äº¦è??ï¼?äººé?´æ£é??æ?¯æ²§æ¡?ã?? Tag: Test cases for WLAN SDIO interface Tag: 105459
  - 15
    - custom page size and dmPaperLength/dmPaperWidth If in Microsoft Word's "Page Setup" dialog I select custom page size and enter 1.5 inch width by 1 inch high, how does this information get passed to the printer driver? I expected that the DEVMODE passed to DrvEnablePDEV would contain the correct dmPaperLength and dmPaperWidth, but these values seem to be the default form size for the printer. I set a breakpoint at DrvEnablePDEV and inspected every DEVMODE passed to the driver. All of them contained the default page size as set in the "Printing Preferences" property pages. Several of the calls showed the DEVMODE dmFields did have DM_PAPERLENGTH and DM_PAPERWIDTH set, but the values for those fields were still the default for the printer. I know these values are available because another vendor's printer driver works correctly in this case. What am I missing? Neal Tag: Test cases for WLAN SDIO interface Tag: 105452
  - 16
    - WPP & KMDF Crash I have been attempting to use WPP tracing in my Bus Driver and when I create a session in TraceView with either the symbols or CTL file I will get a bug check on occasion. I have several function driver which use WPP just fine. Any pointers on where to start looking? PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: 86193940, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: 819da52f, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 819726d8 Unable to read MiSystemVaType memory at 819532e0 86193940 FAULTING_IP: nt!WmipForwardWmiIrp+75 819da52f ff10 call dword ptr [eax] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: 85728b94 -- (.trap 0xffffffff85728b94) ErrCode = 00000000 eax=86193940 ebx=84c6b008 ecx=00000004 edx=00000000 esi=84371178 edi=85728c90 eip=819da52f esp=85728c08 ebp=85728c40 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!WmipForwardWmiIrp+0x75: 819da52f ff10 call dword ptr [eax] ds:0023:86193940=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 818a0ae4 to 818b6b4e STACK_TEXT: 85728b7c 818a0ae4 00000000 86193940 00000000 nt!MmAccessFault+0x158 85728b7c 819da52f 00000000 86193940 00000000 nt!KiTrap0E+0xdc 85728c40 819da169 00000000 00000004 86193940 nt!WmipForwardWmiIrp+0x75 85728c6c 819da1be 00000004 86193940 85728ce8 nt!WmipSendWmiIrp+0x56 85728c9c 819ad46a 00000004 86f56c74 00000040 nt!WmipDeliverWnodeToDS+0x22 85728d18 819ad24b 99abf480 86f82754 8193e8fc nt!WmipProcessLegacyEtwCallback+0x89 85728d44 818a16be 86f82754 00000000 82a8e828 nt!WmipLegacyEtwWorker+0x5e 85728d7c 819ee6ad 86f82754 5ac88d9a 00000000 nt!ExpWorkerThread+0xfd 85728dc0 818d5686 818a15c1 00000001 00000000 nt!PspSystemThreadStartup+0x9d 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!WmipForwardWmiIrp+75 819da52f ff10 call dword ptr [eax] SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!WmipForwardWmiIrp+75 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a FAILURE_BUCKET_ID: 0x50_nt!WmipForwardWmiIrp+75 BUCKET_ID: 0x50_nt!WmipForwardWmiIrp+75 Followup: MachineOwner Tag: Test cases for WLAN SDIO interface Tag: 105444
  - 17
    - BthPort - How do I get the connection? I notice that there are a series of Bluetooth functions that talk to and return a handle to BthPort. I need something like "\\?\BthPort" that I can call from another driver. Unfortunately MS made all the control calls only callable from another device driver (IRP_MJ_INTERNAL_DEVICE_CONTROL) and not from the App layer so I need to write a relay driver to call SCO. I see that BthPen, BthModem, BthEnum, and BthUSB have calls. What is the exported device name for BthPort? Thanks, -Erik Tag: Test cases for WLAN SDIO interface Tag: 105442
  - 18
    - malloc,free,mbtow problem hi i m working on file hooking i had applied two basic hooks i.e NTCreateFile and NtOpenFile i am almost finish but with very simple error and i am unable to resolve: i am allocating dynamic memory to char pointer i.e. char *cPtrDst ; cPtrDst = (char*)malloc(size); and deallocating it by free: free(cPtrDst); and i am converting this array into wchar_t variable using : wchar_t dir[10];//suppose its an array result = mbtowc(dir,cPtrDst,size); when i compile the driver it gives error: error LNK2019: unresolved external symbol __imp__free referenced in function _freePolicyData@0 unresolved external symbol __imp__malloc referenced in function _policyWriteNeither@8 i had included stdlib.h but in vain......... any idea about error? Tag: Test cases for WLAN SDIO interface Tag: 105435
  - 19
    - Filtering the I/O requests sent by non-system applications in a file HI, I'm a newbie in the world of drivers. I'm developing a file system filter driver that needs to process all I/O requests sent in by user mode applications eg; MS Word, Excel etc; I don't want to do any sort of processing on IRPs generated on behalf of the Windows OS itself ( I'm not sure I'm using the correct words here :) ). To put it simple, I want to distinguish between IRPs generated on behalf of the OS processes and those generated on behalf of user mode applications. Could anybode tell me the easiest mechanism to achieve this? Thanks in advance, Shaji. Tag: Test cases for WLAN SDIO interface Tag: 105429
  - 20
    - windows file system internals -o reilly ebook??????? I need to know whether any link is there to download windows NT file system internals book.osr publications.Is there any e book for this is available??? If so can anybody send a link to it. Thanks in advance Tag: Test cases for WLAN SDIO interface Tag: 105424
  - 21
    - STORAGE-0012: Separated Cache Solution WHQL test I have a question about the Separated Cache Solution WHQL test. =46rom the language contained within, it seems the STORAGE-0012 test suite is defined to be more or less a stand-alone set of requirements that is self-contained from the perspective of not having a dependency on any other STORAGE-XXXX tests except STORAGE-0005 (except if a separate flash disk device is exposed in which case the device must be logo=92d separately as well). Barring the separately-exposed device case mentioned immediately above, it appears in particular that a STORAGE-0012 =93storage adapter=94 does not imply/include a requirement to meet all STORAGE-002 (Storage host controllers and adapters) requirements For one thing, it seems that if that was the intention, it would have been explicitly mentioned as that is the convention throughout the Windows Hardware Logo Program Requirements document. if anybody could give us an opinion on the relationship or non- relationship of STORAGE-0002 to STORAGE-0012, it would be most greatly appreciated. Thanks. Tag: Test cases for WLAN SDIO interface Tag: 105420
  - 22
    - returning DCR_HALFTONE from DrvDitherColor What does it mean to return DCR_HALFTONE from my printer drivers DrvDitherColor function? The DDK states that the return value should be "DCR_HALFTONE if the engine should create a halftone approximation for the driver." I return DCR_HALFTONE but this seems to have zero effect on the use of gray or colored brushes used by applications when drawing into my printer DC. In most cases, anything that is not white is printed as black. For example, black text on a gray background prints as a black block. Also, the following is from the comments section of the DDK documentation for DrvDither Color. What the heck does this mean? "Monochrome device drivers, including most raster printers, should use the iMode parameter to tell GDI how to get good gray-scale patterns." I don't understand. The "iMode" parameter is passed to my driver. What does that statement mean "to tell the GDI" ??? Tag: Test cases for WLAN SDIO interface Tag: 105415
  - 23
    - FileSystem: Non cached read. Hi all, i am writing the file system driver. There is a problem with non-cached read. here is the sample code, whenever the call reaches to keWaitForSingleObject() it hangs (waits) there infinitely? can anyone please tell me what could be the problem? i am using my own buffer ( allocated paged memory ). is it the case that i have to lock the buffer? i have tried with locking the buffer also. this problem occurs only in Windows XP not in Vista. is there any specific thing we need to take care? please help me, thanks hitesh ughreja here is the sample code. KEVENT Event; PIRP Irp; IO_STATUS_BLOCK IoStatus; NTSTATUS Status; KeInitializeEvent(&Event, SynchronizationEvent, FALSE); Irp = IoBuildSynchronousFsdRequest( IRP_MJ_READ, TargetDeviceObject, Buffer, Length, (PLARGE_INTEGER)(&Offset), &Event, &IoStatus ); if (!Irp) { Status = STATUS_INSUFFICIENT_RESOURCES; } Status = IoCallDriver(TargetDeviceObject, Irp); if (Status == STATUS_PENDING) { KeWaitForSingleObject( &Event, Executive, KernelMode, FALSE, NULL ); Status = IoStatus.Status; } if(!NT_SUCCESS(Status)) { DbgPrint("Read disk failure\n"); return Status; } Tag: Test cases for WLAN SDIO interface Tag: 105413
  - 24
    - PnP device recognition Hi. i have a question regarding the PnP mechanism. my driver (WDF based) controls a pci board. my system can have between one to ten boards on its backplane. my question is - is there a way for me to know (to be sure) that PnP have finished dealing with all of my boards (that are related to my driver) in a given moment. my user mode side of the system needs to know weather there are still boards that were not handled by the PnP. a possible soulution might be using some kind of configuration, meaning that the user mode will have to know how many boards exist on a given system and will be able to query the driver of how many boards were found in a given moment. but since i try to avoid this kind of solution i would to know if the OS/pnp mechanism can help me with that. thanks a ot, kobi. Tag: Test cases for WLAN SDIO interface Tag: 105409
  - 25
    - USB Composite Device and Selective Suspend on Windows XP Hi, Does anyone know if the Common Class Generic Parent driver (usbccgp.sys) supports USB Selective Suspend on Windows XP? Is there a minimum SP (i.e. SP3) needed to support this? TIA Pete Tag: Test cases for WLAN SDIO interface Tag: 105408

Hi All,
I am working in WLAN driver with SDIO interface. I have some
refrence code of WLAN but i dont know how to test this WLAN through
SDIO interface.I am very pretty new in this filed and mean to say ,
need some test plan to make some test cases for this driver
interface.

I will appreiciate if someone extend his arms.

Thnaks
Shivmangal

Top

Re: Test cases for WLAN SDIO interface by Pavel

Pavel
Mon May 05 13:35:45 CDT 2008

<soft.shivmangal@gmail.com> wrote in message
news:0d6c49c6-fd5a-4064-80a9-137933e277f0@b5g2000pri.googlegroups.com...
> Hi All,
> I am working in WLAN driver with SDIO interface. I have some
> refrence code of WLAN but i dont know how to test this WLAN through
> SDIO interface.I am very pretty new in this filed and mean to say ,
> need some test plan to make some test cases for this driver
> interface.
>
> I will appreiciate if someone extend his arms.
>
> Thnaks
> Shivmangal

Try NDIStest (it's part of WLK but can run standalone).

Regards,
--PA

Top