News:

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

+-+-

+-User

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

+-Site Stats

Members
Total Members: 16646
Latest: Amping
New This Month: 10
New This Week: 5
New Today: 1
Stats
Total Posts: 133934
Total Topics: 16692
Most Online Today: 55
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 2
Guests: 58
Total: 60

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

Unable to log into fpp 8.x by JonD
Today at 07:17:06 AM

Does the Falcon f16v4 support TM1814 RGBW LEDs? by btm231
Today at 12:31:52 AM

F16V2 Power Voltage Input Very Low by k6ccc
November 06, 2024, 05:28:04 PM

Pi 5 does not boot with fresh image of 8.2 by JonD
November 06, 2024, 04:42:27 PM

Weird date / time issue by Poporacer
November 05, 2024, 07:42:36 PM

Having problems upgrading my system from WLED to FPP with differential receiver by MikeKrebs
November 04, 2024, 08:35:49 PM

Getting an error on Initial Set up of v 8.2 FPP by MikeKrebs
November 04, 2024, 08:24:42 PM

F48 Output Issues - Pixel Strand by dbarton02
November 03, 2024, 01:52:25 PM

F16 v5 invalid file by JonD
November 03, 2024, 11:08:00 AM

3D Printable X-Connect connectors by dreiman
November 03, 2024, 09:47:45 AM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod