Title: Flashing new kernel.img and resources.img [Print This Page] Author: return0 Time: 6/25/2015 10:27 Title: Flashing new kernel.img and resources.img Hi everyone,
I am working on some modifications on the kernel device-tree (Firefly) and as the kernel re-compilation ends, the new images kernel.img and resources.img are ready to be flashed.
Using the Rockchip tools (AndroidTool v2.3 for Windows) I can successfully flash these images on the board however changes do not take effect.
Looking at the bash script mkimage.sh, developers can decide to create an OTA compatible boot image (boot.img) and same for the recovery image (recovery.img) which can also contain the kernel image itself.
In case boot.img and/or recovery.img already contain the kernel image, will flashing a stand-alone kernel.img be ignored until new boot.img/recovery.img are flashed as well?
Thank you!Author: busybee Time: 6/25/2015 12:59
If boot.img contains kernel (OTA mode), it will take precedence over kernel.img, which means kernel.img is always ignored.Author: cappybob Time: 6/25/2015 22:51
I have always been told that one will have to also tick on the parameter to reenter the new Kernel and Resource.img's. I assume that this will show where to load these .img's in the partician.
In the end, I solved the problem by compiling the full Android SDK and creating (then flashing) a boot.img without kernel - now every time I flash a modified kernel.img and resource.img the new kernel (and device tree) are correctly initialised!
Welcome Firefly Open Source Community (https://bbs.t-firefly.com/)