FPP PB16 Pixel Cont...
 
Notifications
Clear all

FPP PB16 Pixel Controller

630 Posts
62 Users
6 Reactions
389.4 K Views
Posts: 447
(@glycerine)
Honorable Member
Joined: 7 years ago
woganaga wrote:Hi Scott & PB16 Experts -

Quick question on the circuit design - what is the EEPROM IC for - what data is flashed on to it, what does it enable the board to do?

Thank you!

There's a bin file that get's flashed to the EEPROM. I'm not sure the totality of what it does, but I believe it essentially stores settings about the board, so if you re-image the sd card, those settings will persist.


Reply
Posts: 629
(@dkulp)
Honorable Member
Joined: 14 years ago
woganaga wrote:
Quick question on the circuit design - what is the EEPROM IC for - what data is flashed on to it, what does it enable the board to do?

Bit of history: When the Beagles were first used to drive pixels, the pins that were associated with each port were hard coded into FPP. The original F4B, F16B, and RGBCape48 pinouts were compiled directly into FPP. This basically meant that anyone that was designing new capes that used a different pinout had to add a bunch of code into FPP, wait for an FPP release, etc... in order for the boards to work. In the 2.x timeframe, the pinouts were moved out of FPP and into json files. They were still part of FPP releases (in /opt/fpp/capes/bbb ) but it made it a lot easier to update things as well as to add new boards. In 2019, when I designed my new boards, I decided to add an eeprom to the boards and have the pinouts JSON stored on the eeprom. Thus, in the future, FPP doesn't need to know ahead of time what the pinout is and such. While doing this, I also allowed storing other things on the eeprom (like default string configs, default settings, etc...). Anyway, that's pretty much what is on the eeprom image. Just makes it possible for FPP to know what the cape is and configure itself appropriately without needed a bunch of changes in FPP for each board.


Reply
ukewarrior
Posts: 4674
(@ukewarrior)
Illustrious Member
Joined: 18 years ago

Brilliant!

dkulp wrote:Bit of history: When the Beagles were first used to drive pixels, the pins that were associated with each port were hard coded into FPP. The original F4B, F16B, and RGBCape48 pinouts were compiled directly into FPP. This basically meant that anyone that was designing new capes that used a different pinout had to add a bunch of code into FPP, wait for an FPP release, etc... in order for the boards to work. In the 2.x timeframe, the pinouts were moved out of FPP and into json files. They were still part of FPP releases (in /opt/fpp/capes/bbb ) but it made it a lot easier to update things as well as to add new boards. In 2019, when I designed my new boards, I decided to add an eeprom to the boards and have the pinouts JSON stored on the eeprom. Thus, in the future, FPP doesn't need to know ahead of time what the pinout is and such. While doing this, I also allowed storing other things on the eeprom (like default string configs, default settings, etc...). Anyway, that's pretty much what is on the eeprom image. Just makes it possible for FPP to know what the cape is and configure itself appropriately without needed a bunch of changes in FPP for each board.

Reply
Posts: 22
(@woganaga)
Eminent Member
Joined: 6 years ago
dkulp wrote:Bit of history: When the Beagles were first used to drive pixels, the pins that were associated with each port were hard coded into FPP. The original F4B, F16B, and RGBCape48 pinouts were compiled directly into FPP. This basically meant that anyone that was designing new capes that used a different pinout had to add a bunch of code into FPP, wait for an FPP release, etc... in order for the boards to work. In the 2.x timeframe, the pinouts were moved out of FPP and into json files. They were still part of FPP releases (in /opt/fpp/capes/bbb ) but it made it a lot easier to update things as well as to add new boards. In 2019, when I designed my new boards, I decided to add an eeprom to the boards and have the pinouts JSON stored on the eeprom. Thus, in the future, FPP doesn't need to know ahead of time what the pinout is and such. While doing this, I also allowed storing other things on the eeprom (like default string configs, default settings, etc...). Anyway, that's pretty much what is on the eeprom image. Just makes it possible for FPP to know what the cape is and configure itself appropriately without needed a bunch of changes in FPP for each board.

Dan - Thank you very much!


Reply
Posts: 447
(@glycerine)
Honorable Member
Joined: 7 years ago

I have a bunch of the diff receivers built and plan to use them this year. Was thinking of just getting a kulp 40d-pb since it's a little more compact. These diff receivers would work with the kulp, right?


Reply
Page 62 / 126
Share: