1. 11/8/2018 8:19 PM
HW-98P
Windows 8 kernel debugging: New protocols and certification requirements
Tanya Radeva
Program Manager
Microsoft Corporation
Joe Ballantyne
Principle Software Design Engineer
Microsoft Corporation
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Agenda Modern Kernel Debug Transports Debuggable Windows Machines
Windows Certification Debug Requirements
You’ll leave knowing how to
Leverage Windows 8 inbox support for new debug transports
Design debuggable systems certified for Windows 8

3. Existing Kernel Debug Transports
Existing PC debugging hardware is going away
Serial is gone
1394 is being phased out
USB2 debugging hardware is available
Hard to setup
Requires external dongle
USB2 is being replaced with USB3

4. Modern Kernel Debug Transports
USB3.0 XHCI and Network Debugging
- Easy to setup
- No special cables needed
- Much faster than serial and USB2
- Ship in modern form factor machines

5. Network Kernel Debugging
Kernel debug target machines directly over the network
Can debug single NIC machines and still use Windows Networking
Debug connection requires encryption and authentication, and this requires a shared secret 256 bit key.
Supports a number of Ethernet NICs from different vendors

6. Network Kernel Debug Setup
Automatic Setup
Use Visual Studio target machine configuration
Manual Setup
Target machine
Bcdedit –dbgsettings net hostip:w.x.y.z port:50000
Bcdedit –debug on
Host machine
Windbg –k net:port=50000, key=paste.your.generated.keyhere

7. Network Kernel Debugging (KDNET)
demo
Network Kernel Debugging (KDNET)

8. USB 3.0 Debugging Supports USB3 XHCI Debug Compatible Hardware
USB3 XHCI controllers with XHCI debug will support debugging on any of their ports
Much faster than USB2 debugging.
Silicon vendors are starting to produce parts
Should be available on most machines in 1-2 years

9. USB 3.0 Debug Setup Automatic Setup Manual Setup
Use Visual Studio target machine configuration
Manual Setup
Target machine
Bcdedit –dbgsettings usb targetname:mytestmachine
Bcdedit –set dbgtransport kdusb3.dll
Bcdedit –debug on
Host machine
Windbg –k usb:targetname=mytestmachine

10. demo
USB 3.0 Debugging

11. Support USB 3.0 and network kernel debugging in your new Windows Systems

12. Hardware Development Cycle
Device
Driver
Component
Certification

13. Device Lifecycle Cost and Debugging
11/8/2018 8:19 PM
Device Lifecycle Cost and Debugging
Device Lifecycle cost
BOM
Hardware bring-up
Device drivers development
Support
Debuggable Windows systems
Maximum value by reusing the “debug” port
Ensure more than one port for debugging
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

14. Kernel debugging on the Nike tablet
demo
Kernel debugging on the Nike tablet

15. Windows Standardization and Certification
11/8/2018 8:19 PM
Windows Standardization and Certification
Standard debug protocols and chipsets
Windows 8 hardware requirements for debugging
Windows Hardware Certification program
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

16. Windows 8 Hardware Debug Requirements
11/8/2018 8:19 PM
Windows 8 Hardware Debug Requirements
Goals
User accessible debug ports
USB3 XHCI debug support for USB3 controllers
Where to look?
System.Fundamentals.DebugPort.SystemExposesDebugInterface
System.Fundamentals.DebugPort.USB.SystemExposesDebugInterfaceUsb
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

17. Windows 8 Hardware Debug Requirements
USB3 XHCI Debug Registers (3+ Gbps)
Gigabit Ethernet Networking (1+ Gbps)
USB2 OTG Device Function (480 Mbps)
1394 Firewire OHCI (400+ Mbps)
USB2 EHCI Host-Host Cable (480 Mbps)
Serial UART (115 Kbps)

18. Use standard debug transports and existing supported chipsets whenever possible. Support USB 3.0 and Network kernel debugging in your new Windows Systems. Provide more than one port for debugging.

19. Windows Hardware Certification Kit
Verify Windows 8 systems support debugging.
User accessible debug ports
Verify USB 3.0 xHCI controllers support debugging.

20. WHCK Debug Capability Tests

21. Partners

22. Further reading and documentation
MSDN Debugging Tools for Windows or Debugging Help.chm
Windows Hardware Certification Kit
Extensible Host Controller Interface (xHCI) Specification for USB 3.0 
Windows Hardware Dev Center
Setting Up a USB 3.0 Connection in Visual Studio
Debugging Using Visual Studio
Windows Dev Center
Contact info:

23. Related sessions [HW-774T] Building great Windows 8 systems
[HW-256T] Understanding USB 3.0 in Windows 8
[HW-773T] Building great USB 3.0 devices
[HW-659T] Certifying hardware with the Windows Hardware Certification Kit
[HW-260T] Windows Certification: improvements to the logo program

24. thank you Feedback and questions http://forums.dev.windows.com
Session feedback

25. 11/8/2018 8:19 PM
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.