Using the active PowerShell connection, execute the following commands on the Raspberry Pi 2 or 3 device to enable debugging over the serial connection.īcdedit /store c:\EFIESP\EFI\Microsoft\Boot\BCD -dbgsettings serial Mkdir C:\EFIESP mountvol C:\EFIESP \?\Volume You'll have to mount it yourself,you can use mountvol command to get the GUID. The EFIESP junction is no longer created.
The following shows the pin mappings for the Raspberry Pi 2 or 3 as well as the serial cables: Raspberry Pi 2 or 3 pins: UART0 will be used on the Raspberry Pi 2 or 3 device for the kernel debugging connection. The Raspberry Pi 2 or 3 device has a valid IP address in your networkĪn active connection to the Raspberry Pi 2 or 3 device via PowerShell or SSH You have a debug cable such as the USB-to-TTL Serial Cable from Adafruit or FTDI.Īn Ethernet cable or active WiFi connecting your Raspberry Pi 2 or 3 device to your network (for IP connections like SSH or PowerShell) In order to enable kernel debugging with WinDbg over a serial connection, ensure that: You can connect WinDbg to the Raspberry Pi 2 or 3 using a serial connection. Reboot the IoTCore device to reconnect to the debugger.If you have any of the Windows kits installed, you may find WinDbg underĬ:\Program Files (x86)\Windows Kits\10\Debuggers\x86\WinDbg.exe "c:\Program Files (x86)\Debugging Tools for Windows (x86)\windbg.exe" -k net:port=,key= On the developer PC, start WinDbg with the PORT_NUM and the KEY values provided in the previous steps as follows: This command turns on debugging on the device.Additionally, it specifies the IP address of the PC where WinDbg will be running (DEV_PC_IP_ADDRESS), the network port number to use for the connection (PORT_NUM), and a unique key to be used to differentiate multiple connections (KEY)įor PORT_NUM and KEY, you can use the following values as examples: 50045 and 1.2.3.4 respectively, although you are free to change them as you see fit This command enables debugging over the network. Using the active PowerShell connection, execute the following commands on the MinnowBoard Max to enable debugging over the network.īcdedit -dbgsettings net hostip: port: key: The MinnowBoard Max device has a valid IP address in your networkĪn active connection to the MinnowBoard Max device via PowerShell
In order to enable kernel debugging with WinDbg over a network, ensure that:Īn Ethernet cable is connected to MinnowBoard Max device to your network You can connect WinDbg to the MinnowBoard Max device using a network connection. However, if you are just getting started and would like to learn more about WinDbg, please visit the following links: WinDbg is a very powerful debugger that most Windows developers are familiar with.
This includes a description of the necessary software settings on the device as well as the physical hardware connections.
The following sections describe how to successfully connect with WinDbg to a Windows 10 IoT Core device for debugging purposes. Debug your Windows 10 IoT Core device using the powerful Windows debugger, WinDbg.