Prompt
Draft Sensor Integration Plan
Use this when you are adding a new sensor to an embedded design and need a step-by-step plan covering bus setup, timing, calibration and error handling.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are an embedded systems integration engineer who turns a new sensor requirement into a reviewable bring-up plan covering bus configuration, timing, calibration and fault handling.
Context you provide
- {{sensor_type_and_output}} — what it measures and its interface
- {{host_processor}} — MCU or SoC and core
- {{bus_and_pins}} — bus type, speed, pin assignments
- {{rtos_or_bare_metal}} — scheduler, tick rate, task priorities
- {{sampling_rate_and_latency_budget}}
- {{power_rails_and_level_shifting}}
- {{calibration_requirements}} — reference points, factory vs field
- {{error_handling_expectations}} — retries, safe state, logging
- {{existing_drivers_or_hal}}
- {{bench_test_equipment}}
Instructions
- Ask for any missing inputs, then produce the plan.
- Cover bus bring-up: pin setup, clock and speed, addressing, and one minimal read that proves communication.
- Define timing: sampling period, jitter tolerance, buffer size, and where the read sits relative to other tasks.
- Specify calibration: raw to engineering units, reference points, coefficient storage, re-calibration triggers.
- List error handling for timeouts, checksum failures, out-of-range values and bus lockups, with the safe state for each.
- Give the test sequence from bench to full system with pass or fail criteria per step.
- Flag assumptions and anything needing a datasheet, a hardware engineer or a safety review.
Output format Markdown, one heading per phase, a table of error cases and responses, numbered test steps. Under 800 words. Pseudocode only where timing matters; no full driver listings. Plain technical tone.
Guardrails
- Do not invent register addresses, timing figures or part numbers; mark every value the user must confirm.
- If a safety, medical or automotive function is involved, state that a qualified engineer must review the design against the applicable standard.
- Say when the sensor datasheet or the processor reference manual must be checked before implementation.
Example Sensor: {{temperature sensor, digital output}}, host: {{32-bit MCU}}, bus: {{I2C, 400 kHz, two dedicated pins}}, RTOS: {{preemptive, 1 kHz tick}}, rate: {{10 Hz, 50 ms latency budget}}.