new K16 Max, its sick

[gunther]

I got a new K16 Max a month or so back.  I powered it up and it had FPP 9.x installed already, so I fiddled with setup and got through the initial setup and updates.   I didn't try the ports then.

A couple of days ago I decided it was time to try the outputs.  test mode produces no output on any of the ports I tried.  then I noticed the configuration seems to be signed with a Hanson PB signature.   I tried changing to kulp lights in the cape info menu, but the sub menus for choosing a controller don't offer any choices, it seems inactive.  

I tried downloading the k16 max eeprom code from kulp github and uploaded to the controller via the upload button in the cape info menu. The result is the board is accepted as an unlicensed k16 max but no option  to sign. Under eeprom signature, the error is "WARNING: The location field specified in this EEPROM is invalid so the EEPROM is being treated as unsigned."  The upgrade process shows "Upgrading firmware.....

Found Cape: K16-Max  Version: 4.0
Upgrade Complete

======================
Running fppcapedetect:

Did not find 0x50 on i2c2, trying i2c1.
Did not find eeprom on i2c.
EEPROM file doesn't exist .
Using /home/fpp/media/config/cape-eeprom.bin
Found cape K16-Max, Version 4.0, Serial Number: FPP-INTERNAL
- signature verified for key ID: dk
- ERROR eeprom location is NOT valid
- extracted file: /tmp/fppcuGDkVnp/tmp/cape-info.tgz

Finished, please reboot."

The inability to find the eeprom is worrisome.  Any ideas?  

[gunther]

Hey all, it turns out my new board had hardware issues.  The esteemed Mr. Kulp worked through diagnosing the board with me over email, and found the board indeed had issues.  He sent a new board 2nd day delivery!  The new board works perfectly.  Thanks again to KulpLights, what great response!