Thus, in those devices you need a modified dts to "free" the device. The only modification we do over the original boot partition for ps5000 is the splash screen to add version information and easily identify what the user flashed in case they are not skilled enough.Īnd now the longer story: we made the decision of distributing the boot image even though we didn’t get access to the sources because the seller of powkiddy a12/a13 devices introduced a modification in the dts to reset the device if you try to boot with a different rootfs. The sources of the official firmware are not being distributed by the seller, at least not to us, so the most we can provide are the steps to get the dts from the original partition. Regarding documentation, we want to add instructions to unpack (and repack) the boot partition so anyone is able to extract the dts. Another goal is building the whole system from scratch. As above, for the time being we only build the rootfs for ps5000.Īnd now the long story: we want to move to batocera to get a cleaner and more compatible environment. arch/arm/configs/rockchip_ps5000_defconfig.
There are sources of linux that are applicable to this board: Yes/no - linux (based on rockchip-linux||caesar-github 4.4 or 4.16 or upstream) build is done. The dts for ps5000 is not modified by the cfw, should be the same provided by the seller. There is a defconfig for building the rootfs and a hierarchy of overlays for the specific consoles supported: a12/a13 and ps5000. There are sources of u-boot that are applicable to this board: Yes/no - u-boot (based on rockchip-linux||caesar-github 2017-09 or upstream) build is done.
#Rockchip batch tool prepare idb fail rk3066 plus#
The origin of the buildroot that we use comes from a blend between Caesars buildroot modifications to the main rockchip Linux buildroot, plus additional modifications based on batocera.Linux buildroot. You can find a more up to date repo of all those in the Caesar Wang repo ( ), he’s one of the main rockchip contributors. Same applies to rkscript, Linux-rga, Mali (specific rockchip flavor), etc.
Our rootfs only requires a loop module to be compiled from the kernel, and that’s a general Linux module that does not require any of the rockchip modifications. However, you are correct that to get those rockchip specific kernel modifications you need to compile the kernel you need those modified sources from rockchip Linux, same repo as you point out ( ). For the kernel link that you need to build just rootfs you don’t need the modified kernel sources with rockchip specific patches. Number Start (sector) End (sector) Size Name
$ # different verified from boot (serial console), factory build "Jul 8 10:53:" ! $ # different partition start (userdata) from "upgrade_tool"
0 kommentar(er)
