I received another AI Fusion Lab Kit from Amazon, and it has the same problem. I tested the hat on two different Pi 5 16GB boards.
I think you might have a QA problem.
I received another AI Fusion Lab Kit from Amazon, and it has the same problem. I tested the hat on two different Pi 5 16GB boards.
I think you might have a QA problem.
First, we owe you a direct apology.
After reviewing all the logs and test results internally, we confirmed the root cause — and you were right, this is not user error.
The issue is an EEPROM address conflict between the current Fusion HAT+ and the Pironman 5 series (including both your Pironman 5 MAX and the Pro MAX you recently ordered).
Both devices use the standard Raspberry Pi HAT EEPROM address (0x50). When connected together, they conflict on the I2C bus, which is why EEPROM verification failed and the driver could not initialize correctly.
The good news is that your Fusion HAT+ boards are most likely NOT defective.
To work around this, we updated the Fusion HAT software to support a forced device-tree-overlay mode, which bypasses EEPROM detection entirely.
Please try the following:
1. Update the Fusion HAT software
curl -sSL https://raw.githubusercontent.com/sunfounder/sunfounder-installer-scripts/main/install-fusion-hat.sh | sudo bash
2. Force enable the overlay
fusion_hat force_dt_overlay
3. Reboot
4. Verify
fusion_hat doctor
fusion_hat info
This workaround bypasses the EEPROM conflict and should allow Fusion HAT+ to work together with the Pironman 5 series.
We’ve also updated the Pironman 5 software with the same workaround:
curl -sSL “https://raw.githubusercontent.com/sunfounder/sunfounder-installer-scripts/main/pironman5/install.sh” | sudo bash
However, the Pironman 5 Pro MAX has not finished validation yet, so we cannot fully guarantee compatibility on that model at this moment.
Again, we sincerely apologize for the frustration and truly appreciate the detailed debugging work you provided. Your testing helped us identify a real issue that we had not previously encountered internally.
That fixed everything! Thank you!