4 Zero W's boot but can't connect to them

137 views
Skip to first unread message

AJ

unread,
Sep 24, 2022, 8:13:34 AM9/24/22
to ClusterHAT
Hi,
I am running RPI4 (8GB mem) with a clusterhat v2.5 and 4x Zero W's.
I followed the "Simple guide". The images I used were

RPI4 (control) : 2022-04-04/2022-04-04-2-bullseye-ClusterCTRL-arm64-CNAT.zip
P1 : 2022-04-04/2022-04-04-2-bullseye-ClusterCTRL-arm64-lite-p1.zip
P2 : 2022-04-04/2022-04-04-2-bullseye-ClusterCTRL-arm64-lite-p2.zip
P3 : 2022-04-04/2022-04-04-2-bullseye-ClusterCTRL-arm64-lite-p3.zip
P4 : 2022-04-04/2022-04-04-2-bullseye-ClusterCTRL-arm64-lite-p4.zip

I added /boot/ssh to those Px images for each Zero W to enable SSH.
I am using CNAT (FULL) because I am using WIFI on the control.

Powering on the hat, all yellow LEDs light up + each zero starts blinking green, eventually having the green LED blinking. But none of the Px's are pinging.

Here is an ifconfig -a output on the control
++++++++
ei@cnat:~ $ sudo ifconfig -a
br0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether e4:5f:01:ad:e0:85  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8  bytes 1016 (1016.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

brint: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.19.180.254  netmask 255.255.255.0  broadcast 172.19.180.255
        inet6 fe80::e0f9:acff:feb4:49db  prefixlen 64  scopeid 0x20<link>
        ether e2:f9:ac:b4:49:db  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 110  bytes 10164 (9.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether e4:5f:01:ad:e0:85  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 42  bytes 4401 (4.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 42  bytes 4401 (4.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.208  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::fd8f:a716:637a:4aea  prefixlen 64  scopeid 0x20<link>
        ether e4:5f:01:ad:e0:86  txqueuelen 1000  (Ethernet)
        RX packets 9153  bytes 1531243 (1.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2928  bytes 465623 (454.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
++++++++

Before adding the 4 Zero W's, I booted the RPI4 with CNAT image. At that time, I changed the username to ei. Then I added 4 Zero W's. 

ei@cnat:~ $ sudo brctl show
bridge name    bridge id        STP enabled    interfaces
br0        8000.e45f01ade085    no
brint        8000.000000000000    no
ei@cnat:~ $ lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/0p, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 2: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 3: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 3: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 4: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
ei@cnat:~ $

I don't see any /dev/ttyACM or ttypi
ei@cnat:~ $ ls -l /dev/ttyACM*
ls: cannot access '/dev/ttyACM*': No such file or directory
ei@cnat:~ $ ls -l /dev/ttypi*
ls: cannot access '/dev/ttypi*': No such file or directory
ei@cnat:~ $

Any suggestions? 
AJ

AJ

unread,
Sep 24, 2022, 8:46:00 PM9/24/22
to ClusterHAT
I used a wrong image. I needed to use 32bit image. With 32bit images, it is working fine.
Thank you
AJ

Ben Heininger

unread,
Dec 1, 2022, 3:14:06 AM12/1/22
to ClusterHAT
I thought I read somewhere that you can use the 64bit images on the Pi Zero but it failed to work for me too.

Chris Burton

unread,
Dec 1, 2022, 4:19:05 PM12/1/22
to ClusterHAT
Hi,
I thought I read somewhere that you can use the 64bit images on the Pi Zero but it failed to work for me too.

The 64-bit images can be used on Pi Zero 2 W but not the original Pi Zero 1.x models.

Chris. 
Reply all
Reply to author
Forward
0 new messages