Step 1: Select the proper zip file which contains the dmg file of the vcp driver project. For this example, let suppose we have the latest driver version and it is called “tivcp-osx sources 2 zip”. Step 2

Дата канвертавання22.04.2016
Памер18.94 Kb.
TUSB3410 Mac OS-X VCP Driver.
The following guide pretends to show you a quick overview of how to extract, build and install the TUSB3410 VCP driver for Mac OS-X v10.5 (Leopard) and v10.6 (Snow Leopard).
Step 1: Select the proper zip file which contains the DMG file of the VCP driver project. For this example, let suppose we have the latest driver version and it is called “”.

Step 2: Once the DMG has been extracted (TIVCP-OSX_sources-1.2.2.dmg), double-click on it and the “License Agreement” for the VCP driver will show up. Click on “Agree” so the proper disk volume can be mounted into your Desktop.

Step 3: After the proper disk volume has been mounted, double-click on it and select all files and folders. Copy them all into a folder previously created in your Desktop.

Step 4: Select the source code driver project file “TIUMPSerial.xcodeproj” and open it using at least X-Code program v3.1. For this example, we are opening the source code project using X-Code v3.2 so we can compile it for Mac OS-X for both 32-bit and 64-bit targets.

This is a brief description of each file and folder that must be present for compiling the VCP driver for Mac OS-X:

  • TIUMPSerial.xcodeproj – This is the project file for X-Code IDE version 3.1 and higher. To build for Intel 64-bit platform as well you need to use X-Code IDE version 3.2 and higher which run on Mac OS X 10.6.

  • dumpbinsh – This folder contains a script for converting Firmware images (residing in FWImages folder) to compilable source code

  • FWImages – It contains the actual Firmware images in *.i51 format. Because of limitation of kernel extension (driver) architecture on Mac OS-X, firmware must be statically compiled into KEXT binary. For recompilation convenience, it is sufficient to just copy any new FW images to this folder and recompile the driver source code by opening TIUMPSerial.xcodeproj project using X-Code program.

  • build – This folder will be generated once you have successfully built the source code and thus it contains resulting kernel extension/driver (TIVCPSerial.kext).

  • SerialPortSample - This folder contains some source code files for building a testing application - it is a sample code available from Apple website - adapted to enumerate correctly all serial drivers and use /dev/cu.TIVCP3410 device for communication.

  • All other files and folders contain source files important to build the driver.

Step 5: Once the source code project has been opened, check the target boxes for “TIUMPPrimitives.cpp”, “TIUMPSerial-Info.plist” and “UMPSerialDriver.cpp”. These are the files that need to be chosen for properly build the driver source code.

Step 6: From the drop-down menu (located at the top left corner of the X-Code program) check the proper target options for this example: Mac OS X 10.6  Release  TIUMPDriver Universal  x86_64

Step 7: Once the proper settings for the driver project has been selected, it’s time to plug your TUSB3410 board in the Mac OS-X system. If you already know which are the bcdDevice, PID and VID values, you can skip this step. Otherwise, open IORegistryExplorer (already present on the SWAT’s iMac system). Select the IOUSB category from the drop-down menu located in the top left corner, choose the proper TUSB3410 device and look for the “bcdDevice”, “idProduct” and “idVendor” values. For this example the values are:

  • bcdDevice = 0x101

  • idProduct = 0xc0da

  • idVendor = 0xacdc

Step 8: Go back and take a look to the X-Code program. Select the “TIUMPSerial-Info.plist” file and expand the “IOKitPersonalities  TIVCP3410” list. Change the bcdDevice, idProduct and idVendor values according to your TUSB3410 board. For this example, please note the values need to be converted from Hexadecimal to Decimal.

  • bcdDevice = 257 (0x101)

  • idProduct = 49370 (0xc0da)

  • idVendor = 44252 (0xacdc)

Step 9: Once the proper values has been modified in the plist file, it’s time to build the driver. Right-click on “TIUMPDriver Universal” target and select “Build TIUMPDriver Universal”.

A message stating “Save before building?” will show up because you modified the “plist” file. Click on “Save All” to continue with the building process.

In order to check that the build process has succeeded, take a look at the bottom right corner and look for “Succeeded” message

Step 10: Open a terminal session and go to your “release” folder (which contains the built driver) located within the path where you are compiling the driver source code from. For this example the path is Desktop/TIVCP-v1.2.2/build/release/. Once you are there, type the next commands within the terminal session in order to install the VCP driver in the system:
Note: Password for the SWAT’s iMac system is 7password-

  • Copy TIVCPSerial.kext extension into /System/Library/Extensions folder

sudo cp -R TIVCPSerial.kext /System/Library/Extensions

sudo touch /System/Library/Extensions

sudo chown -R root:wheel /System/Library/Extensions/TIVCPSerial.kext

  • Set kext privileges to 755 - it is kext system specification - without it, kext is not recognized by system

sudo chmod -R 755 /System/Library/Extensions/TIVCPSerial.kext

sudo kextcache -e

After the rebooting, the connected TUSB3410 device should be recognized and thus the driver loaded appropriately.

Uninstall drivers in MAC:
kextunload /System/Library/Extensions/nameofextension.kext
Then you can delete the unload “.kext” file simply by dragging it to the trash

База данных защищена авторским правом © 2016
звярнуцца да адміністрацыі

    Галоўная старонка