// FIRMWARE FLASHER · FLYSIGHT 2 · ENGO HUD

FLYSIGHT 2 FIRMWARE FLASHER

Install the ENGO HUD firmware on your FlySight 2. This page works out which firmware your device needs, checks it, and writes it for you. Everything happens on your own machine: no file you touch is uploaded anywhere, and there is no account to make.

You need a computer — Windows, macOS, Linux or ChromeOS — with the FlySight plugged into it by its USB cable, and Chrome or Edge on that computer. A phone or tablet cannot do this. In Safari or Firefox the page can only hand you the file to copy across yourself.

How this actually works

The first install needs a computer: the firmware FlySights are sold with cannot install another one over Bluetooth. What it does have is a bootloader: hold the button until the light turns orange and the device re-appears on your computer as a plain USB drive. Put a firmware file at FW/APP.SFB on that drive, eject it, and the bootloader installs the firmware on the next power-up. After that, the Groundrush app updates the FlySight over Bluetooth and you do not need this page again.

Firmware is encrypted for one manufacturing batch, so there is one file per batch and only one of them will install on your device. Your FlySight says which batch it is in a file called flysight.txt in the top level of its drive. That is the only thing this page needs to read.

Checking what this browser can do…

Jump to: identify & download which file do I need? what this page will and won't do

DEVICE CONSOLE IDLE
Every line above is a real event on this page. Nothing here is a simulation, and there is no progress bar for work that is not happening.

Is the FlySight charged?

This page cannot read the FlySight's battery level. The firmware is installed by the bootloader after you unplug the USB cable, running on the battery alone. If the battery runs out halfway through, the FlySight is left with no firmware at all: an orange light on USB, a red light cycling on and off without it, and nothing works until it has been charged.

Charge it before you start. If in doubt, leave it plugged in for a few hours first.

// PATH B

IDENTIFY & DOWNLOAD

This path works in every browser on a computer, including Safari and Firefox. You show the page your flysight.txt, it works out which firmware you need, and hands it to you already named APP.SFB. You copy it across yourself. It is exactly as safe as the one-click path — it just makes you do the last step by hand.

Plug the FlySight in normally, open its drive, and take the file called flysight.txt from the top level. The file is read in your browser and is not uploaded.

// PATH C

WHICH FILE DO I NEED?

Open flysight.txt from the FlySight's drive in any text editor and find the line that starts with Pubkey_X:. Match it below. The first eight characters are enough to tell them apart.

Batch Pubkey_X starts with File SHA-256
Loading the firmware list…

Firmware version —. Every file is the same firmware; they differ only in which batch of devices they will decrypt on. If your Pubkey_X is not in this table, stop — none of these files can install on your device, and trying the wrong one is a waste of time rather than a way to find out.

Early FlySight 2 (the first ~500 made) show Pubkey_X as all fs: they do not expose their key. They cannot take any custom firmware until FlySight has switched them to their "dev" key — a small file FlySight provides and you copy onto the device once; ask FlySight support for it. After that the DEV file is the one for your device, and official firmware for the dev key stays available from flysight.ca. Nobody has run this path on a real early unit for this site yet.

// THE SMALL PRINT THAT ISN'T SMALL

WHAT THIS PAGE WILL AND WON'T DO

WON'T TOUCH ANYTHING ELSE

The only file it creates on your device is FW/APP.SFB. It also deletes macOS ._ leftovers and abandoned .crswap scratch files inside that same FW folder, because they are junk the bootloader has to scan past. Your logs, your config and everything else are never opened.

WON'T GUESS YOUR BATCH

If your device reports a Pubkey_X this page does not recognise, it says so and stops. The firmware is encrypted per batch, so a near miss is not a near miss — it simply will not install, and pretending otherwise would just waste your evening.

CHECKS BEFORE AND AFTER

The download must start with the four bytes SFU1, be exactly the published size, and match the published SHA-256. After writing, the file is read back off the device and hashed again. A mismatch at any point aborts and removes the file rather than leaving something half-written.

WON'T UPLOAD YOUR FILES

flysight.txt is read in the browser and never uploaded. To see where updates fail, the page reports each step and any error to this site, with the device ID, batch and firmware versions from that file and your browser family — see the privacy policy. The flasher itself needs no account and sets no cookies, and there is no third-party analytics. The firmware itself is served from this site, not fetched from somewhere else.

CAN'T DO IT WIRELESSLY

Not over Bluetooth and not over USB-as-a-device: the FlySight bootloader presents itself as an ordinary disk, and browsers deliberately refuse to talk to storage devices directly. A file on a drive really is the mechanism, not a workaround.

IF SOMETHING GOES WRONG

A failed copy is not a bricked device. The bootloader stays put and keeps accepting files, so you can always try again — or go back to the official firmware the same way. The console above records what happened, so you have something concrete to report.