cannot get windbg working over OSR's 1394 cards

Hi,
We have purchased two PCI based 1394 cards from OSR Online store
and put one in a target (ASUS P6 motherboard) and
the other in a PC.

The boot.ini file on the target has the string /debug /debugport=1394
/channel=40.

Windbg is started and kernel debug is selected from File menu. The
channel number is entered as 40.

In this setup the host can not connect to target over channel 40.

The control-Alt-D on windbg terminal prints

Synchronize…

… Synchronize: 80070002

Any help to solve the problem is appreciated.

Kallol Biswas
NucleoDyne Systems, Inc.

Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
menu?

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
Sent: Thursday, September 09, 2010 4:12 PM
To: Kernel Debugging Interest List
Subject: [windbg] cannot get windbg working over OSR’s 1394 cards

Hi,
We have purchased two PCI based 1394 cards from OSR Online store and put
one in a target (ASUS P6 motherboard) and the other in a PC.

The boot.ini file on the target has the string /debug /debugport=1394
/channel=40.

Windbg is started and kernel debug is selected from File menu. The channel
number is entered as 40.

In this setup the host can not connect to target over channel 40.

The control-Alt-D on windbg terminal prints

Synchronize…

… Synchronize: 80070002

Any help to solve the problem is appreciated.

Kallol Biswas
NucleoDyne Systems, Inc.


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

Yes, I have.
Here is the output I get:

Wrote 0 of 1 bytes of the breakin packet.
Failed to write breakin packet to target. Win32 error 0n2
WARNING: The HOST cannot communicate with the TARGET!

The motherboard has a 1394 port as well. I could use the port on
motherboard to talk to a different system. I have not changed the
channel number since other system is not connected now.

On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
wrote:
> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
> menu?
>
>
> mm
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
> Sent: Thursday, September 09, 2010 4:12 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> Hi,
> ? We have purchased two PCI based 1394 cards from OSR Online store and put
> one in a target (ASUS P6 motherboard) and the other in a PC.
>
> The boot.ini file on the target has the string /debug /debugport=1394
> /channel=40.
>
> Windbg is started and kernel debug is selected from File menu. The channel
> number is entered as 40.
>
> In this setup the host can not connect to target over channel 40.
>
> The control-Alt-D on windbg terminal prints
>
> Synchronize…
>
> … Synchronize: 80070002
>
> Any help to solve the problem is appreciated.
>
> Kallol Biswas
> NucleoDyne Systems, Inc.
>
> —
> 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
>
>
> —
> 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
>

Did you disable the 1394 controller on the TARGET?

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
Sent: Thursday, September 09, 2010 4:24 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards

Yes, I have.
Here is the output I get:

Wrote 0 of 1 bytes of the breakin packet.
Failed to write breakin packet to target. Win32 error 0n2
WARNING: The HOST cannot communicate with the TARGET!

The motherboard has a 1394 port as well. I could use the port on motherboard
to talk to a different system. I have not changed the channel number since
other system is not connected now.

On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
wrote:
> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
> menu?
>
>
> mm
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
> Sent: Thursday, September 09, 2010 4:12 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> Hi,
> ? We have purchased two PCI based 1394 cards from OSR Online store and
> put one in a target (ASUS P6 motherboard) and the other in a PC.
>
> The boot.ini file on the target has the string /debug /debugport=1394
> /channel=40.
>
> Windbg is started and kernel debug is selected from File menu. The
> channel number is entered as 40.
>
> In this setup the host can not connect to target over channel 40.
>
> The control-Alt-D on windbg terminal prints
>
> Synchronize…
>
> … Synchronize: 80070002
>
> Any help to solve the problem is appreciated.
>
> Kallol Biswas
> NucleoDyne Systems, Inc.
>
> —
> 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
>
>
> —
> 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
>


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

No, the host controller on target is not disabled. Let me try
disabling the controller.

Both host and target run XP SP2.

On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
wrote:
> Did you disable the 1394 controller on the TARGET?
>
>
> mm
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
> Sent: Thursday, September 09, 2010 4:24 PM
> To: Kernel Debugging Interest List
> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> Yes, I have.
> Here is the output I get:
>
> Wrote 0 of 1 bytes of the breakin packet.
> Failed to write breakin packet to target. ?Win32 error 0n2
> WARNING: The HOST cannot communicate with the TARGET!
>
> The motherboard has a 1394 port as well. I could use the port on motherboard
> to talk to a different system. I have not changed the channel number since
> other system is not connected now.
>
> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
> wrote:
>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>> menu?
>>
>>
>> mm
>>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
>> Sent: Thursday, September 09, 2010 4:12 PM
>> To: Kernel Debugging Interest List
>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>
>> Hi,
>> ? We have purchased two PCI based 1394 cards from OSR Online store and
>> put one in a target (ASUS P6 motherboard) and the other in a PC.
>>
>> The boot.ini file on the target has the string /debug /debugport=1394
>> /channel=40.
>>
>> Windbg is started and kernel debug is selected from File menu. The
>> channel number is entered as 40.
>>
>> In this setup the host can not connect to target over channel 40.
>>
>> The control-Alt-D on windbg terminal prints
>>
>> Synchronize…
>>
>> … Synchronize: 80070002
>>
>> Any help to solve the problem is appreciated.
>>
>> Kallol Biswas
>> NucleoDyne Systems, Inc.
>>
>> —
>> 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
>>
>>
>> —
>> 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
>>
>
> —
> 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
>
>
> —
> 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
>

You need to on XP, as I recall.

On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
> No, the host controller on target is not disabled. Let me try
> disabling the controller.
>
> Both host and target run XP SP2.
>
> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
> wrote:
>> Did you disable the 1394 controller on the TARGET?
>>
>>
>> mm
>>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
>> Sent: Thursday, September 09, 2010 4:24 PM
>> To: Kernel Debugging Interest List
>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards
>>
>> Yes, I have.
>> Here is the output I get:
>>
>> Wrote 0 of 1 bytes of the breakin packet.
>> Failed to write breakin packet to target. Win32 error 0n2
>> WARNING: The HOST cannot communicate with the TARGET!
>>
>> The motherboard has a 1394 port as well. I could use the port on
motherboard
>> to talk to a different system. I have not changed the channel number
since
>> other system is not connected now.
>>
>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>> wrote:
>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>>> menu?
>>>
>>>
>>> mm
>>>
>>> -----Original Message-----
>>> From: xxxxx@lists.osr.com
>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
>>> Sent: Thursday, September 09, 2010 4:12 PM
>>> To: Kernel Debugging Interest List
>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>
>>> Hi,
>>> We have purchased two PCI based 1394 cards from OSR Online store and
>>> put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>
>>> The boot.ini file on the target has the string /debug /debugport=1394
>>> /channel=40.
>>>
>>> Windbg is started and kernel debug is selected from File menu. The
>>> channel number is entered as 40.
>>>
>>> In this setup the host can not connect to target over channel 40.
>>>
>>> The control-Alt-D on windbg terminal prints
>>>
>>> Synchronize…
>>>
>>> … Synchronize: 80070002
>>>
>>> Any help to solve the problem is appreciated.
>>>
>>> Kallol Biswas
>>> NucleoDyne Systems, Inc.
>>>
>>> —
>>> 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
>>>
>>>
>>> —
>>> 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
>>>
>>
>> —
>> 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
>>
>>
>> —
>> 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
>>
>
> —
> 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

Does not help i.e. even after I disable the host controller on target,
and reboot the target windbg can not connect.

On Thu, Sep 9, 2010 at 2:48 PM, MARTIN OBRIEN
wrote:
> You need to on XP, as I recall.
>
> On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
>> No, the host controller on target is not disabled. Let me try
>> disabling the controller.
>>
>> Both host and target run XP SP2.
>>
>> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
>> wrote:
>>> Did you disable the 1394 controller on the TARGET?
>>>
>>>
>>> mm
>>>
>>> -----Original Message-----
>>> From: xxxxx@lists.osr.com
>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
>>> Sent: Thursday, September 09, 2010 4:24 PM
>>> To: Kernel Debugging Interest List
>>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>
>>> Yes, I have.
>>> Here is the output I get:
>>>
>>> Wrote 0 of 1 bytes of the breakin packet.
>>> Failed to write breakin packet to target. ?Win32 error 0n2
>>> WARNING: The HOST cannot communicate with the TARGET!
>>>
>>> The motherboard has a 1394 port as well. I could use the port on
>>> motherboard
>>> to talk to a different system. I have not changed the channel number
>>> since
>>> other system is not connected now.
>>>
>>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>>> wrote:
>>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>>>> menu?
>>>>
>>>>
>>>> mm
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
>>>> Sent: Thursday, September 09, 2010 4:12 PM
>>>> To: Kernel Debugging Interest List
>>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>>
>>>> Hi,
>>>> ? We have purchased two PCI based 1394 cards from OSR Online store and
>>>> put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>>
>>>> The boot.ini file on the target has the string /debug /debugport=1394
>>>> /channel=40.
>>>>
>>>> Windbg is started and kernel debug is selected from File menu. The
>>>> channel number is entered as 40.
>>>>
>>>> In this setup the host can not connect to target over channel 40.
>>>>
>>>> The control-Alt-D on windbg terminal prints
>>>>
>>>> Synchronize…
>>>>
>>>> … Synchronize: 80070002
>>>>
>>>> Any help to solve the problem is appreciated.
>>>>
>>>> Kallol Biswas
>>>> NucleoDyne Systems, Inc.
>>>>
>>>> —
>>>> 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
>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>
>>> —
>>> 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
>>>
>>>
>>> —
>>> 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
>>>
>>
>> —
>> 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
>
> — 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

Hmm.

Was the CTRL+ALT+D output just that same message (synchronize…) over and
over? If not, please post it.

Also, have you installed windbg on the host more than once (as in EVER)?

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
Sent: Thursday, September 09, 2010 6:06 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards

Does not help i.e. even after I disable the host controller on target, and
reboot the target windbg can not connect.

On Thu, Sep 9, 2010 at 2:48 PM, MARTIN OBRIEN
wrote:
> You need to on XP, as I recall.
>
> On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
>> No, the host controller on target is not disabled. Let me try
>> disabling the controller.
>>
>> Both host and target run XP SP2.
>>
>> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
>> wrote:
>>> Did you disable the 1394 controller on the TARGET?
>>>
>>>
>>> mm
>>>
>>> -----Original Message-----
>>> From: xxxxx@lists.osr.com
>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>> Biswas
>>> Sent: Thursday, September 09, 2010 4:24 PM
>>> To: Kernel Debugging Interest List
>>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394
>>> cards
>>>
>>> Yes, I have.
>>> Here is the output I get:
>>>
>>> Wrote 0 of 1 bytes of the breakin packet.
>>> Failed to write breakin packet to target. ?Win32 error 0n2
>>> WARNING: The HOST cannot communicate with the TARGET!
>>>
>>> The motherboard has a 1394 port as well. I could use the port on
>>> motherboard to talk to a different system. I have not changed the
>>> channel number since other system is not connected now.
>>>
>>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>>> wrote:
>>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>>>> menu?
>>>>
>>>>
>>>> mm
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>> Biswas
>>>> Sent: Thursday, September 09, 2010 4:12 PM
>>>> To: Kernel Debugging Interest List
>>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>>
>>>> Hi,
>>>> ? We have purchased two PCI based 1394 cards from OSR Online store
>>>> and put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>>
>>>> The boot.ini file on the target has the string /debug
>>>> /debugport=1394 /channel=40.
>>>>
>>>> Windbg is started and kernel debug is selected from File menu. The
>>>> channel number is entered as 40.
>>>>
>>>> In this setup the host can not connect to target over channel 40.
>>>>
>>>> The control-Alt-D on windbg terminal prints
>>>>
>>>> Synchronize…
>>>>
>>>> … Synchronize: 80070002
>>>>
>>>> Any help to solve the problem is appreciated.
>>>>
>>>> Kallol Biswas
>>>> NucleoDyne Systems, Inc.
>>>>
>>>> —
>>>> 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
>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>
>>> —
>>> 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
>>>
>>>
>>> —
>>> 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
>>>
>>
>> —
>> 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
>
> — 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


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

You will have no end of problems if you have multiple 1394 controllers in either the host or the target.

Make sure you have 1 1394 controller in both the host and the target.

Then things will work.

If you have a 1394 controller on the motherboard, the first thing you should do, before adding another card, is see if it works for debugging. Most likely you will be pleasantly surprised, and find that it works just fine.

If not, and you have to use an add in 1394 card, then MAKE SURE to disable the on board 1394 controller in the BIOS.

Joe.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
Sent: Thursday, September 09, 2010 3:06 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards

Does not help i.e. even after I disable the host controller on target,
and reboot the target windbg can not connect.

On Thu, Sep 9, 2010 at 2:48 PM, MARTIN OBRIEN
wrote:
> You need to on XP, as I recall.
>
> On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
>> No, the host controller on target is not disabled. Let me try
>> disabling the controller.
>>
>> Both host and target run XP SP2.
>>
>> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
>> wrote:
>>> Did you disable the 1394 controller on the TARGET?
>>>
>>>
>>> mm
>>>
>>> -----Original Message-----
>>> From: xxxxx@lists.osr.com
>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
>>> Sent: Thursday, September 09, 2010 4:24 PM
>>> To: Kernel Debugging Interest List
>>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>
>>> Yes, I have.
>>> Here is the output I get:
>>>
>>> Wrote 0 of 1 bytes of the breakin packet.
>>> Failed to write breakin packet to target. ?Win32 error 0n2
>>> WARNING: The HOST cannot communicate with the TARGET!
>>>
>>> The motherboard has a 1394 port as well. I could use the port on
>>> motherboard
>>> to talk to a different system. I have not changed the channel number
>>> since
>>> other system is not connected now.
>>>
>>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>>> wrote:
>>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>>>> menu?
>>>>
>>>>
>>>> mm
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
>>>> Sent: Thursday, September 09, 2010 4:12 PM
>>>> To: Kernel Debugging Interest List
>>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>>
>>>> Hi,
>>>> ? We have purchased two PCI based 1394 cards from OSR Online store and
>>>> put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>>
>>>> The boot.ini file on the target has the string /debug /debugport=1394
>>>> /channel=40.
>>>>
>>>> Windbg is started and kernel debug is selected from File menu. The
>>>> channel number is entered as 40.
>>>>
>>>> In this setup the host can not connect to target over channel 40.
>>>>
>>>> The control-Alt-D on windbg terminal prints
>>>>
>>>> Synchronize…
>>>>
>>>> … Synchronize: 80070002
>>>>
>>>> Any help to solve the problem is appreciated.
>>>>
>>>> Kallol Biswas
>>>> NucleoDyne Systems, Inc.
>>>>
>>>> —
>>>> 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
>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>
>>> —
>>> 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
>>>
>>>
>>> —
>>> 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
>>>
>>
>> —
>> 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
>
> — 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


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

Good point.

As long as we’ve got you here, Joe, do you happen to know that
boot.ini/bcdedit option that can be used to direct which PCI card to use for
kd? It’s not documented and I know that I reported that as a bug a long
time ago, but I don’t think that it has made its way into an update yet.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
Sent: Thursday, September 09, 2010 6:13 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

You will have no end of problems if you have multiple 1394 controllers in
either the host or the target.

Make sure you have 1 1394 controller in both the host and the target.

Then things will work.

If you have a 1394 controller on the motherboard, the first thing you should
do, before adding another card, is see if it works for debugging. Most
likely you will be pleasantly surprised, and find that it works just fine.

If not, and you have to use an add in 1394 card, then MAKE SURE to disable
the on board 1394 controller in the BIOS.

Joe.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
Sent: Thursday, September 09, 2010 3:06 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards

Does not help i.e. even after I disable the host controller on target, and
reboot the target windbg can not connect.

On Thu, Sep 9, 2010 at 2:48 PM, MARTIN OBRIEN
wrote:
> You need to on XP, as I recall.
>
> On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
>> No, the host controller on target is not disabled. Let me try
>> disabling the controller.
>>
>> Both host and target run XP SP2.
>>
>> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
>> wrote:
>>> Did you disable the 1394 controller on the TARGET?
>>>
>>>
>>> mm
>>>
>>> -----Original Message-----
>>> From: xxxxx@lists.osr.com
>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>> Biswas
>>> Sent: Thursday, September 09, 2010 4:24 PM
>>> To: Kernel Debugging Interest List
>>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394
>>> cards
>>>
>>> Yes, I have.
>>> Here is the output I get:
>>>
>>> Wrote 0 of 1 bytes of the breakin packet.
>>> Failed to write breakin packet to target. ?Win32 error 0n2
>>> WARNING: The HOST cannot communicate with the TARGET!
>>>
>>> The motherboard has a 1394 port as well. I could use the port on
>>> motherboard to talk to a different system. I have not changed the
>>> channel number since other system is not connected now.
>>>
>>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>>> wrote:
>>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>>>> menu?
>>>>
>>>>
>>>> mm
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>> Biswas
>>>> Sent: Thursday, September 09, 2010 4:12 PM
>>>> To: Kernel Debugging Interest List
>>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>>
>>>> Hi,
>>>> ? We have purchased two PCI based 1394 cards from OSR Online store
>>>> and put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>>
>>>> The boot.ini file on the target has the string /debug
>>>> /debugport=1394 /channel=40.
>>>>
>>>> Windbg is started and kernel debug is selected from File menu. The
>>>> channel number is entered as 40.
>>>>
>>>> In this setup the host can not connect to target over channel 40.
>>>>
>>>> The control-Alt-D on windbg terminal prints
>>>>
>>>> Synchronize…
>>>>
>>>> … Synchronize: 80070002
>>>>
>>>> Any help to solve the problem is appreciated.
>>>>
>>>> Kallol Biswas
>>>> NucleoDyne Systems, Inc.
>>>>
>>>> —
>>>> 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
>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>
>>> —
>>> 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
>>>
>>>
>>> —
>>> 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
>>>
>>
>> —
>> 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
>
> — 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


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


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

I only get the following lines…
SYNCTARGET: Timeout.
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
SYNCTARGET: Timeout.

On Thu, Sep 9, 2010 at 3:09 PM, M. M. O’Brien
wrote:
> Hmm.
>
> Was the CTRL+ALT+D output just that same message (synchronize…) over and
> over? ?If not, please post it.
>
> Also, have you installed windbg on the host more than once (as in EVER)?
>
>
> mm
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
> Sent: Thursday, September 09, 2010 6:06 PM
> To: Kernel Debugging Interest List
> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> Does not help i.e. even after I disable the host controller on target, and
> reboot the target windbg can not connect.
>
>
> On Thu, Sep 9, 2010 at 2:48 PM, MARTIN OBRIEN
> wrote:
>> You need to on XP, as I recall.
>>
>> On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
>>> No, the host controller on target is not disabled. Let me try
>>> disabling the controller.
>>>
>>> Both host and target run XP SP2.
>>>
>>> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
>>> wrote:
>>>> Did you disable the 1394 controller on the TARGET?
>>>>
>>>>
>>>> mm
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>> Biswas
>>>> Sent: Thursday, September 09, 2010 4:24 PM
>>>> To: Kernel Debugging Interest List
>>>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394
>>>> cards
>>>>
>>>> Yes, I have.
>>>> Here is the output I get:
>>>>
>>>> Wrote 0 of 1 bytes of the breakin packet.
>>>> Failed to write breakin packet to target. ?Win32 error 0n2
>>>> WARNING: The HOST cannot communicate with the TARGET!
>>>>
>>>> The motherboard has a 1394 port as well. I could use the port on
>>>> motherboard to talk to a different system. I have not changed the
>>>> channel number since other system is not connected now.
>>>>
>>>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>>>> wrote:
>>>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>>>>> menu?
>>>>>
>>>>>
>>>>> mm
>>>>>
>>>>> -----Original Message-----
>>>>> From: xxxxx@lists.osr.com
>>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>>> Biswas
>>>>> Sent: Thursday, September 09, 2010 4:12 PM
>>>>> To: Kernel Debugging Interest List
>>>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>>>
>>>>> Hi,
>>>>> ? We have purchased two PCI based 1394 cards from OSR Online store
>>>>> and put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>>>
>>>>> The boot.ini file on the target has the string /debug
>>>>> /debugport=1394 /channel=40.
>>>>>
>>>>> Windbg is started and kernel debug is selected from File menu. The
>>>>> channel number is entered as 40.
>>>>>
>>>>> In this setup the host can not connect to target over channel 40.
>>>>>
>>>>> The control-Alt-D on windbg terminal prints
>>>>>
>>>>> Synchronize…
>>>>>
>>>>> … Synchronize: 80070002
>>>>>
>>>>> Any help to solve the problem is appreciated.
>>>>>
>>>>> Kallol Biswas
>>>>> NucleoDyne Systems, Inc.
>>>>>
>>>>> —
>>>>> 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
>>>>>
>>>>>
>>>>> —
>>>>> 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
>>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>
>>> —
>>> 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
>>
>> — 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
>
> —
> 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
>
>
> —
> 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
>

It’s /busparams=bus.device.function (period separated), you would typically get the bus/device/function numbers from devmgmt.msc.

This is parsed both for usb and 1394 KD transport modules.

This is documented in debugger.chm under the bcdedit documentation.

  • S (Msft)

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O’Brien
Sent: Thursday, September 09, 2010 3:16 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

Good point.

As long as we’ve got you here, Joe, do you happen to know that boot.ini/bcdedit option that can be used to direct which PCI card to use for kd? It’s not documented and I know that I reported that as a bug a long time ago, but I don’t think that it has made its way into an update yet.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
Sent: Thursday, September 09, 2010 6:13 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

You will have no end of problems if you have multiple 1394 controllers in either the host or the target.

Make sure you have 1 1394 controller in both the host and the target.

Then things will work.

If you have a 1394 controller on the motherboard, the first thing you should do, before adding another card, is see if it works for debugging. Most likely you will be pleasantly surprised, and find that it works just fine.

If not, and you have to use an add in 1394 card, then MAKE SURE to disable the on board 1394 controller in the BIOS.

Joe.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
Sent: Thursday, September 09, 2010 3:06 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards

Does not help i.e. even after I disable the host controller on target, and reboot the target windbg can not connect.

On Thu, Sep 9, 2010 at 2:48 PM, MARTIN OBRIEN wrote:
> You need to on XP, as I recall.
>
> On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
>> No, the host controller on target is not disabled. Let me try
>> disabling the controller.
>>
>> Both host and target run XP SP2.
>>
>> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
>> wrote:
>>> Did you disable the 1394 controller on the TARGET?
>>>
>>>
>>> mm
>>>
>>> -----Original Message-----
>>> From: xxxxx@lists.osr.com
>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>> Biswas
>>> Sent: Thursday, September 09, 2010 4:24 PM
>>> To: Kernel Debugging Interest List
>>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394
>>> cards
>>>
>>> Yes, I have.
>>> Here is the output I get:
>>>
>>> Wrote 0 of 1 bytes of the breakin packet.
>>> Failed to write breakin packet to target. ?Win32 error 0n2
>>> WARNING: The HOST cannot communicate with the TARGET!
>>>
>>> The motherboard has a 1394 port as well. I could use the port on
>>> motherboard to talk to a different system. I have not changed the
>>> channel number since other system is not connected now.
>>>
>>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>>> wrote:
>>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>>>> menu?
>>>>
>>>>
>>>> mm
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>> Biswas
>>>> Sent: Thursday, September 09, 2010 4:12 PM
>>>> To: Kernel Debugging Interest List
>>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>>
>>>> Hi,
>>>> ? We have purchased two PCI based 1394 cards from OSR Online store
>>>> and put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>>
>>>> The boot.ini file on the target has the string /debug
>>>> /debugport=1394 /channel=40.
>>>>
>>>> Windbg is started and kernel debug is selected from File menu. The
>>>> channel number is entered as 40.
>>>>
>>>> In this setup the host can not connect to target over channel 40.
>>>>
>>>> The control-Alt-D on windbg terminal prints
>>>>
>>>> Synchronize…
>>>>
>>>> … Synchronize: 80070002
>>>>
>>>> Any help to solve the problem is appreciated.
>>>>
>>>> Kallol Biswas
>>>> NucleoDyne Systems, Inc.
>>>>
>>>> —
>>>> 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
>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>
>>> —
>>> 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
>>>
>>>
>>> —
>>> 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
>>>
>>
>> —
>> 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
>
> — 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


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


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


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

I remember now (I think): bcdedit /set loadoptions
busparams=..

Not sure if that translates to ‘/busparams=…’ in boot.ini.

mm

-----Original Message-----
From: M. M. O’Brien [mailto:xxxxx@gmail.com]
Sent: Thursday, September 09, 2010 6:16 PM
To: ‘Kernel Debugging Interest List’
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

Good point.

As long as we’ve got you here, Joe, do you happen to know that
boot.ini/bcdedit option that can be used to direct which PCI card to use for
kd? It’s not documented and I know that I reported that as a bug a long
time ago, but I don’t think that it has made its way into an update yet.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
Sent: Thursday, September 09, 2010 6:13 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

You will have no end of problems if you have multiple 1394 controllers in
either the host or the target.

Make sure you have 1 1394 controller in both the host and the target.

Then things will work.

If you have a 1394 controller on the motherboard, the first thing you should
do, before adding another card, is see if it works for debugging. Most
likely you will be pleasantly surprised, and find that it works just fine.

If not, and you have to use an add in 1394 card, then MAKE SURE to disable
the on board 1394 controller in the BIOS.

Joe.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
Sent: Thursday, September 09, 2010 3:06 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards

Does not help i.e. even after I disable the host controller on target, and
reboot the target windbg can not connect.

On Thu, Sep 9, 2010 at 2:48 PM, MARTIN OBRIEN
wrote:
> You need to on XP, as I recall.
>
> On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
>> No, the host controller on target is not disabled. Let me try
>> disabling the controller.
>>
>> Both host and target run XP SP2.
>>
>> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
>> wrote:
>>> Did you disable the 1394 controller on the TARGET?
>>>
>>>
>>> mm
>>>
>>> -----Original Message-----
>>> From: xxxxx@lists.osr.com
>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>> Biswas
>>> Sent: Thursday, September 09, 2010 4:24 PM
>>> To: Kernel Debugging Interest List
>>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394
>>> cards
>>>
>>> Yes, I have.
>>> Here is the output I get:
>>>
>>> Wrote 0 of 1 bytes of the breakin packet.
>>> Failed to write breakin packet to target. ?Win32 error 0n2
>>> WARNING: The HOST cannot communicate with the TARGET!
>>>
>>> The motherboard has a 1394 port as well. I could use the port on
>>> motherboard to talk to a different system. I have not changed the
>>> channel number since other system is not connected now.
>>>
>>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>>> wrote:
>>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>>>> menu?
>>>>
>>>>
>>>> mm
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>> Biswas
>>>> Sent: Thursday, September 09, 2010 4:12 PM
>>>> To: Kernel Debugging Interest List
>>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>>
>>>> Hi,
>>>> ? We have purchased two PCI based 1394 cards from OSR Online store
>>>> and put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>>
>>>> The boot.ini file on the target has the string /debug
>>>> /debugport=1394 /channel=40.
>>>>
>>>> Windbg is started and kernel debug is selected from File menu. The
>>>> channel number is entered as 40.
>>>>
>>>> In this setup the host can not connect to target over channel 40.
>>>>
>>>> The control-Alt-D on windbg terminal prints
>>>>
>>>> Synchronize…
>>>>
>>>> … Synchronize: 80070002
>>>>
>>>> Any help to solve the problem is appreciated.
>>>>
>>>> Kallol Biswas
>>>> NucleoDyne Systems, Inc.
>>>>
>>>> —
>>>> 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
>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>
>>> —
>>> 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
>>>
>>>
>>> —
>>> 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
>>>
>>
>> —
>> 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
>
> — 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


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


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

My bad - I thought that it wasn’t documented.

Thanks,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Skywing
Sent: Thursday, September 09, 2010 6:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

It’s /busparams=bus.device.function (period separated), you would typically
get the bus/device/function numbers from devmgmt.msc.

This is parsed both for usb and 1394 KD transport modules.

This is documented in debugger.chm under the bcdedit documentation.

  • S (Msft)

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O’Brien
Sent: Thursday, September 09, 2010 3:16 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

Good point.

As long as we’ve got you here, Joe, do you happen to know that
boot.ini/bcdedit option that can be used to direct which PCI card to use for
kd? It’s not documented and I know that I reported that as a bug a long
time ago, but I don’t think that it has made its way into an update yet.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
Sent: Thursday, September 09, 2010 6:13 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

You will have no end of problems if you have multiple 1394 controllers in
either the host or the target.

Make sure you have 1 1394 controller in both the host and the target.

Then things will work.

If you have a 1394 controller on the motherboard, the first thing you should
do, before adding another card, is see if it works for debugging. Most
likely you will be pleasantly surprised, and find that it works just fine.

If not, and you have to use an add in 1394 card, then MAKE SURE to disable
the on board 1394 controller in the BIOS.

Joe.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
Sent: Thursday, September 09, 2010 3:06 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards

Does not help i.e. even after I disable the host controller on target, and
reboot the target windbg can not connect.

On Thu, Sep 9, 2010 at 2:48 PM, MARTIN OBRIEN
wrote:
> You need to on XP, as I recall.
>
> On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
>> No, the host controller on target is not disabled. Let me try
>> disabling the controller.
>>
>> Both host and target run XP SP2.
>>
>> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
>> wrote:
>>> Did you disable the 1394 controller on the TARGET?
>>>
>>>
>>> mm
>>>
>>> -----Original Message-----
>>> From: xxxxx@lists.osr.com
>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>> Biswas
>>> Sent: Thursday, September 09, 2010 4:24 PM
>>> To: Kernel Debugging Interest List
>>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394
>>> cards
>>>
>>> Yes, I have.
>>> Here is the output I get:
>>>
>>> Wrote 0 of 1 bytes of the breakin packet.
>>> Failed to write breakin packet to target. ?Win32 error 0n2
>>> WARNING: The HOST cannot communicate with the TARGET!
>>>
>>> The motherboard has a 1394 port as well. I could use the port on
>>> motherboard to talk to a different system. I have not changed the
>>> channel number since other system is not connected now.
>>>
>>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>>> wrote:
>>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>>>> menu?
>>>>
>>>>
>>>> mm
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>> Biswas
>>>> Sent: Thursday, September 09, 2010 4:12 PM
>>>> To: Kernel Debugging Interest List
>>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>>
>>>> Hi,
>>>> ? We have purchased two PCI based 1394 cards from OSR Online store
>>>> and put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>>
>>>> The boot.ini file on the target has the string /debug
>>>> /debugport=1394 /channel=40.
>>>>
>>>> Windbg is started and kernel debug is selected from File menu. The
>>>> channel number is entered as 40.
>>>>
>>>> In this setup the host can not connect to target over channel 40.
>>>>
>>>> The control-Alt-D on windbg terminal prints
>>>>
>>>> Synchronize…
>>>>
>>>> … Synchronize: 80070002
>>>>
>>>> Any help to solve the problem is appreciated.
>>>>
>>>> Kallol Biswas
>>>> NucleoDyne Systems, Inc.
>>>>
>>>> —
>>>> 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
>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>
>>> —
>>> 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
>>>
>>>
>>> —
>>> 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
>>>
>>
>> —
>> 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
>
> — 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


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


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


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


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

I don’t recall if I mentioned this already, but if you’ve ever upgraded
windbg on the host, it’s possible that the new 1394 kd transport drivers
aren’t loading correctly. I don’t recall exactly when this happened, but I
THINK that it was two windbg versions ago. If you think that this might be
the case, take a look at the ‘relnotes.txt’ file in your windbg root
directory and read and follow the steps regarding removing the old windbg
1394 drivers.

Also, getting desperate (in case your problem is not one of multiple 1394
cards), you might want to check your bios for a setting called something
like ‘plug and play os’ and make sure that it is set to ‘no/disabled/off.’

Good luck,

mm

-----Original Message-----
From: M. M. O’Brien [mailto:xxxxx@gmail.com]
Sent: Thursday, September 09, 2010 6:23 PM
To: ‘Kernel Debugging Interest List’
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

My bad - I thought that it wasn’t documented.

Thanks,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Skywing
Sent: Thursday, September 09, 2010 6:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

It’s /busparams=bus.device.function (period separated), you would typically
get the bus/device/function numbers from devmgmt.msc.

This is parsed both for usb and 1394 KD transport modules.

This is documented in debugger.chm under the bcdedit documentation.

  • S (Msft)

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O’Brien
Sent: Thursday, September 09, 2010 3:16 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

Good point.

As long as we’ve got you here, Joe, do you happen to know that
boot.ini/bcdedit option that can be used to direct which PCI card to use for
kd? It’s not documented and I know that I reported that as a bug a long
time ago, but I don’t think that it has made its way into an update yet.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
Sent: Thursday, September 09, 2010 6:13 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

You will have no end of problems if you have multiple 1394 controllers in
either the host or the target.

Make sure you have 1 1394 controller in both the host and the target.

Then things will work.

If you have a 1394 controller on the motherboard, the first thing you should
do, before adding another card, is see if it works for debugging. Most
likely you will be pleasantly surprised, and find that it works just fine.

If not, and you have to use an add in 1394 card, then MAKE SURE to disable
the on board 1394 controller in the BIOS.

Joe.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
Sent: Thursday, September 09, 2010 3:06 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards

Does not help i.e. even after I disable the host controller on target, and
reboot the target windbg can not connect.

On Thu, Sep 9, 2010 at 2:48 PM, MARTIN OBRIEN
wrote:
> You need to on XP, as I recall.
>
> On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
>> No, the host controller on target is not disabled. Let me try
>> disabling the controller.
>>
>> Both host and target run XP SP2.
>>
>> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
>> wrote:
>>> Did you disable the 1394 controller on the TARGET?
>>>
>>>
>>> mm
>>>
>>> -----Original Message-----
>>> From: xxxxx@lists.osr.com
>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>> Biswas
>>> Sent: Thursday, September 09, 2010 4:24 PM
>>> To: Kernel Debugging Interest List
>>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394
>>> cards
>>>
>>> Yes, I have.
>>> Here is the output I get:
>>>
>>> Wrote 0 of 1 bytes of the breakin packet.
>>> Failed to write breakin packet to target. ?Win32 error 0n2
>>> WARNING: The HOST cannot communicate with the TARGET!
>>>
>>> The motherboard has a 1394 port as well. I could use the port on
>>> motherboard to talk to a different system. I have not changed the
>>> channel number since other system is not connected now.
>>>
>>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>>> wrote:
>>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>>>> menu?
>>>>
>>>>
>>>> mm
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>> Biswas
>>>> Sent: Thursday, September 09, 2010 4:12 PM
>>>> To: Kernel Debugging Interest List
>>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>>
>>>> Hi,
>>>> ? We have purchased two PCI based 1394 cards from OSR Online store
>>>> and put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>>
>>>> The boot.ini file on the target has the string /debug
>>>> /debugport=1394 /channel=40.
>>>>
>>>> Windbg is started and kernel debug is selected from File menu. The
>>>> channel number is entered as 40.
>>>>
>>>> In this setup the host can not connect to target over channel 40.
>>>>
>>>> The control-Alt-D on windbg terminal prints
>>>>
>>>> Synchronize…
>>>>
>>>> … Synchronize: 80070002
>>>>
>>>> Any help to solve the problem is appreciated.
>>>>
>>>> Kallol Biswas
>>>> NucleoDyne Systems, Inc.
>>>>
>>>> —
>>>> 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
>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>
>>> —
>>> 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
>>>
>>>
>>> —
>>> 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
>>>
>>
>> —
>> 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
>
> — 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


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


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


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


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

I have got it working by using the onboard ports on the hosts,
disabling the onboard ports on target and using the OSR device.

I guess the onboard ports on the target should also work.

On Thu, Sep 9, 2010 at 3:29 PM, M. M. O’Brien
wrote:
> I don’t recall if I mentioned this already, but if you’ve ever upgraded
> windbg on the host, it’s possible that the new 1394 kd transport drivers
> aren’t loading correctly. ?I don’t recall exactly when this happened, but I
> THINK that it was two windbg versions ago. ?If you think that this might be
> the case, take a look at the ‘relnotes.txt’ file in your windbg root
> directory and read and follow the steps regarding removing the old windbg
> 1394 drivers.
>
> Also, getting desperate (in case your problem is not one of multiple 1394
> cards), you might want to check your bios for a setting called something
> like ‘plug and play os’ and make sure that it is set to ‘no/disabled/off.’
>
>
>
> Good luck,
>
> mm
>
> -----Original Message-----
> From: M. M. O’Brien [mailto:xxxxx@gmail.com]
> Sent: Thursday, September 09, 2010 6:23 PM
> To: ‘Kernel Debugging Interest List’
> Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> My bad - I thought that it wasn’t documented.
>
>
> Thanks,
>
> mm
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Skywing
> Sent: Thursday, September 09, 2010 6:20 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> It’s /busparams=bus.device.function ?(period separated), you would typically
> get the bus/device/function numbers from devmgmt.msc.
>
> This is parsed both for usb and 1394 KD transport modules.
>
> This is documented in debugger.chm under the bcdedit documentation.
>
> - S (Msft)
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O’Brien
> Sent: Thursday, September 09, 2010 3:16 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> Good point.
>
> As long as we’ve got you here, Joe, do you happen to know that
> boot.ini/bcdedit option that can be used to direct which PCI card to use for
> kd? ?It’s not documented and I know that I reported that as a bug a long
> time ago, but I don’t think that it has made its way into an update yet.
>
>
> mm
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
> Sent: Thursday, September 09, 2010 6:13 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> You will have no end of problems if you have multiple 1394 controllers in
> either the host or the target.
>
> Make sure you have 1 1394 controller in both the host and the target.
>
> Then things will work.
>
> If you have a 1394 controller on the motherboard, the first thing you should
> do, before adding another card, is see if it works for debugging. ?Most
> likely you will be pleasantly surprised, and find that it works just fine.
>
> If not, and you have to use an add in 1394 card, then MAKE SURE to disable
> the on board 1394 controller in the BIOS.
>
> Joe.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
> Sent: Thursday, September 09, 2010 3:06 PM
> To: Kernel Debugging Interest List
> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> Does not help i.e. even after I disable the host controller on target, and
> reboot the target windbg can not connect.
>
>
> On Thu, Sep 9, 2010 at 2:48 PM, MARTIN OBRIEN
> wrote:
>> You need to on XP, as I recall.
>>
>> On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
>>> No, the host controller on target is not disabled. Let me try
>>> disabling the controller.
>>>
>>> Both host and target run XP SP2.
>>>
>>> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
>>> wrote:
>>>> Did you disable the 1394 controller on the TARGET?
>>>>
>>>>
>>>> mm
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>> Biswas
>>>> Sent: Thursday, September 09, 2010 4:24 PM
>>>> To: Kernel Debugging Interest List
>>>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394
>>>> cards
>>>>
>>>> Yes, I have.
>>>> Here is the output I get:
>>>>
>>>> Wrote 0 of 1 bytes of the breakin packet.
>>>> Failed to write breakin packet to target. ?Win32 error 0n2
>>>> WARNING: The HOST cannot communicate with the TARGET!
>>>>
>>>> The motherboard has a 1394 port as well. I could use the port on
>>>> motherboard to talk to a different system. I have not changed the
>>>> channel number since other system is not connected now.
>>>>
>>>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>>>> wrote:
>>>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>>>>> menu?
>>>>>
>>>>>
>>>>> mm
>>>>>
>>>>> -----Original Message-----
>>>>> From: xxxxx@lists.osr.com
>>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>>> Biswas
>>>>> Sent: Thursday, September 09, 2010 4:12 PM
>>>>> To: Kernel Debugging Interest List
>>>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>>>
>>>>> Hi,
>>>>> ? We have purchased two PCI based 1394 cards from OSR Online store
>>>>> and put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>>>
>>>>> The boot.ini file on the target has the string /debug
>>>>> /debugport=1394 /channel=40.
>>>>>
>>>>> Windbg is started and kernel debug is selected from File menu. The
>>>>> channel number is entered as 40.
>>>>>
>>>>> In this setup the host can not connect to target over channel 40.
>>>>>
>>>>> The control-Alt-D on windbg terminal prints
>>>>>
>>>>> Synchronize…
>>>>>
>>>>> … Synchronize: 80070002
>>>>>
>>>>> Any help to solve the problem is appreciated.
>>>>>
>>>>> Kallol Biswas
>>>>> NucleoDyne Systems, Inc.
>>>>>
>>>>> —
>>>>> 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
>>>>>
>>>>>
>>>>> —
>>>>> 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
>>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>
>>> —
>>> 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
>>
>> — 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
>
> —
> 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
>
>
> —
> 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
>
>
> —
> 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
>
> —
> 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
>
>
> —
> 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
>

The onboard 1394 controller on the target should work fine if you are using Vista SP2, or Win7. It may not work if you are using some flavor of XP. There were several fixes to kd1394.dll that went into Win7, and which I believe were back ported to Vista SP2 that allowed most controllers to work. I don’t believe those fixes have been back ported to any version of XP.

Note also that the busparams are in decimal for 1394, as well as for USB for Win7 and later, but are in hex for USB on Vista. I don’t know if the USB decimal busparams change went into any of the Vista service packs or not.

I am pretty sure that you can specify /busparams=b.d.f in a boot.ini file and it will work. b is the bus number, d is the device number and f is the function number as shown in the properties page of device manager for the debug device.

Joe.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
Sent: Thursday, September 09, 2010 4:19 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards

I have got it working by using the onboard ports on the hosts,
disabling the onboard ports on target and using the OSR device.

I guess the onboard ports on the target should also work.

On Thu, Sep 9, 2010 at 3:29 PM, M. M. O’Brien
wrote:
> I don’t recall if I mentioned this already, but if you’ve ever upgraded
> windbg on the host, it’s possible that the new 1394 kd transport drivers
> aren’t loading correctly. ?I don’t recall exactly when this happened, but I
> THINK that it was two windbg versions ago. ?If you think that this might be
> the case, take a look at the ‘relnotes.txt’ file in your windbg root
> directory and read and follow the steps regarding removing the old windbg
> 1394 drivers.
>
> Also, getting desperate (in case your problem is not one of multiple 1394
> cards), you might want to check your bios for a setting called something
> like ‘plug and play os’ and make sure that it is set to ‘no/disabled/off.’
>
>
>
> Good luck,
>
> mm
>
> -----Original Message-----
> From: M. M. O’Brien [mailto:xxxxx@gmail.com]
> Sent: Thursday, September 09, 2010 6:23 PM
> To: ‘Kernel Debugging Interest List’
> Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> My bad - I thought that it wasn’t documented.
>
>
> Thanks,
>
> mm
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Skywing
> Sent: Thursday, September 09, 2010 6:20 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> It’s /busparams=bus.device.function ?(period separated), you would typically
> get the bus/device/function numbers from devmgmt.msc.
>
> This is parsed both for usb and 1394 KD transport modules.
>
> This is documented in debugger.chm under the bcdedit documentation.
>
> - S (Msft)
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O’Brien
> Sent: Thursday, September 09, 2010 3:16 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> Good point.
>
> As long as we’ve got you here, Joe, do you happen to know that
> boot.ini/bcdedit option that can be used to direct which PCI card to use for
> kd? ?It’s not documented and I know that I reported that as a bug a long
> time ago, but I don’t think that it has made its way into an update yet.
>
>
> mm
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
> Sent: Thursday, September 09, 2010 6:13 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> You will have no end of problems if you have multiple 1394 controllers in
> either the host or the target.
>
> Make sure you have 1 1394 controller in both the host and the target.
>
> Then things will work.
>
> If you have a 1394 controller on the motherboard, the first thing you should
> do, before adding another card, is see if it works for debugging. ?Most
> likely you will be pleasantly surprised, and find that it works just fine.
>
> If not, and you have to use an add in 1394 card, then MAKE SURE to disable
> the on board 1394 controller in the BIOS.
>
> Joe.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
> Sent: Thursday, September 09, 2010 3:06 PM
> To: Kernel Debugging Interest List
> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> Does not help i.e. even after I disable the host controller on target, and
> reboot the target windbg can not connect.
>
>
> On Thu, Sep 9, 2010 at 2:48 PM, MARTIN OBRIEN
> wrote:
>> You need to on XP, as I recall.
>>
>> On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
>>> No, the host controller on target is not disabled. Let me try
>>> disabling the controller.
>>>
>>> Both host and target run XP SP2.
>>>
>>> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
>>> wrote:
>>>> Did you disable the 1394 controller on the TARGET?
>>>>
>>>>
>>>> mm
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>> Biswas
>>>> Sent: Thursday, September 09, 2010 4:24 PM
>>>> To: Kernel Debugging Interest List
>>>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394
>>>> cards
>>>>
>>>> Yes, I have.
>>>> Here is the output I get:
>>>>
>>>> Wrote 0 of 1 bytes of the breakin packet.
>>>> Failed to write breakin packet to target. ?Win32 error 0n2
>>>> WARNING: The HOST cannot communicate with the TARGET!
>>>>
>>>> The motherboard has a 1394 port as well. I could use the port on
>>>> motherboard to talk to a different system. I have not changed the
>>>> channel number since other system is not connected now.
>>>>
>>>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>>>> wrote:
>>>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the ‘Debug’
>>>>> menu?
>>>>>
>>>>>
>>>>> mm
>>>>>
>>>>> -----Original Message-----
>>>>> From: xxxxx@lists.osr.com
>>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>>> Biswas
>>>>> Sent: Thursday, September 09, 2010 4:12 PM
>>>>> To: Kernel Debugging Interest List
>>>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>>>
>>>>> Hi,
>>>>> ? We have purchased two PCI based 1394 cards from OSR Online store
>>>>> and put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>>>
>>>>> The boot.ini file on the target has the string /debug
>>>>> /debugport=1394 /channel=40.
>>>>>
>>>>> Windbg is started and kernel debug is selected from File menu. The
>>>>> channel number is entered as 40.
>>>>>
>>>>> In this setup the host can not connect to target over channel 40.
>>>>>
>>>>> The control-Alt-D on windbg terminal prints
>>>>>
>>>>> Synchronize…
>>>>>
>>>>> … Synchronize: 80070002
>>>>>
>>>>> Any help to solve the problem is appreciated.
>>>>>
>>>>> Kallol Biswas
>>>>> NucleoDyne Systems, Inc.
>>>>>
>>>>> —
>>>>> 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
>>>>>
>>>>>
>>>>> —
>>>>> 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
>>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>
>>> —
>>> 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
>>
>> — 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
>
> —
> 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
>
>
> —
> 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
>
>
> —
> 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
>
> —
> 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
>
>
> —
> 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
>


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

Thanks, Joe.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
Sent: Thursday, September 09, 2010 7:35 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards

The onboard 1394 controller on the target should work fine if you are using
Vista SP2, or Win7. It may not work if you are using some flavor of XP.
There were several fixes to kd1394.dll that went into Win7, and which I
believe were back ported to Vista SP2 that allowed most controllers to work.
I don’t believe those fixes have been back ported to any version of XP.

Note also that the busparams are in decimal for 1394, as well as for USB for
Win7 and later, but are in hex for USB on Vista. I don’t know if the USB
decimal busparams change went into any of the Vista service packs or not.

I am pretty sure that you can specify /busparams=b.d.f in a boot.ini file
and it will work. b is the bus number, d is the device number and f is the
function number as shown in the properties page of device manager for the
debug device.

Joe.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
Sent: Thursday, September 09, 2010 4:19 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards

I have got it working by using the onboard ports on the hosts, disabling the
onboard ports on target and using the OSR device.

I guess the onboard ports on the target should also work.

On Thu, Sep 9, 2010 at 3:29 PM, M. M. O’Brien
wrote:
> I don’t recall if I mentioned this already, but if you’ve ever
> upgraded windbg on the host, it’s possible that the new 1394 kd
> transport drivers aren’t loading correctly. ?I don’t recall exactly
> when this happened, but I THINK that it was two windbg versions ago. ?
> If you think that this might be the case, take a look at the
> ‘relnotes.txt’ file in your windbg root directory and read and follow
> the steps regarding removing the old windbg
> 1394 drivers.
>
> Also, getting desperate (in case your problem is not one of multiple
> 1394 cards), you might want to check your bios for a setting called
> something like ‘plug and play os’ and make sure that it is set to
‘no/disabled/off.’
>
>
>
> Good luck,
>
> mm
>
> -----Original Message-----
> From: M. M. O’Brien [mailto:xxxxx@gmail.com]
> Sent: Thursday, September 09, 2010 6:23 PM
> To: ‘Kernel Debugging Interest List’
> Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> My bad - I thought that it wasn’t documented.
>
>
> Thanks,
>
> mm
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Skywing
> Sent: Thursday, September 09, 2010 6:20 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> It’s /busparams=bus.device.function ?(period separated), you would
> typically get the bus/device/function numbers from devmgmt.msc.
>
> This is parsed both for usb and 1394 KD transport modules.
>
> This is documented in debugger.chm under the bcdedit documentation.
>
> - S (Msft)
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O’Brien
> Sent: Thursday, September 09, 2010 3:16 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> Good point.
>
> As long as we’ve got you here, Joe, do you happen to know that
> boot.ini/bcdedit option that can be used to direct which PCI card to
> use for kd? ?It’s not documented and I know that I reported that as a
> bug a long time ago, but I don’t think that it has made its way into an
update yet.
>
>
> mm
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
> Sent: Thursday, September 09, 2010 6:13 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> You will have no end of problems if you have multiple 1394 controllers
> in either the host or the target.
>
> Make sure you have 1 1394 controller in both the host and the target.
>
> Then things will work.
>
> If you have a 1394 controller on the motherboard, the first thing you
> should do, before adding another card, is see if it works for
> debugging. ?Most likely you will be pleasantly surprised, and find that it
works just fine.
>
> If not, and you have to use an add in 1394 card, then MAKE SURE to
> disable the on board 1394 controller in the BIOS.
>
> Joe.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol Biswas
> Sent: Thursday, September 09, 2010 3:06 PM
> To: Kernel Debugging Interest List
> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394 cards
>
> Does not help i.e. even after I disable the host controller on target,
> and reboot the target windbg can not connect.
>
>
> On Thu, Sep 9, 2010 at 2:48 PM, MARTIN OBRIEN
> wrote:
>> You need to on XP, as I recall.
>>
>> On Sep 9, 2010 5:47 PM, “Kallol Biswas” wrote:
>>> No, the host controller on target is not disabled. Let me try
>>> disabling the controller.
>>>
>>> Both host and target run XP SP2.
>>>
>>> On Thu, Sep 9, 2010 at 1:41 PM, M. M. O’Brien
>>> wrote:
>>>> Did you disable the 1394 controller on the TARGET?
>>>>
>>>>
>>>> mm
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>> Biswas
>>>> Sent: Thursday, September 09, 2010 4:24 PM
>>>> To: Kernel Debugging Interest List
>>>> Subject: Re: [windbg] cannot get windbg working over OSR’s 1394
>>>> cards
>>>>
>>>> Yes, I have.
>>>> Here is the output I get:
>>>>
>>>> Wrote 0 of 1 bytes of the breakin packet.
>>>> Failed to write breakin packet to target. ?Win32 error 0n2
>>>> WARNING: The HOST cannot communicate with the TARGET!
>>>>
>>>> The motherboard has a 1394 port as well. I could use the port on
>>>> motherboard to talk to a different system. I have not changed the
>>>> channel number since other system is not connected now.
>>>>
>>>> On Thu, Sep 9, 2010 at 1:15 PM, M. M. O’Brien
>>>> wrote:
>>>>> Did you tell it to break in - Ctrl+Break or ‘Break in’ from the
‘Debug’
>>>>> menu?
>>>>>
>>>>>
>>>>> mm
>>>>>
>>>>> -----Original Message-----
>>>>> From: xxxxx@lists.osr.com
>>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of Kallol
>>>>> Biswas
>>>>> Sent: Thursday, September 09, 2010 4:12 PM
>>>>> To: Kernel Debugging Interest List
>>>>> Subject: [windbg] cannot get windbg working over OSR’s 1394 cards
>>>>>
>>>>> Hi,
>>>>> ? We have purchased two PCI based 1394 cards from OSR Online store
>>>>> and put one in a target (ASUS P6 motherboard) and the other in a PC.
>>>>>
>>>>> The boot.ini file on the target has the string /debug
>>>>> /debugport=1394 /channel=40.
>>>>>
>>>>> Windbg is started and kernel debug is selected from File menu. The
>>>>> channel number is entered as 40.
>>>>>
>>>>> In this setup the host can not connect to target over channel 40.
>>>>>
>>>>> The control-Alt-D on windbg terminal prints
>>>>>
>>>>> Synchronize…
>>>>>
>>>>> … Synchronize: 80070002
>>>>>
>>>>> Any help to solve the problem is appreciated.
>>>>>
>>>>> Kallol Biswas
>>>>> NucleoDyne Systems, Inc.
>>>>>
>>>>> —
>>>>> 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
>>>>>
>>>>>
>>>>> —
>>>>> 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
>>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>>
>>>> —
>>>> 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
>>>>
>>>
>>> —
>>> 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
>>
>> — 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
>
> —
> 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
>
>
> —
> 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
>
>
> —
> 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
>
> —
> 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
>
>
> —
> 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
>


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


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