Getting Started with TEP DISCUSSION

What information makes an intermittent-reset question answerable?

Started by andreatigor debugging helpreset diagnosisbrownoutwatchdogminimal reproduction
3 replies 248 views 4 participants
Latest activity · 27 Sep 2026

What information makes an intermittent-reset question answerable?

andreatigor Getting Started with TEP Forum
#1

For a board that resets only when a sensor and radio run together, what should a useful help request include? A full project can be difficult for another member to reproduce, but a tiny example may remove the failure.

How would you reduce the problem while keeping the evidence needed to distinguish a brownout, watchdog timeout and software fault?

Community replies 3

Re: What information makes an intermittent-reset question answerable?

#2

List the exact board and revision, power source, attached modules, firmware framework and library versions. Include the reset reason captured as early as possible after boot. State the event that triggers the reset and how often it occurs. A wiring diagram is more useful than saying the connections are correct, especially when the radio and sensor share a supply or bus.

Re: What information makes an intermittent-reset question answerable?

#3

Reduce one variable at a time. Keep the sensor task running while disabling radio transmission, then restore the radio and replace sensor reads with a fixed value. Record whether the reset remains in each case. Avoid changing the power supply, timing and firmware simultaneously: a successful run would then leave several possible explanations. Share the smallest example that still fails, not merely the smallest program.

Re: What information makes an intermittent-reset question answerable?

#4

Measure the supply at the board during the triggering event, with an appropriately rated probe and short ground connection. A multimeter can miss a short voltage dip. Add timestamps around blocking calls and describe the watchdog configuration. Remove credentials from logs before posting, but retain error codes, timing and version details. Those details allow others to propose a specific next measurement.

TEP COMMUNITY