about aiy camera issue (as aiy is archived by the owner on Feb 9, 2023)

[lida2003]

@ricardodeazambuja as aiy is archived by the owner on Feb 9, 2023, I can't ask any questions.

I saw you have met the same issue.
So I wanna ask how to solve this. Well, it's might be NOT the right place for this question. :(

PS: hardware is ok, connection/camera etc.

My comparative tests shows that it's a software issue.

Sequence as below:
a) AIY Kits Release 2021-04-02: first time i got this kit, (Flash latest image) was OK
b) bullseye(raspbian image): camera issue
c) AIY Kits Release 2021-04-02: second time(Flash) failed. upgrade, then it's OK
d) bullseye(raspbian image): Flash again, camera issue

• Vision Bonnet board not working #720
• AIY Vision Kit: Could not enable camera whatsoever #618

pi@piCamera:~ $ raspistill -v -o test.jpg

"raspistill" Camera App (commit e39c6354b784 Tainted)

Camera Name imx219
Width 3280, Height 2464, filename test.jpg
Using camera 0, sensor mode 0

GPS output Disabled

Quality 85, Raw no
Thumbnail enabled Yes, width 64, height 48, quality 35
Time delay 5000, Timelapse 0
Link to latest frame enabled  no
Full resolution preview No
Capture method : Single capture

Preview Yes, Full screen Yes
Preview window 0,0,1024,768
Opacity 255
Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 0, Video Stabilisation No, Exposure compensation 0
Exposure Mode 'auto', AWB Mode 'auto', Image Effect 'none'
Flicker Avoid Mode 'off'
Metering Mode 'average', Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
Camera component done
Encoder component done
Starting component connection stage
Connecting camera preview port to video render.
Connecting camera stills port to encoder input port
Opening output file test.jpg
Enabling encoder output port
Starting capture -1
Camera control callback  cmd=0x4f525245mmal: No data received from sensor. Check all connections, including the Sunny one on the camera board

[ricardodeazambuja]

So, as I understood the option a) is working, therefore it's clearly not a physical hardware problem.
The problem you are facing is the change in the way the Raspberry Pi OS is dealing with the camera. They broke the compatibility to move away from the proprietary stuff (I think they are getting ready to launch a board that doesn't use all that Broadcom binary blobs) making the software stack more like all other linux systems. You can read something about the new system here.
Possible solution (I haven't tested it mysef with the AIY kit) is to enable the legacy camera stack:

1. Ensure your system is up-to-date sudo apt update && sudo apt upgrade and reboot it sudo reboot now.
2. Run sudo raspi-config.
3. Navigate to Interface Options and select Legacy camera to enable it.
4. Reboot your Raspberry Pi again sudo reboot now.

Another option (I haven't tested this one either) could be to use their legacy image.

Please, post a reply here telling which one worked for you!

[lida2003]

1. Ensure your system is up-to-date `sudo apt update && sudo apt upgrade` and reboot it `sudo reboot now`.

2. Run `sudo raspi-config`.

3. Navigate to `Interface Options` and select `Legacy camera` to enable it.

4. Reboot your Raspberry Pi again `sudo reboot now`.

Previous image bullseye is selecting legacy camera by default(well, it's wfb_ng 23.01 image based on bullseye). I disabled lagacy camera(reboot of course) if, it seems both raspistill & libcamera-still do not work.

pi@piCamera:~/userland $ raspistill -v -o test.jpg
ERROR: the system should be configured for the legacy camera stack
pi@piCamera:~/userland $ libcamera-still -o test.jpg
Made DRM preview window
[0:20:01.790819432] [848]  INFO Camera camera_manager.cpp:299 libcamera v0.0.4+22-923f5d70
[0:20:01.956535704] [849]  WARN RPI raspberrypi.cpp:1357 Mismatch between Unicam and CamHelper for embedded data usage!
[0:20:01.963306756] [849]  INFO RPI raspberrypi.cpp:1476 Registered camera /base/soc/i2c0mux/i2c@1/imx219@10 to Unicam device /dev/media3 and ISP device /dev/media0
[0:20:01.968322794] [848]  INFO Camera camera.cpp:1028 configuring streams: (0) 1640x1232-YUV420
[0:20:01.972568827] [849]  INFO RPI raspberrypi.cpp:851 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected sensor format: 1640x1232-SBGGR10_1X10 - Selected unicam format: 1640x1232-pBAA
[0:20:25.659838633] [849]  WARN V4L2 v4l2_videodevice.cpp:2007 /dev/video0[13:cap]: Dequeue timer of 23534000.00us has expired!
[0:20:25.660353636] [849] ERROR RPI raspberrypi.cpp:1984 Unicam has timed out!
[0:20:25.660552637] [849] ERROR RPI raspberrypi.cpp:1985 Please check that your camera sensor connector is attached securely.
[0:20:25.660763639] [849] ERROR RPI raspberrypi.cpp:1986 Alternatively, try another cable and/or sensor.
ERROR: Device timeout detected, attempting a restart!!!

[lida2003]

Switch back to legacy camera if.

Well, it seems libcamera doesn't work on AIY board.

Ref: How to fix raspistill ERROR: the system should be configured for the legacy camera stack

pi@piCamera:~ $ libcamera-still -o test.jpg
ERROR: the system appears to be configured for the legacy camera stack
pi@piCamera:~ $ raspistill -v -o test.jpg

"raspistill" Camera App (commit e39c6354b784 Tainted)

Camera Name imx219
Width 3280, Height 2464, filename test.jpg
Using camera 0, sensor mode 0

GPS output Disabled

Quality 85, Raw no
Thumbnail enabled Yes, width 64, height 48, quality 35
Time delay 5000, Timelapse 0
Link to latest frame enabled  no
Full resolution preview No
Capture method : Single capture

Preview Yes, Full screen Yes
Preview window 0,0,1024,768
Opacity 255
Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 0, Video Stabilisation No, Exposure compensation 0
Exposure Mode 'auto', AWB Mode 'auto', Image Effect 'none'
Flicker Avoid Mode 'off'
Metering Mode 'average', Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
Camera component done
Encoder component done
Starting component connection stage
Connecting camera preview port to video render.
Connecting camera stills port to encoder input port
Opening output file test.jpg
Enabling encoder output port
Starting capture -1
Camera control callback  cmd=0x4f525245mmal: No data received from sensor. Check all connections, including the Sunny one on the camera board
mmal: Aborting program

pi@piCamera:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

[lida2003]

brand new flash with 2023-02-21-raspios-bullseye-armhf-lite.img.xz // from raspberry pi web

default configuration is not lagacy camera interface

daniel@raspberrypi:~ $ lsmod
Module                  Size  Used by
cmac                   16384  3
algif_hash             16384  1
aes_arm                16384  3
aes_generic            40960  1 aes_arm
ecb                    16384  1
algif_skcipher         16384  1
af_alg                 28672  6 algif_hash,algif_skcipher
bnep                   20480  2
imx219                 20480  1
spidev                 20480  0
vc4                   290816  2
brcmfmac              307200  0
hci_uart               45056  1
btbcm                  20480  1 hci_uart
bluetooth             425984  26 hci_uart,bnep,btbcm
ecdh_generic           16384  2 bluetooth
ecc                    40960  1 ecdh_generic
libaes                 20480  3 bluetooth,aes_arm,aes_generic
snd_soc_hdmi_codec     20480  1
cec                    49152  1 vc4
brcmutil               20480  1 brcmfmac
8021q                  32768  0
garp                   16384  1 8021q
stp                    16384  1 garp
llc                    16384  2 garp,stp
sha256_generic         16384  0
libsha256              16384  1 sha256_generic
drm_kms_helper        270336  2 vc4
cfg80211              782336  1 brcmfmac
snd_soc_core          233472  2 vc4,snd_soc_hdmi_codec
bcm2835_unicam         45056  0
v4l2_dv_timings        40960  1 bcm2835_unicam
snd_compress           20480  1 snd_soc_core
i2c_mux_pinctrl        16384  0
snd_pcm_dmaengine      16384  1 snd_soc_core
v4l2_fwnode            20480  2 bcm2835_unicam,imx219
i2c_mux                16384  1 i2c_mux_pinctrl
raspberrypi_hwmon      16384  0
syscopyarea            16384  1 drm_kms_helper
bcm2835_codec          45056  0
sysfillrect            16384  1 drm_kms_helper
v4l2_async             24576  3 bcm2835_unicam,imx219,v4l2_fwnode
sysimgblt              16384  1 drm_kms_helper
fb_sys_fops            16384  1 drm_kms_helper
bcm2835_v4l2           45056  0
v4l2_mem2mem           36864  1 bcm2835_codec
bcm2835_isp            28672  0
rfkill                 32768  6 bluetooth,cfg80211
bcm2835_mmal_vchiq     32768  3 bcm2835_isp,bcm2835_codec,bcm2835_v4l2
videobuf2_vmalloc      16384  1 bcm2835_v4l2
videobuf2_dma_contig    20480  3 bcm2835_unicam,bcm2835_isp,bcm2835_codec
videobuf2_memops       16384  2 videobuf2_dma_contig,videobuf2_vmalloc
videobuf2_v4l2         32768  5 bcm2835_unicam,bcm2835_isp,bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem
videobuf2_common       61440  9 bcm2835_unicam,bcm2835_isp,bcm2835_codec,videobuf2_dma_contig,videobuf2_vmalloc,videobuf2_memops,bcm2835_v4l                            2,v4l2_mem2mem,videobuf2_v4l2
snd_bcm2835            24576  0
snd_pcm               114688  5 snd_compress,snd_pcm_dmaengine,snd_soc_hdmi_codec,snd_bcm2835,snd_soc_core
videodev              237568  9 bcm2835_unicam,imx219,bcm2835_isp,bcm2835_codec,videobuf2_common,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2,v4                            l2_async
snd_timer              32768  1 snd_pcm
snd                    86016  6 snd_compress,snd_soc_hdmi_codec,snd_timer,snd_bcm2835,snd_soc_core,snd_pcm
i2c_bcm2835            16384  0
spi_bcm2835            20480  0
vc_sm_cma              32768  2 bcm2835_isp,bcm2835_mmal_vchiq
mc                     49152  9 bcm2835_unicam,imx219,bcm2835_isp,bcm2835_codec,videobuf2_common,videodev,v4l2_mem2mem,videobuf2_v4l2,v4l2_a                            sync
uio_pdrv_genirq        16384  0
fixed                  16384  3
uio                    20480  1 uio_pdrv_genirq
drm                   528384  3 vc4,drm_kms_helper
fuse                  126976  1
drm_panel_orientation_quirks    16384  1 drm
backlight              20480  2 drm_kms_helper,drm
ip_tables              28672  0
x_tables               36864  1 ip_tables
ipv6                  491520  18
daniel@raspberrypi:~ $ sudo raspi-config
daniel@raspberrypi:~ $ libcamera-still -o test.jpg
Preview window unavailable
[0:05:46.624450836] [747]  INFO Camera camera_manager.cpp:299 libcamera v0.0.3+40-9b860a66
[0:05:46.827137010] [748]  WARN RPI raspberrypi.cpp:1308 Mismatch between Unicam and CamHelper for embedded data usage!
[0:05:46.833668016] [748]  INFO RPI raspberrypi.cpp:1425 Registered camera /base/soc/i2c0mux/i2c@1/imx219@10 to Unicam device /dev/media3 and ISP device /dev/media0
[0:05:46.839945022] [747]  INFO Camera camera.cpp:1028 configuring streams: (0) 1640x1232-YUV420
[0:05:46.843412025] [748]  INFO RPI raspberrypi.cpp:805 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected sensor format: 1640x1232-SBGGR10_1X10 - Selected unicam format: 1640x1232-pBAA
[0:06:10.500275871] [748]  WARN V4L2 v4l2_videodevice.cpp:2007 /dev/video0[12:cap]: Dequeue timer of 23534000.00us has expired!
[0:06:10.500718873] [748] ERROR RPI raspberrypi.cpp:1875 Unicam has timed out!
[0:06:10.500922874] [748] ERROR RPI raspberrypi.cpp:1876 Please check that your camera sensor connector is attached securely.
[0:06:10.501119875] [748] ERROR RPI raspberrypi.cpp:1877 Alternatively, try another cable and/or sensor.
ERROR: Device timeout detected, attempting a restart!!!
^C
daniel@raspberrypi:~ $ raspistill -v -o test.jpg
ERROR: the system should be configured for the legacy camera stack
daniel@raspberrypi:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

switch to legacy interface, reboot

daniel@raspberrypi:~ $ libcamera-still -o test.jpg
ERROR: the system appears to be configured for the legacy camera stack
daniel@raspberrypi:~ $ raspistill -v -o test.jpg

"raspistill" Camera App (commit e39c6354b784 Tainted)

Camera Name imx219
Width 3280, Height 2464, filename test.jpg
Using camera 0, sensor mode 0

GPS output Disabled

Quality 85, Raw no
Thumbnail enabled Yes, width 64, height 48, quality 35
Time delay 5000, Timelapse 0
Link to latest frame enabled  no
Full resolution preview No
Capture method : Single capture

Preview Yes, Full screen Yes
Preview window 0,0,1024,768
Opacity 255
Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 0, Video Stabilisation No, Exposure compensation 0
Exposure Mode 'auto', AWB Mode 'auto', Image Effect 'none'
Flicker Avoid Mode 'off'
Metering Mode 'average', Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
Camera component done
Encoder component done
Starting component connection stage
Connecting camera preview port to video render.
Connecting camera stills port to encoder input port
Opening output file test.jpg
Enabling encoder output port
Starting capture -1
Camera control callback  cmd=0x4f525245mmal: No data received from sensor. Check all connections, including the Sunny one on the camera board

[lida2003]

@ricardodeazambuja Is there any links available to understand AIY Vision Bonnet hardware?

schmatic pdf???? does this hardware need os to load firmware before use?

Since I can't get through "the great fire wall", I can't access the apt repo to Install the AIY Projects software.

And there is no mirror in China(well, I didn't find). Do you know how to compile from the AIY source code?

Ref:
The Vision Bonnet introduction, basics of the chip
AIY Vision Bonnet IOs

[lida2003]

I will be totally honest, I don't know how to solve this problem after reading your last messages.

Well, I'm trying to use driver from apt repo. Really slow due to "the great fire wall"

Before going down any rabbit hole, where are you connecting the camera?

the official way you mentioned. camera==> Vision Bonnet ==> RPI Zero W

I had a problem in the past where I couldn't use the camera and I solved it by connecting the camera directly to the RPI Zero (the official way is to connect the camera to the AIY Vision Bonnet and use another flat cable to connect the AIY Vision Bonnet to the RPI Zero).
I did that because I realised all the communication with the AIY board was through SPI (I can't remember which files I looked at to figure that out).

OK, it makes sense.

[ricardodeazambuja]

Yup, official way means camera==> Vision Bonnet ==> RPI Zero W
My way was camera==> RPI Zero W

[lida2003]

I think we should take a look at (Which i 'm tring now):

Install Vision Bonnet packages(Install the bonnet drivers)
sudo apt-get install -y aiy-vision-dkms

[lida2003]

I think we should take a look at (Which i 'm tring now):

Install Vision Bonnet packages(Install the bonnet drivers) sudo apt-get install -y aiy-vision-dkms

Well, it seems aiy-repo & bullseye has some compatible issue.

pi@piCamera:~ $ sudo apt-get install -y aiy-vision-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  aiy-dkms aiy-vision-firmware dctrl-tools dkms raspberrypi-kernel-headers
Suggested packages:
  debtags menu
The following NEW packages will be installed:
  aiy-dkms aiy-vision-dkms aiy-vision-firmware dctrl-tools dkms raspberrypi-kernel-headers
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 31.2 MB/31.3 MB of archives.
After this operation, 190 MB of additional disk space will be used.
Get:1 https://packages.cloud.google.com/apt aiyprojects-stable/main armhf aiy-dkms all 2.0-1 [12.1 kB]
Get:2 https://packages.cloud.google.com/apt aiyprojects-stable/main armhf aiy-vision-firmware all 1.2-0 [2,464 kB]
Get:3 https://mirrors.tuna.tsinghua.edu.cn/raspberrypi bullseye/main armhf raspberrypi-kernel-headers armhf 1:1.20230306-1 [28.7 MB]
Get:4 https://packages.cloud.google.com/apt aiyprojects-stable/main armhf aiy-vision-dkms all 1.2-1 [13.4 kB]
Fetched 29.0 MB in 3min 28s (139 kB/s)
Selecting previously unselected package dctrl-tools.
(Reading database ... 43730 files and directories currently installed.)
Preparing to unpack .../0-dctrl-tools_2.24-3_armhf.deb ...
Unpacking dctrl-tools (2.24-3) ...
Selecting previously unselected package dkms.
Preparing to unpack .../1-dkms_2.8.4-3_all.deb ...
Unpacking dkms (2.8.4-3) ...
Selecting previously unselected package raspberrypi-kernel-headers.
Preparing to unpack .../2-raspberrypi-kernel-headers_1%3a1.20230306-1_armhf.deb ...
Unpacking raspberrypi-kernel-headers (1:1.20230306-1) ...
Selecting previously unselected package aiy-dkms.
Preparing to unpack .../3-aiy-dkms_2.0-1_all.deb ...
Unpacking aiy-dkms (2.0-1) ...
Selecting previously unselected package aiy-vision-firmware.
Preparing to unpack .../4-aiy-vision-firmware_1.2-0_all.deb ...
Unpacking aiy-vision-firmware (1.2-0) ...
Selecting previously unselected package aiy-vision-dkms.
Preparing to unpack .../5-aiy-vision-dkms_1.2-1_all.deb ...
Unpacking aiy-vision-dkms (1.2-1) ...
Setting up raspberrypi-kernel-headers (1:1.20230306-1) ...
Setting up aiy-vision-firmware (1.2-0) ...
Setting up dctrl-tools (2.24-3) ...
Setting up dkms (2.8.4-3) ...
Setting up aiy-dkms (2.0-1) ...
Loading new aiy-2.0 DKMS files...
It is likely that 5.15.84+ belongs to a chroot's host
Building for 5.15.84+, 5.15.84-v7+, 5.15.84-v7l+ and 5.15.84-v8+
Building initial module for 5.15.84+
Error! Bad return status for module build on kernel: 5.15.84+ (armv6l)
Consult /var/lib/dkms/aiy/2.0/build/make.log for more information.
dpkg: error processing package aiy-dkms (--configure):
 installed aiy-dkms package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of aiy-vision-dkms:
 aiy-vision-dkms depends on aiy-dkms; however:
  Package aiy-dkms is not configured yet.

dpkg: error processing package aiy-vision-dkms (--configure):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.9.4-2) ...
Errors were encountered while processing:
 aiy-dkms
 aiy-vision-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

Just install aiy-dkms before aiy-vision-dkms, let's see what's wrong.

pi@piCamera:~ $ sudo apt-get install -y aiy-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
aiy-dkms is already the newest version (2.0-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up aiy-dkms (2.0-1) ...
Removing old aiy-2.0 DKMS files...

------------------------------
Deleting module version: 2.0
completely from the DKMS tree.
------------------------------
Done.
Loading new aiy-2.0 DKMS files...
It is likely that 5.15.84+ belongs to a chroot's host
Building for 5.15.84+, 5.15.84-v7+, 5.15.84-v7l+ and 5.15.84-v8+
Building initial module for 5.15.84+
Error! Bad return status for module build on kernel: 5.15.84+ (armv6l)
Consult /var/lib/dkms/aiy/2.0/build/make.log for more information.
dpkg: error processing package aiy-dkms (--configure):
 installed aiy-dkms package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of aiy-vision-dkms:
 aiy-vision-dkms depends on aiy-dkms; however:
  Package aiy-dkms is not configured yet.

dpkg: error processing package aiy-vision-dkms (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 aiy-dkms
 aiy-vision-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

Well, there might be something wrong with post scripts installed aiy-dkms package post-installation script subprocess returned error exit status 10

[lida2003]

Build aiy-2.0 with kernel 5.15.84+ failed. I'm NOT sure aiy-2.0 is related with which tag source code.

it needs more specific dev guides. just build those code from repo to locate the issues.

$ cat /var/lib/dkms/aiy/2.0/build/make.log
DKMS make.log for aiy-2.0 for kernel 5.15.84+ (armv6l)
Thu  9 Mar 11:09:54 HKT 2023
make: Entering directory '/usr/src/linux-headers-5.15.84+'
  CC [M]  /var/lib/dkms/aiy/2.0/build/aiy/mfd/aiy-io-i2c.o
  CC [M]  /var/lib/dkms/aiy/2.0/build/aiy/gpio/gpio-aiy-io.o
  CC [M]  /var/lib/dkms/aiy/2.0/build/aiy/pwm/pwm-aiy-io.o
/var/lib/dkms/aiy/2.0/build/aiy/pwm/pwm-aiy-io.c: In function ‘aiy_pwm_remove’:
/var/lib/dkms/aiy/2.0/build/aiy/pwm/pwm-aiy-io.c:380:6: error: void value not ignored as it ought to be
  380 |  err = pwmchip_remove(&aiy_pwm->chip);
      |      ^
make[3]: *** [scripts/Makefile.build:289: /var/lib/dkms/aiy/2.0/build/aiy/pwm/pwm-aiy-io.o] Error 1
make[2]: *** [scripts/Makefile.build:552: /var/lib/dkms/aiy/2.0/build/aiy/pwm] Error 2
make[1]: *** [scripts/Makefile.build:552: /var/lib/dkms/aiy/2.0/build/aiy] Error 2
make: *** [Makefile:1902: /var/lib/dkms/aiy/2.0/build] Error 2
make: Leaving directory '/usr/src/linux-headers-5.15.84+'

[lida2003]

@ricardodeazambuja

camera==> RPI Zero W

I have tested, it works. Now I'm 100% sure it's AIY driver issue.

Key point: Vision bonnet hardware is initialized by driver , which raspbian don't have.

camera==> Vision Bonnet ==> RPI Zero W

[ricardodeazambuja]

I think they ask people to install much more things than needed when you connected the camera directly to the RPI Zero. As I mentioned before, the communication with the AIY Vision Bonnet is using SPI, nothing complex in the RPI Zero side. Why don't you use the image from here?

[lida2003]

I'm using wfb-ng and need to do a little bit of object recognition here.

now there are two options:

1. Fix AIY repo's compile issue
2. Using AIY-Vision-Kit-Utils, and that's great!

Thanks very much for the talk and info here.

[viraniac]

you can try installing aiy-dkms package from here

[viraniac]

I have created an aiyprojects image based on the latest raspbian os image and 6.1.21 kernel. In case anyone needs it you can download it from https://github.com/viraniac/aiyprojects-raspbian/releases/tag/v20230326

I have tested it on both voice bonnet and vision bonnet and it works ok. Please let me know if anyone faces any issue with the same.

[ricardodeazambuja]

@viraniac, using your new image do you still need to connect the camera directly to the RPI Zero instead of the "official" way?

[viraniac]

I have tested with my camera connected to the vision bonnet and it works fine. I did reverted to the legacy camera stack in my image though as the joy detection python code is based on Picamera library that needs legacy stack. If you are not going to use the api's provided by the aiy-projects-python package, then you can revert to new camera stack and use the picamera2 library in your code. The camera works fine both ways