Supporting FPP development since 2022. Proceeds go to help further FPP development.

Is there any difference in functionality between a cape that is signed by the cape vendor versus a cape that is signed using a license key.

Currently the only capes which contain signed EEPROMs are Kulp capes sold by KulpLights and various other vendors. A new Pi cape for the DPIPixels output is under development by David Pitts and will include a signed EEPROM when sold. Capes by Dan Kulp and David Pitts which contain a signed EEPROM (the original PiCap does NOT have an EEPROM) are sold with full functionality and do not need a license key applied. When a cape from a 3rd party vendor is signed, it is signed using the ‘fp’ (Falcon Player) signature and contains information about the device the cape is attached to and the license key which was used to sign the cape. After a cape EEPROM is signed, the only real difference between a Kulp/Pitts cape and a 3rd party cape is the fact that the 3rd party cape is tied to the Beagle or Pi the cape was signed on. If the cape is moved to another Beagle or Pi, the cape must be re-signed using the same license key and order originally used in the FPP EEPROM signing UI. This is done to prevent someone from copying a signed EEPROM and installing it on multiple capes without having to buy license keys for each cape.