Home > Troubleshooting > CONFIGURATION MANAGEMENT
New firmware is being posted in the download area of the ComBlock web site. How can I verify that the version loaded in the ComBlock is current?
The FPGA firmware version and option can be read
using the ComBlock Control Center software. Highlight the module of interest and
select the properties windows. In the lower part of the window, the option and
version of the firmware currently loaded in the ComBlock FPGA are displayed. The
1-byte code is as follows:
version 0 - 9 -> shown as 0 - 9
version 10 -> shown as 'A'
version 11 -> shown as 'B'
etc...
Is it possible to accidentally load the wrong firmware file in a ComBlock?
Yes. Do not panic: no damage can occur. However, the wrong firmware may inhibit any further communications with the module. If this happens, take the following steps:
COM-1XXX, COM-8XXX, COM-11XX: one should turn the power off, hold a wire between a ground pin and the INIT test point and hold the wire for 10 seconds while turning the power back on. This procedure prevents the FPGA from being configured. Then reload the correct firmware using the ComBlock Control Center.
COM-12XX, COM-14XX: one should turn the power off, place a jumper between the BOOT and +3.3V pins and hold the jumper in place for 5 seconds while turning the power back on. This procedure loads the default configuration (personality 1) into the FPGA and restores all means of communication. Then use the ComBlock Control Center to reload the correct firmware and set the desired default personality.
COM-13XX: one should turn the power off, short the pins A20 and B20 for 5 seconds while turning the power back on. This procedure loads the default configuration (personality 1) into the FPGA and restores all means of communication. Then use the ComBlock Control Center to reload the correct firmware and set the desired default personality.
After downloading new firmware into a ComBlock, the ComBlock Control Center does not recognize all the blocks in the assembly. Why?
The firmware download may not have been successful. If so, the module to be upgraded is now unable to communicate with other ComBlocks.
Case 1): the DONE test point is low. In this case, the FPGA configuration stored in Flash memory is likely to be corrupted.
Case 2): Custom firmware: the FPGA .mcs
configuration file was created with no constraint file (.ucf) or with an
erroneous .ucf file. The FPGA pinout is wrong, thus preventing communication.
Remedy: add the .ucf constraint file to the ISE project and redo the translate,
map, place and route steps.
For COM-1XXX, COM-8XXX or COM-11XX, please connect a serial link directly to
that module and reload the firmware. For COM-12XX, COM-14XX, please follow the
jumper method described above.
How to create a .mcs FPGA configuration file for a custom Xilinx project (for use on a FPGA development platform)?
Step-by-step instructions are listed in the following documents: Creating a mcs file using Xilinx ISE.pdf