Dear OSR-Community,
due to the fact that it’s incredible difficult to find a german driver developer I’ve decided to ask here for help. I really hope you can excuse me for my bad english skills.
I own two notebooks equipped with the Windows 10 operating system. Both contain the VS 2015 Enterprise IDE as well as the latest WDK.
As soon as I try to configure the target-system by clicking on Driver -> Tests -> Configure Devices… (described somewhere in this guide: https://msdn.microsoft.com/en-us/library/windows/hardware/hh439665(v=vs.85).aspx) VS says: "impermissible request for export of a part that belongs to another (not released?) boundary/part. That way it’s impossible for me to debug the “Hello World” KMDF-Driver.
My target notebook is connected to a TP-Link plug with a CAT5-Standard cable. The host notebook uses wirelles W-LAN. Even though thats probably not important for now, I’m wondering if it’s possible to do so for debugging.
It would be awesome if somebody could help me to solve this problem. I appreciate any hints!
Personally, I’ve never been able to get the VS driver target deployment stuff to work. I just manually set the remote target to use a network debugging transport and run windbg on the debugger machine. I also set windbg to automatically update the driver binaries with the .kdfiles command, so once a driver is installed, all I have to do is disable/enable the device (a script that calls deacon makes this one click) or reboot the target to update the driver binaries. This get’s the edit-compile-debug cycle down to as little as a minute or two (assuming a trivial source change).
Jan
On 2/13/16, 10:51 AM, “xxxxx@lists.osr.com on behalf of xxxxx@web.de” wrote:
>Driver -> Tests -> Configure Devices
Hello Jan, first of all I would like to thank you for the answer!
Could you perhaps tell me in which way you connect your machines when using WinDBG? The problem is, that neither of my notebooks are equipped with a wirefire plug. Is there actually any way to make WinDBG work by using a crossover cable?
Thank’s ahead!
Nikey
Windbg works fine with the network transport, assuming your target machine is at least Win 8, and has a compatible network device (there is a list of compatible wired Ethernet devices).
The debugger machine should be ok with ANY network device, I currently use a Win 7 debugger laptop with a USB to wired Ethernet dongle to my Server 2012 R2 target wired Ethernet port. I go through a little Ethernet router, which does DHCP for me, although static IP assignment I’m almost positive works too. For direct wired Ethernet port to wired Ethernet port you might need a crossover cable, although some Ethernet devices I believe just cope automatically.
A quick checklist might be:
- Assure target machine has compatible wired Ethernet device
- Assure target is Win 8 or later
- Assure if you disable kernel debugging on target you can ping between target and debugger machine
40 Assure that when you enable network kernel debugging on the target, the network kernel debugger NIC device shows up in the device manager. If your target has multiple debug compatible NICs, yo might need to manually set the bcdedit parameters to select the correct one.
The network transport can share the physical devices, so if the debug Ethernet is the only connectivity you can run remote desktop and kernel debug over the same physical NIC. Performance is degraded over normal use of the NIC, so don’t put lots of traffic (like WHQL tests) over a shared debug NIC.
Jan
On 2/13/16, 2:12 PM, “xxxxx@lists.osr.com on behalf of xxxxx@web.de” wrote:
>Hello Jan, first of all I would like to thank you for the answer!
>Could you perhaps tell me in which way you connect your machines when using WinDBG? The problem is, that neither of my notebooks are equipped with a wirefire plug. Is there actually any way to make WinDBG work by using a crossover cable?
>
>Thank’s ahead!
>
>Nikey
>
>—
>NTDEV is sponsored by OSR
>
>Visit the list online at: http:
>
>MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
>Details at http:
>
>To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></http:>
I’ve always run into problems trying to debug over Ethernet. I constantly
get the lost connection message or it will just hang with “waiting to
reconnect.” Either way, I find it much easier to debug on a VM using
VirtualKD (http://virtualkd.sysprogs.org/). It hooks into VMWare
Workstation so it will automatically pop open a Windbg instance configured
to do what you need once the VM loads. If you are not tied to the dual
machine setup, I’d take a look at that.
On Sat, Feb 13, 2016 at 5:49 PM, Jan Bottorff
wrote:
> Windbg works fine with the network transport, assuming your target machine
> is at least Win 8, and has a compatible network device (there is a list of
> compatible wired Ethernet devices).
>
> The debugger machine should be ok with ANY network device, I currently use
> a Win 7 debugger laptop with a USB to wired Ethernet dongle to my Server
> 2012 R2 target wired Ethernet port. I go through a little Ethernet router,
> which does DHCP for me, although static IP assignment I’m almost positive
> works too. For direct wired Ethernet port to wired Ethernet port you might
> need a crossover cable, although some Ethernet devices I believe just cope
> automatically.
>
> A quick checklist might be:
>
> 1) Assure target machine has compatible wired Ethernet device
> 2) Assure target is Win 8 or later
> 3) Assure if you disable kernel debugging on target you can ping between
> target and debugger machine
> 40 Assure that when you enable network kernel debugging on the target, the
> network kernel debugger NIC device shows up in the device manager. If your
> target has multiple debug compatible NICs, yo might need to manually set
> the bcdedit parameters to select the correct one.
>
> The network transport can share the physical devices, so if the debug
> Ethernet is the only connectivity you can run remote desktop and kernel
> debug over the same physical NIC. Performance is degraded over normal use
> of the NIC, so don’t put lots of traffic (like WHQL tests) over a shared
> debug NIC.
>
> Jan
>
>
>
>
> On 2/13/16, 2:12 PM, “xxxxx@lists.osr.com on behalf of
> xxxxx@web.de” > xxxxx@web.de> wrote:
>
> >Hello Jan, first of all I would like to thank you for the answer!
> >Could you perhaps tell me in which way you connect your machines when
> using WinDBG? The problem is, that neither of my notebooks are equipped
> with a wirefire plug. Is there actually any way to make WinDBG work by
> using a crossover cable?
> >
> >Thank’s ahead!
> >
> >Nikey
> >
> >—
> >NTDEV is sponsored by OSR
> >
> >Visit the list online at: <
> http://www.osronline.com/showlists.cfm?list=ntdev>
> >
> >MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> >Details at http:
> >
> >To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: <
> http://www.osronline.com/showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:></http:>
From a long practice, I learned to never use cross cables for debugging. Always put a powered hub or switch in between. Saved me a ton of nerve cells.
Regards,
– pa
Paul wrote:
I’ve always run into problems trying to debug over Ethernet. I
constantly get the lost connection message or it will just hang with
“waiting to reconnect.”
That’s interesting. Although 1394 is my preferred method, I’ve never
had trouble with Windbg over Ethernet. It just plugged and played.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.