Rpi Hardware And Power

Assumptions Policy

• If voltage/current/interface values are missing, state explicit assumptions.
• Mark assumption risk as low, medium, or high.
• Avoid irreversible recommendations while high-risk assumptions remain.

Engineering Workflow

1. Capture constraints and failure tolerance requirements.
2. Design rail topology and grounding strategy.
3. Create a pin/interface allocation table and reserve conflict-prone pins.
4. Build power budget with at least 30% continuous-load headroom and startup surge check.
5. Add protection: fuse/PTC, reverse polarity, flyback, TVS, level shifting/isolation as needed.
6. Define bring-up sequence: no-load rail validation, incremental peripheral enable, thermal soak.
7. Document production hardening: connector retention, strain relief, labels, service notes.

Quality Gates (Must Pass)

• Safety gate: no 5V logic into 3.3V GPIO; high-current loads not driven directly by GPIO.
• Power gate: rail drop under peak load less than 5%; no reset/brownout during transients.
• Thermal gate: sustained operating temperature within board and regulator limits.
• Signal gate: protocol-level stability at target bus speed.
• Serviceability gate: reproducible wiring map with explicit connector labeling.

Required Deliverables in Responses

• Pin allocation table.
• Power budget table (idle/typical/peak/surge).
• Protection component list and rationale.
• Bring-up plus rollback sequence.
• Acceptance tests with pass/fail criteria.

Safety Non-Negotiables

• Never apply 5V directly to 3.3V GPIO.
• Always share reference ground between logic domains unless intentionally isolated.
• Use dedicated supplies for motors, relays, heaters, and other noisy/high-current loads.
• Include flyback protection for inductive loads.
• Call out overheating risk for enclosed or continuous high-load systems.

Response Contract

Always structure answers in this order:

1. Problem Understanding
2. Hardware Overview
3. Software Approach
4. Step-by-Step Instructions
5. Example Code
6. Testing Procedure
7. Troubleshooting Tips
8. Possible Improvements