UniFlash FAQ

From Texas Instruments Wiki
Jump to: navigation, search

Contents

Installation

1. Where do I find the download links to the latest version of the software?

Please go to the following location for download links and instructions: http://processors.wiki.ti.com/index.php/CCS_UniFlash_Release_Notes_Latest#Installation_Instructions

2. What options are available during installation?

On top of choosing your installation directory, you will also have the ability to specify the emulation and device support you want to include for your installation. These options allow customers to tailor the application to support only the emulators and devices they need, while reducing the install size and installation time.

General

1. How do I find out if my device is supported in UniFlash?

For the latest list of supported devices, go to the following link: List of Supported Devices

2. How do I find out if the communication interfaces/emulators I am using is supported in UniFlash?

For the latest list of supported communication interfaces/emulators, go to the following link: List of Supported Communcation Interfaces/Emulators

3. What file types are supported in UniFlash?

For the latest list of supported file types, go to the following link: List of Supported File Types

4. I generated a configuation CCXML file from the UniFlash application, is there any way to modify the properties in this file?

Currently, no configuration editor is shipped with UniFlash for modifying advanced settings in a CCXML configuration file. But since CCXML files are compatible with both CCS and UniFlash (assuming the emulator and device is supported in both CCS and UniFlash), you can import the configuration file in CCS and use the Target Configuration view to edit the file. Alternately,you can also manually modify the XML content of the configuration file using a XML or text editor.

5. I can't find a feature that I need. What do I need to do to get this feature into the application?

First, read the Quick Start Guide and latest Release Note to make sure the feature is not already supported. If you can't find any information on the feature, please post a topic for an enhancement request in the forums. We will process these requests and determine if we can address it in our current software development schedule. If so, a public ClearQuest (CQ) entry will be issued and customers will be able to track the enhancement via the CQ number.

Graphical User Interface

1. How do I use the UniFlash application to program my device?

Please read the step-by-step guide for more information and instructions on using the application for Flash Programming.

2. How does the sessions in the GUI work?

A session is automatically created when you specify a CCXML configuration file in the GUI. Session files store the changes you make to the Flash settings, as well as the program file paths you added to the Program tab. When you restart UniFlash with the same CCXML configuration file, the session file will automatically be reloaded and your settings and program file list will be restored.

Session files can also be shared between different UniFlash applications, as well as with the command line and scripting tools. To export the current session information, go to 'Session->Save Settings as a Copy' in the top menu. This file can then be loaded in another instance of UniFlash, in the command line tool (via the -loadSettings parameter), or in your script (via DebugSession.flash.options.loadSessionSettings()).

For more information, go to the following link: Session Information

3. What is the purpose of the 'Program' tab under each core in the GUI? How does it differ to the 'Load Program' menu item under the 'Program' menu.

The 'Load Program' menu item allows you to program a single program file to the core of your choosing, while the 'Program' tab allows you to load multiple programs at the same time to a core (also known as 'multi-loading'). The 'Program' view allows you to Add and Remove program files to a list, Check and Uncheck the ones you want to program in this list, and finally Program these files to Flash memory in top-down order.

Although the erase policy depends on the device you are using, as well as the erase settings you selected in the GUI, the general idea is that the Flash is erased only before the first program load (unless the option is to erase necessary sectors only).

Note: the GUI assumes that the programs you are trying to load do not overlap. Please make sure this is the case before using the multi-load feature.

4. Can you let me know what Flash Setting <X> means?

The available Flash settings in the GUI is dynamically populated depending on the device you configured for. Each device will have unique options, and therefore we do not have a central location for looking up information on each option. To find out more information on your devices' Flash capability, please look up the Datasheet for your device in the Texas Instruments product page.

5. What is the device connect/disconnect policy in the GUI?

Currently, the device is connected/disconnected as needed. The application will only connect to the device when an operation is invoked in the GUI, and will disconnect as soon as it is completed. This will allow customers to switch out devices while using the application without worrying if the device is still being accessed.

6. How do I save the content of Flash memory to a file?

To save/export the memory on the target, go to the menu 'Program->Save Memory...' and fill in all of the necessary information in the dialog. A list of supported file types can be found in the release notes.

7. How do I update the application to the latest version?

To search for available updates, go to the menu 'Help->Check for Updates'. This will search for all of the specified Update Sites and return the list of components that have available updates. Customers will be able to choose which components to update.

8. When programming a binary file, what do I specify for Start Address?

It depends on where you want to load the binary. In most cases it is the start address of Flash for your device, but if your application requires it to be loaded to a different address, you could specify that.

Scripting

1. Where do I get more information on writing scripts for UniFlash?

Read the Scripting Quick Start Guide here.

2. Are scripts written in CCS compatible with UniFlash scripting and vise versa?

Yes, both CCS and UniFlash scripting is powered by Debug Server Scripting (DSS), and therefore they can be exporting from one application and run using the other application. But note that this will only be successful if both the communication interface and device you are using in your script is support in both solutions.

3. How do I access Flash options in my script?

Each Flash option that you see in the GUI has an associated property ID. You can access each option using the ID via the DebugSession.Options class.

To get all available Flash options ID, use the following line in your script:
> DebugSession.options.printOptionById("FlashProgrammerNode");

Command Line Support

1. Where can I find more information on the command line tool?

Read the Command Line tool Quick Start Guide here.

2. Can I access multiple cores in the same command using the command line tool?

No, you can only access one core at a time with a single command. To access multiple cores, you will need to execute multiple commands one after the other.

3. How do I access Flash options in my command?

To view the available Flash option IDs, configure your device in the command line (via -ccxml or -createConfig), and use the -viewOptions parameter. The tool will configure the device, query and display the list of available Flash options for the device.

To set the options, use the -setOptions parameter, and providing the id and value pair in the necessary format (view the help dialog for more information).

Serial Communication Interface Support (v2.0 Feature)

1. How do I set up my configuration to use the Serial Support?

First, you will need to choose to install the Serial Connection Support component when installing UniFlash. This option will only be available if the "C28x 32-bit Real-time MCUs" option was selected (Since C28x Concerto is the only supported target).

In the GUI, click on "New Target Configuration". Under Connection, choose "Serial Connection", and you will see the list of supported devices in the Board or Device drop-down list. After choosing the device, the configuration file will be generated, and the GUI will provide you with the Serial Connection options. You can choose to save this configuration under "File -> Save Target Configuration File"

2. What options are available when using Serial Connection?

Currently, you can configure the COM Port (via ID "FlashSerialCOMPort" in scripting and command line tool) and Baud Rate (via ID "FlashSerialBaudRate").

The COM Port field is a String field that allows you to enter to full name of the port, depending on the OS you are currently using. Examples include "COM1" for Windows and "/dev/ttyS0" for Linux; no quotes are needed when entering this information into the GUI text box.

The Baud Rate is a numeric value and is default to 115200.

On top of that, the Flash options and operations supported on the Concerto devices is the same as in the JTAG based communication interface.

3. I modified the COM port settings in my Concerto Serial Configuration file, but I can't seem to program the C28x core?

The serial configuration settings are per core basis. This allows the two cores to have separate serial configurations, but this also means that if both cores are using the same serial interface, you will need to configure the two cores (ie; entering the same COM port and baud rate information) separately.

Therefore, if you modified the COM port setting, make sure it is for the core you are working on, and also make sure to remember to modify the settings on other cores when you need to interface with another core.

4. Is my device supported with Serial Connection?

Starting with v2.0, the Concerto Series of devices (F28M35x, F28M36x) is supported. We will continue to evaluate the possibility of adding additional device support for the supported communication interfaces in future releases.