MVX-A16 MKII/MKIII Xilinx iMPACT FPGA upgrade failure - ".cfi does not exist"

When using Xilinx iMPACT to program the FPGA of an MVX-A16 MKII/MKIII, the process can fail and report that a .cfi file does not exist.

 

If you encounter this issue, follow the steps below to program the FPGA successfully.

CPU cards must be removed from the frame during this upgrade

When the iMPACT software is started, it will ask if you want to automatically create and save a project.

Click Yes.

 

Select ‘Configure Devices using Boundary-Scan (JTAG)’ and ‘Automatically connect to a cable and identify Boundary-Scan chain’

Click OK.

 

iMPACT will now initialize the JTAG chain and the devices will be displayed in the Boundary-Scan window.

iMPACT will ask if you want to assign configuration files. Click No.

 

The Device Programming Properties window will now pop up. Click Cancel.

 

Right click on SPI/BPI and select the .mcs upgrade file.

 

Select ‘SPI PROM’ and ‘S25FL032P’.

Click OK

The console will still report that the .cfi file does not exist but should continue to program without issue.

 

Windows Environmental Variable must be set to skip device ID check. https://clear-com.atlassian.net/wiki/spaces/SF/pages/213385233

 

Impact version 14.7 (nt64) ,  Windows 10

Environmental variable set XIL_IMPACT_SKIPIDCODEC… = 1

CPU cards must be removed from the frame during this upgrade

 

CAN'T FIND YOUR ANSWER? CLICK HERE TO CONTACT SUPPORT


This solution was provided to you by Clear-Com via a question submitted to us by customers like you. If your question wasn’t answered, you need help or you have a recommended solution for our database, please send us an email at support@clearcom.com

The information on this page is owned by Clear-Com and constitutes Clear-Com’s confidential and proprietary information, may be used solely for purposes related to the furtherance of Clear-Com’ business and shall not be disclosed, distributed, copied or disseminated without Clear-Com’s prior written consent. Click Here for Clear-Com's privacy statement.