[nvmewin] Static Driver Verification

[Thomas.Freeman at hgst.com]

I'm new to HCK testing, but I understand part of the testing requires a
Driver Verification Log (which contains the results from Code Analysis and
Static Driver Verifier). This is required for the Static Tools Logo test
(under the Device.Fundamentals category).
When I run those tools, I'm getting a large number of errors. The code
analysis shows over 50 warnings and the Static Driver Verifier fails
because the Callback roletypes (sp_DRIVER_INITIALIZE, HW_INITIALIZE, etc)
are not defined. Fixing the roletypes allows a new set of errors to appear.
I'm running with VS 2013 and WDK 8.1.
Am I missing something? Has anyone else run these tools against the code?


Tom Freeman
SSD Device Drivers/Firmware
HGST, a Western Digital company
Thomas.Freeman at HGST.com
507-322-2311/232311