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

    Cellular radio firmware release (SQN3330) for both Cat-M1 and NB-IoT

    Scheduled Pinned Locked Moved Announcements & News
    firmware
    48 Posts 18 Posters 17.1k Views 22 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.
    • D Offline
      daniel
      last edited by

      Hello everyone,

      I know many of you were expecting this. We have made available 2 new firmware files for the Cellular radio in the FiPy, GPy and G01 modules. All the details and instructions can be found here:

      https://github.com/pycom/pycom-libraries/tree/master/lib/sqnsupgrade

      Cheers,
      Daniel

      A C 2 Replies Last reply Reply Quote 5
      • A Offline
        arneme @daniel
        last edited by

        @daniel That is great news and an important step forward. Could you say more about the roadmap to support Huawei base stations and guard band deployments?

        1 Reply Last reply Reply Quote 1
        • B Offline
          bali
          last edited by

          @daniel Any chance why i get this? !0_1521819285071_Screen Shot 2018-03-23 at 11.33.31 AM.png

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

            @bali can you try removing power, inserting a SIM card and trying again?

            B 1 Reply Last reply Reply Quote 0
            • B Offline
              bali @daniel
              last edited by

              @daniel I tried, i got the exact same thing unfortunately. The reason why i'm trying to update the firmware is because when i try to call lte = LTE() the GPy hangs.

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

                Do you have SIM card properly inserted? Can you double check?

                B 1 Reply Last reply Reply Quote 0
                • B Offline
                  bali @daniel
                  last edited by

                  @daniel I double checked it, still not working. 1_1521820926411_IMG_2343 (2).jpg 0_1521820926410_IMG_2342 (2).jpg

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

                    @bali have you ever been able to call lte = LTE() without hanging?

                    B 1 Reply Last reply Reply Quote 0
                    • B Offline
                      bali @daniel
                      last edited by

                      @daniel with firmware 1.16.0.b1 yes, but i could never attch to cellular network because i’m on At&T and in 1.16 there was no way to configure for it.

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

                        @bali can you try changing the baud rate from 921600 to 115200 or 345600 and maybe 57600? Just in case somehow the default baudrate is different in your board...

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

                          @bali OK then it seems that some of the new logic is causing your device to hang. Are you able to build a custom firmware? Then we can disable the background LTE logic and simply run the upgrade...

                          B 1 Reply Last reply Reply Quote 0
                          • B Offline
                            bali @daniel
                            last edited by

                            @daniel I did try at 921600, 345600, 115200, 57600 and it failed the same way at every baud rate. Unfortunately i can't build custom firmware. If you could send me one with the LTE disabled i could try it. I ordered the GPy but was never able to the the LTE on it :(

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

                              @bali Could you please check what happens if you run the following commands on your GPy?

                              from network import LTE
                              lte = LTE()
                              lte.send_at_cmd('AT+CFUN=0')
                              

                              Christian Ehlers

                              B 1 Reply Last reply Reply Quote 0
                              • B Offline
                                bali @Xykon
                                last edited by

                                @xykon hangs right after issuing lte=LTE()

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

                                  @bali Please open a technical support request at https://pycom.io/contact as it seems your GPy is faulty.

                                  Christian Ehlers

                                  1 Reply Last reply Reply Quote 0
                                  • N Offline
                                    nathanh
                                    last edited by

                                    So I think this just rendered my entire FiPy useless....

                                    I upgraded the CAT-M firmware yesterday without issue to see if I could connect more successfully to Telstra and besides not getting reliable connections the upgrade process seemed to go ok.

                                    Today I tried to upload the NB-IOT firmware and it got stuck at 6% for over 5 minutes exactly like the description in the instructions (https://github.com/pycom/pycom-libraries/tree/master/lib/sqnsupgrade). So I power cycled as per the instructions and now I get stuck on this:

                                    <<< Welcome to the SQN3330 firmware updater >>>
                                    

                                    And nothing... I have let it run for over 10 minutes and power cycled multiple times. I also notice now I lose all UART REPL command/interface after about 1-2 minutes of powering up my FiPy and it is a race against the clock to even execute the update code. If I wait a while the REPL just freezes and won't accept any input, so essentially making the device unusable.

                                    And as per @bali now when I can get in quick enough and try and call lte = LTE() my device hangs. So it looks like my device that was working is no longer functioning and I followed the instructions as directed...

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

                                      @nathanh @bali I will contact each one of you directly to help resolve your issues.

                                      Cheers,
                                      Daniel

                                      V 1 Reply Last reply Reply Quote 0
                                      • V Offline
                                        vigmeister @daniel
                                        last edited by vigmeister

                                        @daniel FWIW I seem to have run into exactly the same symptoms as @nathanh If and when a resolution is found, I would appreciate if you post it here. I would also not mind getting in on the debugging action if that would help.

                                        V 1 Reply Last reply Reply Quote 0
                                        • V Offline
                                          vigmeister @vigmeister
                                          last edited by

                                          @daniel @nathanh Additional hint from my observation. I looked at the TX buffer of the serial interface by inserting s.wait_tx_done(5000) after the s.write("ATE0\r\n") line in sqnsupgrade.py and I get "False" as the response. Will try moving downstream in the sqnsupgrade.py code later in the day and share my findings.

                                          V 1 Reply Last reply Reply Quote 0
                                          • V Offline
                                            vigmeister @vigmeister
                                            last edited by

                                            I tinkered a bit further and by setting the default timeout to 2000 instead of 20000 in sqnsupgrade.read_rsp , I was able to get my FiPy to get further along, but ran into @bali ‘s issue of AT+SMSWBOOT=3, 0 failed!

                                            Looks like the issues are roughly the same, but that @nathanh and I have unstable REPL on top :/

                                            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
                                            • 3
                                            • 1 / 3
                                            • First post
                                              Last post

                                            Pycom on Twitter

                                            Pycom