Troubleshooting

Troubleshooting works best when every check narrows the possible causes. Change one variable at a time and keep the last known-good state visible.

A reliable sequence

1. Describe the symptom without guessing the cause.
2. Reproduce it with the smallest useful setup.
3. Check power, ground, transport, and configuration in that order.
4. Compare the result with a known-good device or measurement.
5. Record the change that restored or altered the behavior.

Escalate with evidence

Include the device revision, firmware, supply conditions, logs, measurements, and the exact step where behavior diverges. This turns a support request into a short investigation.

Diagnostic note: A failed test is still useful when its setup and expected result are documented.

If the issue is outside the documented paths, continue to Support.