Skip to content

docs(troubleshooting): add a camera-not-detected entry - #1419

Open
FabienDanieau wants to merge 1 commit into
mainfrom
771-docs-camera-not-detected
Open

FabienDanieau wants to merge 1 commit into
mainfrom
771-docs-camera-not-detected

Conversation

@FabienDanieau

Copy link
Copy Markdown
Contributor

A loose or upside-down camera ribbon cable makes every app fail to start while head and body movements keep working, and the visible error is a refused connection that says nothing about the camera. #771 lost days to this. The microphone already has two troubleshooting entries covering the same failure mode; the camera had none.

Adds one entry in Vision & Audio, and a one-line pointer from "My app crashes silently or doesn't start", which is where someone with this symptom actually looks.

Both commands were run on a Wireless before documenting them:

  • rpicam-hello --list-cameras lists imx708_wide (and libcamera-hello no longer exists on the image)
  • dmesg | grep "camera module ID" prints imx708 0-001a: camera module ID 0x0302, and dmesg needs no sudo

The note in the entry is the important part: the CM4 exposes two CSI ports and we only use one, so a healthy robot always logs imx708 10-001a: failed to read chip id 708, with error -5 for the unused port. Any diagnostic that greps dmesg for imx708 errors will therefore fire on every working robot, which is what the recommendations attached to the issue proposed doing.

Fixes #771

🤖 Generated with Claude Code

A loose or upside-down camera ribbon cable makes every app fail to start
while head movements keep working, and nothing in the visible error
mentions the camera. The microphone has two entries covering exactly this
failure; the camera had none.

Add one entry in Vision & Audio with the cable check and the two commands
that actually discriminate, and point at it from "My app crashes silently
or doesn't start", which is where users with this symptom land.

Both commands were run on a Wireless: `rpicam-hello --list-cameras` lists
imx708_wide, `dmesg | grep "camera module ID"` prints the sensor line, and
dmesg needs no sudo. The note about `failed to read chip id 708` matters:
the CM4's unused second CSI port always logs that probe failure, so an
imx708 error line in dmesg is not a symptom.

Fixes #771

Assisted-by: Claude:claude-opus-5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improving error messages when there is a camera problem causing every app to fail.

1 participant