• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 3 answers
  • Subscribers 34 subscribers
  • Views 1037 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

TUSB3410: Modified 64-bit driver ver 6.7.4.0 failing Device Guard HCK test

TUSB3410: Modified 64-bit driver ver 6.7.4.0 failing Device Guard HCK test

Michael Linden
Prodigy 90 points
Part Number: TUSB3410


Hello. I am reopening this forum question, as it was not actually resolved in my email correspondence before my contact had left the company. Below is the copied text from the last post. Thanks.

Hi. As stated in the thread title, we are currently running version 6.7.4.0 of the usbuart driver through certification with our INF modifications but it has failed the Device Guard test. I understand this test is somewhat new and this driver version went through certification late last year or early this year, I think. Did the unmodified version pass this test or was it not in place at the time? And is there a way we can massage the driver into passing? The message I received from the lab is below:

We have a failure on the 64 bit driver.  The driver is not compatible with Windows 10 Device Guard. 

 

WDTF_TEST : Non-zero Code Integrity statistic found: Execute Pool Type Count: == 8

 

WDTF_TEST : Non-zero Code Integrity statistic found: Execute-Write Section Count: == 1

 

Please see https://blogs.msdn.microsoft.com/windows_hardware_certification/2015/05/22/driver-compatibility-with-device-guard-in-windows-10/ for information on how to test your driver for device guard compatibility.

  • 0
    TI__Expert 4325 points

    Hi Micheal,

    This driver was written by a 3rd party back and submitted for WHQL in Sept 2016 (Windows 10 Client family versions 1506 and 1511, x64).  I was not able to access the weblink you provided, but I found Device Guard was added in version 1709 so this would not have been tested. 

    AFAIK, device guard is an optional feature which we do not support.  We did not write this driver but I believe a code change and rebuild with latest WDK would be required to pass those tests.

    Regards,
    Brian

  • 0 in reply to Brian Quach
    Prodigy 90 points

    Hi Brian,

    Thanks for your reply. 

    My understanding is that the device guard test was optional in the past but that it ceased to be optional about a year ago. At least, my testing lab is not aware of a way to opt out of the test. Is there any way I can update the driver? We were this one test away from passing certification before the project stalled out on this issue.

    Thanks, 

    Mike

  • 0 in reply to Michael Linden
    TI__Expert 4325 points
    Hi Mike,

    I cannot release the source code so the best I can do is raise the request to my management to update the driver. What's your projected yearly volume for this part?

    Regards,
    Brian
  • 0 in reply to Brian Quach
    Prodigy 90 points

    Hi Brian,

    Sorry for the delay. It took awhile to get numbers from those in the know. This year we've shipped about 963 so far. We also have plans for 2 more variants of the device that uses this part if we can get the driver past certification.

    Thanks,

    Mike