3

I am pretty new to I2C protocol, but I managed to write to my device. I bought the ADV7630 evaluation board, which is an HDMI switch controlled by I2C.

I can write to registers using I2c, also i2cDetect works showing all devices. I also tried to read register contents, but whatever I try to read, I always get 'Read failed'. Also i2Cdump get all 'XX'.

Whai I read somewhere is bad connection, so I double checked, and soldered connectors, but this does not helped.

My hardware is ADV7630 Evaluation board from Analog Device, and a Raspberry Pi using raspbian latest distro.

Any clue about that would be really appreciated.

Thanks.

Command used:

i2cdetect -y 1

I got only 0x74 device (which is normal according to the adv7630 datasheet)

i2cset -y 1 0x58 0xff 0xff  # reset device
i2cset -y 1 0x58 0x0c 0x40  # disable chip powerdown
i2cset -y 1 0x58 0xea 0xc8  # set TXB main map address
i2cset -y 1 0x58 0xeb 0x80  # set TXB packet map address
i2cset -y 1 0x58 0xec 0x8e  # set TXB EDID map address
i2cset -y 1 0x58 0xed 0x8c  # set TXB Test map address
i2cset -y 1 0x58 0xee 0xb8  # set TXA main map address 
i2cset -y 1 0x58 0xef 0x70  # set TXA packet map address
i2cset -y 1 0x58 0xf0 0x7e  # set TXA EDID map address
i2cset -y 1 0x58 0xf1 0x7a  # set TXA test map address
i2cset -y 1 0x58 0xf9 0x64  # set repeater map address
i2cset -y 1 0x58 0xfa 0x6c  # set EDID map address
i2cset -y 1 0x58 0xfb 0x68  # set HDMI rx map address


i2cget -y 1 0x58 0xe1

Error: Read failed

i2cdetect -y 1

I got devices numbers detected: (in this case: 38,3d,3f,40,46,47,64,74) which is expected.

Pang
  • 9,564
  • 146
  • 81
  • 122
Eric Jalbert
  • 81
  • 1
  • 8
  • Include the actual code you're using. It'll make diagnosing the problem easier. – Marshall Davis Jun 14 '17 at 17:11
  • I am using i2ctools package, so there is no source code for that. The command I am using are i2cget -y 1 0x58 0xe1 which is reading device 0x58 register 0xe1 – Eric Jalbert Jun 14 '17 at 17:27
  • What I meant was that you include those commands or setup information. Something so that those who maybe could answer the question will know what you've done, exactly, and can help find where it went wrong. – Marshall Davis Jun 14 '17 at 17:32
  • Thank you helping me. I edited my original post to include all command I used. I hope this is more complete. – Eric Jalbert Jun 14 '17 at 18:15
  • I wonder if you want to read from `0x58` as this address is not in the list of detected devices. Have you tried `i2cget -y 1 ` without data-address. – stovfl Jun 15 '17 at 07:58
  • you're right, 0x58 is not in detected devices, but it is a device actually since I write to it and the chip reacts. 0x58 is the IO configuration in adv7630 datasheet. when I set other devices addresses using 0x58 (all the i2cset lines), it works fine. Also I tried to read from detected devices too, and got the same read error. – Eric Jalbert Jun 15 '17 at 14:45

1 Answers1

4

I found out what happened. Actually my device require something caled i2c repeat start condition. Since this is not activated by default on i2ctools, it is not working with my device.

The way you can activate i2c repeat start condition with Raspbian and i2ctools is this:

Create a file at /etc/modprobe.d/i2c.conf and set content to this:

options i2c_bcm2708 combined=1

and it works fine!

Thank you for your help!

References:

https://ez.analog.com/message/77452

http://rabbit-note.com/2015/02/15/raspberry-pi-i2c-repeated-start/

Eric Jalbert
  • 81
  • 1
  • 8