none
USB 2.0 & 3.0 SCSI Compliance test (LOGO) fails in Windows Hardware Certification Kit Signing Process RRS feed

  • Question

  • Hi,

           I am running USB 2.0 & 3.0 SCSI Compliance test (LOGO) task in Windows Hardware Certification Kit for Certification for my USB Filter Driver.

    Task was failed with RMB bit = 0x1 with Logging an error.

    Attaching the log info,

    Policy: REQUIRED
    Start: ASSERTION: INQUIRY Checking RMB bit, TUID=
    Description: For devices into which we can't insert/remove media, example: UFD, RMB bit should be set to 0. For devices into which we can insert/remove media, example: USB card reader, RMB bit should be set to 1. This test is run only on Removable storage devices.
    Reference: SCSI Primary Commands - 3 (SPC-3) Revision 23 (or published) specification Section 6.4 http://www.t10.org/ftp/t10/drafts/spc3/spc3r23.pdf
    Expectation: Correct value for RMB bit depending on the device
    Sending SCSI command to device.
    INQUIRY Command:
     12 00 00 00 ff 00
    DeviceIoControl SUCCEEDED.
    SCSI status: 0x00
        (GOOD)
    Sense bytes: 0x00
    Data bytes:  0x48

          00       04        08       0C      
          ---------------------------------------------------------------
     000  00800612 43000000  53616E44 69736B00    ....C...SanDisk.
     010  4372757A 65722042  6C616465 00000000    Cruzer Blade....
     020  312E3030 34433533  31303031 34373035    1.004C5310014705
     030  30353130 33353734  00006004 87000000    05103574..`.....
     040  3017C004 00000000  00000000 00000000    0...............
    == DONE ==============================================================
    Returned data size is 0x48 bytes.
    RMB bit = 0x1
    Error: 0x0, Error 0x00000000
    Logging an error
    File=testsrc\driverstest\storage\wdk\scsicompliance\lib\core\policyscenario.cpp Line=213
    End: Fail, ASSERTION: INQUIRY Checking RMB bit, TUID=, Repro=scsicompliance.exe  /device \\.\PhysicalDrive1 /verbosity 4 /scenario UsbDisk /operation test /version 2 /protocol BOT /rm 1 /wtg 0

    Can anyone had faced similar issue earlier and resolve it?

    Note : Even the same test case was failed without my filter driver. 

    Friday, April 6, 2018 6:02 AM