embedded-gui-feedback

Captures LCD display output via camera and analyzes layout, font, and color issues.

Updated Sep 3, 2024
One-click install
npx skills add https://github.com/eminboydak/duckTerm --skill embedded-gui-feedback-eminboydak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: embedded-gui-feedback
Source: https://github.com/eminboydak/duckTerm/tree/main/.agents/skills/embedded-dev/skills/embedded-gui-feedback
Command: npx skills add https://github.com/eminboydak/duckTerm --skill embedded-gui-feedback-eminboydak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Human visual inspection of embedded LCD displays misses timing, alignment, and color defects. This Skill replaces subjective judgment with camera-captured evidence and structured AI analysis to detect display issues in GUI projects. ## Core Features & Use Cases - Camera-Based Capture: Uses a USB webcam to capture timestamped screenshots of the physical LCD display via a Python capture script. - Structured Issue Detection: Analyzes captures for blank screens, partial display, wrong colors, offsets, mirroring, flickering, and missing lines, mapping each symptom to a likely cause such as MADCTL values or DMA chunking. - Before/After Comparison: Captures images before and after fixes, then compares them to verify that corrections resolved the issue. - Use Case: After flashing a new LCD driver to an ESP32 board, capture the display with a webcam, detect that content is mirrored, identify the MADCTL rotation bits as the cause, apply the fix, and re-capture to confirm. ## Quick Start Capture my LCD display with the camera and analyze it for layout, color, and alignment issues.

Frequently Asked Questions about embedded-gui-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an embedded LCD display output automatically?

Capture the physical display with a USB webcam using the camera_capture.py script, then run image analysis checking layout, font, color, alignment, and overlap. Compare the capture against the expected output and map any symptom to its likely cause using the issue table.

How to debug a blank or partially rendered LCD screen?

A blank screen usually indicates a wrong initialization sequence, while partial display points to an incorrect MADCTL value. Capture the screen with the camera, confirm the symptom visually, then fix the driver init or MADCTL setting and re-capture to verify.

What camera setup is needed for LCD display capture?

Use a 1080p USB webcam centered on the LCD screen at 15-30cm distance with uniform lighting to avoid glare. The capture script lists available cameras with the --list flag and supports Windows, Linux, and macOS.

Why does my LCD show wrong colors or mirrored content?

Wrong colors typically come from a color format mismatch such as RGB565 versus RGB666, while mirrored content is caused by MADCTL rotation bits 5, 6, or 7. Capture the display, identify the symptom, and adjust the corresponding driver configuration.

When should I not use camera-based GUI verification?

Skip this workflow for projects without any GUI or display component, since there is no visual output to capture. It is designed to run after functional verification passes on display projects, not as a replacement for code-level testing.