Engineering acceptance guide
Phase acceptance for an I2C board should cover normal communication, error responses and recovery for the target device, matched to schematic, driver and documentation revisions. Measurement accuracy, calibration and system reliability have separate validation conditions that belong in the agreed scope.
Confirm the interface conditions first
Prepare device documentation, register revision, controller, supplies, voltage levels, address, pull-ups and connections. Address documents may use seven-bit notation or include a read/write bit; agree the representation. Refer to NXP I2C specification UM10204 for bus timing and electrical conditions. Device operations remain subject to the relevant datasheet and target hardware.
Swipe the table horizontally to view all columns.
| Deliverable | Checks | Records to retain |
|---|---|---|
| Schematic and connection table | Supplies, levels, pins, address and pull-ups | Drawing revision, wiring and inspection |
| Registers and driver | Access, configuration readback and parsing | Inputs, returned values and logic-analysis records |
| Error interface | No acknowledgement, timeouts and incomplete transfers | Triggers, error codes and application feedback |
| Recovery path | State after disconnection, restart or agreed recovery | Permitted actions, timing and remaining state |
| Prototype and material | Match hardware, build, interfaces and untested items | Delivery index, revisions, hashes and acceptance items |
Define a reproducible failure case
A case needs repeatable steps and permitted hardware operations. Check electrical and safety conditions before disconnecting signals or injecting faults; an unconfirmed operation is not a test design.
Swipe the table horizontally to view all columns.
| Case field | Suggested contents |
|---|---|
| Case and target | Case ID, sensor, controller and board revision |
| Preconditions | Supplies, connections, timing, address and driver version |
| Trigger | Normal access or an approved fault trigger |
| Expected response | Agreed returned value, error code and application feedback |
| Recovery decision | Permitted steps, target state and pass condition |
| Result and evidence | Actual response, timing, log or waveform location |
These are delivery-method and case fields, with no preset error codes or passing results. Record each project case against its implementation and sampling conditions.
Separate communication from measurement acceptance
Successful register access supports the communication result for that case. Measurement error also requires a reference, sampling conditions and comparison method. Define continuous operation, EMC and certification separately instead of extending a single communication result.
Related project and enquiry inputs
The IMX585 sensor board case, in Chinese illustrates coordination between board interfaces and sensor control. Design the actual I2C cases for the selected sensor and controller. For hardware development, in Chinese, provide device material, receiver interface, connections, prototype stage and acceptance targets to define review, board changes, drivers and integration.
Online
Phone
WeChat
Top