en

User Tools

Site Tools


vmware.png nfs.png tftp.png subversion.png eclipse.png logo.png tutorial.png

BIOS Overview

BIOS Revision ME Firmware Version PCI Configurations BIOS Binary
5.5.01.0052.07 10.0.36.1030 1 PCIe Lanes TQMx50UC_5.5.01.0052.07_X64.bin
1×4 PCIe Lanes TQMx50UC_5.5.01.0052.07_X64_pcie1x4.bin
1×2 + 2×1 PCIe Lanes TQMx50UC_5.5.01.0052.07_X64_pcie1x2_2x1.bin
5.5.01.0052.06 10.0.36.1030 1 PCIe Lanes TQMx50UC_5.5.01.0052.06_X64.bin
1×4 PCIe Lanes TQMx50UC_5.5.01.0052.06_X64_pcie1x4.bin
1×2 + 2×1 PCIe Lanes TQMx50UC_5.5.01.0052.06_X64_pcie1x2_2x1.bin
5.5.01.0052.05 10.0.36.1030 1 PCIe Lanes TQMx50UC_5.5.01.0052.05_X64.bin
5.5.01.0052.04 10.0.36.1030 1 PCIe Lanes TQMx50UC_5.5.01.0052.04_X64.bin

Changelog

5.5.01.0052.07

5.5.01.0052.06

5.5.01.0052.05

5.5.01.0052.04


BIOS-Update-USB Stick

Prerequisites

  • FAT formated USB-Stick with at least > 32 MiB storage
  • Latest H2OFFT™ (Firmware Flash Tool)

Creating BIOS-Update-USB Stick

Copy Insyde Firmware Flash Tool to USB-Stick

<USB key>
    ├───H2OFFT-Sx64.efi
 

The BIOS-Update-USB Stick is now ready for updating and flashing BIOS images.
For further Information please see the BIOS Update section.

BIOS Update

Prerequisites

<USB key>
    ├───H2OFFT-Sx64.efi
    ├───TQMx50UC_5.5.01.0052.07_X64.bin    

Perform BIOS Update

Attention: keyboard layout is US by default in BIOS setup!

  • Insert BIOS-Update-USB Stick to a Starterkit USB port
  • Boot up the system and navigate into the EFI Shell (Boot Manager > Internal EFI Shell)
  • After starting the EFI Shell switch path to the USB stick by typing fs0:. This depends on the amount of connected mass storage devices. With command ls you can check the content of the path.
  • Launch BIOS update
fs0:\> H2OFFT-Sx64.efi <BIOS_Image>.bin –ALL -RA <Enter>

Example

⇒ BIOS will reboot into EFI shell after the update has finished succesfully

  • Leave EFI shell
Shell> exit
  • Select “Boot Manager”
  • Select desired boot device (e.g. Internal HD)
    ⇒ System will reboot from selected boot device



Boot Logo Replacement

This instruction guides you through the procedure of replacing the Bootlogo using the Insyde UEFI/BIOS tool called H2OLRT (Logo Replacement Tool).

Please note that the logo replacement can only be done in the integrated EFI Shell.
Furthermore, this tool is only available on request, please contact support@t1;-group.com.

Prerequisites

Prepare BIOS-Update-USB Stick and add the following components:

  • Logo Replacement Tool (H2OLRT-Sx64.efi)
  • Appropriate BIOS file for your TQ module (e.g. TQMx50UC_5.5.01.0052.07_X64.bin)
  • Picture formated as *.jpg (e.g. example_picture.jpg)

Replace Boot Logo via EFI Shell

The H2OLRT (Logo Replacement Tool)generates a BIOS file that contains the desired Boot Logo instead of the TQ Logo.

  • Insert the BIOS-Update-USB Stick to a Starterkit USB port
  • Boot up the system and navigate into the EFI Shell (Boot Manager > Internal EFI Shell)
  • After starting the EFI Shell switch path to the USB stick by typing fs0:.This depends on the amount of conected mass storage devices; with command ls you can check the content of the path.
  • The generic command and the following example shows how to start the Logo Replacement.
H2OLRT-Sx64.efi –replogo:<SrcBIOSImageName> –logopath:<LogoImagePathName> -logoindex:<IndexNum> –logoconvert:<ConvertNum> –out:<OutBIOSImageName>

Example


H2OLRT-Sx64.efi Variable description

Variable Description
<SrcBIOSImageName> BIOS file in which the logo should be replaced
<LogoImagePathName> Path and name of the replacement picture
<IndexNum> Default index, where the picture must be stored.
e.g. TQMx50UC Logoindex: 4
<ConvertNum> 0 = keep original image's format and dimension.
1 [default] = auto convert the image's format and dimension.
<OutBIOSImageName> path and name of the generated BIOS file


  • Next step is to flash the customized BIOS Binary, please see the BIOS Update section.

Boot from external BIOS

MB-COME6-1

X23
SM Bus CLK 1 2 I2C Bus CLK
SM Bus DAT 3 4 I2C Bus DAT
SM Bus Alert 5 6 3V3
BIOS_DIS0# 7 8 GND
BIOS_DIS1# 9 10 GND


If there is no Jumper present on the BIOS_DIS1# signal the module will load its BIOS from the internal SPI flash.
If there is a Jumper on the BIOS_DIS1# signal (between signal and GND) the module loads its BIOS from the flash in the SPI socket of the carrier board.



Downloads


BIOS Downloads


TQMx50UC 5.5.01.0052.07
MD5SUM:D1EA51C19732A4C9E6BA3EDA1D4B4159

TQMx50UC 5.5.01.0052.06
MD5SUM:7B57232C94798393D02E8685341B7136

TQMx50UC 5.5.01.0052.05
MD5SUM:2E45ED19A54E0FB1FEB7271F2D5B59F4

TQMx50UC 5.5.01.0052.04
MD5SUM:6FB2309D8E26B8111D546DA746381204

Driver Downloads


Driver package for TQMx50UC Windows 10 64-bit
MD5SUM:96F14890EC7B1A60C3CF1521B0E76F89

Driver package for TQMx50UC Windows 10 32-bit
MD5SUM:E3E5883684DC00A5479EF776341838AB

Driver package for TQMx50UC Windows 7 64-bit
MD5SUM:BBF6B16CF9C33EF3D0FEC821A6ABD4CA

Driver package for TQMx50UC Windows 7 32-bit
MD5SUM:B48E2F83A48C9554D945C2FB13213DE1


en/x86/tqmx50uc/data.txt · Last modified: 2019/11/28 11:45 by bujupib


Disclaimer

TQ-Systems GmbH provides the Board Support Packages (BSP) free of charge. The software included in the shipment has been configured individually for the starter kits. The software is only intended to evaluate the module. The use of the Board Support Packages (BSP) is only allowed within the scope of functionality described by TQ-Systems GmbH. TQ-Systems GmbH does not accept any liability for all further changes of the Board Support Package and for any damage resulting from its use.


Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki