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

    Where is FiPy firmware

    Scheduled Pinned Locked Moved Firmware
    fipy
    9 Posts 3 Posters 3.1k 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.
    • M Offline
      markopraakli
      last edited by

      Hello
      Why autoupdater not work for FiPy? I'll also tried search but still not available https://software.pycom.io/findupgrade?key=fipy.fipy with esp32

      I accidentally flashed WiPy firmware on FiPy but i'm unable to restore old firmware. How I can do that now?

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

        @markopraakli
        Sorry to hear about that. We're still working on the new upgrade tool for the FiPy and it'll be released later this week.

        @Xykon will reach out to you to get your WiFi Mac address so we can remove the incorrect board from the database.

        Once the new tool is out you'll be able to select the correct board and upgrade.

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

          @markopraakli Did you use the Pycom firmware update tool to flash the FiPy with the WiPy firmware? If so can you still access the REPL (via serial or WiFi) and run the following commands?

          import binascii,machine
          binascii.hexlify(machine.unique_id())
          

          If you can get the ID this way then please send this in an email to support@pycom.io and I will reset your device.

          If your FiPy doesn't boot then please let me know the OS you are using so I can put together the necessary command line instructions.

          Christian Ehlers

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

            @xykon Hi FiPy connects to serial but crash instantly and red led shows. Seems like update tool still "uploading" same WiPy firmware that tells me something can be restore. I'm using Linux os.

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

              @markopraakli Inside the firmware update tool folder please run python bin/updater.py -p /dev/ttyUSB0 wmac while the board is in firmware update mode. If you have a Pytrack/Pysense use ttyACM0 instead.

              It should show something like this:

              Connecting.........
              Uploading stub...
              Running stub...
              Stub running...
              Changing baud rate to 115200
              Changed.
              WMAC=240AC40C0254
              

              Please email us the last line at the bottom.

              Christian Ehlers

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

                As for the crashing that is unfortunately the expected behaviour right now. This will automatically be fixed during the first firmware flash.

                Christian Ehlers

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

                  @xykon Thats weird... right on morning I reconected my FiPy to USB with extensionboard and suddenly it works again?! How's that possible...
                  Now what I see from my side that "bricked" FiPy version is now MicroPython v1.8.6-849-g0af003a4 on 2017-11-24; WiPy with ESP32 and brand new FiPy version is MicroPython v1.8.6-834-g5677703c on 2017-11-13; FiPy with ESP32... So what happened over night :) ?
                  Anyways "bricked" FiPy MAC address is: 30aea42a4d38 (used command "machine.unique_id()")

                  Any ideas?

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

                    @markopraakli I have removed your device from the database, so once the FiPy firmware is available you can choose the correct board.

                    Christian Ehlers

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

                      @xykon Thank you!
                      But still... do you have self-healing devices :) ?

                      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