I have been using 1394 as the debug connection on the target system for quite some time.
Recently my debug system died and I am interested in switching to a laptop.
I was forced to purchase a new 4-6 1394 cable for the laptop because I previously used a 6-6 1394 cable between two tower systems.
I plugged the cable into the 1394 port on the laptop and the target system.
I started up the x64 version of WinDbg and attempted to connect.
I saw this:
Wrote 0 of 1 bytes of the breakin packet.
Failed to write breakin packet to target. Win32 error 0n2
WARNING: The HOST cannot communicate with the TARGET!
Wrote 0 of 1 bytes of the breakin packet.
Failed to write breakin packet to target. Win32 error 0n2
WARNING: The HOST cannot communicate with the TARGET!
Is this merely a confirmation that my new cable is bad?
I checked the 1394 settings on the target system and it seems to be fine.
Is there something else obvious that I may have missed?
I have been using 1394 as the debug connection on the target system for
quite some time.
Recently my debug system died and I am interested in switching to a laptop.
I was forced to purchase a new 4-6 1394 cable for the laptop because I
previously used a 6-6 1394 cable between two tower systems.
I plugged the cable into the 1394 port on the laptop and the target system.
I started up the x64 version of WinDbg and attempted to connect.
I saw this:
Wrote 0 of 1 bytes of the breakin packet.
Failed to write breakin packet to target. Win32 error 0n2
WARNING: The HOST cannot communicate with the TARGET!
Wrote 0 of 1 bytes of the breakin packet.
Failed to write breakin packet to target. Win32 error 0n2
WARNING: The HOST cannot communicate with the TARGET!
Is this merely a confirmation that my new cable is bad?
I checked the 1394 settings on the target system and it seems to be fine.
Is there something else obvious that I may have missed?
Here is a little more information about the laptop I am using.
It is a Lenovo T410 ThinkPad.
According to the Computer Management panel there is a Ricoh 1394 OHCI compliant host controller and a 1394 Windows Debug Driver installed on that.
I may have upgraded WinDbg while installing software on the new system. I thought I was just installing the same version of the WDK (7600.16385.1). I believe that I was using the x86 version on the older system and I am using x64 now. Since the old system is dead, I really can’t check much else about the software.
There is only one 1394 port on each device. I simply selected 0 as the channel number within WinDbg.
I may have upgraded WinDbg while installing software on the new system. I
thought I was just installing the same version of the WDK (7600.16385.1). I
believe that I was using the x86 version on the older system and I am using
x64 now. Since the old system is dead, I really can’t check much else about
the software.
There is only one 1394 port on each device. I simply selected 0 as the
channel number within WinDbg.
When I checked the dbgsettings in bcdedit on the target, it only shows 1394 and I don’t see a channel. I will go back and see if there was more information available with additional parameters.
When I checked the dbgsettings in bcdedit on the target, it only shows 1394
and I don’t see a channel. I will go back and see if there was more
information available with additional parameters.
On my Dell, it would not work with the Ricoh 1394 OHCI. By the way, to
de-confuse MM, I’ve assumed that you are switching out the HOST, and that it
is the HOST that is not working.
Here is a little more information about the laptop I am using.
It is a Lenovo T410 ThinkPad.
According to the Computer Management panel there is a Ricoh 1394 OHCI
compliant host controller and a 1394 Windows Debug Driver installed on that.
