Lines Matching full:emulator

9 Zephyr supports a simple emulator framework to support testing of external peripheral drivers
13 various subsystems. For example, it is possible to write an emulator
32    :alt: Emulator architecture showing tests, emulators and drivers
36 controller/emulator which passes I2C traffic from the AT24 driver to the AT24
68 Creating a Device Driver Emulator
71 The emulator subsystem is modeled on the :ref:`device_model_api`.  You create
72 an emulator instance using one of the :c:func:`EMUL_DT_DEFINE()` or
76 device driver. This means that your emulator defines ``DT_DRV_COMPAT`` using the
89   #. ``bus_api`` - This points to the API for the upstream bus that the emulator
93      the emulator. The ``_backend_api`` parameter is optional.
103 The real code is shown in green, while the emulator code is shown in yellow.
109 emulator.
111 The ``_backend_api`` provides a mechanism for tests to manipulate the emulator
118 Each emulator is responsible for updating the correct vendor specific registers
124   #. Test connects a charger using the BC1.2 emulator backend.
126   #. Test disconnects a charger using the BC1.2 emulator backend.
136 * I2C emulator driver, allowing drivers to be connected to an emulator so that
139 * SPI emulator driver, which does the same for SPI
141 * eSPI emulator driver, which does the same for eSPI. The emulator is being
144 * MSPI emulator driver, allowing drivers to be connected to an emulator so that
184 #. Bosch BMI160 sensor driver connected via both I2C and SPI to an emulator:
192    connected via I2C an emulator: