BIOS Flash Tools - HowTo
BIOS Flash Tools - HowTo
BIOS Flash Tools - HowTo
Windows
Update
Recovery
EFI
Linux Transfer
Version 2.0
BIOS Flash Tools
Revision History
Date Version Notes
26.04.2022 2.0 Added information about ProductName in Deskflash archive file
Moved and updated some information from chapter “Technical Background” to “General
03.12.2021 1.9
Notes and Infos”, Moved “Download Location of Tools to “Upgrading/Downgrading”
Added chapter “Download locations”, Updated Linux driver and tool installation chapters.
14.10.2021 1.8
Added “Content of typical BIOS update package”
13.09.2021 1.7 Updated chapter “Recovery” – Added typical pin outs for recovery jumper.
Renamed chapter “EfiFlash for EFI (D35xx or newer) to “BIOS Update Utility in
09.08.2021 1.6 Bootmenu”. Adjusted chapter order. Updated description. New section “System
Requirements”.
29.06.2021 1.5 Updated first page
19.01.2021 1.4 Updated section 5.4.3 and 5.5.3 – Commandline option /O
15.04.2020 1.3 Updated section 5.2.1 – creating a FreeDOS bootable device
06.03.2020 1.2c Updated section 6: Moved the red marked hint from chapt.6 to 6.2
29.01.2020 1.2b Updated Efiflash.efi section – Location of the tool
24.01.2020 1.2a Updated section 1 and 5.5 – driver FUJ04x0 necessary for Deskflash
Re-Ordered file extension table, Updated Efiflash for EFI section, Added Efiflash in EFI
Shell chapter. Updated “Transfer BIOS settings” with Efiflash in EFI shell. Updated FTP
22.01.2020 1.2
links and changed design to Kontron. Moved Version-Information from Filename to
Fileheader.
31.08.2018 1.1 Added chapter Deskflash for Windows (CoffeLake) and updated Archive chapter.
22.06.2018 1.0 First released version (some content based on “Efiflash HowTo 1.2”)
Please always check for updated available version of the flash tools.
Please check System Requirements and General Notes and Information chapter first!
Still, since the term BIOS is well established, it is generally used to refer to the UEFI firmware, and both
terms are used interchangeably.
On Legacy BIOS systems, BIOS Setup settings used to be saved in a battery buffered memory region of
the main chipset commonly referred to as “CMOS”. With UEFI, these Setup settings are saved in the
same flash memory chip as the main BIOS, in an area called NVRAM. Thus, on many UEFI systems,
clearing the CMOS, for example by removing the CMOS Battery for a while, will not reset the Setup
settings. Please refer to the BIOS Recovery procedure description for how to reset the Setup settings on
those systems.
Some tools have additional drivers integrated (e.g. Fujitsu/Kontron GABI BIOS Interface driver - FscGabi) and
install them temporarily if needed.
For D371x motherboards a driver installation kit will be available, which installs all Kontron specific
motherboard drivers (e.g. FUJ0430, FSCGABI, SystemMonitoring) at once.
Download it from FTP server: ftp://ftp.kontron.com/Products/Motherboards/0_Drivers/
“SMS Driver Installer_V5.x.zip” [tbd]
SMS (“System Management Suite”) driver kit is only released for D371x-V/R boards. It may work with
CoffeeLake or earlier, but was not tested with them!
Installing the precompiled driver on RHEL and SLES distribution (only V1.xx packages):
1) Extract the tar.gz package and run kmp_installer.sh to install drivers.
Start drivers:
It is necessary, to load the driver modules by hand. Use sobcontrol start.
Sobcontrol script is located in /opt/deskview/[deskflash|biosset]/device/ path if Biosset or
DeskFlash RPM package was installed before. Otherwise copy sobcontrol from driver_src-
xxxx.tar.gz.
During a BIOS upgrade or downgrade, all BIOS Setup settings, as well as all customizations (like custom
boot logo, MS licensing data, …) are kept. It is not necessary to load setup defaults afterwards.
All mentioned BIOS update tools are only preparing the BIOS update process, e.g. writing the BIOS
content to memory and set the flag for BIOS Capsule update ready. The actual BIOS update process will
be executed during POST with the “Capsule Update” mechanism of UEFI BIOS.
In very rare cases it could be necessary to load default values after BIOS flash, e.g. if you have problems
after BIOS flash or some internal BIOS settings have changed. They will only take effect after loading BIOS
default values manually. If you have customized the BIOS settings with EditCMOS/Biosset, these settings
will be loaded.
You can update the BIOS versions in any sequence. So when going for example from 1.1.0 to 1.3.0, you
do not need to flash 1.2.0. before flashing 1.3.0.
In very rare cases, a new BIOS version might require a certain minimum BIOS version to be present.
Occasionally the changes in new BIOS versions are so huge that downgrading to very old BIOS versions is
not possible any more. The BIOS Update's description text file will explain such requirements and
limitations. The flash tool will give a warning and will not flash the BIOS in such cases.
After upgrading / downgrading the BIOS, the motherboard MUST be restarted before additional BIOS
changes or settings can be applied. EFIFlash / DskFlash / deskflash will automatically issue a reset or
power cycle at the end of the flash procedure. For boards with BIOS Capsule Update mechanism the
reboot will be initiated automatically.
For Deskflash Archive restore it is mandatory, that the archive is created on a system with the same
“Product Name” as the target system. An archive with ProductName “Example1” cannot be flashed to a
system with ProductName “Example2”. Error message of Deskflash in this case: “Invalid or missing File –
Return code 8”
Here are explanations for the most commonly used EfiFlash command line options:
/? Display possible options. The possible options will also be shown when calling
efiflash.exe without any option.
/U Update only if file contains a newer BIOS version than the one that is
currently active.
/D Update only if file contains a different BIOS version than the one that is
currently active.
/Y This makes EfiFlash not ask for confirmation, but automatically assume an
answer "Yes" for all user prompts.
/LAST_CAP_STATUS Returns Capsule Flash update status from the previous attempt.
/LOG Displays the history of previous BIOS flash operations, listing the BIOS version
used, the type of flash update, and the date/time of these BIOSes' creation.
Please note that the date/time when the BIOS was flashed is NOT shown
because it is not logged. The type of flash update can be one of the following:
TOTAL = This BIOS had been programmed at the Kontron factory
UPDATE = normal flash update
ARCHIVE = Archive flash update
/ARCHIVE This creates a BIOS archive file (*.arc). Please see the chapter "Transferring
BIOS Setup settings, defaults and other BIOS customizations (Archive)" for
details.
Errorlevel Meaning
0 Terminated normally, everything went OK
6.6.1 Preparing the USB stick with an EFI shell environment [updated v1.8]
EfiFlash.efi can be used in two modes: As Boot menu utility (see chapter “BIOS Update Utility in
Bootmenu”) or as a stand-alone EFI shell tool. In stand-alone mode, you are able to script your
workflow.
Here are explanations for the most commonly used EFIFlash command line options*:
/? Display possible options. The possible options will also be shown when
/HELP calling efiflash.efi without any option.
*Note: The mentioned commands are available since D36xx (CoffeeLake)! The function set of Efiflash.efi
for D35xx and prior motherboards (D34xx) is similar to the DOS version. So please refer to the DOS
section of Efiflash.exe in that case.
Errorlevel Meaning
0 Terminated normally, everything went OK
1 EfiFlash.exe generated error
2 BIOS generated error
3 Hardware error detected
4 Service not supported
5 File read/write error
6 Error parsing User Options
Bios Interface not found (not an Kontron motherboard with UEFI
55
firmware)
1) Plug the prepared USB stick to any USB port on the target system
2) Power on system and hit F12 to open boot menu.
3) Choose "FUJITSU Update Utility".
4) EfiFlash.EFI initializes flash update process automatically.
5) Confirm update or decline it to choose another operation. See “Additional functions”.
6) Wait until the flash update is completely done. It may take up to a few minutes, in certain cases
even without visible progress.
3 Create dump file (*.DMP) and afterwards update the BIOS flash (same as option 2 + 1)
5 Save BIOS config data to .SCD file (replaces /Archive-Dump of older platforms)
6 Restore BIOS config data from .SCD file. No full BIOS-update necessary, (compared to
Archive-flash procedure)
7 Restore BIOS config data from .SCD file and afterwards update the BIOS flash (same as
option 6 + 1). Replaces Archive-BIOS flash. It is possible to restore your specific BIOS
settings and update the BIOS in one step.
Q Quit application
*Note: The mentioned commands are available since D36xx (CoffeeLake)! The function set of
Efiflash.efi for D354x motherboards is similar to the DOS version.
To flash the BIOS manually (“AUTO” mode also possible, see parameter /UPD in table below):
1) Open command line with administrator rights and navigate to the extracted BIOS admin package
WINDOWS folder
2) Run DskFlash.exe /UPD /FRB /WD=<path-to-BUP-file> /O=<filename>
3) Check the message box content and press the OK button.
4) Wait until the flash update preparation is completely done. It may take up to a few minutes, in
certain cases even without visible progress.
5) After BIOS flash preparation is done, the system will restart automatically to perform the flash
process during BIOS POST (“BIOS capsule update”).
Here are explanations for the most commonly used DskFlash command line options:
/UPD Update motherboard BIOS. Without the parameter /O it automatically searches for
the latest available update file in the tool directory, suitable for the installed
motherboard.
/ARC Save the system configuration data (*.ARCHIVE.NVUX). Please see chapter
"Transferring BIOS Setup settings" for details.
/BUPINFO Display detail information about the provided BIOS update (.BUP) or configuration
file (.NVUX)
/WD Set the current working directory for loading and saving files and for storing the
logfile too.
/O Name the object file or file pattern for loading and saving.
Note: Only file-names allowed. Use /WD to set the correct source path of the object
file!
/OV Allow DeskFlash to overwrite a current BIOS or an existing file. Only needed, if
installed BIOS is newer than the BIOS you want to flash. Take care about the BIOS
setup option “Allow System Firmware Rollback”, too.
/ARB Allow DeskFlash to reboot the system if required.
/NRB Suppress required reboot of DeskFlash to perform the reboot on an alternate way.
/FRB Force DeskFlash to reboot the system after finishing the job.
/S Hide control dialog and display warning dialog.
/W Hide warning dialog too.
/LF Enable logfile output and name the logfile.
/? Show full help of DskFlash tool
/AST Show last action status (not documented in the tool help)
Errorlevel Meaning
0 Success
1 Warning
2 General error
4 Syntax error in command line
8 Valid BIOS file missing
64 Insufficient privileges
400 BIOS successfully prepared for POST update action
401 POST update action failed
402 POST update action pending
To flash the BIOS manually (“AUTO” mode also possible, see parameter /UPD in table below):
1) Open command line with administrator rights and navigate to the extracted BIOS admin package
WINDOWS folder
2) Run DskFlash.exe /UPD /FRB /WD=<path-to-BUP-file> /O=<filename>
3) Check the message box content and press the OK button.
4) Wait until the flash update preparation is completely done. It may take up to a few minutes, in
certain cases even without visible progress.
5) After BIOS flash preparation is done, the system will restart automatically to perform the flash
process during BIOS POST (“BIOS capsule update”).
Here are explanations for the most commonly used DskFlash command line options:
/UPD Update motherboard BIOS. Without the parameter /O it automatically searches for
the latest available update file in the tool directory, suitable for the installed
motherboard.
/AR Creates an Archive BIOS and NVRAM settings file (*.ARCHIVE.BUP). Please see
chapter " Transferring BIOS Setup settings" for details.
Please note, that the current “ProductName” is included in archive file and restore is only possible on
systems with the same ProductName.
/WD Set the current working directory for loading and saving files and for storing the
logfile too.
/O Name the object file or file pattern for loading and saving.
Note: Only file-names allowed. Use /WD to set the correct source path of the object
file!
/OV Allow DeskFlash to overwrite a current BIOS or an existing file. Only needed, if
installed BIOS is newer than the BIOS you want to flash.
/ARB Allow DeskFlash to reboot the system if required.
/NRB Suppress required reboot of DeskFlash to perform the reboot on an alternate way.
/FRB Force DeskFlash to reboot the system after finishing the job.
/S Hide control dialog and display warning dialog.
/W Hide warning dialog too.
/LF Enable logfile output and name the logfile.
/? Show full help of DskFlash tool
/AST Show last action status (not documented in the tool help)
Errorlevel Meaning
0 Success
1 Warning
2 General error
4 Syntax error in command line
8 Valid BIOS file missing; Wrong ProductName found in archive file.
64 Insufficient privileges
400 BIOS successfully prepared for POST update action
401 POST update action failed
402 POST update action pending
6.10.1 Installing Linux driver for deskflash and the tool itself [updated v1.10]
3) Download "Deskflash_V1.xx-00xx_Linux64.zip" from the FTP server:
a. ftp://ftp.kontron.com/Services/Software_Tools/BIOS-Flash-Tools/
4) Extract the package on your Linux system to any user folder.
5) There are several packages included:
a. precompiled_drv-xxxx.tar.gz: Precompiled BIOS driver for RHEL and SLES (only V1 pkg)
b. driver_src-xxxx.tar.gz: BIOS driver source packages to compile the driver by yourself
c. deskflash-xxxx.rpm: RPM package of the BIOS flash tool “deskflash”
d. deskflash-xxxx.deb: DEB package of BIOS flash tool “deskflash”
Here are explanations for the most commonly used DskFlash command line options:
-at Automatically searches for the latest available update file in the active location,
suitable for the installed motherboard.
-ar Creates an Archive BIOS and NVRAM settings file (*.archive.bup). Please see
chapter " Transferring BIOS Setup settings" for details
-d Set the current working directory for loading and saving files and for storing the
logfile too.
-o Name the object file or file pattern for loading and saving.
-ov Allow deskflash to overwrite a current BIOS or an existing file. Only needed, if
installed BIOS is newer than the BIOS you want to flash.
-arb Allow deskflash to reboot the system if required.
-narb Suppress required reboot of deskflash to perform the reboot on an alternate way.
-lf Enable logfile output and name the logfile.
-i Display system and BIOS information
-h Show full help of deskflash tool
-ast Show last action status (not documented in the tool help)
Errorlevel Meaning
0 No error
1 General error occured, check protocol
2 Syntax error in command line
16 Provided file is not valid
64 Missing confirmations (-arb, -ov, -fcu) for action
128 Insufficient priviledges for action
129 The BIOS version in the file is not update compatible with the version
installed.
130 Downgrading to this BIOS version is prohibited.
140 BIOS successfully prepared for POST update action
141 POST update action failed
142 POST update action pending
240 No support module for this hardware found
The following Items are transferred if they are different from the target motherboard:
The whole NVRAM
(this contains the BIOS Setup Defaults, current BIOS Setup settings, Boot order, BIOS passwords)
The BIOS Boot Logo
(created with UEFIModL and applied via Flash tool or direct uploaded Logo via Flash tool.)
Customized fan control and temperature limits data
(created with SilentFanConfig and applied with SMCO)
Customized EDID data for LVDS attached flat panel displays
(created with Phoenix and applied with LVDS)
Customized DMI data „System Manufacturer“ = DMI Type 1 Offset 4 and Type 3 Offset 4
(set with OEMIDENT)
Some parts of the main system BIOS (only for ARC files)
/NVRAM Restore only the NVRAM (BIOS setup settings) from a .nvux file
DskFlash /NVRAM /O=<config.nvux>
/PASSWORDS Restore only the passwords (BIOS setup settings) from a .nvux file
DskFlash /PASSWORDS /O=<config_archive.nvux>
/BOOTORDER Restore only the boot order (BIOS setup settings) from a .nvux file or from
combined.bup
DskFlash /BOOTORDER /O=<config_archive.nvux>
You can also combine a BIOS update file (.bup) and a configuration file (.nvux) to update the
system BIOS and activate your settings in one step:
/MAKE Create a combined archive from a .nvux file and a .bup file
DskFlash /MAKE /O=<output_combined.bup>
/CINP=<config_archive.nvux> /BINP=<original_bios.bup>
Apply the combined image in the same way like flashing a standard BIOS file (see chapter
“Upgrading / Downgrading the BIOS”).
You can also combine a BIOS update file (.bup) and a configuration file (.nvux) to update the
system BIOS and activate your settings in one step:
--make Create a combined archive from a .nvux file and a .bup file
deskflash --make -o <output_combined.bup> -cinp
<config_archive.nvux> -binp <original_bios.bup>
Apply the combined image with –nvu parameter. It updates the BIOS and apply the settings
from NVUX file in one step.
Attention: Different usage of parameters in Windows and Linux deskflash!
Note: When later upgrading / downgrading the BIOS, all customizations and settings will be preserved.
Note: When later upgrading / downgrading the BIOS, all customizations and settings will be preserved.
Caution: Do NOT apply an archive file to a motherboard with a different BIOS version than was used to create
the archive! As described above, some parts of the BIOS are not updated during applying an archive, only during
normal BIOS update. This could result in the BIOS version shown as the one used to create the BIOS archive, but
not all parts of the BIOS would actually match this version.
Typically there are two different layouts available (depending on the motherboard model):