Does anyone have any ideas on how to get the camera working? I have tried editing the /boot/firmware/config.txt file in many different ways but I still can't get the camera stream to work and show up. The camera is a Raspberry Pi Camera Module 3 Wide.
The command sudo libcamera-hello --list-cameras gives the following response:
8 months ago I threw that camera in the box. Now I dug it out and tried to get it to work. I downloaded the new Imager and the latest Octoprint camera version. I still can't get it to work, the camera works in the RaspController program. Can anyone help?
When I type rpicam-still -o test.jpg
I get these warnings: [2:22:53.916905779] [3430] WARN CameraSensorProperties camera_sensor_properties.cpp:499 No static properties available for 'imx708_wide'
[2:22:53.916927205] [3430] WARN CameraSensorProperties camera_sensor_properties.cpp:501 Please consider updating the camer a sensor properties database
[2:22:54.008599790] [3430] INFO IPAProxy ipa_proxy.cpp:180 Using tuning file /usr/share/libcamera/ipa/rpi/pisp/imx708_wide .json
[2:22:54.022424850] [3430] WARN CameraSensor camera_sensor_legacy.cpp:501 'imx708_wide': No sensor delays found in static properties. Assuming unverified defaults.
Ok b-morgan, not help. How I should to edit this config.txt file?
When I type: sudo nano /boot/firmware/config.txt
I get:
arm_64bit=0
# For more options and information see
# http://rptl.io/configtxt
# Some settings may impact device functionality. See link above for details
# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
# Additional overlays and parameters are documented
# /boot/firmware/overlays/README
# Automatically load overlays for detected cameras
camera_auto_detect=1
# Automatically load overlays for detected DSI displays
display_auto_detect=1
# Automatically load initramfs files, if found
auto_initramfs=1
# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2
# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1
# Disable compensation for displays with overscan
disable_overscan=1
# Run as fast as firmware / board allows
arm_boost=1
[cm4]
# Enable host mode on the 2711 built-in XHCI USB controller.
# This line should be removed if the legacy DWC2 controller is required
# (e.g. for USB device mode) or if USB support is not required.
otg_mode=1
[cm5]
dtoverlay=dwc2,dr_mode=host
[all]
# enable raspicam
start_x=1
gpu_mem=128
Sorry if I'm not being helpful. I believe the data you provided in February is completely irrelevant because you said:
I downloaded the new Imager and the latest Octoprint camera version
Exact version numbers would be useful as well as a new systeminfo bundle.
The OctoPi (new experimental camera stack) version uses camera-streamer to control the camera. For OctoPrint to use the camera, camera-streamer must be active. When camera-streamer is active, RaspController can't use the camera (at least that's how it works on my RPi4).
FWIW, the /boot/firmware/config.txt on my RPi4 is identical to the one on your system so I don't believe it needs to be edited.
Oh, so when camera working in RaspController camera-streamer is not active. Yep, that's the problem and I can't to start camera-streamer.
I can use my 3D printer without camera or I can connect Pi4+old camera to my printer BUT I want to know, what's the problem and same time learning. I want to see the solution, maybe one day someone will solve this
I believe the solution is to figure out why you can't start camera-streamer but we will need your help to do so. If you upload a new systeminfo bundle then we can start by examining the log.
Note: Searching this forum for "camera-streamer" may provide some useful information.
/usr/bin/list-libcamera-devices is a shell script and it is looking for /base/soc in the data returned by rpicam-hello. The output from your wide camera is /base/axi.
I created the script based on what the camera modules I had here were reporting, /base/axi is something I didn't know about. But if it works with that, I could look into changing the script and updating the image.
(upload another bundle afterwards).