The ClusterHAT v2.6 uses an ATtiny1616 to emulate the XRA1200P I/O expander, to update the firmware using the built-in UPDI programmer
Images dated 2025-11-24-2 and earlier use the ACM+RNDIS protocols for the USB Gadget Ethernet. Images 2025-11-24-3 and later use ACM+NCM.
Control of the ClusterCTRL Stackis done using an ATmega328P (or ATmega328PB), the IC can be reprogrammed using either a standard
Control of the Cluster Triple is done using an ATmega328P (or ATmega328PB), the IC can be reprogrammed using either a
Control of the ClusterCTRL Stackis done using an ATmega328P (or ATmega328PB), the IC can be reprogrammed using either a standard
Create a file ~/.config/pcmanfm/LXDE-pi/pcmanfm.conf for the "default" user (the one created when installed) with the following contents.
[volume]
mount_on_startup=0
mount_removable=0
autorun=1
After a reboot USB
When using a Pi 5 and 4x Pi Zero 2 with the official 27W Pi 5 I wouldn't expect any
If you're using one of the provided ClusterCTRL images the cluserctrl tool will already be installed but those using the
The FAN header on the Cluster HAT v2.5 is controlled via GPIO pin BCM18 (set to output and set high
Solder jumpers on the Cluster HAT allow you to modify the default behaviour and configuration. To change the configuration you
Cluster HAT v1.0
USB connector: On left (SMT)Serial connector: THGPIO connector: Bottom entry + headerPower control: GPIOPower connector: 2 pin header
If you've got the Cluster HAT connected and you're having problems with one or more Pi Zeros not being visible
To prevent loading of device tree files (etc) from a HAT EEPROM add the following to the config.txt file in
To enable auto logins on the TTY running on any serial port on the Controller log in and run the
Control of the Cluster Triple is done using an ATmega328P (or ATmega328PB), the IC can be reprogrammed using either a standard
The pX number of a node for control is set by it's priority (this might not be the same as
Running "clusterctrl status" you will get output similar to the below text.
clusterhat:1
clusterctrl:2
maxpi:10
ctrl_bus:20:4:3 21:3:3
hat_version:1.2
hat_version_major:1
hat_version_minor:2
hat_size:4
hat_uuid:622aef87-17d6-4022-a370-781e1c3fe2b9
hat_vendor:8086 Consultancy
hat_product_id:0x0004
throttled:0x0
hat_alert:0
p1:0
p2:0
p3:0
p4:0
ctrl20:FW:1.1 ADC1:5014mV T1:18.60C
p5:0
u5:1
p6:0
u6:1
p7:0
u7:1
ctrl21:FW:1.1 ADC1:4891mV T1:23.52C
p8:0
u8:1
p9:0
u9:1
p10:0
u10:1
clusterhat:False if no
A Compute Module will boot as a USB device if either USBBOOT is enabled or it can't find bootcode.txt in
To boot a Compute Module as a USB device USBBOOT must be enabled.
Background
When using ClusterCTRL with Compute Modules "clusterctrl status"
To boot a Compute Module from the eMMC USBBOOT must be disabled.
If your Compute Module doesn't already have a bootable
To write an image to the eMMC on a Compute Module you need to boot it as a USB Device
The time dhcpcd waits before using the fallback IP can be set in the configuration file.
Edit /etc/dhcpdcd.conf
Add a line containing
From testing I have seen this happen when dhcpcd is unable to obtain an IP address for the interface before
To resize the last partition in a disk image, for example a Raspberry Pi SD card image first increase the
If you're using an newer style Cluster CTRL image (the file /etc/default/clusterctrl exists) please follow Cluster CTRL instructions.
On the Cluster