EEPROM stands for Electrically Erasable Programmable Read-Only Memory. So while it says Read-Only, it can actually be erased and re-written, but the number of writes may be limited. FPP uses EEPROMs on capes to store cape configuration and vendor information. Most FPP-compatible capes created in the past few years include an EEPROM on them.

A Voucher is essentially a coupon for a specific license key. A voucher may be redeemed during the checkout process to grant the purchaser a free license.

For the purpose of discussion around FPP, a “3rd party” refers to a non-developer who is selling capes.

Banks allow a cape to control more direct attached pixel outputs than are physically present on the Pi or Beagle driving the cape. The Channel Output creates banks of pixels by essentially time-slicing the output on a physical port. If there are 24 physical outputs on a Pi, the DPIPixels Channel Output can use 16 of these in bank mode which can create 32 or 48 outputs. In this mode, the first output in each bank is connected to the same physical output on the Pi and are added together to share the same 800 or 1600 pixel max depending on the sequence timing. In this scenario, outputs 1, 17, and 33 must add up to less than the total max. Not all DPIPixels capes support banked mode as it requires extra circuitry onboard.

If used correctly as intended by their designers, BeagleBones and PocketBeagles use Capes and Raspberry Pis use Hats. You will probably just hear and see us using the term Cape to refer to both Beagle Capes and Pi Hats. This is partially due to the fact that the Pi Hats require a specially formatted EEPROM which we do not require since FPP has its own EEPROM format which is cross-platform and usable on both platforms.