Re-reading your description of the symptoms, it does sound like the presence of the add-in card is interfering with the kernel debugger. (If the debugger selects the wrong one, then you won't have access to your hardware.) Since you have 2 NICs, you do need to use theīusparams keyword to force the debugger to select the right one. Unfortunately that hardware is old and doesn't support PCIe which is the hardware I have tried to enable this driver and theĪre two physical adapters necessary to debug/develop device drivers? My last project had a different target machine with two physical adapters and I had greater luck debugging. There is another entry for a Microsoft Kernel Debug Network Adapter that is disabled. I did notice in the Network Connections in the Control Panel of the target that the Ethernet adapter is enabled and working. The firewall settings for the target machine are all off. I used the bcdedit utility to ensure that debug is on and the dbgsettings are set to point to my host machine and all looks good as far as I can tell. I have tried with both Visual Studio and WinDbg on my host to get control I have not been able to break into the target machine to get control. I have been able to configure the computers, update and install the device driver on my target machine successfully. The target machine has one built-in network adapter that is listed as compatible for network development and My target machine is running Windows 8.1. I am starting a new KMDF device driver and am using Visual Studio 2013 on my Win 7 host machine.
0 Comments
Leave a Reply. |