Problem connecting to Toshiba 5105 laptop target.

John_Hensley-1 · August 7, 2002, 4:21pm

Has anyone been able to get WinDbg to work with a Toshiba 5105 XP Pro
laptop as the target? WinDbg won’t connect to this machine as a target
using 1394 and the machine has no legacy COM ports. There doesn’t seem
to be anything noticeably wrong with the 1394 drivers on the Toshiba
because this machine works fine as the WinDbg host and connects via
the 1394 cable to my development machine which has no problem being a
1394 target. The Toshiba has no problem accessing other 1394 devices
through this port. Both machines use the TI OHCI Compliant IEEE 1394
host controller and both machines are using Microsoft ohci1394.sys
driver version 5.1.2600.1079 (xpsp1.020717-1800) and both have the
same settings in boot.ini.

Are there any other options for debugging boot drivers on this machine
if 1394 can’t be made to work?

Thanks,
John Hensley

OSR_Community_User · August 7, 2002, 4:44pm

I’ve had similar problem debugging my Dell laptop.
Somebody from MS debugger team told me at WinHEC that “1394 debugging support is broken in XP.”
I was advised to try it on XP SP1 or .NET Server. I later found that it worked fine on both.

This is what I do for the time being to make it work on XP 2600.

start debugger on the host.
boot target in 1394 debugging mode. Debugger on host will appear not detecting target.
run something that causes exception on target. Simple app with int3 would do.
target will lock up.
close debugger on host and the restart it. In 9 out of 10 cases new instance of debugger will
see target automatically. Otherwise I have to manually break into it (Ctrl+Break.)

– Max.

— John Hensley wrote:
>
> Has anyone been able to get WinDbg to work with a Toshiba 5105 XP Pro
> laptop as the target? WinDbg won’t connect to this machine as a target
> using 1394 and the machine has no legacy COM ports. There doesn’t seem
> to be anything noticeably wrong with the 1394 drivers on the Toshiba
> because this machine works fine as the WinDbg host and connects via
> the 1394 cable to my development machine which has no problem being a
> 1394 target. The Toshiba has no problem accessing other 1394 devices
> through this port. Both machines use the TI OHCI Compliant IEEE 1394
> host controller and both machines are using Microsoft ohci1394.sys
> driver version 5.1.2600.1079 (xpsp1.020717-1800) and both have the
> same settings in boot.ini.
>
> Are there any other options for debugging boot drivers on this machine
> if 1394 can’t be made to work?
>
> Thanks,
> John Hensley
>
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@yahoo.com
> To unsubscribe send a blank email to %%email.unsub%%

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com

OSR_Community_User-361 · August 7, 2002, 4:55pm

We got 1394 to work on XP. Just follow the WinDbg help.
But do use latest debugger 6.0.17.0. or later

Juan
-----Original Message-----
From: Max Paklin [mailto:xxxxx@yahoo.com]
Sent: Wednesday, August 07, 2002 3:41 PM
To: Kernel Debugging Interest List
Subject: [windbg] Re: Problem connecting to Toshiba 5105 laptop target.

I’ve had similar problem debugging my Dell laptop.
Somebody from MS debugger team told me at WinHEC that “1394 debugging
support is broken in XP.”
I was advised to try it on XP SP1 or .NET Server. I later found that it
worked fine on both.

This is what I do for the time being to make it work on XP 2600.

start debugger on the host.
boot target in 1394 debugging mode. Debugger on host will appear not
detecting target.
run something that causes exception on target. Simple app with int3
would do.
target will lock up.
close debugger on host and the restart it. In 9 out of 10 cases new
instance of debugger will
see target automatically. Otherwise I have to manually break into it
(Ctrl+Break.)

– Max.

— John Hensley wrote:
>
> Has anyone been able to get WinDbg to work with a Toshiba 5105 XP Pro
> laptop as the target? WinDbg won’t connect to this machine as a target
> using 1394 and the machine has no legacy COM ports. There doesn’t seem
> to be anything noticeably wrong with the 1394 drivers on the Toshiba
> because this machine works fine as the WinDbg host and connects via
> the 1394 cable to my development machine which has no problem being a
> 1394 target. The Toshiba has no problem accessing other 1394 devices
> through this port. Both machines use the TI OHCI Compliant IEEE 1394
> host controller and both machines are using Microsoft ohci1394.sys
> driver version 5.1.2600.1079 (xpsp1.020717-1800) and both have the
> same settings in boot.ini.
>
> Are there any other options for debugging boot drivers on this machine
> if 1394 can’t be made to work?
>
> Thanks,
> John Hensley
>
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@yahoo.com
> To unsubscribe send a blank email to %%email.unsub%%

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com

—
You are currently subscribed to windbg as: martinez@hp.com
To unsubscribe send a blank email to %%email.unsub%%

OSR_Community_User · August 7, 2002, 5:08pm

Yes, it mostly works for me as well.
Dell laptop is the only system that I have had trouble with.

I put “debugging support broken” statement in quotes because that how it was said.
I assume that what was actually meant was “it may not work.”

– Max.

— “Martinez, Juan (Cons)” wrote:
> We got 1394 to work on XP. Just follow the WinDbg help.
> But do use latest debugger 6.0.17.0. or later
>
>
> Juan
> -----Original Message-----
> From: Max Paklin [mailto:xxxxx@yahoo.com]
> Sent: Wednesday, August 07, 2002 3:41 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] Re: Problem connecting to Toshiba 5105 laptop target.
>
> I’ve had similar problem debugging my Dell laptop.
> Somebody from MS debugger team told me at WinHEC that “1394 debugging
> support is broken in XP.”
> I was advised to try it on XP SP1 or .NET Server. I later found that it
> worked fine on both.
>
> This is what I do for the time being to make it work on XP 2600.
>
> 1. start debugger on the host.
> 2. boot target in 1394 debugging mode. Debugger on host will appear not
> detecting target.
> 3. run something that causes exception on target. Simple app with int3
> would do.
> 4. target will lock up.
> 5. close debugger on host and the restart it. In 9 out of 10 cases new
> instance of debugger will
> see target automatically. Otherwise I have to manually break into it
> (Ctrl+Break.)
>
> – Max.
>
>
>
> — John Hensley wrote:
> >
> > Has anyone been able to get WinDbg to work with a Toshiba 5105 XP Pro
> > laptop as the target? WinDbg won’t connect to this machine as a target
> > using 1394 and the machine has no legacy COM ports. There doesn’t seem
> > to be anything noticeably wrong with the 1394 drivers on the Toshiba
> > because this machine works fine as the WinDbg host and connects via
> > the 1394 cable to my development machine which has no problem being a
> > 1394 target. The Toshiba has no problem accessing other 1394 devices
> > through this port. Both machines use the TI OHCI Compliant IEEE 1394
> > host controller and both machines are using Microsoft ohci1394.sys
> > driver version 5.1.2600.1079 (xpsp1.020717-1800) and both have the
> > same settings in boot.ini.
> >
> > Are there any other options for debugging boot drivers on this machine
> > if 1394 can’t be made to work?
> >
> > Thanks,
> > John Hensley
> >
> >
> >
> >
> > —
> > You are currently subscribed to windbg as: xxxxx@yahoo.com
> > To unsubscribe send a blank email to %%email.unsub%%
>
>
>
> Do You Yahoo!?
> Yahoo! Health - Feel better, live better
> http://health.yahoo.com
>
>
> —
> You are currently subscribed to windbg as: martinez@hp.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
> —
> You are currently subscribed to windbg as: xxxxx@yahoo.com
> To unsubscribe send a blank email to %%email.unsub%%

Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com

OSR_Community_User · August 7, 2002, 6:41pm

Try setting your BIOS “Plug-and-play OS” setting to “false” (or your
BIOS “Set-up Plug-andplay” to “true”). This will force the laptop to
initialize any bridge that lies between the 1394 controller and the
CPU, and it’ll also set up the controller to be ready to go when the
kernel loads. Doing so might help.

I’ve seen a Toshiba laptop that didn’t actually have a BIOS screen
you could get into, though, which made me sad.

Cheers,

/ h+

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of John Hensley
Sent: Wednesday, August 07, 2002 1:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Problem connecting to Toshiba 5105 laptop target.

Has anyone been able to get WinDbg to work with a Toshiba 5105 XP Pro
laptop as the target? WinDbg won’t connect to this machine as a target
using 1394 and the machine has no legacy COM ports. There doesn’t seem
to be anything noticeably wrong with the 1394 drivers on the Toshiba
because this machine works fine as the WinDbg host and connects via
the 1394 cable to my development machine which has no problem being a
1394 target. The Toshiba has no problem accessing other 1394 devices
through this port. Both machines use the TI OHCI Compliant IEEE 1394
host controller and both machines are using Microsoft ohci1394.sys
driver version 5.1.2600.1079 (xpsp1.020717-1800) and both have the
same settings in boot.ini.

Are there any other options for debugging boot drivers on this machine
if 1394 can’t be made to work?

Thanks,
John Hensley

You are currently subscribed to windbg as: xxxxx@mindcontrol.org
To unsubscribe send a blank email to %%email.unsub%%

John_Hensley-1 · August 7, 2002, 11:17pm

Thanks to all who replied with suggestions. I tried them all without
success except for disabling PnP in the BIOS. I’ve not found a way to
enter the ROMBIOS setup on this machine, it has a Win32 app for
changing the settings and disabling PnP is not one of the options.

I installed the latest build of the XP SP1 beta on both the host and
target in hopes that the WinDbg guys were acurate in their claims that
it will solve the WinDbg 1394 problems, but no luck.

I’ve been really happy with WinDbg’s 1394 support and this is the
first machine I’ve not been able to connect to. Wouldn’t you know I
bought the machine specifically to act as a debug target for WinDbg:(

I’ve sent an email to the WinDbg suggestion alias and hopefully
someone internally at Microsoft will have a suggestion.

Thanks again,
John

On Wed, 07 Aug 2002 16:17:43 -0400, John Hensley
wrote:

>
>
>Has anyone been able to get WinDbg to work with a Toshiba 5105 XP Pro
>laptop as the target? WinDbg won’t connect to this machine as a target
>using 1394 and the machine has no legacy COM ports. There doesn’t seem
>to be anything noticeably wrong with the 1394 drivers on the Toshiba
>because this machine works fine as the WinDbg host and connects via
>the 1394 cable to my development machine which has no problem being a
>1394 target. The Toshiba has no problem accessing other 1394 devices
>through this port. Both machines use the TI OHCI Compliant IEEE 1394
>host controller and both machines are using Microsoft ohci1394.sys
>driver version 5.1.2600.1079 (xpsp1.020717-1800) and both have the
>same settings in boot.ini.
>
>Are there any other options for debugging boot drivers on this machine
>if 1394 can’t be made to work?
>
>Thanks,
>John Hensley
>
>
>
>