Kernel Panic - TI JTAG Drivers

[Sébastien]

While installing drivers for the TI MSP-FET430UIF JTAG (USB device) I my system entirely locks up. I've tested under both XP and Vista with the latest Fusion and both do the same thing. I'm not sure how to go abouts getting a trace when I boot back up but if someone could show me how I can post those logs.

[vcam]

Same thing happens when loading driver for a TUSB3410 based usb-serial

cable both under windows xp and under linux in VM.

MacOS X (10.4.9) immidiately panics

(no driver is loaded under MacOS X, it doesn't even exist)

All this in Fusion beta3, plain VM, no bootcamp..

panic message copied from crash reporter:

panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:

CR0: 0x8001003b, CR2: 0xc0175d6b, CR3: 0x00d7b000, CR4: 0x000006e0

EAX: 0xc0175c7f, EBX: 0x0326cf00, ECX: 0x140dbc6f, EDX: 0xffff0f00

CR2: 0xc0175d6b, EBP: 0x140dbc88, ESI: 0x02666960, EDI: 0x00000004

EFL: 0x00010286, EIP: 0x00526db4, CS: 0x00000008, DS: 0x02630010

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x140dba58 : 0x128d08 (0x3cb134 0x140dba7c 0x131de5 0x0)

0x140dba98 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)

0x140dbba8 : 0x19ada4 (0x140dbbc0 0x202 0x140dbc18 0x1416ad)

0x140dbc88 : 0x52495d (0x326cf00 0x0 0x4 0x0)

0x140dbcf8 : 0x56de4b (0x326cf00 0x326cc00 0x2 0x1)

0x140dbd18 : 0x3b1c13 (0x326cc00 0x2 0x2fe888c 0x2fe8890)

0x140dbd68 : 0x18a0de (0x326cc00 0x2 0x3073ac4 0x1)

0x140dbdb8 : 0x12b4c3 (0x3073a9c 0x2fe8864 0x0 0x0)

0x140dbdf8 : 0x124b17 (0x3073a00 0x0 0x30 0x140dbedc)

0x140dbf08 : 0x195a42 (0x140dbf44 0x0 0x0 0x0)

0x140dbfc8 : 0x19b21e (0x2bd6760 0x1 0x19ac2b 0x2bd6760) No mapping exists for frame pointer

Backtrace terminated-invalid frame pointer 0xbfffef38

Kernel loadable modules in backtrace (with dependencies):

com.apple.iokit.IOUSBUserClient(2.7.0)@0x56c000

dependency: com.apple.iokit.IOUSBFamily(2.6.5)@0x517000

com.apple.iokit.IOUSBFamily(2.6.5)@0x517000

Kernel version:

Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386

Model: MacBook2,1, BootROM MB21.00A5.B00, 2 processors, Intel Core 2 Duo, 2 GHz, 1 GB

Graphics: Intel GMA 950, GMA 950, Built-In, spdisplays_integrated_vram

Memory Module: BANK 0/DIMM0, 512 MB, DDR2 SDRAM, 667 MHz

Memory Module: BANK 1/DIMM1, 512 MB, DDR2 SDRAM, 667 MHz

AirPort: AirPort Extreme, 1.0.47

Bluetooth: Version 1.7.14f14, 2 service, 0 devices, 1 incoming serial ports

Network Service: Built-in Ethernet, Ethernet, en0

Network Service: Built-in FireWire, FireWire, fw0

Serial ATA Device: TOSHIBA MK1234GSX, 111.79 GB

Parallel ATA Device: MATSHITADVD-R UJ-857D

USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA

USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA

USB Device: TUSB3410 Boot Device, Texas Instruments, Up to 12 Mb/sec, 500 mA

USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA

USB Device: PS/2+USB Mouse, A4Tech, Up to 1.5 Mb/sec, 500 mA

USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA

[Pat_Lee]

Can you both please file service requests on this issue. See the note at the top of the forum on how to file a service request.

Thanks,

Pat

[vcam]

Ok filed service request..

Also forgot to mention

same crash happens when using latest Parallels

(tried a couple of weeks ago).

However everything is ok when running windows xp natively using bootcamp..

And chip used in TI JTAG is the same ie. TUSB3410

Thanks

[Sébastien]

I also have had the same crash with Parallels, though with parallels I couldn't even boot back into the mac after the crash. I had to use the target firewire firmware option and removed the kernel drivers they keep in the /Applications/Parallels (sigh).

Hopefully it gets fixed though, it's the only thing I need windows for!

[vcam]

Any progress on this issue ?

best regards

[jvboone]

I would like to add my voice to the chorus. I have used both VMWare Beta 4 and Parallels 2.5/3.0 and observed this crash when connecting my Texas Instruments eZ430-F2013 development device via USB. The interface IC on the board is a USB-to-serial device: TI TUSB3410. When I plug this device into the MBP \*without* any virtual machine running, the system is fine (although it doesn't do anything with the device as far as I can tell). When I plug the device in while Fusion is running my Boot Camp partition, I get an almost instantaneous (<1 sec) MacOSX kernel crash. See the attached panic.log. The "Jun 10 08:20:29 2007" crash is when Parallels 3.0 was running (same circumstance). The "Jun 10 10:17:33 2007" crash is when VMWare Fusion Beta 4 was running.

Thanks.

[Faceless_User]

I would like to add that today I as well attempted to do some development on the MSP chip with my TI MSP-FET430UIF JTAG adapter and caused a hard crash on my system. This is terrible. This should be looked into.

[Panu]

I have reported this issue to VMWare in April and also filed a support request, but after initial reply I have not heard anything about the status of the bug fix even after emailing directly to support team with filed request number.

It would be nice if someone from VMWare could inform us about the plans of getting this fixed.

[admin]

What's the SR number so I can follow up? Does this happen just by installing drivers, or would we need the hardware to reproduce it? Do you have access to other VMware products, and if so, could you see if this happens on them as well?

[Panu]

Support request number is 186777459.

Installing the drivers is not enough to reproduce the bug, you have to plug in a device. The device of my configuration is Texas Instruments MSP430 USB Debug interface MSP-FET430 UIF, but I guess any device with TUSB3410 chip would do like the one which jvboone describes.

There was a period of time when OS X did not crash every time if the device was connected to virtual machine before booting the Windows, but now the crash seems to happen when ever drivers are loaded and device is connected.

Unfortunately I don't currently have access to other VMWare products.

[admin]

Thanks, I've poked the developers. They'll probably want logs/backtraces/panic.log from the GA build.

Edit: Initial developer reaction is that this isn't global amongst TUSB3410 devices, since a Keyspan USA-19HS has that and works. What version of OS X are people seeing this with? -etung 2007.09.04 18:16

[Panu]

I'll be glad to help you to solve the issue by providing necessary information or testing intermediate builds. I have used only OS X version 10.4.10 with the release version of Fusion, but crashing has occurred also with 10.4.8 and 10.4.9 with Fusion betas and Release candidates.

OK, it is not global TUSB3410 problem. FET-tool appears as two devices in Windows and needs two sets of drivers. Both drivers must be installed and device connected to get kernel panic. I have sent USB probe description of the device with bug report.

[chemoki]

Has this problem been solved?

[Bob_Zimmerman]

I know I'm kind of late to the party, but I wanted to post to let everybody know that I have been able to get a TI ez430 USB debugger to work with Windows xp under Fusion 2.0.1. I'm using version 1.2.11.3 of the MSP-FET430UIF serial port driver and the JTAG tool. Occasionally, Windows says that the JTAG portion didn't initialize successfully. Unplugging and replugging the ez430 fixes that.

I am able to build code for it, send the code to the device, and step debug it. So far, it appears that everything works. Again, here's my environment:

Mac OS 10.5.5 host

Late 2008 MacBook Pro, 2.53 GHz Core 2 Duo, 4 GB of RAM

VMware Fusion 2.0.1

Windows xp SP1 guest

[epirali]

FWIW with Fusion 2.01 on MacOS X 10.5.6 and a XDS510 Plus USB driver I am now getting kernel panics on establishing connection to the device (used to work in pre 10.5.6 and/or 2.0).

Is this a known bug?

[admin]

We've heard about some USB/10.5.6 panics and tentative investigation suggests it's an OS X bug, but we're not sure yet. panic.log would be useful.

[epirali]

Attached is the kernel panic log.

[troll]

I posted a related problem under 1149209. There are two additional panic logs. Has there been any more insight into this problem?[m-1149209]