A dependable FPGA programming workflow starts with more than selecting a bitstream and clicking Run. The programmer must communicate over the correct cable and port, represent the physical JTAG daisy chain accurately, and apply settings that match the target device and memory type. For engineers and system integrators commissioning or maintaining FPGA-based equipment, these checks help make device configuration more deliberate and repeatable.
Gowin Programmer provides a project-based environment for configuring and downloading data stream files to supported FPGAs. Its interface centers on a device table and an output panel: the table describes the chain and programming operations, while the output panel reports errors, warnings, and other information. Exact menus and supported devices can vary by software release, so users should confirm settings against the version installed and the current device documentation.
Build the FPGA programming workflow around the hardware
Programming transfers a data stream to an FPGA’s SRAM, embedded flash, or external flash through a download cable. Before configuring an operation, install the required downloader and driver, connect the cable, and confirm that the target hardware is powered and connected as intended. The cable settings include cable type, available port, and download frequency. The software can detect connected cables and select an available port; frequency is selectable from the options provided by the installed version.
Next, create a project for the programming configuration or open an existing one. An existing project is useful only if its cable and chain settings correspond to the current physical setup. Opening or creating a project closes the current project, so save any configuration that needs to be retained before switching.
Configure and verify the JTAG daisy chain
The device table represents the devices that will be addressed in the chain. The programmer can scan a connected chain and list detected devices in chain order. Where scanning does not identify a device unambiguously—for example, when devices share an ID—the device selection may need to be specified manually.
Compare the software’s device order with the actual hardware connection before programming. The table also allows devices to be added, removed, or moved up and down. This is useful when building a configuration manually, but the resulting order must still reflect the physical chain. Each row includes device information and programming fields; some fields are editable, while others display configuration details such as the selected operation, checksum, user code, or ID code.
The Enable setting determines whether a device is included in programming. A disabled row is treated as not being in the chain and is grayed out. Before configuring pins, security, or download operations for a device, make sure it is included as required. Once the chain is configured, use the available configuration-check function to identify issues before running the download.
Select the programming mode for the target device
Device configuration defines the access mode, operation, and programming file, where applicable. The available choices depend on the device and intended use. Common options include:
- SRAM mode: Operations include reading the ID code or status register, bypassing the device, reprogramming, and programming SRAM. A program-and-verify operation is also available. For JTAG-NOOP configurations, the instruction-register length may need to be specified or obtained from a BSDL file.
- Embedded flash mode: This applies to the GW1N(R) series identified in the guide. Available operations include erase and program, erase-program-verify, and erase only. The guide notes that GW2A/GW2AR devices do not support this mode.
- External flash mode: Configuration includes selecting the external flash device and a start address, as well as choosing an erase, program, verify, or erase-only operation where supported. The documented minimum address unit is one sector, or 4096 bytes.
Check the selected operation and file together. A programming file is required for operations that program data. For external flash, the device model and start address are additional configuration items. The guide also specifies that non-boundary-scan operation requires config-mode pins [2:0] to be set to 011; confirm that this requirement applies to the target setup before proceeding.
Review pin states and security settings carefully
The I/O State Editor lets users set device pin values before running a download. It uses a BSDL file corresponding to the device model and package. Pin states can be changed individually or, where appropriate, set for multiple pins together. Selecting the matching BSDL file is an important part of making the pin configuration relevant to the actual device.
Encrypted bitstream programming may also require writing the bitstream key to the FPGA. The documented key is 128 bits, begins in a zero state, and uses non-volatile one-time-programmable fuses: a bit written as 1 cannot be changed back to 0. Locking prevents subsequent key reading or writing. Because this action has lasting consequences, verify the intended key and security state before applying it. The programmer reports when a key is locked, and the security configuration is then unavailable.
Save, check, and run the download
A practical sequence for programming is:
- Set the cable type, port, and frequency.
- Create or open the project and confirm it matches the connected setup.
- Scan the chain or configure its devices manually, checking their order and enable states.
- Set each device’s access mode, operation, programming file, and any required flash or pin settings.
- Review security settings where encrypted bitstreams are used, then run the configuration check.
- Save the project configuration and execute the download.
After the operation, review the output panel for the reported result, errors, and warnings. The project file preserves the cable and daisy-chain configuration, providing a reference for later programming sessions. A separate file converter is available to convert raw .fs data stream files from ASCII text into binary data stream files.
Conclusion
Reliable FPGA device programming depends on aligning software settings with the real hardware: cable, chain order, target device, memory mode, and programming file. Checking these elements before download—and treating one-time security fuses with particular care—helps engineers and operations teams manage configuration tasks with fewer avoidable setup errors. Keep project files and device-specific documentation aligned with the software version in use, since programmer interfaces and supported options may change.