All pages
Powered by GitBook
1 of 1

Loading...

Firmware & File Operations

File operations let your host move files to and from the reader β€” firmware images, EMV configuration files, certificates, and more. All of them use the File Operations command group and share the Common File Structure format. The most common file operation is updating firmware, covered first below.

Applies to: DynaFamily (DynaFlex II PED, Go, SCR, DynaProx). Examples use the DynaFlex II Go.

Updating firmware

Firmware images are signed by MagTek and delivered as a Firmware File Type object. There are two ways to apply one β€” a code path and a Windows utility.

Using the commands

  1. Get the signed image. Obtain the firmware file for your device (see Getting firmware files below).

  2. Send it to the device with , supplying the image type (boot loader, main app, Wi-Fi, or BLE module), a SHA-256 hash of the image, the payload, and a Load Option (Default or Auto Commit). The device must have more than 5% battery or it won't run the command.

  3. The device validates and authenticates the signed image.

  4. Commit the image:

    • If you sent Auto Commit, the device commits automatically.

    • Otherwise (Default mode), commit it with .

  5. The device reports the result and resets: or. If the image is already current, the device sends .

If you don't need to script it, MagTek's Windows utility performs the same update through a GUI β€” see

The same command group handles non-firmware files β€” for example loading EMV configuration or certificate files, or retrieving files from the device:

For how files are framed, see About Files and the Common File Structure data object. Loading and erasing EMV configuration files specifically is covered in EMV acceptance.

To read the device's current firmware before or after an update, use the Firmware Identification Information properties.

Firmware images and the Windows utility are downloads, not part of this guide β€” find the files for your device in .

Read a file's metadata without downloading it.

Remove a file.

The host uses this command to start sending secured files to the device for storage or processing. It is similar to Start Send File to Device (Unsecured), but is used to send a different subset of file types that impact device security and require some form of authentication from the host.

The host uses this command to start sending unsecured files to the device for storage or processing. It is similar to Start Send File to Device (Secured) but is used to send a different subset of file types that do not impact device security.

`The host uses this command to request a file stored on the device. File types include standard files (images and certificates), MagTek custom files (configuration, firmware), and in some cases even large data blob output (such as signature capture data).

The host uses this command to request the file information of a file stored on the device. File types include standard files (images and certificates), MagTek custom files (configuration, firmware), and in some cases even large data blob output (such as signature capture data).

The host uses this command to request the deletion of a file stored on the device.

Section

Information

0xD811 - Start Send File to Device (Secured)

Send a file that must be sent securely.

0xD812 - Start Send File to Device (Unsecured)

Send a file that doesn't require a secure channel.

0xD821 - Start Get File from Device

Retrieve a file from the device.

Section

Information

0xD801 - Load Firmware File

The host uses this command to send a firmware image file, signed by MagTek, to the device as the first step in updating firmware.

0xD901 - Commit Firmware from File

The host uses this command to commit a file previously uploaded using Command 0xD801 into the device’s permanent memory after the device has authenticated the file.

0xD821 - Start Get File from Device

The host uses this command to request a file stored on the device. File types include standard files (images and certificates), MagTek custom files (configuration, firmware), and in some cases even large data blob output (such as signature capture data).

Section

Information

0x0905 - Firmware Update Successful

This notification reports the successful completion of firmware update operations the host initiated using Load Firmware File and Commit Firmware from File

0x906 - Firmware Update Failed

This notification reports the failure of a Firmware Update command the host initiated using Load Firmware File and Commit Firmware from File.

0x0907 - Firmware is Up to Date 0x0907

This notification reports Firmware is up to date for host initiated Load Firmware File.

Section

Information

EMV acceptance

Guide to loading EMV config files

Using the Firmware Update Utility (Windows)

Working with other files

Checking the firmware version

Getting firmware files

Related

Commands

Notifications

Guides

Need Help?

For additional support, please contact MagTek Support:

Technical Support:

  • πŸ“§ Email: support@magtek.com

  • πŸ“ž Phone: 1-800-788-6835 (US) | +1-562-546-6616 (International)

  • πŸ• Hours: Monday-Friday, 6:00 AM - 5:00 PM PST

Online Resources:

  • 🌐 Official Site:

  • πŸ’¬ Developer Forum:

Documentation Feedback:

Help us improve this documentation!

0xD801 - Load Firmware File
0xD901 - Commit Firmware from File
0x0905 - Firmware Update Successful
0x0906 - Firmware Update Failed
0x0907 - Firmware is Up to Date
How to use the Firmware Update Utility.
Downloads & Compliance
https://www.magtek.com
https://forum.magtek.com
0xD825 - Get File Info from Device
0xD831 - Delete File from Device
0xD811 - Start Send File to Device (Secured)
0xD812 - Start Send File to Device (Unsecured)
0xD821 - Start Get File from Device
0xD825 - Get File Info
0xD831 - Delete File
Submit feedback