1394 Debugging - So Close - Need Help

I've set up my host and target machines for 1394 debugging. I have the
virtual 1394 device drivers installed on the host machine and am able to
connect to the target machine to begin the debug session. Right after the
target's 1394 host controller loads, the debugging connection is lost. When
I check the target's hardware properties, the 1394 host controller is whacked.
I've read the documentation that warns to disable the target 1394 host
controller before debugging with the caution "Be careful not to accidently
disable the 1394 net adapter instead". The problem is, when I disable the
1394 host controller on the target, the 1394 net adapter disappears from the
listing and thereby not allowing a debug connect at all.
Any help would be greatly appreciated.

Don
Fri Feb 02 18:42:34 CST 2007

Disable all the 1394 drivers on the target. The statement "Be careful not
to accidently disable the 1394 net adapter instead".is to warn you not to
think disabling the net adapter is enough, yes you will disable the net
adapter when you disable the host controller driver.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply



"hypervista@newsgroups.nospam"
<hypervistanewsgroupsnospam@discussions.microsoft.com> wrote in message
news:8B943A30-B4A2-483D-BCEF-0A39A9081608@microsoft.com...
> I've set up my host and target machines for 1394 debugging. I have the
> virtual 1394 device drivers installed on the host machine and am able to
> connect to the target machine to begin the debug session. Right after
> the
> target's 1394 host controller loads, the debugging connection is lost.
> When
> I check the target's hardware properties, the 1394 host controller is
> whacked.
> I've read the documentation that warns to disable the target 1394 host
> controller before debugging with the caution "Be careful not to
> accidently
> disable the 1394 net adapter instead". The problem is, when I disable
> the
> 1394 host controller on the target, the 1394 net adapter disappears from
> the
> listing and thereby not allowing a debug connect at all.
> Any help would be greatly appreciated.

Pavel
Fri Feb 02 18:39:36 CST 2007

The 1394 Network adapter is not relevant to debugging, just ignore it.
If the 1394 host controller on target is disabled and you still can't connect, this
might be because of something else.
--PA



"hypervista@newsgroups.nospam" <hypervistanewsgroupsnospam@discussions.microsoft.com> wrote in message
news:8B943A30-B4A2-483D-BCEF-0A39A9081608@microsoft.com...
> I've set up my host and target machines for 1394 debugging. I have the
> virtual 1394 device drivers installed on the host machine and am able to
> connect to the target machine to begin the debug session. Right after the
> target's 1394 host controller loads, the debugging connection is lost. When
> I check the target's hardware properties, the 1394 host controller is whacked.
> I've read the documentation that warns to disable the target 1394 host
> controller before debugging with the caution "Be careful not to accidently
> disable the 1394 net adapter instead". The problem is, when I disable the
> 1394 host controller on the target, the 1394 net adapter disappears from the
> listing and thereby not allowing a debug connect at all.
> Any help would be greatly appreciated.

hypervistanewsgroupsnospam
Fri Feb 02 20:16:00 CST 2007

Thanks Don! That got it working. I appreciate the help very much!

"Don Burn" wrote:

> Disable all the 1394 drivers on the target. The statement "Be careful not
> to accidently disable the 1394 net adapter instead".is to warn you not to
> think disabling the net adapter is enough, yes you will disable the net
> adapter when you disable the host controller driver.
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> http://www.windrvr.com
> Remove StopSpam from the email to reply
>
>
>
> "hypervista@newsgroups.nospam"
> <hypervistanewsgroupsnospam@discussions.microsoft.com> wrote in message
> news:8B943A30-B4A2-483D-BCEF-0A39A9081608@microsoft.com...
> > I've set up my host and target machines for 1394 debugging. I have the
> > virtual 1394 device drivers installed on the host machine and am able to
> > connect to the target machine to begin the debug session. Right after
> > the
> > target's 1394 host controller loads, the debugging connection is lost.
> > When
> > I check the target's hardware properties, the 1394 host controller is
> > whacked.
> > I've read the documentation that warns to disable the target 1394 host
> > controller before debugging with the caution "Be careful not to
> > accidently
> > disable the 1394 net adapter instead". The problem is, when I disable
> > the
> > 1394 host controller on the target, the 1394 net adapter disappears from
> > the
> > listing and thereby not allowing a debug connect at all.
> > Any help would be greatly appreciated.
>
>
>

hypervistanewsgroupsnospam
Fri Feb 02 22:15:01 CST 2007

Thank you Pavel. I'm acting on your advice to move away from VMWare based
testing and test my assembly language routines driver on real hardware. I've
got the 1394 debug working (some of the language in the documentation
confused me a bit). Now I have to see if my code works on a "real machine".


"Pavel A." wrote:

> The 1394 Network adapter is not relevant to debugging, just ignore it.
> If the 1394 host controller on target is disabled and you still can't connect, this
> might be because of something else.
> --PA
>
>
>
> "hypervista@newsgroups.nospam" <hypervistanewsgroupsnospam@discussions.microsoft.com> wrote in message
> news:8B943A30-B4A2-483D-BCEF-0A39A9081608@microsoft.com...
> > I've set up my host and target machines for 1394 debugging. I have the
> > virtual 1394 device drivers installed on the host machine and am able to
> > connect to the target machine to begin the debug session. Right after the
> > target's 1394 host controller loads, the debugging connection is lost. When
> > I check the target's hardware properties, the 1394 host controller is whacked.
> > I've read the documentation that warns to disable the target 1394 host
> > controller before debugging with the caution "Be careful not to accidently
> > disable the 1394 net adapter instead". The problem is, when I disable the
> > 1394 host controller on the target, the 1394 net adapter disappears from the
> > listing and thereby not allowing a debug connect at all.
> > Any help would be greatly appreciated.
>
>
>

hypervistanewsgroupsnospam
Fri Feb 02 22:34:01 CST 2007

Pavel - you were absolutely correct! My code is giving the correct results
on a real machine. It seems VMWare was handling low-level calls in a manner
that enables it to continue virtualization, but was providing my code
incorrect values in one of the registers. Thank you so much for your help.
Now I can move forward.

"Pavel A." wrote:

> The 1394 Network adapter is not relevant to debugging, just ignore it.
> If the 1394 host controller on target is disabled and you still can't connect, this
> might be because of something else.
> --PA
>
>
>
> "hypervista@newsgroups.nospam" <hypervistanewsgroupsnospam@discussions.microsoft.com> wrote in message
> news:8B943A30-B4A2-483D-BCEF-0A39A9081608@microsoft.com...
> > I've set up my host and target machines for 1394 debugging. I have the
> > virtual 1394 device drivers installed on the host machine and am able to
> > connect to the target machine to begin the debug session. Right after the
> > target's 1394 host controller loads, the debugging connection is lost. When
> > I check the target's hardware properties, the 1394 host controller is whacked.
> > I've read the documentation that warns to disable the target 1394 host
> > controller before debugging with the caution "Be careful not to accidently
> > disable the 1394 net adapter instead". The problem is, when I disable the
> > 1394 host controller on the target, the 1394 net adapter disappears from the
> > listing and thereby not allowing a debug connect at all.
> > Any help would be greatly appreciated.
>
>
>