RVConfig is preconfigured to support a number of platforms, but you can add support for more platforms by creating your own platform files.
To add a new platform to the list in the Select Platform dialog box, you must first create a new configuration file.
To create a new configuration file, you can:
Configure a scan chain for the new platform (see Configuring a scan chain).
Make any changes to the device settings that are required. See Configuring devices.
Make any changes to the advanced settings that are required. See Advanced configuration.
Make any changes to the trace settings that are required. See Configuring trace lines.
Specify a new platform name and its manufacturer in the Export As Platform dialog box.
To setup the platform name and manufacturer:
Select File → Export platform file....
In the Export As Platform dialog box, enter the new platform’s name and manufacturer details in the Board Name and Manufacturer fields, respectively. See Figure 4.26.
The platform’s name and manufacturer details are used to name the new platform files, and are displayed in the Select Platform dialog box, as shown in Figure 4.23, for the new platform.
On Windows, the
platformFilesdirectory, shown in Figure 4.26, is located inMy Documents\ARM\rvconfig\platformFiles. In Linux, it is located in~/.rvconfig/platformFiles.Click OK.
Note
A platform detection file is produced if all devices on the scan chain are auto-detected, but if you move devices around before exporting the platform file, the platform detection file will not work.
A .det file is created automatically
when you setup the board name and manufacturer, as in Adding platforms to the Select Platform
dialog box. You can, however,
add more .det files to the platformFiles directory,
which allow different hardware versions to be recognized when you
click the Auto Configure button. A .det file
can contain information for one or more platforms. This platform
description consists of a pattern and a mask for each item on the
JTAG scan chain of the target platform, and the name of the associated .rvc file.
For example:
0x0B73B02F,0xFFFFFFFF, 0x07926001,0xFFFFFFFF, 0,0, 0x2B900F0F,0xFFFFFFFF = mycompany_eg1.rvc
In the above example, the platform is expected to contain
four devices on its scan chain. The first device must have a JTAG
ID code of 0x0B73B02F, the second 0x07926001,
the third device can have any ID code, and the fourth device’s code
must be 0x2B900F0F.
Several .det files can be supplied, and
each file can contain more than one line. For example:
0x22193024, 0xEFFFFFFF, 0,0, 0,0 = mycompany_eg2.rvc
0x08210024, 0xFFFFFFFF, 0,0, 0,0 = mycompany_eg2.rvc
0x05310024, 0xFFFFFFFF, 0,0, 0,0 = mycompany_eg3.rvc
In the above example, a scan chain containing three devices,
where the first device has an ID code of 0x22193024, 0x32193024 or 0x08210024 is
associated with mycompany_eg2.rvc. The mask
value of 0xEFFFFFFF means that both 0x22193024 and 0x32193024 are
identified. If there are three devices, and the first has an ID
code of 0x05310024, then it will be associated
with mycompany_eg3.rvc.
When you click the Auto Configure button,
the detected scan chain is compared against all the platforms described
by .det files. If the connected target matches
any of these platforms, a Select Platform dialog box is displayed,
and asks the user to confirm that the platform has been correctly
detected.
It is possible to create platform information that associates
a given scan chain with several .rvc files.
If this happens, the Select Platform dialog box lists all the platforms that
match, and you will be asked to select the platform that matches
your hardware.
PDF version