Hi All,
My test PC doesn’t have on-board COM port and i have add-on PCI COM port and PCI 1394 port device.
I installed driver for PCI COM Port device and tested with hyperterminal,its work fine.
Later changed boot.ini for COM3 and othermachine running WinDbg.
It is not establishing connection with WinDBG.Any idea why it is happening?.
Thanks in advance,
Santosh
Windbg requires a legacy com port, it will not work with this configuration.
You will need to use 1394 on both machines, and be sure your 1394 controller
is OHCI compliant.
–
Don Burn (MVP, Windows DDK)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply
wrote in message news:xxxxx@windbg…
> Hi All,
>
> My test PC doesn’t have on-board COM port and i have add-on PCI COM port
> and PCI 1394 port device.
> I installed driver for PCI COM Port device and tested with
> hyperterminal,its work fine.
> Later changed boot.ini for COM3 and othermachine running WinDbg.
> It is not establishing connection with WinDBG.Any idea why it is
> happening?.
>
> Thanks in advance,
> Santosh
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4093 (20090521)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4093 (20090521)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
I think target’s side kernel debugger code requires a legacy COM port.
WinDbg’s side can be a PCI COM port.
Regards
Deepak
On Thu, May 21, 2009 at 7:30 PM, Don Burn wrote:
> Windbg requires a legacy com port, it will not work with this
> configuration.
> You will need to use 1394 on both machines, and be sure your 1394
> controller
> is OHCI compliant.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
> Remove StopSpam to reply
>
>
>
>
>
> wrote in message news:xxxxx@windbg…
> > Hi All,
> >
> > My test PC doesn’t have on-board COM port and i have add-on PCI COM port
> > and PCI 1394 port device.
> > I installed driver for PCI COM Port device and tested with
> > hyperterminal,its work fine.
> > Later changed boot.ini for COM3 and othermachine running WinDbg.
> > It is not establishing connection with WinDBG.Any idea why it is
> > happening?.
> >
> > Thanks in advance,
> > Santosh
> >
> >
> > Information from ESET NOD32 Antivirus, version of virus
> > signature database 4093 (20090521)
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4093 (20090521)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
True, but the OP indicated his test machine have the PCI card!
–
Don Burn (MVP, Windows DDK)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply
“Deepak Gupta” wrote in message news:xxxxx@windbg…
>I think target’s side kernel debugger code requires a legacy COM port.
> WinDbg’s side can be a PCI COM port.
>
> Regards
> Deepak
>
> On Thu, May 21, 2009 at 7:30 PM, Don Burn wrote:
>
>> Windbg requires a legacy com port, it will not work with this
>> configuration.
>> You will need to use 1394 on both machines, and be sure your 1394
>> controller
>> is OHCI compliant.
>>
>>
>> –
>> Don Burn (MVP, Windows DDK)
>> Windows Filesystem and Driver Consulting
>> Website: http://www.windrvr.com
>> Blog: http://msmvps.com/blogs/WinDrvr
>> Remove StopSpam to reply
>>
>>
>>
>>
>>
>> wrote in message news:xxxxx@windbg…
>> > Hi All,
>> >
>> > My test PC doesn’t have on-board COM port and i have add-on PCI COM
>> > port
>> > and PCI 1394 port device.
>> > I installed driver for PCI COM Port device and tested with
>> > hyperterminal,its work fine.
>> > Later changed boot.ini for COM3 and othermachine running WinDbg.
>> > It is not establishing connection with WinDBG.Any idea why it is
>> > happening?.
>> >
>> > Thanks in advance,
>> > Santosh
>> >
>> >
>> > Information from ESET NOD32 Antivirus, version of virus
>> > signature database 4093 (20090521)
>> >
>> > The message was checked by ESET NOD32 Antivirus.
>> >
>> > http://www.eset.com
>> >
>> >
>> >
>>
>>
>>
>> Information from ESET NOD32 Antivirus, version of virus
>> signature database 4093 (20090521)
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>>
>> —
>> WINDBG is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4094 (20090521)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4094 (20090521)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Don and Deepak,
Thanks for reply.At the moment i have only one 1394…i will try it later with two 1394 card and let you the result.
I am curious to know that windbg can work with PCI 1394 card but not with a PCI COM port.what is the reason behind this?.
with thanks,
Santosh
Don and Deepak,
I tried with two 1394 card as mentioned DON. Now i can get the debug prints in windbg.
Thanks again,
Santosh
It’s actually the kd stub in the target (debuggee) that has the limitation. It’s this way because the kd support logic can’t depend on installable drivers and therefore needs to know the specifics of how to talk to hardware.
1394 controllers, USB controllers, and old-style UART serial ports all expose standardized hardware-level interfaces at their lowest edge and don’t need device specific hardware in general for what the kd support needs to do with them - it just needs to know how to talk to the standard host controller interfaces for each respective medium and can then support a wide range of devices compatible with those interfaces.
The debugger end, conversely, works through the usual OS mechanisms and thus can use devices that need specialized drivers, like USB serial adapters and the like.
-----Original Message-----
From: xxxxx@rediffmail.com
Sent: Thursday, May 21, 2009 21:53
To: Kernel Debugging Interest List
Subject: RE:[windbg] Connecting WinDbg using PCI ComPort/PCI 1394.
Don and Deepak,
Thanks for reply.At the moment i have only one 1394…i will try it later with two 1394 card and let you the result.
I am curious to know that windbg can work with PCI 1394 card but not with a PCI COM port.what is the reason behind this?.
with thanks,
Santosh
—
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Ken,
Thanks a lot…
Santosh