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 MicroPython
    19 Posts 11 Posters 5.3k Views 11 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.
    • J Offline
      jmarcelino @pedro
      last edited by jmarcelino

      @pedro
      The new firmware 1.7.5.b2 (like previous 1.7.5.b1) has hardware I2C and should support clock line stretching

      Update: maybe I spoke too soon: https://github.com/espressif/esp-idf/issues/323 not sure if this means no clock stretching at all or just when I2C is slave

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

        @jmarcelino Hmmm. It looks like the '323' issue applies to I2C slave mode only, but some clarification would be nice. We have some testing to do with the new I2C HW support (and we were having troubles with certain I2C peripherals when it comes to clock stretching); I'll see if we can do some specific tests with and without clock stretching to see how the HW I2C handles it.

        L 1 Reply Last reply Reply Quote 0
        • L Offline
          livius @Eric24
          last edited by

          @Eric24
          look at current firmware 1.7.6 there are some i2c releated fixes for hardware init

          think about people first, then computers

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

            Any news on this topic? I would also like to get the Bosch BNO055 IMU working with a Lopy.

            J 1 Reply Last reply Reply Quote 0
            • J Offline
              jmarcelino @digitalfalcon
              last edited by

              @digitalfalcon
              Have you tried it and it doesn't work? This an old topic, a lot has changed since

              D 1 Reply Last reply Reply Quote 0
              • D Offline
                digitalfalcon @jmarcelino
                last edited by

                @jmarcelino As far as I can tell it's still not working.

                J E 2 Replies Last reply Reply Quote 0
                • J Offline
                  jmarcelino @digitalfalcon
                  last edited by

                  @digitalfalcon
                  Most of the issues seem to be around what pull-ups (if any) are used, how is your sensor connected?

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

                    @digitalfalcon Just to confirm, you're using I2C buss 0 or 1 (the hardware busses), right? Bus 2 is a software "bit banged" bus, which will still not support clock stretching.

                    PS - I can not confirm that addition of the hardware I2C bus support solved the clock stretching problems, as I've not yet gotten back to testing that particular aspect of our project.

                    D 1 Reply Last reply Reply Quote 0
                    • D Offline
                      digitalfalcon @Eric24
                      last edited by

                      @Eric24 @jmarcelino I2C Clock Stretching is working on the LoPy. Sorry for the false alarm.

                      1 Reply Last reply Reply Quote 0
                      • C Offline
                        Colateral @abilio
                        last edited by

                        @abilio Do you have an update on clock stretching issue. There is also a new sensor SCD30 (from Sensiron) that face the same clock stretching issue. We can not see device address 0x61 on the BUS bus(0) on (P22, SCL=P23) nor bus(1) on (P9, SCL=P8). Sensor works fine ESP32 (arduino dev)
                        Any workaround for this on pycom?

                        S 1 Reply Last reply Reply Quote 0
                        • S Offline
                          Strevens Pycom Ambassadors @Colateral
                          last edited by

                          @Colateral I had the same issue with the SCD30. The SCD30 also supports modbus as well as I2C, which is how I got the SCD30 to work with the lopy

                          tiborrrT 1 Reply Last reply Reply Quote 0
                          • tiborrrT Offline
                            tiborrr @Strevens
                            last edited by

                            @Strevens great you got it to work. If you have time, could you please take a look at my topic at the following: https://forum.pycom.io/topic/6141/scd30-oserror-i2c-bus-error

                            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