Can't get W2K Debugger connected

NTDEV
1

OK guys, I need some pointers here, even they are just RTFM. I’m working on
my first W2K driver and am running into problems getting the kernel debugger
to connect to the target machine. The steps I’ve done are as follows:

  1. Connected a NULL-Modem cable between the host (on COM2) and target (on
    COM1) machines and verified the connection using hyperterminal on both. I
    also have a simple line analyzer that has LEDs for each signal.

  2. I started the WinDbg on my host machine (W2K Free Build, SP2). The
    debugger version is 5.00.2195.11. I believe there is probably a newer
    version out there.

  3. Set the WinDbg option to do kernel debugging and set the communications
    to COM2, 19200 Baud.

  4. Added the /DEBUG /DEBUGPORT=COM1 /BAUDRATE=19200 /SOS to the boot.ini
    file on the target machine and rebooted using this configuration.

  5. Verified the target machine is trying to communicate with the host via
    the LEDs on the analyzer.

  6. Nothing!

I can stop the debugger on the host and start a terminal emulator and see
something coming from the target machine. It appears that the debugger
isn’t even trying to open the COM port on the host machine! Does anyone
have any ideas where to go from here? I’ve tried everything I can think of
short of removing all of the unnecessary transport layers from the debugger.
If anyone has any ideas, even if it’s just RTFM and a pointer to where, I
would greatly appreciate it.

Thanks,
Greg

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

STOP and goto the microsoft website
http://www.microsoft.com/ddk/debugging/default.asp and download the
FUNCTIONAL version of windbg.

-----Original Message-----
From: Gregory G. Dyess [mailto:xxxxx@pdq.net]
Sent: Friday, October 26, 2001 9:53 AM
To: NT Developers Interest List
Subject: [ntdev] Can’t get W2K Debugger connected

OK guys, I need some pointers here, even they are just RTFM. I’m working on
my first W2K driver and am running into problems getting the kernel debugger
to connect to the target machine. The steps I’ve done are as follows:

  1. Connected a NULL-Modem cable between the host (on COM2) and target (on
    COM1) machines and verified the connection using hyperterminal on both. I
    also have a simple line analyzer that has LEDs for each signal.

  2. I started the WinDbg on my host machine (W2K Free Build, SP2). The
    debugger version is 5.00.2195.11. I believe there is probably a newer
    version out there.

  3. Set the WinDbg option to do kernel debugging and set the communications
    to COM2, 19200 Baud.

  4. Added the /DEBUG /DEBUGPORT=COM1 /BAUDRATE=19200 /SOS to the boot.ini
    file on the target machine and rebooted using this configuration.

  5. Verified the target machine is trying to communicate with the host via
    the LEDs on the analyzer.

  6. Nothing!

I can stop the debugger on the host and start a terminal emulator and see
something coming from the target machine. It appears that the debugger
isn’t even trying to open the COM port on the host machine! Does anyone
have any ideas where to go from here? I’ve tried everything I can think of
short of removing all of the unnecessary transport layers from the debugger.
If anyone has any ideas, even if it’s just RTFM and a pointer to where, I
would greatly appreciate it.

Thanks,
Greg

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

Thanks, I’m doing that now. I’ll let you know what happens. I knew this
list would come through!

Greg

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roddy, Mark
Sent: Friday, October 26, 2001 8:50 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Can’t get W2K Debugger connected

STOP and goto the microsoft website
http://www.microsoft.com/ddk/debugging/default.asp and download the
FUNCTIONAL version of windbg.

-----Original Message-----
From: Gregory G. Dyess [mailto:xxxxx@pdq.net]
Sent: Friday, October 26, 2001 9:53 AM
To: NT Developers Interest List
Subject: [ntdev] Can’t get W2K Debugger connected

OK guys, I need some pointers here, even they are just RTFM. I’m working on
my first W2K driver and am running into problems getting the kernel debugger
to connect to the target machine. The steps I’ve done are as follows:

  1. Connected a NULL-Modem cable between the host (on COM2) and target (on
    COM1) machines and verified the connection using hyperterminal on both. I
    also have a simple line analyzer that has LEDs for each signal.

  2. I started the WinDbg on my host machine (W2K Free Build, SP2). The
    debugger version is 5.00.2195.11. I believe there is probably a newer
    version out there.

  3. Set the WinDbg option to do kernel debugging and set the communications
    to COM2, 19200 Baud.

  4. Added the /DEBUG /DEBUGPORT=COM1 /BAUDRATE=19200 /SOS to the boot.ini
    file on the target machine and rebooted using this configuration.

  5. Verified the target machine is trying to communicate with the host via
    the LEDs on the analyzer.

  6. Nothing!

I can stop the debugger on the host and start a terminal emulator and see
something coming from the target machine. It appears that the debugger
isn’t even trying to open the COM port on the host machine! Does anyone
have any ideas where to go from here? I’ve tried everything I can think of
short of removing all of the unnecessary transport layers from the debugger.
If anyone has any ideas, even if it’s just RTFM and a pointer to where, I
would greatly appreciate it.

Thanks,
Greg

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@pdq.net
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

4

WooHoo! That seems to have fixed it. I knew it was going to be something
simple.

Thank you very much,
Greg

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roddy, Mark
Sent: Friday, October 26, 2001 8:50 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Can’t get W2K Debugger connected

STOP and goto the microsoft website
http://www.microsoft.com/ddk/debugging/default.asp and download the
FUNCTIONAL version of windbg.

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com