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

    "Not enough memory available on the board"

    Scheduled Pinned Locked Moved LoPy
    memorylopy
    3 Posts 2 Posters 1.9k 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.
    • sorenS Offline
      soren
      last edited by

      Hello,

      When I run os.getfree('/flash'), it says there's 441 kb available. despite this, I suddenly get this error "An error occurred: Not enough memory available on the board. Synchronizing failed. Please reboot your device manually".
      The program I'm writing is not exceptionally huge, at all. I tried import gc and running gc.collect on boot, but that didn't help.

      I'm probably misunderstanding the issue at hand.. ?

      1 Reply Last reply Reply Quote 0
      • sorenS Offline
        soren
        last edited by

        so apparently, doing a hard-reset removes the issue for some time only for it to come back. So I would think I need to use gc.collect in my main loop as well, right?

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

          @soren I do not know which program flags this error: "An error occurred: Not enough memory available on the board. Synchronizing failed. Please reboot your device manually". May atom+Pymakr plugin. But besides that:
          There is a difference between the free memory in the flash file system, which is reported by os.getfree("/flash"), and the RAM, which is reported by gc.free_mem(). gc.collect() only affects the RAM and performs a garbage collection there.
          The error message you flag sounds more like being caused by file system problems, and maybe it's not even the free area, which is the reason, but some other file related error, which is faulty reported as "out of free space", since that is the most common reason. You could try to use simple methods like ftp and terminal emulator to upload and run your files. The visibility of what's going on is much better in case of problems
          Errors allocating RAM are reported like: "MemoryError: memory allocation failed, allocating xxxx bytes".

          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