BIOS Update for Compute Card - GKAPLCPX

19058
7/7/2020

Introduction

This download record contains options for updating the BIOS of Intel® Compute Card CD1P64GK and CD1C64GK.

Available Downloads

  • OS Independent
  • Size: 9.3 MB
  • SHA1: BF14B1A1177D612313436A89916A6DA53F6FADB4
  • Windows 10, 64-bit*
  • Size: 7.3 MB
  • SHA1: 8A274440B886C94EF1D7F1DD232A3C2C89C40EED
  • OS Independent
  • Size: 6.9 MB
  • SHA1: 5FCADD4422F1C004D76D53C62FCF95C94EB5EE3B

Detailed Description

Purpose

This download record provides options for updating the BIOS of Intel® Compute Card CD1P64GK and CD1C64GK. You only need to download one.

Which file to choose?

  • Express BIOS update [GKAPLCPX.86A.0056.EB.msi] - Self-extracting Windows*-based update file, designed to be used on Windows systems.
  • Recovery BIOS update [GK0056.bio] - A .BIO file to be used for F7 BIOS Update method or a BIOS recovery process. In the unlikely event that a BIOS update is interrupted, it is possible the BIOS may be left in an unusable state. Use the recovery BIOS update to recover from this condition. It requires a USB flash device or CD.
  • UEFI BIOS update [GKAPLCPX.86A.0056.UEFI.zip] - A DOS-based utility to update the BIOS regardless of operating system. It requires a USB flash device or CD.

The readme file includes BIOS update instructions for advanced users. You can also find detailed step-by-step instructions on how to use each of these BIOS update methods.

What’s new in this release?

See the release notes for installation instructions, supported hardware, what is new, bug fixes, and known issues in this BIOS version.

This download is valid for the product(s) listed below.

Automatic Driver and Software Updates

Identify your products and install Intel driver and software updates for your Windows* system.

Get started

Disclaimers1

Product and Performance Information

1

Intel is in the process of removing non-inclusive language from our current documentation, user interfaces, and code. Please note that retroactive changes are not always possible, and some non-inclusive language may remain in older documentation, user interfaces, and code.