Pippa and Charlie
New elf
- Joined
- Aug 31, 2023
- Messages
- 7
Hi all,
Ive had a HE123 mk2 as my show board for 3 years and I can no longer see it on fpp and my lights no longer output after rebooting.
It has been working this season but a few times I needed to reseat the beaglebone before it worked after throwing the bb string error attached. Now, I'm having the same error and reseating /power cycling isn't working.
My logs indicate that fpp can't see the board via i2c and I'm not sure where to look next. We paid for a fpp license for the board 3 yrs ago and I have the eeprom file and key, but can't see anywhere to upload the eeprom file again.
Power supply is working fine, tested with multimeter. The he123 screen shows normal boot sequence and player is idle with the right ip address even though fpp can't see the cape.
What should I be trying/what am I missing here? Thanks for any help!
Edit:
Adding fpp troubleshooting command fppcapedetect, output below:
fpp@SAFPP:~$ sudo journalctl -u fppcapedetect | tail -20
Feb 09 06:22:40 SAFPP systemd[1]: Starting fppcapedetect.service - FPP Cape Detection...
Feb 09 06:22:40 SAFPP detect_cape[282]: Running detect_cape
Feb 09 06:22:41 SAFPP detect_cape[282]: Running fppcapedetect
Feb 09 06:22:42 SAFPP detect_cape[299]: Did not find 0x50 on i2c2, trying i2c1.
Feb 09 06:22:42 SAFPP detect_cape[299]: Did not find eeprom on i2c.
Feb 09 06:22:42 SAFPP detect_cape[299]: EEPROM file doesn't exist .
Feb 09 06:22:42 SAFPP detect_cape[299]: Could not detect any cape
Feb 09 06:22:42 SAFPP detect_cape[282]: Done fppcapedetect
Feb 09 06:22:43 SAFPP detect_cape[282]: Done
Feb 09 06:22:43 SAFPP systemd[1]: fppcapedetect.service: Deactivated successfully.
Feb 09 06:22:43 SAFPP systemd[1]: Finished fppcapedetect.service - FPP Cape Detection.
Not sure if it is meaningful that the system time/date is wrong. FPP shows the right time and date, connected to an NTP server, but the above output is direct from ssh shell today (3rd Dec 7am)
Ive had a HE123 mk2 as my show board for 3 years and I can no longer see it on fpp and my lights no longer output after rebooting.
It has been working this season but a few times I needed to reseat the beaglebone before it worked after throwing the bb string error attached. Now, I'm having the same error and reseating /power cycling isn't working.
My logs indicate that fpp can't see the board via i2c and I'm not sure where to look next. We paid for a fpp license for the board 3 yrs ago and I have the eeprom file and key, but can't see anywhere to upload the eeprom file again.
Power supply is working fine, tested with multimeter. The he123 screen shows normal boot sequence and player is idle with the right ip address even though fpp can't see the cape.
What should I be trying/what am I missing here? Thanks for any help!
Edit:
Adding fpp troubleshooting command fppcapedetect, output below:
fpp@SAFPP:~$ sudo journalctl -u fppcapedetect | tail -20
Feb 09 06:22:40 SAFPP systemd[1]: Starting fppcapedetect.service - FPP Cape Detection...
Feb 09 06:22:40 SAFPP detect_cape[282]: Running detect_cape
Feb 09 06:22:41 SAFPP detect_cape[282]: Running fppcapedetect
Feb 09 06:22:42 SAFPP detect_cape[299]: Did not find 0x50 on i2c2, trying i2c1.
Feb 09 06:22:42 SAFPP detect_cape[299]: Did not find eeprom on i2c.
Feb 09 06:22:42 SAFPP detect_cape[299]: EEPROM file doesn't exist .
Feb 09 06:22:42 SAFPP detect_cape[299]: Could not detect any cape
Feb 09 06:22:42 SAFPP detect_cape[282]: Done fppcapedetect
Feb 09 06:22:43 SAFPP detect_cape[282]: Done
Feb 09 06:22:43 SAFPP systemd[1]: fppcapedetect.service: Deactivated successfully.
Feb 09 06:22:43 SAFPP systemd[1]: Finished fppcapedetect.service - FPP Cape Detection.
Not sure if it is meaningful that the system time/date is wrong. FPP shows the right time and date, connected to an NTP server, but the above output is direct from ssh shell today (3rd Dec 7am)
Attachments
Last edited:
