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

    FiPy/Pyscan problem

    Scheduled Pinned Locked Moved FiPy
    fipypyscanrfid
    5 Posts 3 Posters 795 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.
    • S Offline
      soulsurfer
      last edited by

      I have a FiPy running "Pycom MicroPython 1.19.0.b4 [v1.9.4-50f84dd] on 2018-07-13; FiPy with ESP32"

      I have just plugged it into a PyScan and I tried running the example main.py from:

      https://github.com/pycom/pycom-libraries/tree/master/pyscan

      I am told:

      Traceback (most recent call last):
        File "main.py", line 14, in <module>
      ValueError: incompatible .mpy file
      

      I now have a copy of MFRC630.mpy uploaded to both /flash & /flash/lib using Filezilla, just in case.

      What else can I try?

      robert-hhR 1 Reply Last reply Reply Quote 0
      • robert-hhR Offline
        robert-hh @soulsurfer
        last edited by

        @soulsurfer How did you create the mpy file? Which version of mpy-cross did you use? The versions created with the master and development version are different, the generated code is incompatible.

        S 1 Reply Last reply Reply Quote 1
        • S Offline
          soulsurfer @robert-hh
          last edited by soulsurfer

          Thanks @robert-hh. That explains my issue! The perils of being a micropython noob :(

          I didn't build it myself. I just grabbed it using git and FTPed it to the FiPy. The documentation is rather sparse!

          Thanks to your hint I have now located where MFRC630.py was hiding:

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

          robert-hhR 1 Reply Last reply Reply Quote 0
          • robert-hhR Offline
            robert-hh @soulsurfer
            last edited by

            @soulsurfer That's nothing to be sad about. I stumbled over that incompatibility last week, and it caused me some time to discover the reason for than unexpected behavior. The make scripts for the firmware do not force re-building of mpy-cross when a different branch is checked out.

            1 Reply Last reply Reply Quote 0
            • danD Offline
              dan
              last edited by

              Hi @soulsurfer,

              Thanks for noticing! I'll let the team know. We're using the .mpy version to save memory, so your project can take up more space.

              May I ask what are you missing from the documentation?

              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