Is this Omni3576/Core3576 project alive?

  • Hello,

    Thank you for your feedback and support, and Happy New Year! Below is our response to the issues you raised:

    Regarding the Python 2 Issue
    Currently, our SDK is derived from an earlier version provided by RK, so we are temporarily using a Python 2 environment to ensure compatibility and system stability. We have planned an upgrade for our localized repo, and after thorough testing, we will gradually transition to Python 3 to meet higher system security and modernization requirements.

    Regarding the Compile Environment
    To avoid dependency and architecture compatibility issues that may arise from compiling directly on the device, we recommend compiling the SDK on an X86 platform using Ubuntu 22.04 LTS. This ensures that all required tools and dependencies are correctly configured, providing a more stable compilation experience.

    Regarding the Kernel Version and Future Updates
    Our current kernel is based on a fork provided by RK at a certain point in time, and RK does not update the kernel in real time. Each time we pull in updates, extensive testing is required to ensure system compatibility and stability, so updates are relatively infrequent. However, please rest assured that the Omni3576 board remains under active development and maintenance. In the future, we will gradually release firmware and SDK updates in accordance with security and functional requirements.

    Thank you again for your valuable feedback. Your input is crucial to our ongoing product improvements. If you have any further questions or need additional assistance, please do not hesitate to contact us.

    Wishing you smooth and successful work!
  • Hello,
    Thank you for your response.
    I'm very glad to hear that this project is still alive. Once this thing works properly (with updates), it will be unmatched.

    However, I want to add the following: When I wrote, "I took a notebook and installed a Debian-compatible OS just so I could use the SDK." I was, of course, referring to an x86 notebook. However, I installed Ubuntu 24.x.

    Just for testing, I performed a general downgrade to version 22.04 and repeated the entire build process exactly as described in the wiki.

    And although the error message is slightly different, it STILL states the exact same issue: build.sh fails to build the root filesystem because Debian 12 does not want to work with this kernel (Kernel 6.1) – at least, that's how I interpret it.

    So the bottom line remains: The method described in the wiki for using the SDK no longer works. Not even when installing the exact recommended host system for the build.

    Best regards,

    PS:
    This is the output where build.sh fails:

    Code: Select all

    Not Found io-domains in kernel/arch/arm64/boot/dts/rockchip/luckfox-omni3576.dts
    Running mk-kernel.sh - build_kernel succeeded.
    ==========================================
              Start building rootfs(debian)
    ==========================================
    
    Your live-build doesn't support bookworm
    Please replace it:
    sudo apt-get remove live-build
    git clone https://salsa.debian.org/live-team/live-build.git --depth 1 -b debian/1%20230131
    cd live-build
    rm -rf manpages/po/
    sudo make install -j8
    
    ERROR: Running /home/sfox/sdk/device/rockchip/common/scripts/mk-rootfs.sh - build_debian failed!
    ERROR: exit code 1 from line 133:
        "$RK_SCRIPTS_DIR/check-debian.sh"
    ERROR: call stack:
        mk-rootfs.sh: build_debian(133)
        mk-rootfs.sh: build_hook(291)
        mk-rootfs.sh: main(321)
    ERROR: Running /home/sfox/sdk/device/rockchip/common/build-hooks/99-all.sh - build_all failed!
    ERROR: exit code 1 from line 21:
        "$RK_SCRIPTS_DIR/mk-rootfs.sh"
    ERROR: call stack:
        99-all.sh: build_all(21)
        99-all.sh: build_hook(128)
        build-helper: try_func(63)
        build-helper: try_hook(96)
        build-helper: source(174)
        99-all.sh: main(139)
    ERROR: Running /home/sfox/sdk/device/rockchip/common/build-hooks/99-all.sh - try_func build_hook all failed!
    ERROR: exit code 1 from line 67:
        build_hook
    ERROR: call stack:
        build-helper: try_func(67)
        build-helper: try_hook(96)
        build-helper: source(174)
        99-all.sh: main(139)
        
    Last edited by SFoX on 2025-02-12 22:53, edited 1 time in total.
  • 您好,
    您需要的答案就在build.sh的输出中
    Your live-build doesn't support bookworm
    Please replace it:

    Code: Select all

    sudo apt-get remove live-build
    git clone https://salsa.debian.org/live-team/live-build.git --depth 1 -b debian/1%20230131
    cd live-build
    rm -rf manpages/po/
    sudo make install -j8
  • Eng33 wrote: 2025-02-08 8:10

    Regarding the Python 2 Issue
    Currently, our SDK is derived from an earlier version provided by RK, so we are temporarily using a Python 2 environment to ensure compatibility and system stability. We have planned an upgrade for our localized repo, and after thorough testing, we will gradually transition to Python 3 to meet higher system security and modernization requirements.

    And? Did you guys already get rid of the 6 year dead Python 2? Or is it still "in progress"?

    OrionBeta wrote: 2025-02-16 10:36

    您好,
    您需要的答案就在build.sh的输出中

    Your live-build doesn't support bookworm
    Please replace it:

    Code: Select all

    sudo apt-get remove live-build
    git clone https://salsa.debian.org/live-team/live-build.git --depth 1 -b debian/1%20230131
    cd live-build
    rm -rf manpages/po/
    sudo make install -j8

    本文由人工智能翻译,因为我不会说中文。
    谢谢,我已经找到了那条信息。
    但我的问题并不是:“这个说明写在哪里?”
    我的问题更准确地说是:为什么我必须先修复制造商提供的 SDK,才能使用它?
    我必须自己安装一个特定版本的 live-build,还必须下载并从源代码编译早已停止维护的 Python 2,然后按照官方说明把它设置为系统默认的 Python。
    这可能会破坏系统中的其他软件,因为现在的软件和系统工具通常都是为 Python 3 构建的。

    Last edited by SFoX on 2026-07-17 5:53, edited 2 times in total.