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

    Pycom Firmware Upgrade - Failed to connect to ESP32: Timed out

    Scheduled Pinned Locked Moved Issues & Bugs
    upgrade firmwlopy4 firmware
    3 Posts 2 Posters 154 Views 2 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.
    • A Offline
      Alephus
      last edited by

      Good evening

      Tryed to upgrade the firmware on a Lopy4 + 3.1 expansion board and it seems i was unable to no matter what i tryed.

      Details:
      -OS: Windows 10
      -Checked COM port, and the port selected is the correct one
      -Can connect to devices to upload/download code trough USB + IDE like Atom
      -Have the latest version of the upgrade tool
      -IDE is closed when tool is open

      The error occurs when the tool tries to read information about the board with the following error:

      3adb65ed-5a19-476d-bdad-fbe08c391d5b-image.png

      i do note that from the moment i try to use the tool, the expansion board led indicator named "LED" is blinquing quickly.

      When the error happens, if i imediatly close the tool and open the IDE to see the output of the device, it seems he is in a loop with this mensage:

      39703fd5-7308-49e9-9f14-506272223265-image.png

      only way to get the LoPy to come back to normal is to either unpower it or by pressing the reset button on board.

      Any sugestions?

      extra note: was able to use the tool on a complitely diferent lopy4 and board the day before, so drivers or windows bugs shoulnt be a problem

      1 Reply Last reply Reply Quote 0
      • G Offline
        Gijs
        last edited by

        Hi,
        I have not seen this issue before, but it seems the device is stuck in a boot loop as it could not find a bootloader at 0x1000. Now this can (probably) be fixed when using the command line interface: https://docs.pycom.io/advance/cli/ but Im not 100% sure

        A 1 Reply Last reply Reply Quote 1
        • A Offline
          Alephus @Gijs
          last edited by

          @Gijs will try, i dont have much experience with the cli. Any positive results i will post here. Meanwhile any others tips are welcome

          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