FPP PB16 Pixel Controller

[scooter_seh]

Sorry maybe I didn't understand the license process correctly, I thought Chris had to generate a EEPROM with the "99" signature included in it.

Uhh... What does the FPP6 license stuff have to do with generating an eeprom at all? You should still be able to generate an unsigned eeprom with your cape-info, default configs, string config, etc...

[dkulp]

Sorry maybe I didn't understand the license process correctly, I thought Chris had to generate a EEPROM with the "99" signature included in it.

He needs to start with an actual eeprom.bin file for the board. That would then be signed as part of either process. For the DYI stuff, he would take the bin and sign it and send it back (I think). If the user preferred to purchase the license (generally faster, can be done in minutes), the eeprom would need to be already flashed on the board and then everything can be done from the cape-info pages in FPP and in the store. Either way, the eeprom.bin for the board is the important starting point.