rk3399-box-model-ab - Githubissues

nevack commented 2 years ago

Hi, I use this repository to build Android 9 firmware for Rock960 by following steps from this doc.

Is it possible to adapt you manifests to build Android 10 or Android 11 for this device (rk3399-userdebug lunch combo and rk3399-rock960-model-ab.img kernel image). 96rocks made no updates for more than a year now. I just want to know if this is possible at all :)

Thanks!

jack-ma commented 2 years ago

It's possible, just do this :-)

nevack commented 2 years ago

Okay, glad to hear it.

What I have tried: 1) repo sync with rockchip-r-release.xml manifest from Android11_Radxa_rk10.1 branch. 2) copied kernel/arch/arm64/boot/dts/rockchip/rk3399-rock960-model-ab.dts from 96rocks android 9 repo to this checkout. 3) Compiled u-boot with ./make.sh rk3399. 4) Compiled kernel with

  export ARCH=arm64
  export CROSS_COMPILE=aarch64-linux-gnu-
  make rockchip_defconfig android-11.config rk3399.config
  make rk3399-rock960-model-ab.img -j$(nproc)

5) Compiled AOSP with:

 source build/envsetup.sh
 lunch rk3399_Android11-userdebug
 make -j$(nproc)

5) Got error, that indicated the kernel is too large, so changed CONFIG_IKHEADERS=y to CONFIG_IKHEADERS=m in kernel/.config and rebuilt the kernel. 6) Successfully built AOSP. 7) Prepared image with:

  ln -s RKTools/linux/Linux_Pack_Firmware/rockdev/ rockdev
  ./mkimage.sh
  cd rockdev
  ln -s Image-rk3399_Android11 Image
  ./mkupdate_rk3399.sh
  ./android-gpt.sh

8) Flashed rk3399_loader_v1.26.126.bin from u-boot and gpt.img from rockdev/Image. 9) Got device booting with "Erasing" screen, but it doesn't boot in recovery or the system.

The same issue with rockchip-q-release.xml manifest from rockchip-android-10 branch. Is there something I miss?

Ahren-Li commented 2 years ago

@nevack I think you should reference Rock PI DTS, You can't use DTS directly from android9.

radxa / manifests

rk3399-box-model-ab #11