Re: WINDBG
From: Tim Roberts (timr_at_probo.com)
Date: 03/24/05
- Next message: Arkady Frenkel: "Re: driver needs Administrator rights to load?"
- Previous message: Tim Roberts: "Re: WINDBG"
- In reply to: Stuart: "Re: WINDBG"
- Next in thread: Maxim S. Shatskih: "Re: WINDBG"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Mar 2005 21:59:24 -0800
Stuart <Stuart@discussions.microsoft.com> wrote:
>
>Hi Maxim.. actually I specified 57600 in both the boot.ini cmd line and
>windbg itself on the other machine which is the host. But since I can still
>open the port via hyperterm, doesn't this mean the kernel on the host is not
>using it ? My target just keeps stating waiting for connect...
You mean the host keeps waiting, right? The target, presumably, has
continued on to boot normally.
Do you see the target pause during boot just after the boot.ini choice
screen? If your "null modem" cable is screwed up, the target will try to
connect, see nothing, time out, and assume that you didn't really want the
debugger. You're sure you have the right connector for the COM port you've
chosen?
Where did you get the cable? Did you follow the "rules" for crossing the
wires and shorting the proper pins? Have you tried a different null modem
cable?
If both machines have 1394 ports, you would be much better off to use 1394
debugging. You lose all of the serial cable problems.
-- - Tim Roberts, timr@probo.com Providenza & Boekelheide, Inc
- Next message: Arkady Frenkel: "Re: driver needs Administrator rights to load?"
- Previous message: Tim Roberts: "Re: WINDBG"
- In reply to: Stuart: "Re: WINDBG"
- Next in thread: Maxim S. Shatskih: "Re: WINDBG"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
