This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/DLPC6401: DLPC6401:I2C communication with MCU

Part Number: DLPC6401
Other Parts Discussed in Thread: DLPC350

Tool/software: Linux

Hi,

  The  status of DLPC debugging is:

The power supply is 1.2v, 1.9v, 1.8v and 3.3v and it is normal,  the electricity timing sequence is satisfied.32MHz clock is normal;The Flash program verification of DLPC6401 is not a problem (another development board verifies the light function diagram);PWRGOOD and POSENSE are high level, GPIO26 is low level.

Doc1.docx

The current problem is that our main control RK3288 and DLPC's I2C cannot communicate with each other. We found the problem through datasheet:

1. According to the specification, the read-write address is 8 bits, all of which are 0x34. According to the standard I2C protocol, the read-write address is 7 bits, and the 8th position is read and write bit. Does this not conform to this standard protocol?


2. The following specification has a flowchart showing that the writing is 0x34, reading is 0x35, and the above text indicates which is right?Can you provide a complete description of the I2C agreement?

  • Hello,

    Thanks for using the E2E forums! I believe you are correct that there is an error in the programmers guide. The read address should always be 35. For further information please investigate the DLPC350 programmers guide section 1.1.1. I realize they are different parts, but they operate in a similar manner: www.ti.com/.../dlpu010f.pdf

    Hope that helps!

    Best,
    ~Danny W