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

    Pytrack V1.0 upgrade?

    Scheduled Pinned Locked Moved Expansion Board
    pytrackfirmwarupgrade
    5 Posts 3 Posters 470 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.
    • N Offline
      Nicholas
      last edited by

      Hello. Here is a new member in this forum. My question has to do with the pytrack firmware upgrade. Despite its recent purchase, the version is 1.0 (at least this is shown at the back of the PCB). Unless I am mistaken , all the upgrade how-to documents refer to V3. How do I upgrade this board? I need both required files and procedure, if possible. Here is a hint of the problem: On my code lines:
      ------ code snippet----------------
      from pytrack import Pytrack
      py=Pytrack()
      s=py.read_fw_version()
      ---- end of code -------------------

      I get this error:
      File "<stdin>", line 7, in <module>
      File "/flash/lib/pytrack.py", line 8, in init
      File "/flash/lib/pycoproc.py", line 108, in init
      ValueError: Firmware out of date

      Thanks in advance

      J 1 Reply Last reply Reply Quote 0
      • J Offline
        jcaron @Nicholas
        last edited by

        @nicholas I believe references to V3 are for the expansion board, not the Pytrack. The procedure should be similar for both, though.

        N 1 Reply Last reply Reply Quote 0
        • N Offline
          Nicholas @jcaron
          last edited by

          @jcaron Thank you. This is what I suspected, I wanted to make sure, though, as I did not want to brick my board! I will give it a try. BTW, I have a Lopy4 already connected to it. Do I need to remove it for the upgrade, or it does not matter? Thanks, again

          P 1 Reply Last reply Reply Quote 0
          • P Offline
            Paul Thornton @Nicholas
            last edited by

            @nicholas Remove it. :)

            N 1 Reply Last reply Reply Quote 0
            • N Offline
              Nicholas @Paul Thornton
              last edited by

              @paul-thornton Thanks to both, the upgrade went flawless, and it seems to be much easier doing it from within linux. It gave me a scare though, in that not only I could not make my (VC) pymakr to connect to it, but it crashed the computer a few times. That, until I deleted the directory .vscode from the working folder. Next I have to look into the Lopy4 upgrade (current code 1.18.2 r1)

              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