https://e2e.ti.com/administrators1/digital_interface/Products covered in this section are 1394, PCI, PCIe, SATA, DisplayPort, DVI/HDMI, FlatLink/FPD-Link and FlatLink3Gen-USTelligent Community 13https://e2e.ti.com/administrators1/digital_interface/m/videos__files/198722Wed, 14 Jul 2010 13:48:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e8dc369c-d32e-47fb-ba62-ba1178883063DHarmonThese TUSB3410 drivers for the MAC OS X operating systems have not been officially released by Texas Instruments, however unsupported, as-is drivers are available for evaluation use. Please do not contact TI support if you run into any issues. Please provide feedback on the Consumer & Computing Interface Forum . Also, the drivers were developed for the TUSB3410UARTPDK . The TUSB3410 is also used by the multipe MSP430 tools as the USB interface, but are not hardware identical. These MSP430 tools use different USB VID/PID and this may need to be accounted for when you load it on the MAC. Here is an extract from a customer using the EZ430 and a MAC - they needed the source code to get this to work: ----------------------- Under Windows OS and using the USBView app (freeware), I first observed that the eZ430-F2013 stick presented itself to the OS as: bcdDevice=0x101 VID=0x0451 PID=0xF430 Then I obtained the decimal values for each of them: bcdDevice=257 VID=1105 PID=62512 Then I moved to my Mac platform. These steps MUST be performed in order to properly recognize any TUSB3410 device: 1) Modified the “TIUMPSerial-info.plist” file that comes along with our VCP driver’s source files (see Pic1 attached). For the IOKitPersonalities I used: For TIVCP3410: bcdDevice = 257 idProduct = 62512 idVendor = 1105 For TIVCP3410Boot: bcdDevice = 257 idProduct = 62512 idVendor = 1105 2) I recompiled the VCP driver using XCode and the “TIUMPSerial.xcodeproj” included in our source files. 3) I installed the driver using the commands shown in our driver’s documentation. 4) I rebooted the machine with the EZ430 stick plugged in. 5) I opened a terminal session and look for the EZ430 stick in /dev/. There are two instances shown: “cu.TIVCP34103d20” and “tty.TIVCP34103d20”. 6) I opened the IORegistryExplorer and this is how the EZ430 stick is detected. I tried to do my best explaining how to install/detect any TUSB3410 device using the VCP driver doing proper list edition and driver buildMAC OSXTUSB3410MACVCPVirtual Com Porthttps://e2e.ti.com/administrators1/digital_interface/m/videos__files/198719Wed, 14 Jul 2010 13:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:deb6da3a-68a8-4501-bbd7-2984c320e126DHarmonThese TUSB3410 drivers for the MAC OS X operating systems have not been officially released by Texas Instruments, however unsupported, as-is drivers are available for evaluation use. Please do not contact TI support if you run into any issues. Please provide feedback on the Consumer & Computing Interface Forum . Also, the drivers were developed for the TUSB3410UARTPDK . The TUSB3410 is also used by the multipe MSP430 tools as the USB interface, but are not hardware identical. These MSP430 tools use different USB VID/PID and this may need to be accounted for when you load it on the MAC. Here is an extract from a customer using the EZ430 and a MAC - they needed the source code to get this to work: ----------------------- Under Windows OS and using the USBView app (freeware), I first observed that the eZ430-F2013 stick presented itself to the OS as: bcdDevice=0x101 VID=0x0451 PID=0xF430 Then I obtained the decimal values for each of them: bcdDevice=257 VID=1105 PID=62512 Then I moved to my Mac platform. These steps MUST be performed in order to properly recognize any TUSB3410 device: 1) Modified the “TIUMPSerial-info.plist” file that comes along with our VCP driver’s source files (see Pic1 attached). For the IOKitPersonalities I used: For TIVCP3410: bcdDevice = 257 idProduct = 62512 idVendor = 1105 For TIVCP3410Boot: bcdDevice = 257 idProduct = 62512 idVendor = 1105 2) I recompiled the VCP driver using XCode and the “TIUMPSerial.xcodeproj” included in our source files. 3) I installed the driver using the commands shown in our driver’s documentation. 4) I rebooted the machine with the EZ430 stick plugged in. 5) I opened a terminal session and look for the EZ430 stick in /dev/. There are two instances shown: “cu.TIVCP34103d20” and “tty.TIVCP34103d20”. 6) I opened the IORegistryExplorer and this is how the EZ430 stick is detected. I tried to do my best explaining how to install/detect any TUSB3410 device using the VCP driver doing proper list edition and driver buildMAC OSXTUSB3410MACVCPVirtual Com Porthttps://e2e.ti.com/administrators1/digital_interface/m/videos__filesSat, 12 Dec 2009 09:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:75ecf186-2b62-4abd-9dc5-82fb79bc00cfhttps://e2e.ti.com/administrators1/digital_interface/Sat, 12 Dec 2009 09:52:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:29cf6339-6c2e-412e-8842-614116b2fc78Products covered in this section are 1394, PCI, PCIe, SATA, DisplayPort, DVI/HDMI, FlatLink/FPD-Link and FlatLink3G