LATEST RELEASE:  FPP 6.3 - Download from here -



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

+-Site Stats

Total Members: 15659
Latest: PaulDzRGB
New This Month: 9
New This Week: 3
New Today: 0
Total Posts: 128432
Total Topics: 15791
Most Online Today: 48
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 4
Guests: 19
Total: 23

Eeprom, json, bin files for cape type

Started by AAH, January 18, 2022, 03:49:43 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.


In order to solve a problem with Xlights upload changing the cape type of my HE123 and HE123Mk2 to F4-B I'm chasing info on what I need as far as eeprom, json and bin files. According to what is detailed in I can add my cape name to the eeprom which should solve the upload issue. I would however like the full config to be automatically available including whether or not the board has an oled, what IO's are used for what pixel outputs, what pixel type, what IO's are used for user inputs for FPP navigation and if possible have my logo embedded as per what I have with the rPi-MFC.

Currently I have a script to configure the rPi-MFC but I need ones for
HE123, HE123Mk2, rPi-28D and would like to be able to configure them myself if possible. It would actually be nice if Xlights in conjunction with FPP could push the info into the capes but manually running a script to burn the data to the eeprom would definitely do me and it would solve the issue of novices having to keep changing the cape type every time an xlight upload is done.

thanks in advance


Alan, check out the sample JSONs on guthub, you would need to create one of these and put it inside your eeprom

Also check out the FPP code that handles the eeproms for further understanding


The raw eeprom format is documented at:

That's to binary format of how the bytes need to be arranged on the eeprom.   For the most part, the eeprom is used to populate files into /home/fpp/media/tmp.   Thus, you need to figure out what files you need to create to dump in there.   The cape-info.json and cape-image.xbm would be the first things.   The next would likely be a defaults directory with configuration files that you want copied to config if they don't exist there already.   The two important ones in there would be the default strings configuration and the config for GPIO inputs (for navigating the OLED menus).   You can create those from the UI and just copy them from the fpp/media/config directory to package into the eeprom.     You'd also want a strings/CAPENAME.json file to describe the string output config.  Likely can copy the RGBCape48F.json as a starting point and just update the few lines at the top.

That all said, if xLights is changing the cape type, that seems to be a bug in xLights.   If you tell xLights you have a particular cape, it should push the config with that ID.   I think the issue is that the ID for the HE123 is set to HE123 instead of RGBCape48F.      Changing that in the xLights config may fix the issue.   However, an actual
Daniel Kulp -

Support FPP

+- Recent Topics

Warning/Error: Network incomplete frames hit 250. by JonD
Today at 10:59:15 AM

F16V3 with 2 expansion boards at 40 fps MAX PIXELS per output? by tbone321
February 06, 2023, 10:51:55 AM

F48V4-NS at 40 fps using all 48 pixel output ports? by Poporacer
February 06, 2023, 10:27:09 AM

Unable to update RPi 5.5 to latest version by JonB256
February 05, 2023, 07:23:16 PM

help getting started, next step? by rayster
February 05, 2023, 04:24:09 PM

F48v4NS - Pi or No Pi? by joeyblasko
February 05, 2023, 09:15:33 AM

Huidu Controllers LED matrix by CaptainMurdoch
February 04, 2023, 10:18:47 AM

FPP6.2 universes by darylc
February 03, 2023, 08:48:57 PM

F16v4 Ports vs Universe Configuration Question by k6ccc
February 03, 2023, 09:32:48 AM

Need Expert Advise on F16v4 Ports vs Universe Configuration by Kairus
February 03, 2023, 09:32:33 AM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod