Re: How to debug by COM port
- From: "Andy Allred [MS]" <andyall@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 26 Oct 2005 09:59:25 -0700
Try reducing the baud rate to something like 57600 or 19200 in the boot.ini
and ensure the machine with winddbg is capable of the same rate.
-andy
--
Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.
"C.C. Wu" <cc_wu@xxxxxxxxxxxx> wrote in message
news:uIGjBlg2FHA.3912@xxxxxxxxxxxxxxxxxxxxxxx
> Hi all,
> I'd like to get embedded XP debug infomation of kernel boot procedure. I
> have installed Windows Debugger Version 6.5.0003.7 in a host computer,
> and
> I boot my system from a target computer.
> The target computer's boot.ini is
> [boot loader]
> timeout=0
> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Embedded" /debug
> /debugport=com1 /baudrate=115200
> .
>
> I launched WinDbg on my host computer, and executed Kernel Debug, but I
> can
> not make host connect with target.
>
> Microsoft (R) Windows Debugger Version 6.5.0003.7
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Opened \\.\COM1
> Waiting to reconnect...
>
>
> I have tested communcation between them. The host always sends 0x69 0x69
> 0x69 0x69 0x06 0x00 0x00 0x00...., so the COM port works normally.
>
> Does anybody know what's going on with my embedded XP? Do I need some
> components for kernel debug?
>
> Thanks.
> C.C. Wu
>
>
>
>
>
>
>
.
- Follow-Ups:
- Re: How to debug by COM port
- From: C.C. Wu
- Re: How to debug by COM port
- References:
- How to debug by COM port
- From: C.C. Wu
- How to debug by COM port
- Prev by Date: Re: CMI Explorer
- Next by Date: Registry EWF RAM Problems
- Previous by thread: How to debug by COM port
- Next by thread: Re: How to debug by COM port
- Index(es):
Relevant Pages
|
|