@maxlem
ok I was using the Pi Os Lite version, with the full version (still on buster) it worked without issues.
Thanks for your help
@maxlem
ok I was using the Pi Os Lite version, with the full version (still on buster) it worked without issues.
Thanks for your help
@veye_xumm
Hi, thanks again for the answer. What version do you suggest I used?
The article you point at talks about a special case for "Legacy camera interface" for bullseye. My understanding is that I need that legacy interface for your camera. On buster it is supposed to be built in. Isn't it what I did activate with raspi-config when I enabled the camera. Is that something to look for in the kernel logs or dmesg to know for sure what the source of the problem is?
I don't mind upgrading my pios version though. But I'd prefer not to blindly try many versions without really knowing the source of the problem
Thanks
@veye_xumm
Hi, thanks for replying.
I'm using 32bits:
lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.10.17-v7l+ #1403 SMP Mon Feb 22 11:33:35 GMT 2021 armv7l GNU/Linux
pi@raspberrypi:~ $ getconf LONG_BIT
32
I can see the i2c part is working:
./cs_mipi_i2c.sh -r -f productmodel
PRODUCT MODEL is CS-MIPI-SC132
./cs_mipi_i2c.sh -r -f mipistatus
r mipi count 16953, mipi state 1
./cs_mipi_i2c.sh -r -f i2caddr
r i2caddr 0x3b
Thank you!
Hi I tried for over 1 hour to make my sc132 work with my rpi4 model b, running buster.
I enabled the camera and i2c via raspi-config
I ran the
./enable_i2c_vc.sh
./camera_i2c_config
and used the cs_mipi_i2c.sh script to read and set videofmt
everything seems normal
but when I try
./veye_paspipreview -md 1 -t 20000 -p '0,0,1200,720'
hardware version: c03112
before create camera com
mma1: mma1_component_create_core: could not find component 'vc.ril.rawcam'
mma1: Failed to ....
...
mma1: Camera not detected
I tried 3 times to reconnect the cable.
Please help!
Thank you