Programming AMC13 Flash with AMC13ToolFlash

These instructions are for initial programming of the AMC13 or for recovery of AMC13 after flash has been corrupted. This tool is not meant for typical firmware updates of a working AMC13. Firmware update should follow instructions using AMC13Tool2: AMC13Tool2Recipes. Flash sectors should be programmed using the latest firmware for all sectors.

Environmental variable AMC13_ADDRESS_TABLE_PATH set to the directory with AMC13 address tables (same path as for AMC13Tool2)

Programming instructions:

To get firmware for both the Spartan and Kintex chips download the latest '.mcs' files from here. The firmware database is the easiest place to find the most up to date versions for any chip type. Match mcs files with the chip type on your card for T2 (lx25t vs lx45t). Put the firmware files in your current directory (the tool searches the current directory for files).

Running the AMC13ToolFlash

Run the Flash Tools using:

$ AMC13ToolFlash.exe -c 55/c -f pa

The -c option can either be an IP address or a serial number. Also /c can be used for control hub.

The flash command to execute is given by the -f option. Here "pa" means program all which will program all four sectors. Other options for programming just one sector or verifying sectors are available. Use --help to see all options.

More options such as listing firmware and reloading flash are available and outlined with --help.

After pressing enter a prompt will appear to pick a mcs file located in your current directory like below:

Input the number corresponding to the mcs file you want to use from the prompt. Here the command is Verify Flash Header (-f vfh) so there is only one file, but multiple files will show up if more than one version is in the current directory.

Once you have all sectors programmed, run the flash tool again with the -r option to reload the flash memory (or power cycle the board):

AMC13ToolFlash.exe -c SN/c -r

(NOTE: Do NOT power cycle board until all sectors are programmed successfully, do so will erase the any bit files programmed to T2 and will attempt to apply the firmware currently in flash, which can cause errors if there is nothing available from a given flash sector).

The flash sectors should be programmed in the following order if not using the pa option: