Binho Pulsar: Firmware

The Pulsar runs two pieces of software: the bootloader, which only installs firmware, and the firmware (the application), which does everything else.

Latest firmware

The latest Pulsar firmware, its download and how to install it are in the Latest Firmware table. What changed in each version, and the known limitations, are in the Firmware Release Notes.

Which file to install

File	For
pulsar-app-<version>.afx	Pulsar, Airlock bootloader
.gfi	Pulsar, legacy bootloader

Danger

Never load Supernova firmware on a Pulsar. A cross-loaded image can leave the adapter unusable until it is recovered at the factory. Check the product name in the file name before copying it.

Which bootloader is installed

If the adapter runs firmware 4.3.0 or later, it has the Airlock bootloader: it takes .afx files and works with dfu.binho.io. Firmware 4.2.x and older runs on the legacy bootloader, which takes .gfi files and needs a one-time migration before it can run 4.3.0 or later.

To read the firmware version and tell the bootloaders apart, see Check the Firmware and Bootloader.

Note

Mission Control 2.16.1 and earlier do not work with Pulsar firmware 4.x. Use Mission Control 3 for this adapter.

What depends on the firmware version

• I2C and SPI target mode need firmware 4.5.0 or later.
• RS-485 and CAN-FD need firmware 4.4.0 or later. See Virtual COM Port Modes.
• Some behaviors differ before and after 4.6.2. See the known limitations.

Update the firmware

There are three ways to install it:

• In the browser, with dfu.binho.io (Chrome or Edge)
• By drag and drop
• With PyCosmicSDK

An adapter on firmware 4.2.x or earlier needs the one-time bootloader migration first.

If the adapter shows up as a USB drive named PULSAR, or a firmware file is rejected, see Firmware and Bootloader.