I2c test tool

Get the value of bit register 0x00 of the I2C device at 7-bit address 0x48 on bus 1 i2c-1 , after user confirmation:. This assumes that the device automatically increments its internal pointer register on every read, and supports read byte transactions read without specifying the register address, "Receive Byte" in SMBus terminology.

Note that this is only safe as long as nobody else is accessing the I2C device at the same time. This manual page was strongly inspired from those written by David Z Maze for i2cset. Source file: i2cget. Found a problem? See the FAQ. Hardware Specifications General Mechanical Dimensions 5. Test clips are also included. Download Datasheet. Buy Now. Learn More. Download Whitepaper. Benefits Monitor displays high-level view of I2C bus traffic.

Ordering Information Part Number Request Help. Request Technical Support. Complete the form below to request technical support. Select a product CPXI Please describe your reason for contacting us in detail. I consent to my submitted data being collected and stored.

This field is for validation purposes and should be left unchanged. Thanks for reaching out! Talk to you soon, The Corelis Team. Register for Training Please provide the requested information to register for a training class at our facility in Cerritos, California. Please select your preferred training session dates. November , Ships with a 12 inch interface cable that terminates in flying leads suitable for connection to 0. This website requires cookies to provide all of its features.

For more information on what data is contained in the cookies, please see our Privacy Policy page. To accept cookies from this site, please click the Allow button below.

Engineers developing embedded systems have several options when it comes to selecting a communication protocol for their hardware device. One such option, the I2C communication protocol , offers unique advantages that make it an attractive choice for engineers.

The inter-integrated circuit or I2C communication protocol is a two-wire, clock synchronized protocol with a two-way data line and a one-way clock line. I2C protocol is fairly simple in the sense that it relies on just two lines of communication, but its complexity arises from the fact that all devices on the bus must communicate with each other using only these two lines. An I2C bus may have several master and slave devices connected on the same lines, and bus arbitration must be used to handle bus contentions and ensure that the correct data is driven on the bus.

I2C is asynchronous communication protocol, meaning that, like the SPI protocol, the output of bits is synchronized to the sampling of bits by a clock signal that is shared between the master and slave devices on the bus. In an I2C device, the master device always retains control of the clock signal. To successfully achieve communication on an I2C bus, a number of initial conditions have to be satisfied.

The wiring on the device must be done correctly, the bus speed must be set to a speed that is usable by the master and slave devices, and the proper pull-up resistors must be present within the system. The master device must send the proper commands and the slave device should respond appropriately with an acknowledge ACK bit when the commands are received. A useful starting point for debugging your I2C system is performing verification that each of the above requirements is being fulfilled.

Here are the most important best practices to follow when debugging your I2C system. Most guidance documents for I2C circuit design recommend that the user first develops the master device and tests it completely with a test slave before continuing development.

Testing cannot be fully completed until the master and slave have been integrated, but delaying testing until this late stage can result in complicated errors that are difficult to resolve.

Instead, embedded engineers should test the master with a test slave that provides the necessary interfaces along with some additional test hooks.