Mac OSx with VMFusion running Windows Pro: programming Propellers. . . .
Ken Gracey
Posts: 7,400
Hey there,
I've just switched over to a Macintosh.
BST works wonderfully, but the Parallax Propeller Tool running in a Windows VMFusion environment doesn't seem to detect or program Propellers. In the Device Manager the addition/removal of FTDI hardware doesn't show up as a VCP serial port - does anybody have the same hardware setup and know how to get this functioning?
Thanks,
Ken Gracey
I've just switched over to a Macintosh.
BST works wonderfully, but the Parallax Propeller Tool running in a Windows VMFusion environment doesn't seem to detect or program Propellers. In the Device Manager the addition/removal of FTDI hardware doesn't show up as a VCP serial port - does anybody have the same hardware setup and know how to get this functioning?
Thanks,
Ken Gracey
Comments
I normally use Parallels Desktop, but I have an old copy of VMWare as well and it works the same.
When you start VMWare, you also have to tell it which environment "owns" which USB devices. I know Parallels Desktop has a menu item for the I/O devices and the USB device list is on that menu. You can check or un-check each device to specify whether it is controlled by the MacOS or Windows.
I've run all the Windows software for the Propeller under either Parallels Desktop or VMWare's Fusion including the Propeller Tool, the PropScope software, ViewPort. I also run the Stamp Editor that way and it all works fine.
To run it I have to enable serial port (Com1) in VirtualBox, then attach it to /dev/ttyUSB0 on linux host.
Then Parallax Propeller Tools detected a propeller on com1
No FT232 drivers needed in virtual windows. Windows think it accesses normal com port.
It is not the same environment, but maybe it can help.
Very surprising to see a Windows XP system running on a Mac in this way - wow!
Ken Gracey
If you only have XP you need to use a virtual machine because since Lion, Boot Camp does not support XP.