| |||
Home > Getting Started > Loading FPGA and PLD images > Upgrading your hardware |
Use one of the progcards utilities and the board description
(*.brd
) files to load configuration images
to the FPGA. There are three versions of the utility:
progcards_rvi.exe
uses RealView ICE and
the JTAG interface. It runs on a PC host in a DOS window and communicates
with the RealView ICE interface box.
See Procedure for progcards_rvi.exe for detailed instructions.
progcards_multiice.exe
uses Multi-ICE
and the JTAG interface. It is a TAPOp program that runs on a PC
host in a DOS window and communicates with the Multi-ICE server.
See Procedure for progcards_multiice.exe for detailed instructions.
progcards_usb.exe
uses the built-in USB
to JTAG interface logic on the baseboard. A standard USB cable
connects the baseboard to the PC running progcards_usb.exe.
See Procedure for progcards_usb.exe for detailed instructions.
The latest version of the RVI firmware can be downloaded from the Technical Support area of the ARM web site.
Ensure that the RealView ICE firmware
is version 1.4.1 (or later) and has the additional patch required
for running progcards_rvi
. The patch can be downloaded
from the downloads page on the Technical Support section of the ARM
web site. See the readme
file supplied with progcards_rvi
for
information on updating the firmware.
Connect the 20-way JTAG cable from the RealView ICE JTAG interface to the box header on the platform baseboard. See Figure 2.8.
Move the CONFIG switch S1 to the ON position, see Connecting JTAG debugging equipment. The orange CONFIG LED lights.
Turn on the power.
Start a command window by selecting Run from
the Start menu and entering command
in
the text box.
Change directory to the directory that contains
board description (*.brd
) files for the design
to be programmed.
Start the programming utility by entering progcards_rvi
at
the command prompt.
A menu is displayed asking which interface box you want to connect to. Select the interface that is connected to the baseboard.
See the documentation supplied with progcards_rvi
for
information on connecting directly to a specified interface that
is connected to either the network or the local USB connection on
the PC.
RVI attempts to autoconfigure. If auto-configuration
fails, see the documentation supplied with progcards_rvi
.
progcards_rvi
searches for
board description files that match the JTAG scan chain. All board
descriptions matching the first part of the chain are presented
as a menu and you can select the file to use.
progcards_rvi
runs through the steps
required to completely reprogram the boards. The output is similar
to the example transcript is shown in Example 2.2.
To bypass programming a Logic Tile or the baseboard
select the Skip
option from the menu. progcards_rvi
then
looks for board description files that match the next segment of
scan chain and so on.
Typically one menu is displayed for the Logic Tile and one menu is displayed for the baseboard. If only one board description matches your hardware, it is automatically selected and no menu is displayed.
Ensure that the image file you are loading matches your system configuration. If the incorrect files are loaded, the baseboard and tiles might not function or might be unreliable.
After downloading the image completes, turn the baseboard power off and move the CONFIG switch to the OFF position.
Set the configuration switches to match the boot option you are using, see Setting the configuration switches.
Power on the baseboard and use the Boot Monitor to load your application (see Using the baseboard Boot Monitor and platform library).
If you are not using the Boot Monitor, use a JTAG debugger to load and run an application. See the documentation supplied with your debugger for details.
If it is not already installed, install the Multi-ICE server (revision 2.2.6 or later).
Connect the 20-way JTAG cable from the JTAG interface (Multi-ICE) to the box header on the platform baseboard. See Figure 2.8.
Move the CONFIG switch S1 to the ON position, see Connecting JTAG debugging equipment. The orange CONFIG LED lights.
Turn on the power.
Start the Multi-ICE server. See the documentation supplied with the JTAG hardware for details on using the interface.
Select File → Auto-Configure. The display should be updated to show a number of FPGA and PLD devices in the scan chain.
If auto-configuration fails, you must manually load an appropriate
configuration. Select File → Load → Configuration and
then choose the file in the multi-ice
subdirectory
that matches your hardware configuration.
The configuration files automatically set the transfer timing (TCK) to 1MHz, therefore manually setting the transfer timing is not necessary.
Start a command window by selecting Run from
the Start menu and entering command
in
the text box.
Open a command prompt window and change directory
to the directory that contains board description (*.brd
)
files for the design to be programmed.
The command to start progcards_multiice
depends
on your hardware setup:
If you are
using Multi-ICE and the server is running on a different machine than
you are using to enter the commands, invoke progcards_multiice
by entering:
C:\Boardfiles
> progcards_multiiceserver_name
If the Multi-ICE server is running on the same machine,
there is no need to supply a server name as the local host is the
default. Invoke progcards_multiice
by entering:
C:\Boardfiles
> progcards_multiice
progcards_multiice
searches
for board description (*.brd
) files that match
the JTAG scan chain shown on the Multi-ICE server window. All board
descriptions matching the first part of the chain are presented
as a menu and you can select the file to use.
progcards_multiice
runs through the steps
required to completely reprogram the boards. An example transcript
is shown in Example 2.2.
To bypass programming a Logic Tile or the baseboard
select the Skip
option from the menu. progcards_multiice
then
looks for board description (*.brd
) files that match
the next segment of scan chain and so on.
Typically one menu is displayed for the Logic Tile and one menu is displayed for the baseboard. If only one board description matches your hardware, it is automatically selected and no menu is displayed.
Ensure that the image file you are loading matches your system configuration. If the incorrect files are loaded, the baseboard and tiles might not function or might be unreliable.
After downloading the image completes, turn the baseboard power off and move the CONFIG switch to the OFF position.
Set the configuration switches to match the boot option you are using, see Setting the configuration switches.
Power on the baseboard and use the Boot Monitor to load your application (see Using the baseboard Boot Monitor and platform library).
If you are not using the Boot Monitor, use a JTAG debugger to load and run an application. See the documentation supplied with your debugger for details.
Example 2.2. Example transcript for Multi-ICE and progcards_muiltiice.exe
C:\BoardFiles> progcards_multiice ARM Development Card Logic Programmer Version 2.53 Attempting to connect to Multi-ICE server Multi-ICE reports 4 TAP controllers Several possible boards detected at TAP position 0:- 0: Quit progcards 1: Skip (eb) 2: EB (HBI-01409C) CTMPCore FPGA flash image 0 build28, Character LCD Mux build 3 Make a choice: 2 Step 1: PLD/SVF download of an1151/an151_eb_140c_xc2v6000_ct926umc_le_build3_mux_xc2c128_build2.svf Progress: 100.00% Step 2: FPGA download of an1151/an151_eb_140c_xc2v6000_via_build1.bit Progress: 100.00%, Throughput: 23.19k/s, Frame: 1458 Step 3: Intel flash download of an1151/an151_eb_140c_ctmpcore_li_build7.bit Progress: 100.00%, Throughput: 31.68k/s Step 4: Intel flash verify against an1151/an151_eb_140c_xc2v6000_ctmpcore_li_build7.bit Progress: 100.00%, Throughput: 29.46k/s, Errors: 0% Step 5: PLD/SVF download of an1151/an151_eb_140c_mux_xc2c128_build1.svf Progress: 100.00%
If it is not already installed, install the USB Debug Direct Control software.
Windows USB Debug drivers must be installed before using the progcards_usb
utility.
Information on installing the USB drivers can be found in \
.boardfiles
\USB_Debug_driver\readme.txt
Connect the USB cable from the host PC to the USB debug port (near the screw terminals) on the platform baseboard. See Figure 2.12.
Move the CONFIG switch to the ON position, see Connecting JTAG debugging equipment.
Turn on the power. The orange CONFIG LED lights.
Start a command window by selecting Run from
the start menu and entering command
in
the text box.
Change directory to the directory that contains
board description (*.brd
) files for the design
to be programmed.
Start the programming utility by entering progcards_usb
at
the command prompt.
If progcards_usb.exe
is not in the current
working directory, set your PATH
environment
variable to point to the directory that contains progcards_usb.exe
.
Progcards_usb
searches for
board description files that match the scan chain. All board descriptions
matching the first part of the chain are presented as a menu and you
can select the file to use.
progcards_usb
runs through the steps
required to completely reprogram the boards. The output is similar
to the example transcript is shown in Example 2.2.
To bypass programming a Logic Tile or the baseboard
select the Skip
option from the menu. progcards_usb
then
looks for board description files that match the next segment of
scan chain and so on.
Typically one menu is displayed for the Logic Tile and one menu is displayed for the platform baseboard. If only one board description matches your hardware, it is automatically selected and no menu is displayed.
After downloading the image completes, turn the power off and move the CONFIG switch to the OFF position.
Set the configuration switches to match the boot option you are using, see Setting the configuration switches.
Power on the board and use the Boot Monitor to load your application, see Using the baseboard Boot Monitor and platform library.
If you are not using the Boot Monitor, use a JTAG debugger to load and run an application. See the documentation supplied with your debugger for details.