Multiple computers available on 1394 connection?
Alan Adams
multiple computers? Right now I always end up running WinDBG on my
laptop which only as a single 1394 connection anyway, and I just
physically move the 1394 cable to whichever computer out of my rack
that I'm debugging.
But if I had multiple 1394 ports on my host computer, would I be able
to setup and leave "all computers connected" (physical cable to each
target, plugged into single controller on host), and then just select
which target I want via configured channel number? (Possibly even
running two different WinDBG instances concurrently, each connected to
a different 1394-based target.)
I didn't see any explicit acknowledgement of such a configuration in
the WinDBG documentation, and just wondered whether it was common
knowledge or someone had such a configuration working. Maybe I'm even
supposed to be able to achieve this with the single port on my host,
given that I see 1394 "hubs" just like you see for USB.
Could be it's a simple question and I'm just guilty of not paying
attention. Thanks for any information in the right direction.
-Alan
Alan Adams
Jeffrey Tan[MSFT]
I will try to do some internal consulting for this issue, I will update you
ASAP. Thanks
Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Jeffrey Tan[MSFT]
Sorry for letting you wait for so long.
Yes, we can have multiple target computers attached to a single host for
1394 kd.
Based on the feedback from our product team, the limitation for the
connection is 63, however, we recommanded you use no more than 20
connections. The problem that we may run into is that any single problem on
the 1394 bus can take down the entire bus and the likelihood of this
happening increases with more target systems.
Yes, we can use a hub to have all of the systems connected at once, just
make sure that he specifies a unique channel number per target. Also, we'd
recommend that he keeps the 1394 topology as flat as possible 每 plug all
targets into a hub, which plugs into a laptop 每 instead of daisy-chaining
the 1394 targets (which should also work, but this configuration has a
tendency to cause problems).
Hope this information helps
Alan Adams
configuration and won't have to move cables around any more.
Just for the clarity of anyone wishing to use such a configuration,
was there any particular mention of whether you should expect to be
actively debugging more than one target at the same time from the
host?
i.e. The previous information is more or less in line with
capabilities of 1394 itself. But the question of "should I be able to
debug more than one target at the same time from the host" is more a
question of software design of the 1394 driver for WinDBG. i.e. Can I
have one instance of WinDBG debugging the target on channel 22, and
another instance on WinDBG debugging the target on channel 25, at the
same time from the same host.
Obviously I'll try it as soon as I have the configuration; just
wondering whether it's already a known design that "no, the debug
driver for 1394 can only handle a single target at a time". Thanks.
Alan Adams
Jeffrey Tan[MSFT]
Thanks for your feedback.
I am not sure I understand your problem key point very well. For 1394
connections, I think I have provided the information in the last reply. I
am not sure what your current concern is.
Yes, I think we can run multiple Windbg instances at the same time on the
host machine, while each windbg instance connects to different target
machine once the channel is different. For example, we can use one windbg
instance to use COM1 port to one target, while another instance use another
connection to another target.
If you have any other concern, please feel free to clarify for me. Thanks
Alan Adams
running? I finally got around to picking up a 1394 hub for the
purpose of WinDBG, but I'm not having success as of yet.
When I have a direct cable between two 1394 controllers, the Windows
machines detect each other and install the "1394 PC" device. (Until,
of course, I disable the 1394 controller on the target & the 1394
virtual network adapter on the host.)
With the hub in between the two computers, they never see each other
in this manner. (Nor does making a 1394 connection via WinDBG work
after setting everything up as I would for successfully using a direct
cable.)
Plugging in a 1394 device to the hub (such as one of my 1394 hard
drives) is detected and used successfully by the host computer. So
the hub configuration would appear to be "working". The
computer-to-computer connection does not appear to work through the
hub, and nor does the WinDBG connection.
The hub I selected was IOGEAR model GFH610, for being powered & having
six ports (and not seeing other selection criteria that needed
consideration).
If anyone can share the equipment involved in a successful hub-based
WinDBG configuration, or if Microsoft can share any additional
information on what it would take for a successful WinDBG or
computer-to-computer 1394 connection via a hub, the information would
be appreciated. Thanks.
v-j...@online.microsoft.com ("Jeffrey Tan[MSFT]") wrote:
Alan Adams
Alan Adams
using in my tests does not have success when plugged into the hub, and
kept everything from working when plugged in along with other targets.
With that machine removed, I've having exactly the experience
expected: My host laptop with a single 1394 port plugs into the hub,
and the hub in turn is plugged into three different target machines.
After assigning unique channel numbers to each target, I currently
have three different WinDBG instances running on the host machine
concurrently, each debugging a different target machine over 1394.
Alan Adams <alan...@nospam.nospam> wrote:
Alan Adams