**INSTRUCTIONS FOR SETTING UP THE NIGHTLY BUILDS:**

    +-----------------+-----------------+-----------------------------+-------------------+
    | Red Pitaya OS   | OS release date | Nightly Build versions      | Linux OS version  |
    +=================+=================+=============================+===================+
    | 2.00-18         | 26.7.2023       | up to NB 141                | 2.0               |
    +-----------------+-----------------+-----------------------------+-------------------+
    | 2.00-22         | 4.10.2023       | up to NB 160                | 2.01              |
    +-----------------+-----------------+-----------------------------+-------------------+
    | 2.00-23         | 5.10.2023       | up to NB 162                | 2.01              |
    +-----------------+-----------------+-----------------------------+-------------------+
    | 2.00-30         | 11.1.2024       | up to NB 215                | 2.03              |
    +-----------------+-----------------+-----------------------------+-------------------+
    | 2.04-35         | 15.3.2024       | up to NB 258                | 2.04              |
    +-----------------+-----------------+-----------------------------+-------------------+
    | 2.05-37         | 7.8.2024        | up to NB 345                | 2.05              |
    +-----------------+-----------------+-----------------------------+-------------------+
    | IN DEV          | -               | 346 and later               | 2.05 and newer    |
    +-----------------+-----------------+-----------------------------+-------------------+

1.  Download the .zip containing the wanted Nightly Build (usually the latest available version):
    https://downloads.redpitaya.com/downloads/Unify/nightly_builds/

2.  Go to the RedPitaya/downloads page and download the latest Linux OS:
    https://downloads.redpitaya.com/downloads/LinuxOS/

3.  Write the Linux OS to the SD card using the BalenaEtcher.

4.  Extract the ecosystem from the .zip directly to the SD card (if possible without first extracting it to a folder).

When unpacking the ecosystem, some files may be overwritten because the FAT file system is not case sensitive. 

Case-sensitive file systems distinguish between upper and lower case in file names, whereas case-insensitive systems do not. As a result,
files such as CONNMARK.h and connmark.h are recognised by the search system as the same file.

Select the following options (depending on the byte size of the files)

    +---------------+------------------+
    | File name     | File byte size   |
    +===============+==================+
    | Connmark      | 901              |
    +---------------+------------------+
    | Xt_dscp       | 697              |
    +---------------+------------------+
    | Xt_mark       | 184              |
    +---------------+------------------+
    | Xt_rateest    | 859              |
    +---------------+------------------+
    | Xt_tcpmss     | 235              |
    +---------------+------------------+
    | Ipt_ecn       | 901              |
    +---------------+------------------+
    | Ipt_ttl       | 375              |
    +---------------+------------------+
    | Ip6t_hl       | 408              |
    +---------------+------------------+

Please note that the file names are approximate and for reference only.

    **The general rule**
    Always choose the smaller file unless the difference in size is more than about 200 bytes.
    (For example, if you are asked to choose between file sizes of 199 bytes and 901 bytes, choose 901.
    If the choice is between 235 bytes and 253 bytes, choose 235 (the smaller size)).

This will also happen if you extract to a folder first, but you may not be informed of the change (it happens automatically).
of the change (it happens automatically).

There may be other file combinations that work, this is one that works for us.
This is a problem with the FAT filesystem, which is not case-sensitive, so files like
connmark.h and CONNMARK.h are interpreted as the same file.

If you use a different combination of files, the Red Pitaya will still boot, but it may not be able to connect to the card.

Red Pitaya Team