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

    Development release 1.20.0.rc3 and LittleFS Upload problems

    Scheduled Pinned Locked Moved Issues & Bugs
    lopyfirmware update
    4 Posts 4 Posters 642 Views 4 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.
    • T Offline
      thinginnovations
      last edited by

      I have a number of Lopy boards on Pysense and see issues uploading from Atom/Pymakr when the latest 1.20.0.rc3 has been flashed to the Lopy with the LittleFS. I see the error "Failed to write file, trying again..."
      This happens at the 3rd file.
      Reflashing and selecting FatFS and 'erase during update' has no problems uploading the code afterwards.

      As soon as I select LittleFS I have problems.

      Any ideas?

      Cheers

      Andrew

      robert-hhR C 2 Replies Last reply Reply Quote 0
      • robert-hhR Offline
        robert-hh @thinginnovations
        last edited by

        @thinginnovation I have no problem uploading a complex file/directory structure using FileZilla to a device with Littfs. So the file system itself seems fine, and problem is in the interaction between Pymakr and MP and the way, Pymakr uploads files.

        1 Reply Last reply Reply Quote 0
        • C Offline
          crumble @thinginnovations
          last edited by

          I got such problems with 1.19.*

          I solved it by uploading only main.py as a script. All other files as bytecode (*.mpy).
          The error was not predictable. I assume that it is related to memory fragmentation. A cold boot in front of the upload showed less errors. I switched anyway to upload bytecode for stable code, because the compiler fragmented the memory too much for my buffersize.

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

            Does this always fail on the same 3rd file? How large is that file? I presume its a normal .py file and not some multi MB binary or something equally strange?

            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