2.9.1. Board files

The CD includes both the progcards programming utilities and the images to load into the FPGAs and PLDs. See the Application Note on the CD for the combination of Core Tile that you are using.

Naming conventions for board files

The file name of a board file identifies the PCB, Core Tile, all programmable devices, and revision. Using the board file eliminates the need to load several individual image files. All file names are in lower case with an underscore character separating the fields:

appnote_boardname_number_core_endian_build_devicelist.brd

Where:

appnote

The application note related to this board file.

boardname_number

The name and number identify a specific development board. For example, eb_140c is for the baseboard that uses PCB board HBI-140C.

Note

The full board number is HBI-XXXXR, this is abbreviated to just the significant digits and revision, for example, HBI-0140C becomes 140C.

coretile

The name of the Core Tile that is used with this configuration. For example, ctmpcore_li identifies the CTMPCore Core Tile operating in little-endian mode.

Caution

Ensure that you use the board file that matches your system configuration.

buildn

The build number. The number n increments from 0

devicelist

The name of the programmable devices that are specified in this file.

Naming conventions for image files

The images files contain the image for a single FPGA, PLD, or programmable memory device. The file name of an FPGA or PLD image file identifies the PCB, device and revision. All file names are in lower case with an underscore character separating the fields:

boardname_number_devicename_device_buildn.extension

Where:

boardname_number

The name and number identify a specific development board. For example, eb_140c is for the baseboard that uses PCB board HBI-140C.

devicename_device

The name of the programmable devices that match this file. For example, cfg_xc2c128 identifies the Xilinx XC2C128 configuration PLD.

buildn

The build number. The number n increments from 0

extension

The type of device used by this file. For example .svf is for PLD programming and .bit is for FPGA programming file

Caution

The baseboard is supplied with the PLD images already programmed. The information in this section is provided, however, in case of accidental erasure of the PLDs.You are advised not to reprogram the PLDs with any images other than those provided by ARM Limited. The JTAG routing PLD is pre-programed at manufacture and does not appear in the programming scan chain.

Using the board file to control image file loading minimizes the risk of incorrectly programming the board. The board files contains a list of correct image files and eliminates the requirement to select individual image files for the programmable devices on the baseboard or attached Core Tile or Logic Tile.

Copyright © 2005-2011 ARM Limited. All rights reserved.ARM DUI 0411D
Non-Confidential