AI Fusion HAT+ Not Recognized

Accessories for Raspberry Pi and Arduino
1

I am trying to use the AI Fusion Lab Kit with my Pi 16 GB in the Pironman case.
I used Pi Imager to copy the image to the SD Card.
When I connect the AI Fusion HAT+ to the GPIO port in the case, it is not recognized.​
The Power button on the AI Fusion HAT+ will power the Pi 5 on.

unnamed
unnamed1672×553 8.42 KB

​

pi@ai-fusion:~ $ fusion_hat doctor --fix

==================================================

Fusion Hat Driver Doctor (–fix)

[Before]
[FAIL] EEPROM detected
[OK] Module file
[FAIL] Module loaded
[FAIL] sysfs interface
[FAIL] I2C MCU (0x17)
[OK] DKMS : fusion_hat/1.0.2, 6.12.47+rpt-rpi-2712, aarch64: installed

[Actions]
→ modprobe fusion_hat

[After]
[FAIL] EEPROM detected
[OK] Module file
[OK] Module loaded
[FAIL] sysfs interface
[FAIL] I2C MCU (0x17)
[OK] DKMS : fusion_hat/1.0.2, 6.12.47+rpt-rpi-2712, aarch64: installed

Some issues could not be auto-fixed.
→ Fusion Hat not detected. Check physical connection.

==================================================

unnamed
unnamed631×232 3.09 KB

pi@ai-fusion:~ $ sudo /opt/setup_fusion_hat_audio.sh
Setup Fusion Hat audio driver >>>
script version: 1.0.1
user: pi

apt update…
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
206 packages can be upgraded. Run ‘apt list --upgradable’ to see them.
install apt packages …
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
i2c-tools is already the newest version (4.3-2+b3).
alsa-utils is already the newest version (1.2.8-1+rpt1).
pulseaudio is already the newest version (16.1+dfsg1-2+rpt1.1).
pulseaudio-utils is already the newest version (16.1+dfsg1-2+rpt1.1).
jq is already the newest version (1.6-2.1+deb12u1).
sox is already the newest version (14.4.2+git20190427-3.5).
0 upgraded, 0 newly installed, 0 to remove and 206 not upgraded.

Trying to load dtoverlay googlevoicehat-soundcard …
get_soundcard_index …
soundcard sndrpigooglevoi index: 2

config /etc/asound.conf …
set ALSA speaker volume to 100% …
Failed to set speaker volume, but continuing…
set ALSA microphone volume to 100% …
Failed to set microphone volume, but continuing…

config pulseaudio …
raspi-config enable pulseaudio …
run pulseaudio …

get_sink_index …
sink index: 1
set default sink …
get_source_index …
source index: 2
set default source …
set default Pulseaudio volume to 100% …

Do you wish to test speaker now? [y/N] y
open speaker …
/opt/setup_fusion_hat_audio.sh: line 411: /sys/class/fusion_hat/fusion_hat/speaker: No such file or directory
testing speaker …

speaker-test 1.2.8

Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 2048 to 8192
Period size range from 1024 to 1024
Using max buffer size 8192
Periods = 4
was set period_size = 1024
was set buffer_size = 8192
0 - Front Left
1 - Front Right
Time per period = 2.851967
0 - Front Left
^CWrite error: -4,Interrupted system call
xrun_recovery failed: -4,Interrupted system call
Transfer failed: Interrupted system call

pi@ai-fusion:~ $ pulseaudio
E: [pulseaudio] pid.c: Daemon already running.
E: [pulseaudio] main.c: pa_pid_file_create() failed.
pi@ai-fusion:~ $

image
image977×497 10.1 KB

image(1)
image(1)981×497 3.24 KB

unnamed
unnamed487×462 13.7 KB

pi@ai-fusion:~ $ clear
pi@ai-fusion:~ $ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – –
10: – – – – – – – 17 – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – 3c – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –
pi@ai-fusion:~ $ cd ~/fusion-hat/driver/
pi@ai-fusion:~/fusion-hat/driver $ make
Building Fusion Hat driver and device tree overlay…
make -C /lib/modules/6.12.47+rpt-rpi-2712/build M=/home/pi/fusion-hat/driver modules
make[1]: Entering directory ‘/usr/src/linux-headers-6.12.47+rpt-rpi-2712’
make[1]: Leaving directory ‘/usr/src/linux-headers-6.12.47+rpt-rpi-2712’
Compiling device tree overlay…
dtc -@ -I dts -O dtb -o sunfounder-fusionhat.dtbo sunfounder-fusionhat-overlay.dts
Build completed successfully.
pi@ai-fusion:~/fusion-hat/driver $ sudo make install
Installing Fusion Hat driver and device tree overlay…
rmmod fusion_hat || echo “Warning: Failed to unload fusion_hat module. It may be in use or require additional privileges.”
rmmod: ERROR: Module fusion_hat is not currently loaded
Warning: Failed to unload fusion_hat module. It may be in use or require additional privileges.
make[1]: Entering directory ‘/home/pi/fusion-hat/driver’
Installing kernel module…
make -C /lib/modules/6.12.47+rpt-rpi-2712/build M=/home/pi/fusion-hat/driver modules_install
make[2]: Entering directory ‘/usr/src/linux-headers-6.12.47+rpt-rpi-2712’
INSTALL /lib/modules/6.12.47+rpt-rpi-2712/updates/fusion_hat.ko
XZ /lib/modules/6.12.47+rpt-rpi-2712/updates/fusion_hat.ko.xz
DEPMOD /lib/modules/6.12.47+rpt-rpi-2712
Warning: modules_install: missing ‘System.map’ file. Skipping depmod.
make[2]: Leaving directory ‘/usr/src/linux-headers-6.12.47+rpt-rpi-2712’
Loading required IIO subsystem module…
Updating module dependencies…
depmod -a
Module installation completed.
make[1]: Leaving directory ‘/home/pi/fusion-hat/driver’
make[1]: Entering directory ‘/home/pi/fusion-hat/driver’
Installing device tree overlay to /boot/firmware/overlays/
make[1]: Leaving directory ‘/home/pi/fusion-hat/driver’
Loading fusion_hat module…
modprobe: ERROR: could not insert ‘fusion_hat’: Invalid argument
Warning: Failed to load fusion_hat module. Please check the driver installation.
Installation completed successfully.
pi@ai-fusion:~/fusion-hat/driver $ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – –
10: – – – – – – – 17 – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – 3c – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –
pi@ai-fusion:~/fusion-hat/driver $

pi@ai-fusion:~ $ uname -a
Linux ai-fusion 6.12.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16) aarch64 GNU/Linux
pi@ai-fusion:~ $ cat /etc/os-release
PRETTY_NAME=“Debian GNU/Linux 12 (bookworm)”
NAME=“Debian GNU/Linux”
VERSION_ID=“12”
VERSION=“12 (bookworm)”
VERSION_CODENAME=bookworm
ID=debian
HOME_URL=“https://www.debian.org/”
SUPPORT_URL=“Debian -- User Support”
BUG_REPORT_URL=“https://bugs.debian.org/”
pi@ai-fusion:~ $ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – –
10: – – – – – – – 17 – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – 3c – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –
pi@ai-fusion:~ $ dmesg | grep fusion_hat
[ 146.972962] fusion_hat: loading out-of-tree module taints kernel.
[ 146.973017] fusion_hat: disagrees about version of symbol _dev_info
[ 146.973019] fusion_hat: Unknown symbol _dev_info (err -22)
[ 146.973023] fusion_hat: disagrees about version of symbol device_create_file
[ 146.973025] fusion_hat: Unknown symbol device_create_file (err -22)
[ 146.973027] fusion_hat: disagrees about version of symbol i2c_register_driver
[ 146.973028] fusion_hat: Unknown symbol i2c_register_driver (err -22)
[ 146.973030] fusion_hat: disagrees about version of symbol _dev_err
[ 146.973031] fusion_hat: Unknown symbol _dev_err (err -22)
[ 146.973048] fusion_hat: disagrees about version of symbol i2c_smbus_read_word_data
[ 146.973050] fusion_hat: Unknown symbol i2c_smbus_read_word_data (err -22)
[ 146.973057] fusion_hat: disagrees about version of symbol device_create_with_groups
[ 146.973059] fusion_hat: Unknown symbol device_create_with_groups (err -22)
[ 146.973063] fusion_hat: disagrees about version of symbol device_destroy
[ 146.973064] fusion_hat: Unknown symbol device_destroy (err -22)
[ 146.973067] fusion_hat: disagrees about version of symbol i2c_smbus_write_byte_data
[ 146.973068] fusion_hat: Unknown symbol i2c_smbus_write_byte_data (err -22)
[ 146.973071] fusion_hat: disagrees about version of symbol i2c_smbus_write_word_data
[ 146.973072] fusion_hat: Unknown symbol i2c_smbus_write_word_data (err -22)
[ 146.973074] fusion_hat: disagrees about version of symbol i2c_smbus_read_i2c_block_data
[ 146.973076] fusion_hat: Unknown symbol i2c_smbus_read_i2c_block_data (err -22)
[ 146.973078] fusion_hat: disagrees about version of symbol i2c_del_driver
[ 146.973079] fusion_hat: Unknown symbol i2c_del_driver (err -22)
[ 146.973082] fusion_hat: disagrees about version of symbol param_ops_int
[ 146.973083] fusion_hat: Unknown symbol param_ops_int (err -22)
[ 146.973085] fusion_hat: disagrees about version of symbol i2c_smbus_read_byte_data
[ 146.973086] fusion_hat: Unknown symbol i2c_smbus_read_byte_data (err -22)
[ 146.973089] fusion_hat: disagrees about version of symbol device_remove_file
[ 146.973090] fusion_hat: Unknown symbol device_remove_file (err -22)
[ 304.354868] fusion_hat: disagrees about version of symbol _dev_info
[ 304.354875] fusion_hat: Unknown symbol _dev_info (err -22)
[ 304.354880] fusion_hat: disagrees about version of symbol device_create_file
[ 304.354881] fusion_hat: Unknown symbol device_create_file (err -22)
[ 304.354884] fusion_hat: disagrees about version of symbol i2c_register_driver
[ 304.354885] fusion_hat: Unknown symbol i2c_register_driver (err -22)
[ 304.354887] fusion_hat: disagrees about version of symbol _dev_err
[ 304.354889] fusion_hat: Unknown symbol _dev_err (err -22)
[ 304.354906] fusion_hat: disagrees about version of symbol i2c_smbus_read_word_data
[ 304.354908] fusion_hat: Unknown symbol i2c_smbus_read_word_data (err -22)
[ 304.354915] fusion_hat: disagrees about version of symbol device_create_with_groups
[ 304.354917] fusion_hat: Unknown symbol device_create_with_groups (err -22)
[ 304.354921] fusion_hat: disagrees about version of symbol device_destroy
[ 304.354922] fusion_hat: Unknown symbol device_destroy (err -22)
[ 304.354925] fusion_hat: disagrees about version of symbol i2c_smbus_write_byte_data
[ 304.354926] fusion_hat: Unknown symbol i2c_smbus_write_byte_data (err -22)
[ 304.354929] fusion_hat: disagrees about version of symbol i2c_smbus_write_word_data
[ 304.354930] fusion_hat: Unknown symbol i2c_smbus_write_word_data (err -22)
[ 304.354933] fusion_hat: disagrees about version of symbol i2c_smbus_read_i2c_block_data
[ 304.354934] fusion_hat: Unknown symbol i2c_smbus_read_i2c_block_data (err -22)
[ 304.354936] fusion_hat: disagrees about version of symbol i2c_del_driver
[ 304.354937] fusion_hat: Unknown symbol i2c_del_driver (err -22)
[ 304.354940] fusion_hat: disagrees about version of symbol param_ops_int
[ 304.354941] fusion_hat: Unknown symbol param_ops_int (err -22)
[ 304.354943] fusion_hat: disagrees about version of symbol i2c_smbus_read_byte_data
[ 304.354944] fusion_hat: Unknown symbol i2c_smbus_read_byte_data (err -22)
[ 304.354947] fusion_hat: disagrees about version of symbol device_remove_file
[ 304.354949] fusion_hat: Unknown symbol device_remove_file (err -22)
pi@ai-fusion:~ $ lsmod | grep fusion_hat
pi@ai-fusion:~ $ ls /sys/class/fusion_hat/fusion_hat
ls: cannot access ‘/sys/class/fusion_hat/fusion_hat’: No such file or directory
pi@ai-fusion:~ $ cat ~/.ai-fusion
AI Fusion Lab Kit image
#################################
Version: 0.2.1
Date: 2026-04-29
SunFounder
pi@ai-fusion:~ $ clear
pi@ai-fusion:~ $ history -c
pi@ai-fusion:~ $ clear
pi@ai-fusion:~ $ uname -a
Linux ai-fusion 6.12.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16) aarch64 GNU/Linux
pi@ai-fusion:~ $ cat /etc/os-release
PRETTY_NAME=“Debian GNU/Linux 12 (bookworm)”
NAME=“Debian GNU/Linux”
VERSION_ID=“12”
VERSION=“12 (bookworm)”
VERSION_CODENAME=bookworm
ID=debian
HOME_URL=“https://www.debian.org/”
SUPPORT_URL=“Debian -- User Support”
BUG_REPORT_URL=“https://bugs.debian.org/”
pi@ai-fusion:~ $ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – –
10: – – – – – – – 17 – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – 3c – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –
pi@ai-fusion:~ $ dmesg | grep fusion_hat
[ 146.972962] fusion_hat: loading out-of-tree module taints kernel.
[ 146.973017] fusion_hat: disagrees about version of symbol _dev_info
[ 146.973019] fusion_hat: Unknown symbol _dev_info (err -22)
[ 146.973023] fusion_hat: disagrees about version of symbol device_create_file
[ 146.973025] fusion_hat: Unknown symbol device_create_file (err -22)
[ 146.973027] fusion_hat: disagrees about version of symbol i2c_register_driver
[ 146.973028] fusion_hat: Unknown symbol i2c_register_driver (err -22)
[ 146.973030] fusion_hat: disagrees about version of symbol _dev_err
[ 146.973031] fusion_hat: Unknown symbol _dev_err (err -22)
[ 146.973048] fusion_hat: disagrees about version of symbol i2c_smbus_read_word_data
[ 146.973050] fusion_hat: Unknown symbol i2c_smbus_read_word_data (err -22)
[ 146.973057] fusion_hat: disagrees about version of symbol device_create_with_groups
[ 146.973059] fusion_hat: Unknown symbol device_create_with_groups (err -22)
[ 146.973063] fusion_hat: disagrees about version of symbol device_destroy
[ 146.973064] fusion_hat: Unknown symbol device_destroy (err -22)
[ 146.973067] fusion_hat: disagrees about version of symbol i2c_smbus_write_byte_data
[ 146.973068] fusion_hat: Unknown symbol i2c_smbus_write_byte_data (err -22)
[ 146.973071] fusion_hat: disagrees about version of symbol i2c_smbus_write_word_data
[ 146.973072] fusion_hat: Unknown symbol i2c_smbus_write_word_data (err -22)
[ 146.973074] fusion_hat: disagrees about version of symbol i2c_smbus_read_i2c_block_data
[ 146.973076] fusion_hat: Unknown symbol i2c_smbus_read_i2c_block_data (err -22)
[ 146.973078] fusion_hat: disagrees about version of symbol i2c_del_driver
[ 146.973079] fusion_hat: Unknown symbol i2c_del_driver (err -22)
[ 146.973082] fusion_hat: disagrees about version of symbol param_ops_int
[ 146.973083] fusion_hat: Unknown symbol param_ops_int (err -22)
[ 146.973085] fusion_hat: disagrees about version of symbol i2c_smbus_read_byte_data
[ 146.973086] fusion_hat: Unknown symbol i2c_smbus_read_byte_data (err -22)
[ 146.973089] fusion_hat: disagrees about version of symbol device_remove_file
[ 146.973090] fusion_hat: Unknown symbol device_remove_file (err -22)
[ 304.354868] fusion_hat: disagrees about version of symbol _dev_info
[ 304.354875] fusion_hat: Unknown symbol _dev_info (err -22)
[ 304.354880] fusion_hat: disagrees about version of symbol device_create_file
[ 304.354881] fusion_hat: Unknown symbol device_create_file (err -22)
[ 304.354884] fusion_hat: disagrees about version of symbol i2c_register_driver
[ 304.354885] fusion_hat: Unknown symbol i2c_register_driver (err -22)
[ 304.354887] fusion_hat: disagrees about version of symbol _dev_err
[ 304.354889] fusion_hat: Unknown symbol _dev_err (err -22)
[ 304.354906] fusion_hat: disagrees about version of symbol i2c_smbus_read_word_data
[ 304.354908] fusion_hat: Unknown symbol i2c_smbus_read_word_data (err -22)
[ 304.354915] fusion_hat: disagrees about version of symbol device_create_with_groups
[ 304.354917] fusion_hat: Unknown symbol device_create_with_groups (err -22)
[ 304.354921] fusion_hat: disagrees about version of symbol device_destroy
[ 304.354922] fusion_hat: Unknown symbol device_destroy (err -22)
[ 304.354925] fusion_hat: disagrees about version of symbol i2c_smbus_write_byte_data
[ 304.354926] fusion_hat: Unknown symbol i2c_smbus_write_byte_data (err -22)
[ 304.354929] fusion_hat: disagrees about version of symbol i2c_smbus_write_word_data
[ 304.354930] fusion_hat: Unknown symbol i2c_smbus_write_word_data (err -22)
[ 304.354933] fusion_hat: disagrees about version of symbol i2c_smbus_read_i2c_block_data
[ 304.354934] fusion_hat: Unknown symbol i2c_smbus_read_i2c_block_data (err -22)
[ 304.354936] fusion_hat: disagrees about version of symbol i2c_del_driver
[ 304.354937] fusion_hat: Unknown symbol i2c_del_driver (err -22)
[ 304.354940] fusion_hat: disagrees about version of symbol param_ops_int
[ 304.354941] fusion_hat: Unknown symbol param_ops_int (err -22)
[ 304.354943] fusion_hat: disagrees about version of symbol i2c_smbus_read_byte_data
[ 304.354944] fusion_hat: Unknown symbol i2c_smbus_read_byte_data (err -22)
[ 304.354947] fusion_hat: disagrees about version of symbol device_remove_file
[ 304.354949] fusion_hat: Unknown symbol device_remove_file (err -22)
pi@ai-fusion:~ $ lsmod | grep fusion_hat
pi@ai-fusion:~ $ ls /sys/class/fusion_hat/fusion_hat
ls: cannot access ‘/sys/class/fusion_hat/fusion_hat’: No such file or directory
pi@ai-fusion:~ $ cat ~/.ai-fusion

Please let me know if I can provide any further information to assist you.

Conflicting drivers for pironman5 and fusion hat
2

Thank you for the detailed information and logs.

From your fusion_hat doctor --fix result, we can see:

[FAIL] EEPROM detected

This indicates that the Fusion HAT EEPROM is blank or corrupted, so the Raspberry Pi cannot properly identify the HAT.

Today, our development team updated the Fusion HAT repository and improved the EEPROM recovery tool. Please follow the steps below again to update the tools and reflash the EEPROM:

Step 1 – Update Fusion HAT
Run the following command in the terminal:

curl -sSL https://raw.githubusercontent.com/sunfounder/sunfounder-installer-scripts/main/install-fusion-hat.sh | sudo bash

Step 2 – Reflash the EEPROM
After rebooting, run:

fusion_hat doctor --fix

This will guide you through reflashing the EEPROM. Please follow the on‑screen instructions carefully, then reboot again when prompted.

Step 3 – Verify the repair
After the repair process completes, please run fusion_hat doctor again.

If everything is working normally, you should now see all Fusion HAT related information correctly detected.

Please let us know the results after trying these steps.

4

I think its this, middle left on your photo, but please await official reply!

885
885478×492 40.3 KB

The eeprom is the 8 pin chip below the 5 holes in your photo

888
888750×1000 170 KB

1 Like
5

OK, well, I guess I’m blind. Thank you.

1 Like
6

[3/4] Flash EEPROM…
sudo: /usr/local/lib/python3.11/dist-packages/fusion_hat/scripts/eepflash.sh: command not found

[FAIL] EEPROM write failed. Check output above for details.

==================================================

Fusion Hat Doctor (–fix)

-> EEPROM reflash failed

==================================================

7

OK, I’m at my wits’ end here! I found the 5-pin header, shorted the pins as directed, and it failed!

[3/4] Flash EEPROM…
sudo: /usr/local/lib/python3.11/dist-packages/fusion_hat/scripts/eepflash.sh: command not found

I honestly think it’s time to cut my losses with Sunfounder and just throw the damn HAT+ in the garbage!

8

(post deleted by author)

9

First of all, we sincerely apologize for the frustrating troubleshooting experience you have had, and we truly appreciate the considerable time and patience you have put into this process.

We carefully reviewed all the logs and details you provided, and we would like to explain a few points:

1. About the 5-pin header location

This was indeed caused by our instructions not being clear enough.

Previously, we only described it as “the 5-pin header next to the EEPROM,” but did not provide a clearly marked image. For the Fusion HAT+, this could certainly be confusing.

This was our shortcoming, and we should have provided a picture showing the exact location.

We will improve the repair guide and add this information to the FAQ section of the documentation to help prevent other users from encountering the same issue.

2. About the permission / command issue

The “eepflash.sh: command not found” issue was indeed caused by a script configuration problem in our library. This was our mistake.

We have now updated the Fusion HAT library to fix this issue.

Also, we have to say that you did an excellent job identifying and resolving the permission issue yourself. This shows how carefully and professionally you approached the troubleshooting process, and we truly appreciate your patience.

3. About the EEPROM still not being detected after the repair

Based on the final log you provided:

Writing…

Done.

the EEPROM flashing process appears to have completed successfully.

However, at the final step:

[4/4] Remove short. Then reboot to detect the HAT.

it looks like the reboot may not have been performed afterward, so the system did not reload the EEPROM information. As a result, it continued to show “EEPROM not detected.”

Therefore, could you please try the following steps:

1. Remove the write-protect short.

2. Fully reboot the Raspberry Pi:

sudo reboot

3. After the reboot, run:

fusion_hat doctor

At this point, it looks very likely that the EEPROM has already been repaired successfully, and the system simply needs one reboot to detect it and load the driver．

Once again, we sincerely apologize for the unclear instructions and the script issue.

Your feedback is very important to us, and we have already started improving the related tools and documentation based on your experience.

Thank you again for your continued patience and cooperation throughout this troubleshooting process.

10

pi@ai-fusion:~ $ fusion_hat doctor --fix

============================================================

Fusion Hat EEPROM Update

[1/4] Downloading EEPROM binary…
[OK] Downloaded: o1908v10_fusion_hat.eep (99 bytes)

[2/4] Short write-protect pins

The EEPROM chip is write-protected. To enable writing,
short the two OUTERMOST holes of the 5-pin header next to
the EEPROM chip on the Fusion Hat board.

||||
┌────┐
│ │
│ │[ o ] ← short this
│ │[ o ]
└────┘[ o ]
|||| [ o ]
[ o ] ← short this

WARNING: Only short the two marked pins (outermost).
Shorting other holes may cause the Pi to shut down.

Press ENTER after you have shorted the pins…

[3/4] Flash EEPROM…
This will attempt to talk to an eeprom at i2c address 0x50. Make sure there is an eeprom at this address.
This script comes with ABSOLUTELY no warranty. Continue only if you know what you are doing.
Writing…
Closing EEPROM Device.
Done.

[4/4] Done. You can remove the short from the write-protect pins now.
Reboot to detect the HAT? (y/N): y
Rebooting…

Broadcast message from root@ai-fusion on pts/1 (Wed 2026-05-20 12:02:25 EDT):

The system will reboot now!

pi@ai-fusion:~ $ fusion_hat doctor
[sudo] password for pi:

==================================================

Fusion Hat Driver Status

✗ HAT detected
✗ EEPROM chip (0x50)
✓ I2C MCU (0x17)
✓ Module file
✗ Module loaded
✗ sysfs interface
✓ DKMS : fusion_hat/1.0.2, 6.12.47+rpt-rpi-2712, aarch64: installed

HAT not detected — EEPROM chip not found on I2C.
→ Check the HAT is properly seated on the GPIO header.

==================================================

pi@ai-fusion:~ $ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – –
10: – – – – – – – 17 – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – 3c – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –