DMA Firmware Maintenance After Game and Driver Updates

Firmware maintenance is a process, not a promise that a single file will work forever. Game, Windows and driver updates can change the surrounding environment, so a documented check is safer than immediately flashing a new image.
Before updating
Save the current firmware version, JTAG identity report, tool version and a known-good configuration. Note the date and the software update that triggered the review. These details create a baseline for comparison.
After updating
- Reboot and confirm that the board is visible to the expected driver.
- Run a read-only JTAG identity check.
- Compare IDCODE, DNA and configuration status with the baseline.
- Run the documented data-path test without changing firmware.
- Record the result and any error text.
When to pause
Pause if the target changes, the JTAG chain is incomplete, the programmer reports a different device or the release notes are unclear. Do not use a random image as a workaround; it can make diagnosis harder and remove a known-good rollback path.
Send the before/after logs to the NAPOLEON team on Discord for a documented compatibility check.
