1394 debug from a Vista host

NTDEV
1

Hi all,

I am trying to set up a debugging session from a Vista machine. I run WinDbg and use the kernel debug option, but the system says that it cannot install the 1394 drivers needed to connect to the target machine.

My host PC uses a 1394 chip from Ricoh and the target machine has a PCI to 1394 adapter that uses a chip from Agere.

Any help would be extremely wellcomed.

Thanks in advance,

Eugenio Barahona Marciel

2

Did you start WinDbg using “Run As Administrator,” or disable UAC in Group Policy (GPEdit.MSC)? It sounds like you need to do one of two.
While you provided excellent information about the 1394 Chipsets, which most people don’t, your host chipset should not matter, as it is using the adapter as any application would. You are very correct that on the target, certain 1394 chipsets can and not uncommonly do cause problems (I don’t know about Agere; those from TI are the ones that almost always work, but most others work these days as well, in my experience), but this wouldn’t account for the particular problem which you are having.

Good luck,

mm

3

I did not have any Windbg problems with my Vista host, it ran smoothly from
start. I found that some target machines, both Vista and XP, are sensitive
to which 1394 chip they’re running, so I finally had our IT guys only buy
Belkin boards with TI chips, and that seems to solve the problem.

Alberto.

----- Original Message -----
From:
To: “Windows System Software Devs Interest List”
Sent: Sunday, September 16, 2007 4:24 AM
Subject: [ntdev] 1394 debug from a Vista host

> Hi all,
>
> I am trying to set up a debugging session from a Vista machine. I run
> WinDbg and use the kernel debug option, but the system says that it cannot
> install the 1394 drivers needed to connect to the target machine.
>
> My host PC uses a 1394 chip from Ricoh and the target machine has a PCI to
> 1394 adapter that uses a chip from Agere.
>
> Any help would be extremely wellcomed.
>
> Thanks in advance,
>
> Eugenio Barahona Marciel
>
> —
> NTDEV 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

4

“Run as Administrator” solved the problem on the host machine, but WinDbg waits forever to connect to the target XP machine (Agere PCI to 1394 adapter board). I will get a 1394 board with a TI chip and try again.

Thanks a lot for your help.

Eugenio Barahona Marciel

5

When you say that it takes forever to connect, does that mean that WinDbg doesn’t connect, but the target still halts? If so, this is probably caused by one of the following:

  1. starting WinDbg with -b
  2. starting WinDbg with -d
  3. adding halbreakpoint to the target with bcdedit; as you are trying to connect to an XP machine, the equivalent would be adding “/BREAK” to the boot.ini, but I don’t know if this item affects XP machines or not.
  • or -
  1. you done none of the above, and failed to either press “ctrl+break,” or take “Break” from the “Debug” menu.

The first three issues are specific to the two most recent version of WinDbg (6.7.5.0 & 6.7.5.1, I believe); the last is just the way it works.

If it’s none of these, it may be the chipset. Try a 1394 card based on a TI chipset.

Good luck,

mm