Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    I2C Clock Stretching

    Scheduled Pinned Locked Moved Discussion
    i2cclock stretch
    7 Posts 6 Posters 2.3k Views 7 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R Offline
      RicZeDuck
      last edited by

      Re: I2C Clock Stretching

      Anything happening on the stretching part?

      I have to get an Adafruit BNO055 up and running on LoPy before the end of March.

      It is supposed to be used on a FiPy combined with a GPS for an Inertial Navigation System prototype project.

      1 Reply Last reply Reply Quote 0
      • I Offline
        iannucci
        last edited by

        I just implemented functionality for the TI BQ27441 Battery Fuel (Gas) Gauge today and was having no success in getting the device to respond until I hooked up an I2C debugger and saw that, when the battery gauge stretched the clock and then let go, the LoPy I2C interface never came back to life. So I've re-discovered this old problem. The short-term fix for this particular part is to slow its I2C transactions down to 10kHz (wasting energy in the process...).

        Running MicroPython v1.8.6-464.

        What is the status of the real clock-stretching fix?

        Thanks.

        L B 2 Replies Last reply Reply Quote 1
        • L Offline
          livius @iannucci
          last edited by

          @iannucci
          This is because I2C i still software not hardware.
          Maybe @daniel can say more..

          think about people first, then computers

          1 Reply Last reply Reply Quote 0
          • D Offline
            daniel
            last edited by

            @livius and @iannucci I have good news, the hardware implementation of the I2C is ready and will be merged very soon.

            I E 2 Replies Last reply Reply Quote 3
            • I Offline
              iannucci @daniel
              last edited by

              @daniel I would be happy to test.

              1 Reply Last reply Reply Quote 0
              • E Offline
                Eric24 @daniel
                last edited by

                @daniel I'm happy to test, too. I'm seeing I2C problems any time a slave attempts clock-stretching.

                1 Reply Last reply Reply Quote 0
                • B Offline
                  brotherdust @iannucci
                  last edited by

                  @iannucci I'm curious if you ever got this working. The TI documentation is a hot mess. If you did, can you post up some example code, please? =)

                  1 Reply Last reply Reply Quote 0

                  Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                  Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                  With your input, this post could be even better 💗

                  Register Login
                  • 1 / 1
                  • First post
                    Last post

                  Pycom on Twitter

                  Pycom