Programmer Messages
The following section lists warning and error messages that the software may display and explains how to fix them.
| Message | on_program Device is not available |
| Reason | 1. Board not connected or powered off. 2. USB driver is not
installed. |
| To fix | 1. Connect board to host and power on the board. 2. Install USB
driver. |
| Message | USBError(2, 'Entity not found') |
| Reason | USB driver is not installed. |
| To fix | Install USB driver. |
| Message | *Cannot get JTAG url, Please check your board profile configuration*int() argument must be a string, a bytes-like object or a real number, not 'NoneType'--(idcode=None) |
| Reason | USB driver is not installed in interface 1 (JTAG). |
| To fix | Install USB driver for interface 1. |
| Message | ERROR: Incompatible file extension for programming mode, please use .bit file for JTAG programming |
| Reason | JTAG chosen as programming mode but .hex file specified in bitstream file. |
| To fix | Specifiy correct the .bit bitstream file. |
| Message | ERROR: Incompatible file extension for programming mode, please use .hex file for SPI Active programming |
| Reason | SPI Active chosen as programming mode but .bit file specified in bitstream file. |
| To fix | Specifiy correct the .hex bitstream file. |
| Message | ERROR: Incompatible file extension for programming mode, please use .hex file for SPI Passive programming |
| Reason | SPI Passive chosen as programming mode but .bit file specified in bitstream file. |
| To fix | Specifiy correct the .hex bitstream file. |
| Message | ERROR: Incompatible file extension for programming mode, please use .hex file for SPI Active using JTAG Bridge programming |
| Reason | SPI Active using JTAG Bridge chosen as programming mode but .bit file specified in bitstream file. |
| To fix | Specifiy correct the .hex bitstream file. |
| Message | ERROR: Incompatible file extension for programming mode, please use .hex file for SPI Active x8 using JTAG Bridge programming |
| Reason | SPI Active x8 using JTAG Bridge chosen as programming mode but .bit file specified in bitstream file. |
| To fix | Specifiy correct the .hex bitstream file. |
| Message | ERROR: Check board is plugged in, and then click on "Refresh USB Targets" |
| Reason | Board disconnected or powered off during programming. |
| To fix | Reconnect the board and click the refresh button. |
| Message | Image file not found |
| Reason | Bitstream file not loaded. |
| To fix | Load the bitstream file. |
| Message | Failure to configure was detected |
| Reason | Programmer internally failed to enter configuration mode. |
| To fix | Program again. |
| Message | Unable to configuire from flash device. |
| Reason | JTAG state failed to enter USER mode. |
| To fix | Reprogram the bitstream. |
| Message | Unable to determine status of device. |
| Reason | 1. JTAG programming in unknown state; potentially hardware issue. 2. Different width
chosen to program the bitstream file. For example, the bitstream is x1
width but SPI Active x8 is chosen. |
| To fix | 1. Try to reprogram the bitstream. If using C323HM cable, check the
connectivity. 2. Choose the correct width or run the bitgen
again. |
| Message | ERROR: Flash verify unsuccessful... mismatch found |
| Reason | 1.Programmed flash does not match with the selected bitstream.2. The board does not support the selected verify method. |
| To fix | 1. Reprogram the bitstream.2. Select "Normal verify." |
| Message | ERROR: Unable to verify JTAG interface, cannot determine configuration status |
| Reason | JTAG mode used to program the board, but JTAG interface 1 is unstable or the JTAG connection using C2323HM is incorrect or disconnected. |
| To fix | Check the driver for the JTAG interface or check the wire connection. |
| Message | ERROR: Unknown error trying to read flash device, aborting. Aborting flash programmingFtdiProgram error: could not get flash device |
| Reason | Attempted to program the board via SPI Active or SPI Passive while interface 0 (SPI) is disabled. |
| To fix | Check the driver for the SPI interface. If it is unsupported (using C232HM), then it is not possible to program with SPI. |
| Message | FtdiProgram error: Device is in CONFIGURATION_FAIL state instead of user mode after programming JTAG Bridge Image! |
| Reason | Wrong or incomplete JTAG Bridge image specified. |
| To fix | Specify the correct JTAG Bridge image. |
| Message | Unsupported JTAG Bridge version: 0.0. Please choose the latest bundled JTAG Bridge image and then try again., aborting flash programming FtdiProgram error: |
| Reason | Used an older or unsupported version of the flash loader. |
| To fix | Use the supported version of the flash loader. |
| Message | ERROR: JTAG Bridge Image not found. Please specify correct file path.- ERROR: File = "" |
| Reason | JTAG Bridge image not specified when SPI Active using JTAG Bridge is selected as programming mode. |
| To fix | Specify the correct JTAG Bridge image. |
| Message | ERROR: Invalid speed entered, please only input numbers |
| Reason | Invalid character entered for Custom JTAG Clock Speed. |
| To fix | Use a numerical speed value. |
| Message | ERROR: Invalid speed entered, out of range, please enter a number between 1000 and 30,000,000" |
| Reason | Invalid character entered for Custom JTAG Clock Speed. |
| To fix | Use a valid value between 1000 and 30,000,000. |
| Message | ERROR: The FPGA given in the bitstream file does not match the FPGA you are trying to program. Check that you are using the correct bitstream file. |
| Reason | Wrong bitstream file specified for the board in use. |
| To fix | Specify the correct bitstream file. |
| Message | Detected 4Byte flag in bitstream but flash is smaller or equal to 16MiB Aborting flash programmingFtdiProgram error:Detected 4Byte flag in bitstream but flash is smaller or equal to 16MiB |
| Reason | 1. Erase or read flash attempted with a starting flash address greater than the flash
capacity. 2. Erase length specified greater than the flash
capacity. |
| To fix | 1. Specify the correct starting address. 2. Specify the correct length. |
| Message | ERROR: Unable to retrieve flash status Check board is plugged in, and then click on ""Refresh USB Targets"" Unrecognized Flash device. Will use Generic Flash profile. Please contact support if you face any problem. |
| Reason | Programmed bistream contains an incorrect or mismatched header with the board. |
| To fix | Verify that the bitstream header is correct. |
| Message | ERROR: Export SVF feature is disabled for T8/T20 bitstreams |
| Reason | T8 or T20 bitstream exported to SVF. |
| To fix | SVF is not supported for T8 or T20. |
| Message | ERROR: Cannot edit SPI Active clock settings for .bit file, please use the .hex file |
| Reason | Opened Edit SPI Active Clock on a .bit file. |
| To fix | Edit SPI Active Clock only works for .hex files. |
| Message | ERROR: Input file has been corrupted, unable to determine target device |
| Reason | Opened Edit SPI Active Clock on a corrupted .hex file. |
| To fix | Replace the corrupted .hex file to a valid one. |
| Message | ERROR: Unable to read input image file, file maybe have been corrupted |
| Reason | Opened Edit SPI Active Clock on a corrupted .hex file. |
| To fix | Replace the corrupted .hex file to a valid one. |
| Message | ERROR: Device code for JTAG Bridge image CANNOT be Unknown. Please ensure you are using correct bitstream file |
| Reason | 1. Programmer is unable to detect the device code. 2. Connectivity issue. 3. USB
driver missing for the JTAG interface. 4. Programmer is unable to
detect non-Efinix device. |
| To fix | Ensure there is a valid device ID at Device Select. |
| Message | ERROR: Export feature only works with Efinity bitstreams |
| Reason | Export failed because the bitstream is not originally from Efinity. |
| To fix | Bitsream exports not originally from Efinity are not supported. |
| Message | ERROR: Cannot detect JTAG chain setup. Please import JTAG chain file |
| Reason | Programmer is unable to detect non-Efinix device. |
| To fix | Import the JCF. |
| Message | Calculated IR width is invalid. Please import JTAG chain file |
| Reason | A board in the chain is powered off. |
| To fix | Power on the board and click the refresh button. |
| Message | Total IR width of the previous JCF does not match actual total IR width. Please import JTAG chain file again. |
| Reason | Programmer is unable to detect non-Efinix device and cannot auto-detect IR length of the board in the JTAG chain. |
| To fix | Import the JCF. |
| Message | ERROR: The Programmer cannot detect the FPGA in the JTAG chain. Check the JTAG cable or header for connectivity issues |
| Reason | Incorrect connection of the chain or improperly connected wire. |
| To fix | Check the wire connectivity and check the IDCODE through the SVF Player. |
| Message | ERROR: Invalid ASCII character detected in header, cannot display header text |
| Reason | Bitstream header is incorrectly formatted. |
| To fix | Run the bitstream again to generate a new bitstream. |
| Message | ERROR: JTAG chain file does not match XSD standard |
| Reason | The JCF file in the wrong format. |
| To fix | Fix the format of the JCF. |
| Message | Error occured. OpenocdNotRunning("An error occurred when waiting for response from the main loop. OpenocdNotRunning('Failed to add a user due to: OpenOCD Error: no device found; Return code: 1')") |
| Reason | Occurs in co-debug mode when the board is disconnected and reconnected. |
| To fix | Close and re-open the Programmer. |
| Message | Failed to detect number of JTAG TAP. JTAG chain connection may be broken or number of TAP is greater than 128 |
| Reason | Failed to auto-detect the board in the JTAG chain. |
| To fix | Import the JCF. |
| Message | ERROR: Invalid output file <file name> specified for image generation |
| Reason | Name of the output file not specified when using Combine Multiple Image Files. |
| To fix | Specify the file in Output File. |
| Message | ['', '', '', '']ERROR: All input files for image generation must be targeted to the same device |
| Reason | 1. No file added to the field at Combine Multiple Image Files. 2. Image mixed with a
different target device. |
| To fix | 1. Add at least one image to use the tool. 2. Only the same targeted device bitstream file
can be used to combine the image. |
| Message | ERROR: Flash address '' is not a valid hexademical number |
| Reason | Flash address unspecified or incorrect at Generic Image Combination. |
| To fix | Specify the flash address in the correct hexadecimal format. |
| Message | ERROR: No input files for image combination |
| Reason | No input file specified for the image combination at Generic Image Combination. |
| To fix | Specify at least one image. |
| Message | ERROR: First flash address '0x00380000' is not equal to 0x00000000 |
| Reason | First flash address specified at Generic Image Combination does not start with 0. |
| To fix | For the first image, the flash address must start with 0. |
| Message | ERROR: Flash address '0x00000000' should be greater than or equal to next availableflash address '0x00121000' |
| Reason | Second or later flash address specified at Generic Image Combination starts with 0. |
| To fix | For the second and later images, the flash address cannot start with 0. |