hi, all
I want to debug driver with windbg.
The windbg version is 6.12.2.633
The com cable is ok, for I use a serial port exe, each could send a string to each other and correct.
i have edit the tartet xp machine boot.ini file as following:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional Debug" /fastdetect /debug /debugport=com1 /baudrate=115200
When the COM cable does not connected, I could start the target xp machine with debugger mode, but i found that "COM1" in device manager is disappeared.
But when host and target connect with COM cable, the target could not start with debugger mode, but could start into non-debugger mode, in non-debugger mode, COM1 exists in device manager.
And when I open the windbg, and select the "file->kernel debug", then start the target with debugger mode, the targe could not start,
press down "ctl+alt+d", and in the windbg windows, display the following content/informations:
=================================================================================
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \.\com1
Waiting to reconnect...
Throttle 0x10 write to 0x1
SYNCTARGET: Timeout.
Throttle 0x10 write to 0x1
SYNCTARGET: Timeout.
Throttle 0x10 write to 0x1
This issue take me for two days.
And i searching on the web, it seems others are face to this issue before.
You should explicitly set the comport with /DEBUGPORT and the baudrate
with /BAUDRATE in the boot.ini. Also, you should check if your
connection works by bringing up hyperterm on both machines and seeing if
they communicate. Take a look at
http://msdn.microsoft.com/en-us/windows/hardware/gg463002 for more
details on checking the debugging environment.
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“workingmailing” wrote in message
news:xxxxx@ntdev:
> hi, all
>
> I want to debug driver with windbg.
> The windbg version is 6.12.2.633
> The com cable is ok, for I use a serial port exe, each could send a string to each other and correct.
>
> i have edit the tartet xp machine boot.ini file as following:
> ====================================================================================================================
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Microsoft Windows XP Professional” /noexecute=optin /fastdetect
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Microsoft Windows XP Professional Debug” /fastdetect /debug /debugport=com1 /baudrate=115200
> ====================================================================================================================
>
> When the COM cable does not connected, I could start the target xp machine with debugger mode, but i found that “COM1” in device manager is disappeared.
>
> But when host and target connect with COM cable, the target could not start with debugger mode, but could start into non-debugger mode, in non-debugger mode, COM1 exists in device manager.
>
> And when I open the windbg, and select the “file->kernel debug”, then start the target with debugger mode, the targe could not start,
> press down “ctl+alt+d”, and in the windbg windows, display the following content/informations:
>
> =================================================================================
> Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Opened \.\com1
> Waiting to reconnect…
> Throttle 0x10 write to 0x1
> SYNCTARGET: Timeout.
> Throttle 0x10 write to 0x1
> SYNCTARGET: Timeout.
> Throttle 0x10 write to 0x1
> ====================================================================================
>
> This issue take me for two days.
> And i searching on the web, it seems others are face to this issue before.
Get another cable that worked for sure with windbg. Correct cable pinout and
grounding are very important.
Hyperterm is more forgiving.
–pa
“workingmailing” wrote in message
news:xxxxx@ntdev…
> hi, all
>
> I want to debug driver with windbg.
> The windbg version is 6.12.2.633
> The com cable is ok, for I use a serial port exe, each could send a string
> to each other and correct.
>
> i have edit the tartet xp machine boot.ini file as following:
> ====================================================================================================================
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Microsoft Windows XP
> Professional” /noexecute=optin /fastdetect
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Microsoft Windows XP
> Professional Debug” /fastdetect /debug /debugport=com1 /baudrate=115200
> ====================================================================================================================
>
> When the COM cable does not connected, I could start the target xp machine
> with debugger mode, but i found that “COM1” in device manager is
> disappeared.
>
> But when host and target connect with COM cable, the target could not
> start with debugger mode, but could start into non-debugger mode, in
> non-debugger mode, COM1 exists in device manager.
>
> And when I open the windbg, and select the “file->kernel debug”, then
> start the target with debugger mode, the targe could not start,
> press down “ctl+alt+d”, and in the windbg windows, display the following
> content/informations:
>
> =================================================================================
> Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Opened \.\com1
> Waiting to reconnect…
> Throttle 0x10 write to 0x1
> SYNCTARGET: Timeout.
> Throttle 0x10 write to 0x1
> SYNCTARGET: Timeout.
> Throttle 0x10 write to 0x1
> ====================================================================================
>
> This issue take me for two days.
> And i searching on the web, it seems others are face to this issue before.
>
On 6/11/2011 3:04 PM, workingmailing wrote:
I want to debug driver with windbg.
The com cable is ok, for I use a serial port exe, each could send a
string to each other and correct.
If a serial connection works OK with a terminal program, this does not
guarantee that WinDbg can also use it.
E.g., USB->Serial converters will not work for debugging with WinDbg.
Issue fixed.
The serial cable I used is with 9 separate lines in it.
When I cut the other 6 lines, only keep the 2,3,5, it works well.
TX to RX(2-3,3-2)
GND to GND(5-5)
For USB to RS232, it work well when this USB device work on host.
But no good for targe device, for this device need driver, while target machine boot, this device without driver, so.