dwisk

Hi, after updating brickd to 2.4.6 it does not connect to the hat anymore on a Raspberry Pi 4 Model B Rev 1.5. (Hat firmware did not show any available updates before). I checked that SPI is enabled. 2024-07-27 13:21:51.398294 <I> <main_linux.c:385> Brick Daemon 2.4.6 started (architecture: arm64, pid: 2212, daemonized: 1) 2024-07-27 13:21:51.398344 <I> <main_linux.c:391> Running on Linux system (sysname: Linux, release: 6.1.21-v8+, version: #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023, machine: aarch64) 2024-07-27 13:21:51.409885 <I> <bricklet.c:274> Found supported HAT product_id 0x084e in device tree, using default HAT Brick config 2024-07-27 13:21:51.409905 <I> <bricklet.c:315> Found Bricklet port A (spidev: /dev/spidev0.0, driver: gpio, name: GPIO23, num: 23) 2024-07-27 13:21:51.409988 <I> <bricklet_stack_linux.c:87> Using spidev backend for Bricklets, because Raspberry Pi without BCM2835 detected 2024-07-27 13:21:51.411273 <I> <bricklet.c:315> Found Bricklet port B (spidev: /dev/spidev0.0, driver: gpio, name: GPIO22, num: 22) 2024-07-27 13:21:51.412419 <I> <bricklet.c:315> Found Bricklet port C (spidev: /dev/spidev0.0, driver: gpio, name: GPIO25, num: 25) 2024-07-27 13:21:51.413494 <I> <bricklet.c:315> Found Bricklet port D (spidev: /dev/spidev0.0, driver: gpio, name: GPIO26, num: 26) 2024-07-27 13:21:51.414650 <I> <bricklet.c:315> Found Bricklet port E (spidev: /dev/spidev0.0, driver: gpio, name: GPIO27, num: 27) 2024-07-27 13:21:51.415818 <I> <bricklet.c:315> Found Bricklet port F (spidev: /dev/spidev0.0, driver: gpio, name: GPIO24, num: 24) 2024-07-27 13:21:51.416855 <I> <bricklet.c:315> Found Bricklet port G (spidev: /dev/spidev0.0, driver: gpio, name: GPIO7, num: 7) 2024-07-27 13:21:51.417584 <E> <bricklet_stack_linux_spidev.c:263> Could not find line GPIO7 2024-07-27 13:21:52.417727 <I> <main_linux.c:579> Brick Daemon 2.4.6 stopped Any ideas on what went wrong? Also downgrading to brickd 2.4.3 seems not available with aptget. There it did connect. Regards Amely

Sorry, couldn't work on this for a while. Just tested it and it works. brickd starts and brickv can connect. Thanks a lot!

Understood. Any chance to get an update for break daemon anytime soon? Would love to use the rpi5 :) and thanks anyway

Would it be possible to change the GPIO numbers already through /etc/brickd.conf ? I would try, just have no idea about which numbers to use.

I seem to be stuck in a similar problem on a raspberrypi5 with a zerohat. Firmware is updated and on rpi5 brickd v.2.4.5 is running. I tried the changes in /etc/brickd.conf but it didn't change anything. Brickd is not running.. The following output is when I run brickd directly. root@hexagon-rpi5:~# brickd 2024-03-22 15:26:03.167727 <I> <main_linux.c:369> Brick Daemon 2.4.5 started (pid: 2448, daemonized: 0) 2024-03-22 15:26:03.167737 <I> <main_linux.c:375> Running on Linux system (sysname: Linux, release: 6.6.20+rpt-rpi-2712, version: #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07), machine: aarch64) libusb: warning [libusb_init] installing new context as implicit default 2024-03-22 15:26:03.170565 <I> <bricklet.c:304> Found supported HAT product_id 0x085d in device tree, using default HAT Zero Brick config 2024-03-22 15:26:03.170571 <I> <bricklet.c:345> Found Bricklet port A (spidev: /dev/spidev0.0, driver: gpio, name: gpio426, num: 426) 2024-03-22 15:26:03.170588 <I> <bricklet_stack_linux.c:87> Using spidev backend for Bricklets (unsupported suffix 5 after 'Raspberry Pi' in /proc/device-tree/model) 2024-03-22 15:26:03.170613 <E> <gpio_sysfs.c:77> Could not write to '/sys/class/gpio/export' to export GPIO 426: EINVAL (22) 2024-03-22 15:26:03.170616 <E> <bricklet_stack_linux_spidev.c:78> Could not export gpio426: EINVAL (22) 2024-03-22 15:26:03.170809 <I> <main_linux.c:563> Brick Daemon 2.4.5 stopped root@hexagon-rpi5:~# brickd --version 2.4.5 Regards Amely