Sorry to say but my Host machine 1394 host controller device is enumerated as "OHCI compliant IEEE 1394 host controller " . I believe this is the default driver as provided by Microsoft.
I confirmed on Target machine that 1394 bus driver is getting loaded and 1394 host controller device gets yellow mark stating is is hooked by kernel debugger.
Can anybody suggest me some way to test the firewire ports and wire. I have already changed two wires with no success.
Regards,
Pranav
The two laptops are :
Compaq Presarion M2208 and HP 6510 B
Please let m know if any 4 port card of specific manufacturer works fine. The one at OSR store is 6 Pin.
Thanks in advance.
Regards,
Pranav
xxxxx@gmail.com wrote:
Sorry to say but my Host machine 1394 host controller device is enumerated as "OHCI compliant IEEE 1394 host controller " . I believe this is the default driver as provided by Microsoft.
We didn’t ask about the driver. We asked about the manufacturer. If
nothing else, look at the PCI vendor ID in Device Manager.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
PCI vendor for Target machine : Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI vendor for Host machine : OHCI Compliant IEEE 1394 Host Controller, actually for host machine no specific vendor name is visible in registry or device manager.
Regards,
Pranav
You were asked for the VID/PID of the device. Look with device manager and
give us the ‘device IDs’. However, since the target is TI that is the best
1394 and what the kernel debugger in the OS was written specifically to use,
I don’t think that is your problem. I have used VIA and others on the host
and it usually works. Make sure your cable is good and of high quality.
Sometimes I have found that I need to unplug and replug the cable from the
target when the OS is looking for the host. The other sync options in
windbg don’t help with 1394 AFAIK. Ensure the 1394 controller is disabled
on the target system. I always do it and while it says it is not needed, I
find it just works better when I do it automatically. When installing XP
use the network manual setup and deselect all protocols for the 1394
controller(s) also. I use 1394 daily between a Dell notebook and systems
under test (SUT). I even sometimes use a Belkin 1394 hub and run multiple
debug sessions using multiple channels at the same time to multiple SUTs.
The Belkin hub is a little white box that retails at Fry’s for about $50
(USD). My Dell notebook has a VEN_1217&DEV_00F7&SUBSYS_01CC1028 1394
controller. It appears that is an O2Micro controller.
wrote in message news:xxxxx@windbg…
> PCI vendor for Target machine : Texas Instruments OHCI Compliant IEEE
> 1394 Host Controller
>
> PCI vendor for Host machine : OHCI Compliant IEEE 1394 Host Controller,
> actually for host machine no specific vendor name is visible in registry
> or device manager.
>
> Regards,
> Pranav
>
H/W details for Target machine : Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_104C&DEV_8032&SUBSYS_3080103C&REV_00\4&AD1B67F&0&4AF0
H/W details for Host machine : OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1180&DEV_0832&SUBSYS_30C0103C&REV_02\4&3B3A03B5&0&21F0
Both of the machines are win XP SP3.
Regards,
Pranav
xxxxx@gmail.com wrote:
H/W details for Target machine : Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_104C&DEV_8032&SUBSYS_3080103C&REV_00\4&AD1B67F&0&4AF0H/W details for Host machine : OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1180&DEV_0832&SUBSYS_30C0103C&REV_02\4&3B3A03B5&0&21F0
1180:0832 is part of a motherboard chipset by Ricoh.
I’m surprised you’re having trouble. The troublesome part tends to be
the target side, and TI controllers are known to be pretty good.
I’m out of ideas.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Hello All,
I am back again but with few more observations to the issue, any way thanks to all the kind responders.
I formatted both of the laptops with win XP SP2. Now too the state remains same. The TI machine i.e. the target is not sending anything to host , while Ricoh machine i.e. the host is “waiting to reconnect.”
I tried IEEE 1394 (PC to PC) connection , it works fine. When ever the cable is taken out of jacks it shows message “IEEE …is now connected” and vice versa while it is removed. But assigning static IP’s to TCP/IP in both connections and disabling firewall doesnt make Ping to each other success.
Does this mean that ports and cable are fine and working properly ?
Why i am unable to ping the machines from each other ?
Thanks in advance.
Regards,
Pranav
I’m out of ideas here. Assuming that you’ve correctly tried everything that has been suggested here, it sure seems like this would
have to be some sort of hardware issue, but I have no idea. Just to make sure:
I think that this has already been covered, but have you disabled the target’s 1394 controller? I don’t recall which version of
the OS introduced the feature of not having to disable it, but I feel like I’ve run across cases where I had to do so in order to
get a kd connection working, and I don’t think it would ever be a problem.
You have told the debugger to break in in some fashion?
Even though WinDbg is not breaking in, does the target still halt by any chance? That is, WinDbg doesn’t change, but the target
(including the mouse) is non-responsive? I’ve seen a relatively recent version of WinDbg (but I think you’re using the most
recent) do this under some circumstances.
I have no idea of how 1394 networking works.
Sorry I don’t have anything better,
mm
xxxxx@gmail.com wrote:
Hello All,
I am back again but with few more observations to the issue, any way thanks to all the kind responders.
I formatted both of the laptops with win XP SP2. Now too the state remains same. The TI machine i.e. the target is not sending anything to host , while Ricoh machine i.e. the host is “waiting to reconnect.”
I tried IEEE 1394 (PC to PC) connection , it works fine. When ever the cable is taken out of jacks it shows message “IEEE …is now connected” and vice versa while it is removed.
But assigning static IP’s to TCP/IP in both connections and disabling firewall doesnt make Ping to each other success.
Does this mean that ports and cable are fine and working properly ?
Why i am unable to ping the machines from each other ?Thanks in advance.
Regards,
Pranav
If you set both boxes to have static IPs on the same subnet on 1394 and you disabled all firewalls, and you still cannot ping, that’s a bad sign.
Can you try another cable, or perhaps a PC Card/ExpressCard 1394 adapter?
At this point, I would suspect hardware.
-----Original Message-----
From: xxxxx@gmail.com
Sent: Sunday, October 12, 2008 02:09
To: Kernel Debugging Interest List
Subject: RE:[windbg] 1394 Debug problem using WinXP SP3
Hello All,
I am back again but with few more observations to the issue, any way thanks to all the kind responders.
I formatted both of the laptops with win XP SP2. Now too the state remains same. The TI machine i.e. the target is not sending anything to host , while Ricoh machine i.e. the host is “waiting to reconnect.”
I tried IEEE 1394 (PC to PC) connection , it works fine. When ever the cable is taken out of jacks it shows message “IEEE …is now connected” and vice versa while it is removed. But assigning static IP’s to TCP/IP in both connections and disabling firewall doesnt make Ping to each other success.
Does this mean that ports and cable are fine and working properly ?
Why i am unable to ping the machines from each other ?
Thanks in advance.
Regards,
Pranav
—
You are currently subscribed to windbg as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Hi,
I tried PC to PC , connection again. The ping fails but the 1394 network “connect and disconnected” messages are displayed upon connecting and removing the firewire cable connection. Moreover there is packet transfer between the two connections as per connection status tab.
Can anybody confirm if there is still possibility of H/W failure ?
Is there any way through which firewire cable and cards can be checked ?
The latest discovery is that one port is loose so requires cable pluggin in special manner in order to make PC to PC connection success.
Thanks and regards,
Pranav
Well, if you can’t push data through enough to get a ping working over IP/1394, that’s not a good sign - that has always worked for me (before Microsoft decided to cut that feature, irritatingly enough, dropping one of the good means of actually verifying that 1394 was working and that you weren’t experiencing a KD-related problem).
You could try another 1394 adapter or cable. Do you have a third 1394-enabled computer that you could try connecting to with both computers in an attempt to narrow down the problem? If it doesn’t work with either, I would suspect the cable. Otherwise, you may have a hardware problem with the card of the box for which it doesn’t work with. If it still doesn’t work with either after replacing the cable, then something’s fishy. 
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Thursday, October 16, 2008 8:07 AM
To: Kernel Debugging Interest List
Subject: RE:[windbg] 1394 Debug problem using WinXP SP3
Hi,
I tried PC to PC , connection again. The ping fails but the 1394 network “connect and disconnected” messages are displayed upon connecting and removing the firewire cable connection. Moreover there is packet transfer between the two connections as per connection status tab.
Can anybody confirm if there is still possibility of H/W failure ?
Is there any way through which firewire cable and cards can be checked ?
The latest discovery is that one port is loose so requires cable pluggin in special manner in order to make PC to PC connection success.
Thanks and regards,
Pranav
You are currently subscribed to windbg as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com