Repository navigation
axera: toolchain-only configs for AX620E and AX620U - #2852
Conversation
Cut from #2670: only the two toolchain configs, which build a cross toolchain and nothing else. aarch64 musl with 5.15 headers for AX620E, arm musleabihf with 4.19 headers for AX620U. These are the kernel versions the deployed firmware's modules carry in their vermagic. The board images, the osdrv packages and the kernel configs wait for hardware and for a majestic build.
They build no image, so ci-matrix lists them in UNBUILT_BOARDS the same way as hi3519dv500_toolchain. toolchain.yml now names them, so a dispatch publishes toolchain.axera-ax620e and toolchain.axera-ax620u.
PR Summary by QodoAdd toolchain-only builds for Axera AX620E and AX620U
AI Description
Diagram
High-Level Assessment
Files changed (4)
|
Code Review by Qodo
1. AX620E SDK gets the wrong kernel headers
|
|
On "AX620E SDK gets the wrong kernel headers": this doesn't happen. For an internal toolchain, Buildroot picks headers from the Here is the resolved config from The packaged SDK's sysroot |
Problem
Axera AX620E (aarch64, kernel 5.15) and AX620U (Cortex-A7, kernel 4.19) have no published OpenIPC toolchain. Until one exists, majestic can't be ported to either chip, and without majestic no Axera firmware image can build. Right now
majestic.ax620e.lite.master.tar.bz2andmajestic.ax620u.lite.master.tar.bz2both return 403 from S3.This is the first slice of #2670, and it is the only part that can land without hardware:
ax620e_toolchain_defconfig/ax620u_toolchain_defconfigcome from axera: AX620E and AX620U on OpenIPC's kernel, U-Boot and flash layouts #2670 unchanged, with authorship kept. They work likehi3519dv500_toolchainand build no image.ci-matrix.pylists both inUNBUILT_BOARDSas toolchain configs.toolchain.ymlnames them, so a dispatch publishestoolchain.axera-ax620e.tgzandtoolchain.axera-ax620u.tgz.Everything else in #2670 stays there: the lite defconfigs, kernel configs, osdrv packages, and the
.kofiles taken from factory firmware. Those wait for a camera and a majestic build.Hardware tested on
None, and none applies. This adds no image and changes no shipped file. The two defconfigs only run in
toolchain.yml, which produces the SDK tarball and nothing else.Evidence
Both toolchains were built locally with
make BOARD=<x>_toolchain toolchain:Each binary ran under QEMU linux-user v10.2.0 (
aarch64-linux-user/arm-linux-user, from the qemu-bench tree), with the CPU pinned to the target core. There was one static C program printingLINUX_VERSION_CODEand one C++ program usingstd::stringandstd::thread, the latter built both static and dynamic. The dynamic build ran against the SDK's own sysroot through-L:Note that
ci-matrix.pyis in the diff, so the selector builds the full matrix for this PR. That is intended.Scope
general/package/all-patches/linux/(those go to OpenIPC/linux)general/overlay/or in a sharedload_<vendor>script hardcodes a value specific to my boardLD_PRELOAD, and no binaries that cannot be rebuilt from sourcetoolchain.ymlon dispatch and not by the board matrix, the same ashi3519dv500_toolchain.