GOP Update Tool (Ampere)
Tool to update the UEFI Graphics Output Protocol module in the graphics card firmware file.
Latest version
0.1.1
Supported models
NVIDIA Ampere micro-architecture and newer
Support platform
Windows 7 or later (some effects do not display properly in Windows 7)
*Requires PowerShell 2.0 and higher
Instructions
Use GPU-Z, NVFlash extraction or get the firmware file from the brand’s official support page, drag and drop the firmware file to the GOP Update Tool icon and follow the prompts to update it with the GOP module stored in the local directory.
Q&A
- No file input detected, please drag and drop the firmware file to the batch.
Please re-drag the firmware file or update package to the GOP Update Tool icon.
Since the drag-and-drop function of the Windows platform does not support paths containing some special symbols, please move the file to a directory that does not contain special symbols or enter GOP Update Tool path space firmware file or update package path on the Windows Command Line and press Enter to execute operate.
E.g :
"C:\Users\Your Name\Desktop\GOP Tools\GOP Update Tool.bat" C:\Users\Your Name\Desktop\GA106.rom
-
Please check the file size and try again.
Please check your firmware file size, the GOP Update Tool (Ampere) supports sizes ranging from 500KB to 2MB (2097152 bit).
If the firmware file meets the architecture requirements, the size should not be less than 976KB, otherwise your firmware file may be incomplete or corrupted.
Given the nature of the Ampere architecture that allows incomplete firmware to be written, the firmware size should be at least greater than 500KB. -
Missing available GOP module files, please confirm and try again.
Unable to find GOP module files from inventory directory, please keep files with .efi suffix and try again. -
Firmware read error, please check and try again.
Please close programs that may be using the firmware file or update package and check the file’s read permissions. -
Unsupported architectures (0x…) .
Firmware that does not support this architecture, for Turing architectures (0x500…) Please consider using the GOP Tools (Turing), and for AMD and earlier architectures, please consider using the GOP Updater. -
No GOP module detected.
The GOP module could not be detected from the imported firmware file. Some mobile platforms (laptops or tablets) use the integrated graphics card built into the CPU for video output and initialization, so the graphics card is not configured with the GOP function. -
Which version should I choose?
Comparing the versions, it is clear that in addition to the structural refactoring of the program in some specific versions, updated versions usually include additional code additions and modifications. From experience, we believe that this represents functional fixes or stability improvements to the original program in some cases. We recommend using the latest version on devices without compatibility issues for a better user experience.
In addition, there may be more than one version of the option that is similar and contains parentheses.
For example, 0x60012 (2504) with parentheses is the Device ID in the GOP parameters; the full Device ID is 10DE-2504, and those without parentheses correspond to 0000-0000.
The device ID in the GOP parameters does not affect the actual functionality, so there is no need to select the exact same device ID version as the device. -
Can I downgrade?
In theory, you’re free to change the version of the GOP module. However, considering the rarity of this requirement and factors such as device stability,This tool does not currently provide this feature. If you have such a need, please contact us. -
Why does the Device ID as 0000-0000？
Some firmware, especially OEM products, have not configured the GOP Device ID during compilation, and therefore use the default value of 0000-0000. -
The GOP module file suitable for version 0x… update was not found.
A GOP module file of the same size and newer than this firmware file could not be found in the current directory, the firmware may already have the latest GOP version for the current technology.
If you want to check for updates manually, you can find the latest released firmware file for a card with the same architecture from the brand or the official support page of the TechPowerUp and check for a higher version using the Extraction and Normalization tool. -
The required file was not found, please confirm and try again.
The required GOP module file is missing, close the program that may have deleted this file and try again.
For Lite mode, check if the original reference file for the EFI module file is missing. -
Cache verification failed, please close unnecessary programs and try again.
The temp\FW2 cache file created by the GOP Update Tool has been modified, please close the program that may have modified this file or folder and retry.
Also, do not run multiple instances at the same time. -
Firmware export failed, a file with the same name already exists.
A firmware file with the same name as the exported file already exists, if you have already performed the update and need to do it again, manually delete the original update file and perform it again. -
Firmware update failed due to unknown error.
The firmware file encountered an error during the update process and failed to validate, please check your Powershell platform version and environment configuration and retry.
If you are still experiencing this issue, please contact us. -
What is Lite Mode?
A storage space-saving solution that contains only digital signatures and parameters and no GOP content. When in use, the GOP Update Tool (Ampere) calls the same version of the file that contains the GOP content to process the firmware. -
Can module files built in using the Extraction and Normalization Tool (Turing) or GOP Updater be used in this release?
Module files extracted using other versions cannot be used in this release. This release introduces support for digital signature extraction in response to feature changes in the ampere and update architectures, and GOP module files extracted using other tools or previous releases do not contain digital signatures and therefore cannot be validated.
Conversely, updating GOP module files extracted by the Extraction and Normalization Tool (Ampere) using the GOP Update Tool (Turing) or the GOP Updater will also result in an error, as digital signatures are not required for GOP modules in the Turing Architecture and previous versions. -
What are the differences from previous versions?
No more update support for non-firmware files such as update packages.
No support for modified GOP module files.
No support for updating to a different sized GOP module.
New lite mode.
Added support for digital signatures.
Added support for updating or extracting non-complete firmware.
…