From f201f95c73c7757aaf8d5dc44c3538d7d88ba36b Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Mon, 3 Aug 2026 15:21:20 -0400 Subject: [PATCH] BRINGUP: coda JPEG capture-buffer sizing fact (noise frames overflow the default) --- docs/BRINGUP.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/BRINGUP.md b/docs/BRINGUP.md index 1586d2f..5dd6e11 100644 --- a/docs/BRINGUP.md +++ b/docs/BRINGUP.md @@ -195,6 +195,12 @@ encode 7 ms**. Two hard-won facts: bounce copy. - The VPU encoder accepts 1296×972 exactly (no MCU-alignment padding needed) with quality via V4L2_CID_JPEG_COMPRESSION_QUALITY. +- **A CSI noise/glitch frame can out-size the coda driver's default + ~2 B/px JPEG capture buffer** (kernel logs "JPEG too large for + capture buffer" + a vb2 WARN; observed once under streaming+motion + load). forgectrl requests 3 B/px and drops error-flagged dequeues as + single bad frames — hardware encode stays active; software fallback + engages only on repeated consecutive hard failures. libjpeg remains the automatic fallback (`FORGECTRL_NO_VPU=1` forces it) and the snapshot path; `/cam/status` reports `"encoder"`.