FPGA DEVICES · ENGINEERING · SOURCING Source-linked information. Clear project requirements.

Tutorials

Artix-7 Flash Update Interrupted: Choose a Recovery Path

Published · Updated

After an interrupted Flash update, first establish what is still accessible. A working recovery image, an available external programming interface and preserved unique data lead to different next steps. Do not begin every recovery case with a full-chip erase.

Record what survived the interrupted update

Current evidenceCurrent evidenceLast logGolden responseJTAG discoveryRead with the conditions in this section.
Current evidence: Last log / Golden response / JTAG discovery.
XC7A100T FPGA with FGG484 package marking on a populated board
Device identification: XC7A100T FGG484. S03311251 / Wikimedia Commons, CC BY-SA 4.0, unmodified. The photo does not show or verify the CSG324 variant, Flash compatibility or a programming connection.

Preserve the last programming log, selected image identity, target board revision and the point at which power or communication was lost. Record observations separately from assumptions: a disconnected client is not proof that the memory operation stopped at the same instant.

Use the board's documented power and connection procedure to inspect the current state. Record whether a recovery image actually responds and whether the expected target can be discovered through JTAG. Leave either result unknown until it has been observed.

Keep relevant configuration-status and pin observations with their capture time. Avoid mixing a current failure with a screenshot from a previous successful boot.

First separate flash boot from JTAG; a successful temporary load does not prove recovery.

If the symptom is intermittent, repeat the startup check under recorded conditions instead of accepting one successful cycle.

Choose a recovery image or external access

Recovery routeRecovery routeKnown recovery imageApproved external jobAccess diagnosisRead with the conditions in this section.
Recovery route: Known recovery image / Approved external job / Access diagnosis.

If the product's recovery image is confirmed to be running, follow that product's approved recovery procedure. If it is unavailable but the documented external programming route works, prepare the corresponding controlled reprogramming job. If neither path has been established, the next task is board-level access diagnosis rather than guessing a write command.

A recovery procedure published for an Alveo-based appliance can illustrate clear checkpoints without providing commands for an Artix-7 board. The same caution applies to automatic-update descriptions from other FPGA families. Identify the exact architecture before applying a procedure.

Do not treat successful JTAG discovery as permission to overwrite every memory region. It proves a useful access path, not the correct image or erase scope.

Preserve the failed attempt, then capture configuration status according to the board procedure.

Define what may be erased or replaced

PreservationPreservationRecovery regionUnique dataPermitted write rangeRead with the conditions in this section.
Preservation: Recovery region / Unique data / Permitted write range.

Confirm the approved image, intended destination and regions that must survive. Calibration, unit identity and the recovery image may have separate preservation requirements. Record whether a reliable backup exists and whether the board's procedure permits reading or restoring that information.

Review the actual erase granularity and programmer range. Byte-separated images can share an erase unit. A recovery operation that restores the application but destroys required per-unit data is not a successful product recovery.

If image protection or access restrictions affect the procedure, use the approved product-specific path. Do not add generic security-reset or provisioning commands to a recovery checklist.

To narrow the startup phase, observe configuration pins and timestamp the observation.

Verify through an independent boot

AcceptanceAcceptanceMemory verificationIndependent startupRuntime + functionRead with the conditions in this section.
Acceptance: Memory verification / Independent startup / Runtime + function.

After the permitted rewrite and its required verification, perform the specified independent startup procedure. Obtain a fresh running-build observation where the design supports it and execute the required application checks. A temporary design loaded over JTAG does not establish persistent recovery.

Keep the interrupted attempt and recovery attempt as separate records. Note which image was restored, which regions changed and which acceptance tests were actually completed. Preserve unresolved checks rather than collapsing everything into a single restored label.

The recovery worksheet exports the current evidence, candidate path and stopping conditions. It does not connect to hardware or promise that a board is repairable. Use the report, exact board identity and sanitized log when requesting engineering assistance.

Evidence obtainedWhat remains unresolved
Expected FPGA appears over JTAGStored image and persistent boot
Temporary JTAG design runsFlash contents and independent startup
Memory verification completesBoot selection, startup and application behavior
Independent boot reaches expected buildAny application tests still required by the product

After a permitted rewrite, confirm the recovered build from the actual running design.

Technical references for this scope: AMD UG470 v1.17 (2023-12-05); AMD UG908 2024.1 — Programming a Configuration Memory Device.

Highlight the three review items

Each highlight marks one item to review, not elapsed hardware time. The static figure contains the same information.

Review-item highlight: Acceptance

Enable JavaScript for the local Interrupted-update recovery triage. The article above provides the manual procedure; no data is submitted automatically.

Review and export your result before opening the engineering discussion entry. Attach the exported text yourself; opening the entry does not submit it.

Reference scope checked 15 November 2026. Calculations and conceptual diagrams describe the stated model. Commands and board behavior require validation in the actual tool and board environment.

Back to Tutorials →

Related evidence and next tasks

Continue the task with the relevant source scope. These reading paths do not establish interchangeability or current supply.

Source addresses and citation trail

Full source addresses are retained below. Read each citation with its document revision, page, table and applicability conditions above.

  1. https://commons.wikimedia.org/wiki/File:Xilinx_Artix7_XC7A100T_FGG484_on_PCB.jpg
  2. https://creativecommons.org/licenses/by-sa/4.0/
  3. https://docs.amd.com/api/khub/documents/FOs3lXmlcWxBhTIFxVKyGA/content
  4. https://docs.amd.com/r/2024.1-English/ug908-vivado-programming-debugging/Programming-a-Configuration-Memory-Device