Hello,
It’s possible that WinDbg does not support debugging over FireWire 800?
I have tried to connect a new MacBook Pro with Windows XP installed.
It’s not possible to get a working connection. I have tried on several Firewire channels and on tree different host computers (with an old and the newest version of WinDbg).
WinDbg output on the host:
Using 1394 for debugging
Checking 1394 debug driver version.
Opened \.\DBG1394_CHANNEL10
Timer Resolution set to 1003 usec.
Waiting to reconnect…
Another very strange thing:
If I reboot the host with the connected cable the Firewire port is not working on the host. WinDbg can not find the Firewire port. If then I disconnect and reconnect the cable it will find the port in WinDbg.
I use a Firewire Kabel 800 IEEE-1394b 9pin/6pin 1,8m.
I have tried to connect this cable on a 6pin Firewire port and on a 4pin Firewire port with 6 to 4 Pin Firewire
michi
When I add a Firewire ExpressCard/34 (6 Pin port) on the target computer (in my case the macbook pro), how can I force the target computer to use the firewire port of the ExpressCard for the debug connection?
/busparams=Bus.Device.Function
http://www.eggheadcafe.com/software/aspnet/31073603/1394-debugging-issues-ta.aspx
xxxxx@hotmail.com wrote:
When I add a Firewire ExpressCard/34 (6 Pin port) on the target computer (in my case the macbook pro), how can I force the target computer to use the firewire port of the ExpressCard for the debug connection?
Which firewire chipset does your MacBookPro have? LSI (FW643) or Ti?
/Uwe
xxxxx@hotmail.com schrieb:
Hello,
It’s possible that WinDbg does not support debugging over FireWire 800?
IEEE 1394 Bus-Hostcontroller
IEEE 1394 OHCI-konformer Hostcontroller-Hersteller
PCI-Bus 5, Ger?t 0, Funktion 0
PCI\VEN_11C1&DEV_5901&SUBSYS_590011C1&REV_06\4&24867FF7&0&00B0
http://www.pcidatabase.com/search.php?device_search_str=5901&device_search=Search
Device Id: 0x5901
Chip Description: firewire chip for macbook pro
Vendor Id: 0x11C1
Vendor Name: Agere Systems, Inc.
michi
So LSI since they bought Agere. Unfortunately, TI is the good chipset.
–
Don Burn (MVP, Windows DDK)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
wrote in message news:xxxxx@ntdev…
IEEE 1394 Bus-Hostcontroller
IEEE 1394 OHCI-konformer Hostcontroller-Hersteller
PCI-Bus 5, Gerät 0, Funktion 0
PCI\VEN_11C1&DEV_5901&SUBSYS_590011C1&REV_06\4&24867FF7&0&00B0
http://www.pcidatabase.com/search.php?device_search_str=5901&device_search=Search
Device Id: 0x5901
Chip Description: firewire chip for macbook pro
Vendor Id: 0x11C1
Vendor Name: Agere Systems, Inc.
michi
Information from ESET NOD32 Antivirus, version of virus signature
database 3930 (20090312)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Information from ESET NOD32 Antivirus, version of virus signature database 3930 (20090312)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
so I have to buy use a Firewire ExpressCard with TI chipset … has someone tested if the Firewire Express card works with WinDbg? (/busparams=Bus.Device.Function)
Your are using an outdated chip revision of the lsi chip.
From my experince I would suggest using at least Rev 7 of this chip.
/Uwe
xxxxx@hotmail.com schrieb:
IEEE 1394 Bus-Hostcontroller
IEEE 1394 OHCI-konformer Hostcontroller-Hersteller
PCI-Bus 5, Gerät 0, Funktion 0
PCI\VEN_11C1&DEV_5901&SUBSYS_590011C1&REV_06\4&24867FF7&0&00B0
http://www.pcidatabase.com/search.php?device_search_str=5901&device_search=Search
Device Id: 0x5901
Chip Description: firewire chip for macbook pro
Vendor Id: 0x11C1
Vendor Name: Agere Systems, Inc.
michi
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
Well, no. But, in general, some 1394 chip sets work better than others. Not just in WinDbg, but in general.
Peter
OSR
Now I have tried to use the MacBook Pro as host and not as target and the debugging works over firewire… but no way to get the MacBook pro to work as target :-/
michi
@Uwe Kirst
using another chip is not so easy, it is in on the MacBook board. This Macbook is from 2009 … bad that apple use old chips on new products.
At least (as I have written before) I can try a firewire express card …
Now I have installed a firewire express card and it works.
The problem was the Firewire 800 chip in the MacBook.
The only special thing to do is setting the boot parameter “/busparams=Bus.Device.Function” in the boot.ini
In my case the boot parameter are: /debug /debugport=1394 /channel=1 /busparams=14.0.0
(the numbers for the busparams we get from Firewire Device in the Device Manager)
The firewire express card is a “DeLock 61387”:
Texas Instruments IEEE 1394 Bus-Hostcontroller
PCI\VEN_104C&DEV_8235&SUBSYS_12345678&REV_01\5&3AE297C4&0&0000B8
The lsi/lucent/agere chip is not really old, but it doesn seen to work
in many applications.
For example the “target disk mode” (use the computer like a firewire
harddisk) also doesnt seem to work.
My driver uses the 1394 stack from microsoft but also doesn’t work with
this chip.
We are complaining about this to apple for over a year now.
It’s also used in other models, first in the iMac.
/Uwe
xxxxx@hotmail.com schrieb:
@Uwe Kirst
using another chip is not so easy, it is in on the MacBook board. This Macbook is from 2009 … bad that apple use old chips on new products.