Hi all,
don't know if you have any idea on how to improve this.
I have a DualSIM phone (android) and I'm trying to flash it's firmware, which require to plug it with no battery to a windows machine and install a driver to handle a virtual com port over an USB connection.
I don't have major problem with the drivers, as they should work OK with both, WinXP and Win7. What is happening is something strange.
When I plug the device, I got the pop-up usb selector windows for less than a second asking if I want to associate the device to my mac or my win-guest os... just after the screen appears, it disappears, and again, for 3-4 times. After that it is not presented anymore, and into the device manager of windows, I can't see the device. Of course any time I try this operation I can listen the audio "bing" notification of device connected, and just after, the device disconnection.
I always assumed that the USB management of device was something "transparent" for Parallels, as it should "digest" almost all the devices. So, strong of this opinion, I tried to look for different causes which were preventing to see my device listed into the device manager.
Note: This is happening with WinXP Pro and with a Win7 Pro... same result.
I went in console and even if I didn't find any Parallel's related line worth to mention, I found this:
15/07/12 23:45:50,000 kernel: USBF: 26514.651 [0xffffff800a985800] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0xfd100000)
15/07/12 23:45:50,000 kernel: USBF: 26515.380 [0xffffff800a985800] The IOUSBFamily was not able to enumerate a device.
15/07/12 23:47:51,000 kernel: cdc_usb_bus:
robe: called
15/07/12 23:47:51,000 kernel: cdc_usb_bus:
robe: called, this driver support ZTE devices only.
15/07/12 23:47:51,000 kernel: usb_bus::stop: called
15/07/12 23:47:51,000 kernel: usb_bus::release_resources: called
15/07/12 23:47:51,000 kernel: com_zte_driver_cdc_usb_bus:
robe fails
15/07/12 23:47:51,000 kernel: cdc_usb_bus:
robe: called
15/07/12 23:47:51,000 kernel: cdc_usb_bus:
robe: called, this driver support ZTE devices only.
15/07/12 23:47:51,000 kernel: usb_bus::stop: called
15/07/12 23:47:51,000 kernel: usb_bus::release_resources: called
15/07/12 23:47:51,000 kernel: com_zte_driver_cdc_usb_bus:
robe fails
15/07/12 23:47:55,000 kernel: cdc_usb_bus:
robe: called
15/07/12 23:47:55,000 kernel: cdc_usb_bus:
robe: called, this driver support ZTE devices only.
15/07/12 23:47:55,000 kernel: usb_bus::stop: called
15/07/12 23:47:55,000 kernel: usb_bus::release_resources: called
15/07/12 23:47:55,000 kernel: com_zte_driver_cdc_usb_bus:
robe fails
15/07/12 23:47:56,000 kernel: cdc_usb_bus:
robe: called
15/07/12 23:47:56,000 kernel: cdc_usb_bus:
robe: called, this driver support ZTE devices only.
15/07/12 23:47:56,000 kernel: usb_bus::stop: called
15/07/12 23:47:56,000 kernel: usb_bus::release_resources: called
15/07/12 23:47:56,000 kernel: com_zte_driver_cdc_usb_bus:
robe fails
So this may means that the device is not recognized by MacOS itself.
My point is. If Parallels works transparently with USB devices (which may not have a relevant USB driver on MacOS, that's why we use an Emulator), why this is trapped by MacOS and not handled by Parallels directly?
[EDIT] Ah, something important. Apparently, under VMWare Fusion 4, it works... [ Apparently, it shows up for few seconds more, but just after few seconds, it disappears as well... ]
Any clue?
Thanks
Regards
gp
Last edited: Jul 16, 2012