Reboot from trying to install TI USB development device

[billsalt]

I sent this on to support, but thought I'd post it here in case anyone had a work-around I had missed.
-----------------------------
I'm running RC3 (3170), and first of all I want to say that I love it! You've done a fantastic job!

I have, however, found a way to kill the machine (I was pleasantly surprised it got as far as it did, I have to admit):

- Using a TI EZ-430 development kit (a USB dongle with a USB/Serial interface chip)
(http://focus.ti.com/docs/toolsw/folders/print/ez430-f2013.html)

- Installed the software (downloadable from TI)
- plug in the USB device
- on the Parallels bar, select Devices/USB/MSP-FET430UIF JTAG Tool
- Windows correctly starts the install process
- point the device installer to the disc copy of the drivers
- drivers start to install for the MSP-FET430UIF (TI USB FET) Adapter
- while installing umpf3410.i51 to C\WINDOWS\system32\drivers, the progress bar gets all the way to completion, then the entire screen wipes and gives the lovely multi-lingual "you need to restart your computer"...


As I said, I was surprised it got this far, but now I have something to ask for! You guys are doing too good of a job!

 

[nall]

I just got the same thing. I'm using build 3188. Windows mentions the driver for the device "is not Windows Logo compatible". Does this matter? Also, a stack trace is generated on reboot. Will this help the developers resolve this issue?

I'd really like to hear if there is any chance of getting this fixed or if a workaround is available.

 

[md2020]

I have experienced the same problem on my XP sp2 install. I'm using build 3188 as well. Just for kicks I tried the beta from vmware, and got the same type of crash/reboot when installing the driver.


-mike

 

[md2020]

FWIW, here is what OSX wants to report after trying to install the USB stick throws a kernel panic.

panic(cpu 0 caller 0x003BCADE): OSString::_RESERVEDOSString12 called

Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x25a43bc8 : 0x128d08 (0x3cb134 0x25a43bec 0x131de5 0x0) 
0x25a43c08 : 0x3bcade (0x3f0dd8 0x3ef63c 0x3ef63c 0xc) 
0x25a43c28 : 0x3c4d28 (0x4aea48 0xc 0x25a43c88 0x6dfe400) 
0x25a43c48 : 0x3bd11dba (0x4a3d4e0 0x2 0x25a43c6f 0x3bd0f6e4) 
0x25a43c88 : 0x3bd0f95d (0x6dfe400 0x0 0x4 0x0) 
0x25a43cf8 : 0x42588e4b (0x6dfe400 0x5175200 0x2 0x1) 
0x25a43d18 : 0x3b1c13 (0x5175200 0x2 0x62c9d8c 0x62c9d90) 
0x25a43d68 : 0x18a0de (0x5175200 0x2 0x634c0c4 0x1) 
0x25a43db8 : 0x12b4c3 (0x634c09c 0x62c9d64 0x0 0x0) 
0x25a43df8 : 0x124b17 (0x634c000 0x0 0x30 0x25a43edc) 
0x25a43f08 : 0x195a42 (0x25a43f44 0x0 0x0 0x0) 
0x25a43fc8 : 0x19b21e (0x411c404 0x1 0x19ac2b 0x411c404) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb091cb28
      Kernel loadable modules in backtrace (with dependencies):
         com.apple.iokit.IOUSBUserClient(2.7.0)@0x42587000
            dependency: com.apple.iokit.IOUSBFamily(2.6.5)@0x3bd02000
         com.apple.iokit.IOUSBFamily(2.6.5)@0x3bd02000

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: MacBookPro1,1, BootROM MBP11.0055.B08, 2 processors, Intel Core Duo, 1.83 GHz, 2 GB
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 128 MB
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x86), 0.1.31.1
Bluetooth: Version 1.7.14f14, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Network Service: Parallels Host-Guest, Ethernet, en2
Network Service: Parallels NAT, Ethernet, en3
Serial ATA Device: FUJITSU MHV2080BH, 74.53 GB
Parallel ATA Device: MATSHITADVD-R   UJ-857, 52.06 MB
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: Keyspan USA-28X, Keyspan, a division of InnoSys Inc., Up to 12 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA
USB Device: MSP-FET430UIF JTAG Tool, Texas Instruments, Up to 12 Mb/sec, 500 mA

 

[gumse]

W2000 & W-XP, Parallels and VMWare

I have the same problem, wich is a pity, embedded development is the only thing that's keeping a Windows box up and running at my desk.

W2000 or XP , Parallels or VMWare, the same kernel panic comes every time i try to install the USB-drivers.

 

[Eru Ithildur]

Why are you installing USB Drivers on your VM? If you need custom drivers you probably need BootCamp. Parallels HAS drivers for you that come with the tools.

 

[md2020]

Why are you installing USB Drivers on your VM? If you need custom drivers you probably need BootCamp. Parallels HAS drivers for you that come with the tools.

Are you saying that we should not expect Parallels to support any USB device that has no OSX drivers available? That sounds fairly lame, but considering that vmware exhibits the same behavior under the same circumstances it sounds like it just may be the case.

I think I'm going to reinstall the vmware beta, reproduce the error, and query their support/development infrastructure (whatever they have available) and see if I can get a straight answer from them. So far my communication with the parallels "team" about this issue has been rather one-sided.

 

[doggkruse]

I've reported this problem with each beta release to Parallels. Same problem either with the small usb fet or the regular ti j-tag tool. A J-Link from Segger ($250) works just fine however.

 

[Eru Ithildur]

Are you saying that we should not expect Parallels to support any USB device that has no OSX drivers available? That sounds fairly lame, but considering that vmware exhibits the same behavior under the same circumstances it sounds like it just may be the case.

Not quite. If the USB device requires a SPECIFIC driver then it is a maybe maybe not. Typically if you are getting into custom drivers don't expect it work. If it does, great, if it doesn't then it sucks. Parallels supports most of the built-in Windows drivers, if not all.

 

[Jisi]

A J-Link from Segger ($250) works just fine however.

Hi, did you use some "special" trick to achieve this? I am also using a J-Link inside Paralles, but it is dog slow (getting around 800bytes/Sec throughput), and sometimes during debugging the driver "looses" the J-Link, i.e. the JLink Firmware crashes with JLink DLL spitting out messages like

EMU_GetFirmwareString: J-Link reports unsupported firmware string size of 19501 (expected 112) Could not identify firmaware (Read failure) Can not connect to J-Link via USB

In this case only physically disconnecting the JLInk from USB helps.

Any ideas?

 

[odin]

MSP430 Dev Kit USB Panic

Same issue here - I was able to install the TI USB drivers within Parallels, but when I connect the FET kit USB dongle and then attach it under Devices>USB I get an immediate and reproduceable panic.

FET Kit works fine under BootCamp.

Keyspan USB serial port does work without issues within Parallels.

MacBook Pro 2GB/ 10.4.9 Parallels build 3188 = WinXP Pro

 

[jvboone]

TI eZ430-F2013 USB device MacOSX kernel panic -- me too.

I would like to add my voice to the chorus. I have used both Parallels 2.5/3.0 and VMWare Beta 4 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 Parallels or Fusion are running my Boot Camp partition, I get an almost instantaneous (<1 sec) MacOSX kernel crash. See the attached panic.log. The May 3 and "Jun 10 08:20:29 2007" crashes are from when Parallels 3.0 was running (same circumstance). The "Jun 10 10:17:33 2007" crash is from when VMWare Fusion Beta 4 was running.

Thanks.