NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

Texas Instruments™ PCIxx12 Integrated FlashMedia Controller Driver, Version 2. The USB 3.0 Host Controller drivers for Vostro 3550/3350 and Inspiron N5110 TI 7412 PCMCIA Driver for Windows Vista. A driver package consists of all the software components that you must supply in order for your device to be supported under Windows. Installing a device or driver involves system-supplied and vendor-supplied components. The system provides generic installation software for all device classes. Vendors must supply one or more device-specific.

Last updated: 02/15/2018

• 3Processor SDK Patching and Rebuilding
• 4Running Pre-Built Applications
• 5Building and Running Sample Application

The Texas Instruments PRU ICSS Industrial Packages is a single scalable software platform for Industrial Protocols/Drives solution that offers streamlined development across different TI Sitara Processors. The Industrial Protocol packages provide fundamental software for development of various Industrial communication protocols like EtherCAT, Profinet, EthernetIP, Profibus etc. PRU-ICSS Industrial Drives package is designed for the Sitara processor AM437x (with PRU-ICSS IP) to enable customers leverage Industrial Drives (position, current sense & control algorithm) capabilities. The packages also include sample demo application which showcase the ability of the software/hardware to implement those.

This package runs on top of Processor SDK and consists of (depending on the package)

• PRU-ICSS firmware to implement Real-Time Ethernet/fieldbus or Industrial Drives interfaces
• Associated drivers
• Stack adaptation layer
• Evaluation versions of protocol stack library for selected protocols
• Sample applications

Protocol packages installer is a windows or linux executable which installs source files, CCS project file scripts, pre-built libraries, documents, tools and other items to the host machine.

PRU-ICSS Industrial Protocols may require patches to be applied on top of recommended version of Processor SDK to fix certain functional issues. In that case, industrial protocol installer will package those patch files. User need to make sure that these patches are applied properly on Processor SDK and affected LLD's are rebuilt before building industrial protocol application projects.

Setting up the patching tool[edit]

1. Go to the link http://gnuwin32.sourceforge.net/downlinks/patch-bin-zip.php, download and save the patch utility.

2. Extract the zip file to the Windows PC. Patch file utility(Patch.exe) can be found in bin folder

NOTE: That this is not a TI tool - see http://savannah.gnu.org/projects/patch/ for more details and licensing information

Locating the patch files in PRU-ICSS industrial protocol package[edit]

After installing the PRU-ICSS Industrial Protocol package, navigate to <INSTALL_DIR>/protocols/pdk_patches/<Processor_SDK_Version> where

INSTALL_DIR : The folder location where the Industrial protocol package is installed.
PROCESSOR_SDK_VERSION : The recommended version of Processor SDK which is compatible with PRU-ICSS Industrial Protocol package.

Patch folder location from Profinet-slave 1.0.2 release package is shown below for reference

Applying the patch[edit]

1. Launch DOS Command prompt(Start->Run->cmd)
2. CD to bin folder
3. Execute patch.exe with following syntax in windows environment

patch.exe -i PATCH_FILE_FULL_PATH -d SOURCE_DIR -p<n> --binary --verbose

Eg: D:patch_utilitypatch-2.5.9-7-binbinpatch.exe -i C:tiPRU-ICSS-Profinet_Slave_01.00.02.02protocolspdk_patches04.02.00PRSDK-3454-finalPrioQueue_mismatch.patch -d C:tipdk_am335x_1_0_9packages -p0 --binary --verbose

Rebuilding the Processor SDK LLD's[edit]

Refer to http://processors.wiki.ti.com/index.php/Rebuilding_The_PDK for details on rebuilding Processor SDK LLD's on windows/linux

The following pre-built applications can be used for a quick start with IDK. Release notes will have the information on where to obtain pre-built binaries for each release,

• EtherCAT Slave Application
• Profinet IRT Slave Application
• Profinet RT Slave + MRP Application
• EnDat Diagnostic Application
• Tamagawa Diagnostic Application
• Motor Control Application

These binaries will be available as a separate package(not available with the installer). Loading the binaries(app) with the corresponding SD Card MLO from PDK should enable a quick setup to validate the environment.

Running Application from SD card/QSPI Flash
[edit]

Refer to http://processors.wiki.ti.com/index.php/Processor_SDK_RTOS_BOOT_AM57x

The Industrial Protocol package includes sample applications which demonstrate the device capabilities. Unlike [| legacy Industrial SDK], the CCS project files are not readily available in the protocol package. Users need to generate this with the help of the Batch file or Shell scripts provided in the protocol installer packages. Refer to specific protocol package user guides Generating project files section for detailed instructions

Importing and Building Sample Project in CCS[edit]

1. Launch CCS.
2. Click Menu->File->Import
3. On new window , Select Code Composer Studio->Existing CCS Eclipse Projects and click Next.
4. Select 'Select search-directory' and browse to locate the sample application project, say [INSTALL-DIR]/<protocols | interfaces | examples>/<protocol name | interface name | example name>/projects
5. The project will be listed under 'Discovered Projects' and Select the required project from the list.
6. It is recommended to keep 'Copy Projects into workspace' tick box un-checked.
7. Click Finish. This will import the project into workspace.
8. The imported project will be shown in CCS Project Explorer tab.
   
9. Right Click on Project, Select 'Build Project'. This will build the sample project's .out file.
10. See the CCS Console tab for build logs.
11. All sample applications have Debug and Release configurations.
    
12. To build for a different configuration, Right click on the project and select Build Configurations ->SetActive ->Debug/Release and build the project once again.
    

Creating a target configuration, if one doesn't exist already.[edit]

1. File menu-> New-> Target Configuration File.
2. Check 'Use shared location' to be available to anyone who uses the workspace. Click Finish. A window opens up which is to configure the connection details
3. Connection: Choose the host-to-target connection details. For example 'Texas Instruments XDS100v2 USB Emulator'
4. Device: Select IDK_AM572x or PRELIM_IDK_AM571x for AM57x, for AM437x select IDK_AM437X
5. Click Save.

Launching and Debugging application in CCS[edit]

1. Connect JTAG Emulator to EVM in-case of IDK or Connect USB cable to board in-case of ICE
2. Select View->Target Configurations. Right click on the required configuration in the list and Select Launch Selected Configuration
3. Right Click on the Cortex A15_0 on AM57x or CortexA9 on AM437x listed in Debug view and select Connect. ( Click View->Debug to view debug window, if not visible. )
4. Select System Reset under
5. Select Suspend
6. Load the GEL file and execute initialization script.
7. Once the initialization is completed, Select Run->Load ->Load Program. Here browse to the required executable and click OK
8. After a successful load, the program is expected to be in suspended state and program counter is pointing to main function. If the program is not in suspended state :
   1. Suspend the application by clicking or Run->Suspend
   2. Restart the application by clicking or Run->Restart
9. Run the application by selecting Menu->Run->Resume.
10. Menu->Run->Resume. This will execute the application.

NOTE

• While launching a debug session for the first time, CCS will ask for the CPU to which the program needs to be loaded. Please select Cortex-A15_0 or CortexA9 (depending on the platform) and continue.
• If TeraTerm does not display an output upon program execution. TeraTerm can be initialized just prior to program execution by performing steps 1-8 and then
  Disconnect the terminal session using File -> Disconnect
  Reconnect the terminal session with File -> New Connection
• If there is a valid application in SPI or NOR flash(in their corresponding boot mode), on 'System Reset' the application loads right away. This might cause issues on the application you load via JTAG. To avoid this, put a hardware breakpoint at 0x402f_0400(in case of MMSCD boot mode) or 0x30000000(in case of qSPI boot mode) and then do a 'System Reset'. You can then continue with Step 4 after this step.

The Sitara Frequently Asked Questions (FAQ) contains answers to a number of common questions on Sitara Industrial topics. The Sitara FAQ is available at: http://processors.wiki.ti.com/index.php/FAQ_Sitara_Industrial .

This package contains project templates and system files for the Texas Instruments MSP430.

CrossWorks Version 2 Installation Instructions

1. Click the Tools > Package Manager menu option to open the package manager window.
2. Right click on the Texas Instruments MSP430 CPU Support Package entry and select Install Selected Packages.
3. Click Next to take you to the summary page.
4. Click Next to install the package.
5. Click Finish to close the package manager window.
6. Click the Tools > Show Installed Packages.
7. Click on the Texas Instruments MSP430 CPU Support Package link to view the package and its contents.

1. Download the file msp430.hzq using your web browser.
2. Click the Tools > Manually Install Packages menu option.
3. Select the file you have just downloaded to install the package.
4. Click the Tools > Show Installed Packages.
5. Click on the Texas Instruments MSP430 CPU Support Package link to view the package and its contents.

Windows Driver Package Texas Instruments For Sale

Release Notes

1.17

• Added support for MSP430G2744 and MSP430G2955.

1.16

• Added missing led and timer samples.

1.15

• Updated device support for CrossWorks for MSP430 version 2.2.

1.14

• Fixed number of breakpoints problem that affected MSP430F23x, MSP430F24x and MSP43024x1 devices.
• Added device support for CC430F512x, CC430F514x and CC430F614x.
• Fixed RAM size of MSP430F112.xml.
• Fixed FLASH start of MSP430F1612.xml.
• Fixed FLASH start of MSP430F47173.xml.
• Added device support for MSP430F521x, MSP430F522x and MSP430F535x.
• Fixed RAM size of MSP430F5513.xml.
• Fixed RAM size of MSP430F5521.xml.
• Added device support for MSP430F565x, MSP430F645x.
• Added device support for MSP430F67xx(1).
• Fixed IO register definitions in MSP430FR57xx.xml.
• Added device support for MSP430FR5949 and MSP430FR5969.
• Fixed RAM size of MSP430G2xxx.xml.
• Added device support for MSP430G2210 and MSP430G2230.
• Supplied build of msp430.dll based on sources of version 2.4.9.001.
• Supplied build of msp430_v3.dll based on sources of version 3.2.5.004.
• Removed Solaris build of msp430.dll.

1.13

• Added support for MSP430F533x, MSP430F643x, MSP430F67xx.
• Fixed info block sizes of MSP430F471xx memory maps.
• Supplied version 3.2.3.015 of msp430.dll for Windows and Linux - this is named msp430_v3.dll. Use this dll for FET430-UIF's that have been upgraded to msp430.dll v3.

1.12

• Added support for MSP430AFE2xx, MSP430G2xx3 and MSP430FR57xx.
• Supplied build of msp430.dll based on sources of version 2.4.8.002.
• Supplied version 2.4.8.002 of TI msp430.dll for Windows - named msp430_ti.dll - use this file if you get communications problems with the default msp430.dll.

1.11

• Added support for MSP430F532x, MSP430F534x, MSP430G2xx2, MSP430FW428 and MSP430FW429.
• Supplied build of msp430.dll based on sources of version 2.4.7.001.
• Supplied version 2.4.7.001 of TI msp430.dll for Windows - named msp430_ti.dll - use this file if you get communications problems with the default msp430.dll.
• Added support for eZ430-RF/LaunchPad on MacOS hosts.

1.10

• Added support for MSP430F438, MSP430F439 and MSP430F663x.
• Supplied build of version 2.4.6.001 of TI msp430.dll.
• Added support for eZ430-F2013 on Linux/Macos/Solaris hosts.
• Added support for eZ430-RF/LaunchPad on Linux hosts.
• Added support for TI TUSB3410 drivers on MacOS hosts.
• Firmware upgrade of FET430-UIF supported on Linux/Macos hosts.
• Fixed number of breakpoints problem on MSP430FG439.

1.9

• Added support for MSP430F550x, MSP430F51xx and MSP430G2xx.
• New CTL project template sets the CTL_IRQ_STACK_SIZE linker symbol to 128.
• The memory size build option is set when an MSP430X target processor is selected that has less than 64K of flash memory.
• Fixed addresses of timer1_a registers in registers window.
• Supplied version 2.4.3 of TI msp430.dll.
• Changed identify string of MSP430FG4616 and MSP430FG4617 to match MSP430FG4619.
• Changed identify string of MSP430F2417 and MSP430F2416 to match MSP430F2418.

1.8

• Fixed addresses of SD16MEMx and SD16IV registers for MSP430F471xx in the registers display.
• Added support for MSP430F471xx, MSP430F461xx, MSP430F4481 and MSP430F4491.
• Device specific header files now supplied.
• Supplied version 2.4.2 of TI msp430.dll.

1.7

• Fixed IE2 bitfields for MSP430F24x, MSP430F24x1 and MSP430F26x in the registers display.

1.6

• Fixed info memory description of MSP430F41x2 devices in memory map files and placement file selection.
• Fixed the names of ADC10AE0 and ADC10AE1 in the registers display.

1.5

• Added support for MSP430F551x, MSP430F552x, MSP430F543xA, MSP430F541xA.

1.4

• Added support for MSP430FG47x, MSP430F47x, MSP430F471x7, MSP430F471x6, MSP430F41x2, CC430F613x, CC430F612x and CC430513x.

1.3

• Fixed FLASH size of MSP430FG4619 memory map file.

1.2

• Fixed RAM size of MSP430FG4618 memory map file.
• Fixed incorrect inclusion of header file for MSP430F2419.
• Chip/board specific CTL file ctl_msp430.c now included in package and project template.

1.1

• Move project templates into package.

1.0

• Initial Release.

Documentation

Project Templates

Project templates are provided to create the following project types:

Windows Driver Package Texas Instruments

• C Executable - an executable project which includes the C startup code.
• Assembly Executable - an executable project.
• CTL Executable - an executable project which includes the CTL support code ctl_msp430.c.
• Externally Built Executable - an externally built executable project.

Header and Memory Map Files

Memory map files are provided for each supported MSP430 device. The appropriate memory map is selected based on the Target project property group value.

Header files are provided for each supported MSP430 device. The top level file msp430.h will include the appropriate file based on the Target project property group value.

Windows Driver Package Texas Instruments For Sale By Owner

MSP430.dll and MSP430_v3.dll

Windows Driver Package Texas Instruments List

Builds of the TI MSP430.dll are provided that interface to FET430UIF and eZ430/LaunchPad devices. On Linux and Windows the standard TUSB3410 Virtual COM Port Driver is used to communicate with the FET430UIF and the eZ430-F2013. On MacOS the unofficial TUSB3410 Virtual COM Port Driver can be used to communicate with the FET430UIF and the eZ430-F2013.

Builds of version 3 of the TI MSP430.dll are provided for Linux and Windows hosts that interface to FET430UIF devices that are running the V3 firmware. To use this you will need to modify the Target Driver DLL Path target property to reference $(PackagesDir)/targets/msp430/MSP430_v3$(HostDLL). You can do this by showing the targets window, right clicking on the target interface and selecting properties.

Windows Driver Package Texas Instruments Nspire

The eZ430-RF/LaunchPad devices are supported on Linux, MacOS and Windows hosts. On MacOS you'll need to install a codeless kext to prevent the MacOS HID driver from claiming the device. There are some instructions on how to do this here. Note that on MacOS you'll need to unplug the ez430-RF/LaunchPad before a target connect.

The MSP430.dll target interface property Port Name is set to be USB by default and will connect to an eZ430-RF/LaunchPad device in preference to any FET430UIF/eZ430-F2013 devices. You can right click on the target in the targets window prior to connection to set the Port Name from a list of potentially applicable device names.