Long-Term Supported Versions

    Installation Preparations

    This section describes the compatibility of the hardware and software and the related configurations and preparations required for the installation.

    Obtaining the Installation Source

    Before installation, obtain the openEuler Raspberry Pi image and its verification file.

    1. Visit openEuler Repo.
    2. Choose openEuler 22.03 LTS SP2.
    3. Click raspi_img. The download list of Raspberry Pi images is displayed.
    4. Click openEuler-22.03-LTS-SP2-raspi-aarch64.img.xz to download the openEuler Raspberry Pi image to the local PC.
    5. Click openEuler-22.03-LTS-SP2-raspi-aarch64.img.xz.sha256sum to download the verification file of the openEuler Raspberry Pi image to the local PC.

    Verifying the Image Integrity


    During package transmission, to prevent software packages from being incompletely downloaded due to network or storage device problems, you need to verify the integrity of the software packages after obtaining them. Only the software packages that pass the verification can be deployed.

    Compare the verification value recorded in the verification file with the verification value that is manually calculated to determine whether the software package is complete. If the two values are the same, the downloaded file is complete. Otherwise, the downloaded file is incomplete and you need to obtain the software package again.


    Before verifying the integrity of the image file, ensure that the following files are available:

    Image file: openEuler-22.03-LTS-SP2-raspi-aarch64.img.xz

    Verification file: openEuler-22.03-LTS-SP2-raspi-aarch64.img.xz.sha256sum


    To verify the file integrity, perform the following procedures:

    1. Obtain the verification value from the verification file. Run the following command:

      cat openEuler-22.03-LTS-SP2-raspi-aarch64.img.xz.sha256sum
    2. Calculate the SHA256 verification value of the file. Run the following command:

      sha256sum openEuler-22.03-LTS-SP2-raspi-aarch64.img.xz

      After the command is executed, the verification value is displayed.

    3. Check whether the verification values obtained from the step 1 and step 2 are consistent.

      If they are consistent, the downloaded file is not damaged. Otherwise, the downloaded file is incomplete and you need to obtain the file again.

    Installation Requirements

    If the openEuler OS is installed in the Raspberry Pi environment, the Raspberry Pi environment must meet the following requirements.

    Hardware Compatibility

    Currently, the openEuler Raspberry Pi image supports the 3B, 3B+, 4B, and 400 versions.

    Minimum Hardware Specifications

    Table 1 lists the minimum hardware specifications for the openEuler Raspberry Pi image.

    Table 1 Minimum hardware specifications

    Component Name

    Minimum Hardware Specifications


    Raspberry Pi version

    • Raspberry Pi 3B
    • Raspberry Pi 3B+
    • Raspberry Pi 4B
    • Raspberry Pi 400



    ≥ 2 GB (4 GB or higher recommended for better user experience)



    8 GB or higher recommended for better user experience


    Bug Catching

    Buggy Content

    Bug Description

    Submit As Issue

    It's a little complicated....

    I'd like to ask someone.


    Just a small problem.

    I can fix it online!

    Bug Type
    Specifications and Common Mistakes

    ● Misspellings or punctuation mistakes;

    ● Incorrect links, empty cells, or wrong formats;

    ● Chinese characters in English context;

    ● Minor inconsistencies between the UI and descriptions;

    ● Low writing fluency that does not affect understanding;

    ● Incorrect version numbers, including software package names and version numbers on the UI.


    ● Incorrect or missing key steps;

    ● Missing prerequisites or precautions;

    ● Ambiguous figures, tables, or texts;

    ● Unclear logic, such as missing classifications, items, and steps.


    ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

    ● Incorrect schematic or architecture diagrams;

    ● Incorrect commands or command parameters;

    ● Incorrect code;

    ● Commands inconsistent with the functions;

    ● Wrong screenshots.

    Risk Warnings

    ● Lack of risk warnings for operations that may damage the system or important data.

    Content Compliance

    ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

    ● Copyright infringement.

    How satisfied are you with this document

    Not satisfied at all
    Very satisfied
    Click to create an issue. An issue template will be automatically generated based on your feedback.
    Bug Catching
    编组 3备份