512-861-3400Log inCreate Account

I2C4 strange behavior

Forums › Devices › OSD32MP15x › I2C4 strange behavior

Viewing 3 reply threads
  • Author
    Posts
    • January 12, 2021 at 6:04 am #11115
      Raimo Onteroraimo
      Participant

        Hi, we are using a custom board with OSD32MP157c. We have a video decoder with i2c address 0x20 (7-bit). This address is defined in the devicetree too. It’s wired to the I2C4 interface. However the linux driver doesn’t find it. The linux i2cdetect utility finds it from 0x50 address. Is there some remapping inside the MPU or some other things that should notice?

      • January 13, 2021 at 6:23 am #11117
        Raimo Onteroraimo
        Participant

          Sorry, there was a mistake on the board. I2c data and clock lines were swapped. So no issue with that.

          • This reply was modified 3 years, 9 months ago by Raimo raimo.
        • January 13, 2021 at 10:51 am #11119
          Neeraj Kumar Reddy DantuNeeraj Dantu
          Moderator

            ramio,

            Glad you could solve your issue. Please let us know if you have more questions.

             

            Best,

            Neeraj

          • February 5, 2021 at 9:47 am #11202
            Lev DowerLevDower
            Participant

              Hello…in my case I copied and executed the I2C Scanner and it gave me Int32 address 112, which i right shifted by 1 and used and it WORKED for my other project!Not sure how on earth one (read, novice like me!) would think of running a scanner to determine an address of a device and then use it.

          • Author
            Posts
          Viewing 3 reply threads
          • You must be logged in to reply to this topic.

          Octavo Systems LLC all rights reserved
          OCTAVO is registered in the U.S. Patent and Trademark Office. OSD, C-SiP, and the Octavo Logo are trademarks of Octavo Systems LLC.