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

    New firmware release v1.18.0

    Scheduled Pinned Locked Moved Announcements & News
    firmware
    24 Posts 13 Posters 4.5k Views 13 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.
    • Charly86C Offline
      Charly86 @iwahdan
      last edited by

      @iwahdan Nice, but that's not my PR so I don't want to get any credit for it ;-)

      A 1 Reply Last reply Reply Quote 0
      • M Offline
        Marike
        last edited by Marike

        I used the Pycom Firmware Updater to update my FiPy from v1.17.3.b1. The Updater says the latest available is 1.15 but when I proceed to the update, it detects the 1.18 stable is available and uses that.

        Issues I've encountered:

        • It takes longer after a RESET to connect to the FiPy REPL shell.
        • It appears the first call to lte.attach() always fails with an error. No error on retry but. . .
        • Connecting to LTE does not succeed (fails to attach). So far, I have tried waiting up to 10 minutes. It previously would attach and connect within 10s.
        X 2 Replies Last reply Reply Quote 0
        • X Offline
          Xykon administrators @Marike
          last edited by

          @marike 1.15.0 is the latest firmware updater tool version, while 1.18.0 is the latest firmware version being flashed onto the device.

          The firmware team will look at the issues raised and provide an update as soon as possible.

          If you wish to downgrade please follow these instructions.

          Christian Ehlers

          1 Reply Last reply Reply Quote 0
          • X Offline
            Xykon administrators @Marike
            last edited by

            @marike Two quick questions: Did you upgrade the firmware of your modem? If yes which firmware are you currently using?

            Which provider (or test system) are you using for LTE-M connectivity?

            Christian Ehlers

            M 1 Reply Last reply Reply Quote 0
            • J Offline
              jbthompson @Xykon
              last edited by jbthompson

              @xykon Recently loaded 1.18.0 onto WiPy2.0 OEM module and having some less than optimal i2c performance.
              Issues:

              1. Doest the new i2c firmware supports i2c clock stretching? I'm communicating with a bno055 imu (that uses clock stretching) and am getting I2C hangs.
                Currently the i2c hangs after I enable the bno055 and do a scan (which returns the address at least once before hanging).

              I have 4.7K pullups for SDA / SCL on my board that is interacting with the WiPy2.0 OEM.
              Setup:
              Talking to fuel gauge and IMU.
              Scan hangs after second attempt....

              >> from machine import I2C, Pin
              >>
              >> bno055_rst = Pin('P23', mode=Pin.OPEN_DRAIN)        # imu reset
              >> bno055_rst.value(1)         #enable imu
              >>
              >> i2c = I2C(0, I2C.MASTER)
              >>
              >> i2c.scan()
              >> [40, 85]     #success, i2c address for the bno055, bq27441
              >>
              >>i2s.scan()
              ... hangs forever, need to hard reset the wipy2.0 OEM
              Note: No hang if I disable the imu by pulling p23 low.
              

              Thank you!

              1 Reply Last reply Reply Quote 2
              • M Offline
                Marike @Xykon
                last edited by Marike

                @xykon

                I'm using Verizon (US) for LTE-M. The firmware for the modem was upgraded last week:

                UE5.0.0.0c
                LR5.1.1.0-33988
                

                It looks like there is something broken with the AT commands. The response to lte.send_at_cmd('X') where X is anything is the same, whether X is valid or not:

                >>> lte.send_at_cmd('AT+CEREG?')
                ''
                >>> lte.send_at_cmd('AT+COPS?')
                ''
                >>> lte.send_at_cmd('FAKE_COMMAND')
                ''
                
                1 Reply Last reply Reply Quote 1
                • bmarkusB Offline
                  bmarkus
                  last edited by bmarkus

                  Updater updates my LoPy to 1.17.5.b6 but not 1.18.0

                  0_1527931077146_07052bab-80ba-44a6-8fe8-c6d9efaf2e21-image.png

                  X 1 Reply Last reply Reply Quote 1
                  • X Offline
                    Xykon administrators @bmarkus
                    last edited by

                    @bmarkus This is the stable firmware. We haven't released a new Pybytes version yet.

                    Christian Ehlers

                    bmarkusB 1 Reply Last reply Reply Quote 0
                    • bmarkusB Offline
                      bmarkus @Xykon
                      last edited by bmarkus

                      @xykon said in New firmware release v1.18.0:

                      @bmarkus This is the stable firmware. We haven't released a new Pybytes version yet.

                      I'm not using pybytes and do not want to have it, just want to update to an ordinary 1.18.0 In the updater all options, like beta versions, pybytes, forced region setting, etc. unselected. Why can't update to 1.18.0?

                      X 1 Reply Last reply Reply Quote 1
                      • X Offline
                        Xykon administrators @bmarkus
                        last edited by

                        @bmarkus Are you using the latest stable firmware updater? Did you change the Type to stable in the Communications window?

                        0_1528056983040_2018-06-03_22-15-03.png

                        Christian Ehlers

                        bmarkusB 1 Reply Last reply Reply Quote 0
                        • bmarkusB Offline
                          bmarkus @Xykon
                          last edited by

                          @xykon Thanks, setting Type to stable solved the problem, update to 1.18.0 was successful. Would be god to change default from pybytes to stable :(

                          X 1 Reply Last reply Reply Quote 3
                          • X Offline
                            Xykon administrators @bmarkus
                            last edited by

                            @bmarkus I can't change the default but the next firmware updater release will remember your choice.

                            Christian Ehlers

                            1 Reply Last reply Reply Quote 0
                            • X Offline
                              Xykon administrators
                              last edited by

                              Please note that as per the update above, we have reverted the master branch of pycom-esp-idf back to the correct commit needed to build the stable firmware.

                              We have also created a new branch idf-dev which contains all the updates previously pushed to master. The source code for the pycom-micropython-sigfox development release will be published some time next week.

                              Christian Ehlers

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

                                Please take a look at this thread:
                                https://forum.pycom.io/topic/3377/fw-1-18-0-increased-boot-time-power-consumption

                                1 Reply Last reply Reply Quote 0
                                • S Offline
                                  shivankgarg98
                                  last edited by

                                  What is LORAWAN MAC version of lopy4 after this firmware update?

                                  1 Reply Last reply Reply Quote 0
                                  • A Offline
                                    Aubreychen @Charly86
                                    last edited by Aubreychen

                                    @charly86 said in New firmware release v1.18.0:

                                    cardgenerator

                                    @iwahdan Nice, but that's not my PR so I don't want to get any credit for it ;-)

                                    Are you still facing this issue?

                                    @charly86 said in New firmware release v1.18.0:

                                    @iwahdan Nice, but that's not my PR so I don't want to get any credit for it ;-)

                                    M 1 Reply Last reply Reply Quote 0
                                    • I Offline
                                      Isabell gracia Banned
                                      last edited by

                                      This post is deleted!
                                      1 Reply Last reply Reply Quote 0
                                      • Z Offline
                                        Zekai Sen Banned
                                        last edited by

                                        This post is deleted!
                                        1 Reply Last reply Reply Quote 0
                                        • M Offline
                                          monika Hoenig Banned @Aubreychen
                                          last edited by

                                          This post is deleted!
                                          1 Reply Last reply Reply Quote 0
                                          • S Offline
                                            Selena Morrissel Banned @Xykon
                                            last edited by

                                            This post is deleted!
                                            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
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post

                                            Pycom on Twitter

                                            Pycom