I2C Multiplexer Testing Summary

i2c multiplexer testing n.w
1 / 8
Embed
Share

Explore the results of testing the I2C multiplexer with a focus on obtaining Chem ID/Battery Type from the fuel gauge. Hardware results captured using an oscilloscope and I2C data read via UART serial communication. Discover the challenges faced and outcomes for each channel tested.

  • I2C
  • Multiplexer
  • Testing
  • Results
  • Hardware

Uploaded on | 1 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. I2C Multiplexer Testing

  2. I2C Mux Schematic NOTE: For the testing, we are testing U501 - one channel only; either Channel 0 or Channel 2. MCU

  3. I2C Mux Testing Summary Tested I2C Mux 1 (U501) Channel 0, Channel 1 and Channel 2 For the testing we focused on getting the Chem ID/Battery Type from the fuel gauge which is supposed to be 0x2158. Hardware results taken using oscilloscope. I2C data read using UART serial comm HyperTerminal. I2C Multiplexer I2C Protocol Hardware Result HyperTerminal Result Slide 1. Slave address format: 0xE0 + <values of A2-A0> + R/W No slave output Chem ID not accurate 4 2. Add I2C Write 0x04 to Slave Address 0xE6 Has slave output Chem ID not accurate 5 3. I2C Write 0x04 to Slave Address 0x73 (TI advice to use 0x73) No slave output Wrong slave address detected 6 4. I2C Write on I2C Mux Address, Channel Select, FG Add, ChemID Has slave output Chem ID not accurate 7 5. (TI advice) Start, I2C MUX ADDRESS [ACK], Channel Select [ACK], Stop Start, CH Slave Address [ACK], Send pointer byte or data [ACK], NACK Stop Has slave output Chem ID not accurate 8 Note: Testing used UART HyperTerminal to read the I2C data.

  4. Testing 1: Slave address format: 0xE0 + <values of A2-A0> + R/W

  5. Testing 2: I2C Write 0x04 to Slave Address 0xE6 TI advised to add an I2C Write 0x04.

  6. Testing 3: I2C Write 0x04 to Slave Address 0x73 I2C Master Data I2C Master Clock I2C Slave Data I2C Slave Clock Detected 230 (E6h) when it is supposed to be 115 (73h).

  7. Testing 4: I2C Write on I2C Mux Address, Channel Select, FG Add, ChemID U501 MUX 1 Channel Selected: Channel 2 I2C Master Data I2C Master Clock I2C Slave Data I2C Slave Clock

  8. Testing 5: Send 0x06 to 0xE6, Send ALtMfrAccess to 0xAA, I2C Read 0xAB

More Related Content