News:

LATEST RELEASE:  FPP 7.0 - Download from here - https://github.com/FalconChristmas/fpp/releases/tag/7.0

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 15930
Latest: mmoulder
New This Month: 20
New This Week: 0
New Today: 0
Stats
Total Posts: 129640
Total Topics: 15981
Most Online Today: 132
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 1
Guests: 74
Total: 75

DIY BBB CAPE

Started by nagyOUT, January 12, 2020, 11:09:53 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

nagyOUT

Hey all!

Been looking at doing my own Cape for the BBB, and during some research in terms of integration with Falcon Player, i discovered that during cape detection, there is checks for a Cape onboard EEPROM, and further signing of a FPP02 header based "file" against public keys stored in script/keys. 

As I haven't looked into the source files in great detail, I assume this is to protect various board makers products by only allowing "signed" boards to work? Will a RGB-123 work without a onboard EEPROM?

In order for me to do my own board, I was unable to find a script which "creates" this FPP02 related file which is stored on the cape's EEPROM. Is there a script or file format detail documented somewhere?

Further, what is the process in submitting my own vendor/public key.. Just a simple Pull request to the main git?

Thanks!

dkulp

One of these days I need to document it...   For basic uses of providing configuration of string mappings, it doesn't need to be digitally signed.   That's important as folks can create boards and provide the pin mappings on the eeprom so we don't need to keep adding mappings into /opt/fpp/capes/* .    All the mappings were getting to be a pain to maintain.   The more advanced things DO require digital signatures and thats to protect the vendors that are supporting and contributing to the development of FPP and the work they have put into it.   Thus, it depends on what you need.  For basic capes that will work and output pixels, it's not something to worry about.
Daniel Kulp - https://kulplights.com

nagyOUT

Being able to store the pin mappings is a great idea.
Anyways, I'll keep an eye out for either further documentation or a script to package up the EEPROM bin data.

Out of interest, what are the more advanced things it's will allow?

WaldoWoodyWoodpecker

Quote from: nagyOUT on January 13, 2020, 04:12:24 AMBeing able to store the pin mappings is a great idea.
Anyways, I'll keep an eye out for either further documentation or a script to package up the EEPROM bin data.

Out of interest, what are the more advanced things it's will allow?
Hi nagyOUT, did you manage to find a script to package up the eeprom?

darylc


CaptainMurdoch

We will likely be adding an official script to the FPP github repository to generate eeprom files, but are still discussing some related topics.  Right now I think there are 4 different implementations out there including the above plugin.
-
Chris

shanebou24

Did you guy ever work out an official script?
I couldn't find one
Cheers,
Shane

Support FPP

+- Recent Topics

MegaTree + Faces kit for sale by dkroz
Today at 12:39:28 PM

DMX problem with F4v3 by JonD
Today at 11:00:35 AM

Maximum Number of Schedules by Poporacer
September 20, 2023, 10:53:53 PM

K16A-B Expansion Board by vttinman
September 20, 2023, 12:39:02 PM

FPP Colorlight config by Wayne Laagewaard
September 20, 2023, 10:57:35 AM

New Falcon F16v4 Troubles with Pixel Output Page by JonB256
September 19, 2023, 08:01:23 PM

GIF or MP4 display on a matrix? by tbone321
September 18, 2023, 01:15:45 PM

F16V4 LCD Screen not working by Timmy
September 18, 2023, 05:35:19 AM

My plugin fpp_install.sh not executed 7.x by esset
September 17, 2023, 11:36:25 AM

Integrating Twilio with Google Sheets by dkulp
September 17, 2023, 10:26:07 AM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod