Hi,

I just tried to update the board and now I get the followin error:
Error updating the board, please try a different zip archive

And the patches won't run throwing this error when trying to compile:
fatal error:
error in backend: IO failure on output stream.
make: *** [build/core/WriteFile.o] Error 1

which a quick search points to be caused by a full disk.

Any hints on how to solve this?

can you do df -h on the console? That should tell you how much space is available on the disk.

This is the output

Filesystem Size Used Avail Use% Mounted on
rootfs 3.5G 3.5G 0 100% /
udev 10M 0 10M 0% /dev
tmpfs 50M 192K 50M 1% /run
/dev/mmcblk0p2 3.5G 3.5G 0 100% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 100M 0 100M 0% /run/shm
/dev/mmcblk0p1 70M 18M 52M 26% /boot/uboot
tmpfs 100M 0 100M 0% /tmp

    loopier rootfs 3.5G 3.5G 0 100% /

    well that means that your file system is full. I see you are using WriteFile. Perhaps that generated some large files that filled up your drive?
    If you do

    du -sh /root/Bela/projects/*

    that you should tell you the size of each project and you can easily tell where the problem lays.

      loopier easyer to read:

      you could use ``` instead:
      ```

      Filesystem Size Used Avail Use% Mounted on
      rootfs 3.5G 3.5G 0 100% /
      udev 10M 0 10M 0% /dev
      tmpfs 50M 192K 50M 1% /run
      /dev/mmcblk0p2 3.5G 3.5G 0 100% /
      tmpfs 5.0M 0 5.0M 0% /run/lock
      tmpfs 100M 0 100M 0% /run/shm
      /dev/mmcblk0p1 70M 18M 52M 26% /boot/uboot
      tmpfs 100M 0 100M 0% /tmp
      ```

      would be displayed as

      
Filesystem      Size  Used Avail Use% Mounted on
rootfs          3.5G  3.5G     0 100% /
udev             10M     0   10M   0% /dev
tmpfs            50M  192K   50M   1% /run
/dev/mmcblk0p2  3.5G  3.5G     0 100% /
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           100M     0  100M   0% /run/shm
/dev/mmcblk0p1   70M   18M   52M  26% /boot/uboot
tmpfs           100M     0  100M   0% /tmp

        Thanks, that was it.

        The zip is still not working, though

        can you please confirm what image you have? do cat /etc/motd and it should say it.

        Bela release image, v0.1.1, 24 October 2016

        ok I tried myself. Despite the error message, the update went through ok.
        Check by doing

        cat /root/update.log

        that should say

        Re-perform the check, just in case ...
Copying /root/Bela to /tmp/belaPatch ...
Applying patch in /tmp/belaPatch...
Restoring directory structure...
Kill the IDE
Stopping currently running IDE...done
Hope we are still alive here
Restart the IDE
Stopping currently running IDE...done
Starting IDE...done
Update succesful

        oh, ok!

        but... if it went through ok, shouldn't the version be a newer one?

        What you do with the update procedure is to update the Bela code, which means the code contained in the Bela repo: github.com/BelaPlatform/Bela/ . This comprises the IDE, the core code and libpd.
        However, the version of the image that you get with cat /etc/motd reflects the operating system and the packages installed, independently from what Bela code is on it. In order to upgrade image you have to re-flash your SD card. This is a slightly more involved process which also requires you to back up your projects, but it gives your board more capabilities.

        For instance, the v0.3.1 image you can find here has an entirely new operating system, boots faster, is recognized by the host computer as a MIDI device, has a more recent and efficient version of Supercollider, has a more recent kernel, which also means more drivers for hardware peripherals. We strongly advise users to upgrade to this image because of all the good things that come with it and because it marks a long-awaited modernization.

        As of now, the Bela code is designed to work on all images, as we realize it is easier to upgrade the core code than upgrading the image. However, in the future we may drop support for older images in the Bela core code.

        I hope it is clear now why the version number in /etc/motd is not updated when updating the core code. However, we understand it would be nice to have a way of check the version of the core code that is currently on the board (through the "About Bela" button in the IDE). This - unfortunately - is not easy with the tools provided by github, as you can see from this ongoing discussion, so we need to look for a better solution in the future. Right now, the best way to get a sense of what version of the core code you are running is:

        grep "BELA_.*_VERSION" /root/Bela/include/Bela.h
        2 months later

        regarding updating the image: i'm on windows 10, and downloaded the win32 disk imager as you suggest. I don't see any instructions on the developers (or yours) website though. I do realize that it shouldnt be that much of an issue - seems pretty straightforward - but being wary of bricking the beagle/bela i would love to know if i should check something in the box "Hash" and if I should check "Read only allocated Partitions", and finally if I should then just click "write" (i would assume so) 🙂

        17 days later