New K8-PB - no voltage at ports

[mtbehnke]

Hi all,

Just bought a new K8-PB (v2.1.0) with Pocket Beagle already mounted and and an imaged SD card.  Connected it up to a 12V Meanwell power supply and was able to connect to it via ethernet and get it all set up.

Tried test mode and couldn't get pixels to light up, eventually realizing that there was no voltage at the string ports.  The LEDs next to each port were also not lit.

Finally realized that the SD card installed FPP 6.3, whereas the K8-PB needs FPP v7 to enable the ports.  Upgraded the OS/FPP to 7.5 via the about page, but that didn't resolve the issue.  A full reimage to v7.5 hasn't fixed the issue either.

I've been using FPP for quite a few years, so I'm pretty familiar with how to set everything up.  I tried manually setting the config, having xLights upload it, tried testing via the FPP test page, the channel page and also xLights outputting directly to the controller.

I also saw on the Kulp K8-PB page it shows a 'FPP Current Monitor' page, which I haven't been able to find anywhere in FPP.

FPP recognizes that there's a K8-PB connected to it, as shown on the Channel Outputs page.  I did notice that the FPP Cape Detect Log shows "detect_cape[308]: Found cape K8-PB, Version 1.0".  My understanding is that the 2.x version of the board replaced the mini-blade fuses with eFuses.

I'm wondering if there's a bug in the cape detection that makes FPP think there's physical fuses, so it's not turning on the efuses for each port or showing the current monitoring page.

Any other ideas?

Thanks,
Mike

[MikeKrebs]

It sure sounds like a bad version of FPP and a bad eeprom for your hardware. I would suggest contacting Daniel and sort it out directly. Since he writes a bunch of FPP stuff, he will know exactly what is going on.

[dkulp]

Sounds like it was flashed with the 1.x firmware and not the 2.0 firmware.  Easy fix with 7.5 from the Cape Info -> Upgrade EEprom  page.   Select the correct vender/board/version from the drop downs and hit flash and it should handle it all for you.

[mtbehnke]

Upgrading to the 2.0 firmware fixed it

Thanks!