Cant get RPI V2 to be detected

The only sign of life I’ve gotten from the camera is it showing up in i2cdetect -a -r 5, This is with the latest image flashed in bb flasher and then an apt update && apt upgrade,

Ive put in any info I can think of that might be useful:

beagle@beagle:~$ sudo beagle-version
eeprom:[BYAI202406002494]
model:[BeagleBoard.org_BeagleY-AI]
dogtag:[BeagleBoard.org Debian Trixie Xfce Image 2025-11-25]
bootloader:[/dev/mmcblk1]:[/boot/firmware/tiboot3.bin]:[U-Boot SPL 2025.10-g6825d60bea17 (Nov 25 2025 - 18:48:22 +0000)]
bootloader:[/dev/mmcblk1]:[/boot/firmware/tispl.bin]:[U-Boot SPL 2025.10-g6825d60bea17 (Nov 25 2025 - 18:48:22 +0000)]
bootloader:[/dev/mmcblk1]:[/boot/firmware/u-boot.img]:[U-Boot 2025.10-g6825d60bea17 (Nov 25 2025 - 18:48:22 +0000)]
UBOOT: Booted Device-Tree:[k3-am67a-beagley-ai.dts]
kernel:[6.1.83-ti-arm64-r72]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade ]
pkg:[bb-u-boot-beagley-ai]:[2026.01.20260105.3-0~trixie+20260210]
WARNING:pkg:[bb-wl18xx-firmware]:[NOT_INSTALLED]
pkg:[bb-customizations]:[1.20260407.0-0~trixie+20260407]
pkg:[bb-usb-gadgets]:[1.20250722.0-0~trixie+20250722]
groups:[beagle : beagle adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal input render netdev i2c bluetooth docker gpio admin tisdk weston-launch]
cmdline:[console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 root=/dev/mmcblk1p3 ro rootfstype=ext4 fsck.repair=yes resume=/dev/mmcblk1p2 rootwait net.ifnames=0]
ti-sci:
ABI: 4.0 (firmware rev 0x000b ‘11.2.6–v11.02.06 (Fancy Rat)’)
optee:
optee: revision 4.8 (86660925433a8d4d)
wlcore:
wlcore: Wireless driver version 1.7.0.114
wlcore: Wireless firmware version 1.7.0.120
wlcore: Wireless PHY version 1.2.36.5.22.66
dmesg | grep remote
[ 6.242077] systemd[1]: Reached target remote-fs.target - Remote File Systems.
[ 10.733715] k3-dsp-rproc 7e000000.dsp: configured DSP for remoteproc mode
[ 10.750263] remoteproc remoteproc0: 7e000000.dsp is available
[ 10.761275] k3-dsp-rproc 7e000000.dsp: register pm nitifiers in remoteproc mode
[ 10.778219] remoteproc remoteproc0: Direct firmware load for j722s-c71_0-fw failed with error -2
[ 10.788330] remoteproc remoteproc0: powering up 7e000000.dsp
[ 10.799616] remoteproc remoteproc0: Direct firmware load for j722s-c71_0-fw failed with error -2
[ 10.813830] remoteproc remoteproc0: request_firmware failed: -2
[ 10.848944] k3-dsp-rproc 7e200000.dsp: configured DSP for remoteproc mode
[ 10.924449] remoteproc remoteproc1: 7e200000.dsp is available
[ 10.931940] k3-dsp-rproc 7e200000.dsp: register pm nitifiers in remoteproc mode
[ 10.955120] remoteproc remoteproc1: Direct firmware load for j722s-c71_1-fw failed with error -2
[ 10.980585] remoteproc remoteproc1: powering up 7e200000.dsp
[ 11.014554] remoteproc remoteproc1: Direct firmware load for j722s-c71_1-fw failed with error -2
[ 11.028736] remoteproc remoteproc1: request_firmware failed: -2
[ 11.335823] platform 79000000.r5f: configured R5F for remoteproc mode
[ 11.438846] remoteproc remoteproc2: 79000000.r5f is available
[ 11.446950] remoteproc remoteproc2: Direct firmware load for j722s-mcu-r5f0_0-fw failed with error -2
[ 11.461302] remoteproc remoteproc2: powering up 79000000.r5f
[ 11.472570] remoteproc remoteproc2: Direct firmware load for j722s-mcu-r5f0_0-fw failed with error -2
[ 11.487218] remoteproc remoteproc2: request_firmware failed: -2
[ 11.631135] remoteproc remoteproc3: 78000000.r5f is available
[ 11.641974] remoteproc remoteproc3: attaching to 78000000.r5f
[ 11.716326] remoteproc remoteproc3: remote processor 78000000.r5f is now attached
[ 11.824342] platform 78400000.r5f: configured R5F for remoteproc mode
[ 11.890183] remoteproc remoteproc4: 78400000.r5f is available
[ 11.900020] remoteproc remoteproc4: Direct firmware load for j722s-main-r5f0_0-fw failed with error -2
[ 11.914322] remoteproc remoteproc4: powering up 78400000.r5f
[ 11.925562] remoteproc remoteproc4: Direct firmware load for j722s-main-r5f0_0-fw failed with error -2
[ 11.940274] remoteproc remoteproc4: request_firmware failed: -2
[ 15.273444] Modules linked in: algif_aead lz4 zram cc33xx rpmsg_ctrl rpmsg_char mac80211 libarc4 crct10dif_ce snd_soc_simple_card snd_soc_simple_card_utils pci_endpoint_test pvrsrvkm(O) cpufreq_dt cc33xx_sdio cfg80211 pwm_fan e5010_jpeg_enc rti_wdt at24 ti_k3_r5_remoteproc btti_uart wave5 videobuf2_dma_contig v4l2_mem2mem bluetooth snd_soc_davinci_mcasp ti_k3_dsp_remoteproc videobuf2_memops videobuf2_v4l2 snd_soc_hdmi_codec snd_soc_ti_udma ti_k3_common videobuf2_common snd_soc_ti_edma snd_soc_ti_sdma snd_soc_core snd_pcm_dmaengine videodev snd_pcm snd_timer mc snd omap_mailbox optee_rng efi_pstore nfnetlink
[ 15.625197] Modules linked in: algif_aead lz4 zram cc33xx rpmsg_ctrl rpmsg_char mac80211 libarc4 crct10dif_ce snd_soc_simple_card snd_soc_simple_card_utils pci_endpoint_test pvrsrvkm(O) cpufreq_dt cc33xx_sdio cfg80211 pwm_fan e5010_jpeg_enc rti_wdt at24 ti_k3_r5_remoteproc btti_uart wave5 videobuf2_dma_contig v4l2_mem2mem bluetooth snd_soc_davinci_mcasp ti_k3_dsp_remoteproc videobuf2_memops videobuf2_v4l2 snd_soc_hdmi_codec snd_soc_ti_udma ti_k3_common videobuf2_common snd_soc_ti_edma snd_soc_ti_sdma snd_soc_core snd_pcm_dmaengine videodev snd_pcm snd_timer mc snd omap_mailbox optee_rng efi_pstore nfnetlink
dmesg | grep pru
dmesg | grep pinctrl-single
[ 1.556604] pinctrl-single 4084000.pinctrl: 34 pins, size 136
[ 1.563547] pinctrl-single f4000.pinctrl: 171 pins, size 684
dmesg | grep gpio-of-helper
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub
lspci
00:00.0 PCI bridge: Texas Instruments Device b010
END

Im not sure if I am doing something wrong or am on the wrong version or what, and I cant seem to find anything online about the camera not being detected so am not sure how to proceed

You’ll need to use the edge-ai image from TI.. the r5 needs firmware from the edge-ai stack to utilize it..

Regards,

Okay, after getting that installed, atleast the driver is trying to get loaded but then it gets stuck,

[    8.470840] imx219 5-0010: supply VANA not found, using dummy regulator
[    8.477873] imx219 5-0010: supply VDIG not found, using dummy regulator
[    8.484774] imx219 5-0010: supply VDDL not found, using dummy regulator
[    8.518396] imx219 5-0010: Error reading reg 0x0000: -121
[    8.537650] imx219 5-0010: error -EREMOTEIO: failed to read chip id 219
[    8.547012] imx219 5-0010: probe with driver imx219 failed with error -121

All I can find online is this topic: RPi Cam V2 (Sony IMX219) w/ Edge AI Demos - #31 by Alaa_Abdelmoneam

Which doesn’t seem to have gotten very far :/, Is the R5 you’re referring to the camera revision or the board revision?

The R5 is the co-processor that is used by the edge-ai stack to help with the camera decoding..

idk, 2. Getting started — Processor SDK Linux Edge AI for AM67A Documentation

that’s the image your now running, so you need to go thru:

Regards,