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

    NB-IoT firmware update bricks device

    Scheduled Pinned Locked Moved GPy
    nb-iot firmwaregpyfipybricked
    3 Posts 2 Posters 700 Views 3 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.
    • E Offline
      Ewoud
      last edited by

      I have a Gpy+pytrack, with updated firmware on the pytrack and Gpy, with the firmware update for CAT M1 applied. When applying the NB firmware update using SD card, it got stuck at 6%, just like described on: https://docs.pycom.io/chapter/tutorials/lte/firmware.html. Quoting from this page:
      "If the module get's stuck in here for more than 1 minute while upgrading to the NB-IoT firmware, you can cycle power and retry. In this case it is safe."

      However, after re-powering, the REPL freezes after ~20 seconds. Before that, I can upload code, change the LED, etc. Also program execution seems to halt after 20 seconds. I can press the reset button for a fresh 20 seconds of action. A freeze is caused instantly if I call: lte = LTE(). Trying to apply the firmware update before the module freezes does not progress further than: <<< Welcome to the SQN3330 firmware updater >>>

      I have had the same issue with a Fipy. I managed to do a successful NB update on a different Gpy. I have two more Gpys that I wish to update, but I am not confident at all that it will work.

      I want to salvage the bricked modules, please tell me how to flash the Sequans chip in a different way.

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

        @ewoud Please use https://pycom.io/contact/ (use the "Technical" option) to get in touch with us.

        Christian Ehlers

        E 1 Reply Last reply Reply Quote 0
        • E Offline
          Ewoud @Xykon
          last edited by

          @xykon I did that more than a week ago, but didn't get a response (PYCSD-271). I figured my chances would be better on the forum, and it turns out they are ;) . You are welcome to help me here or via the support portal, I have no preference in that respect.

          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