Thanks I got the error regarding the size of boot.img during the build, not when flashing. So I assume that these limits in BoardConfig.mk are checked during the build. These settings should probably also reflect the hardware, for all of them to match, and show any errors during the build itself.
On Oct 4, 5:23 pm, SungWook Jung <[email protected]> wrote: > Open BoardConfig.mk file. Change partition size. > If you don't have below contents then insert this. > > NEED to CHANGE PARTITION_SIZE !!! > ===================================================== > > BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00500000 > BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000 > BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x06900000 > BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x05000000 > BOARD_FLASH_BLOCK_SIZE := $(BOARD_NAND_PAGE_SIZE) * 64 > > 2010/10/3 nature lover <[email protected]> > > > I tried to do a build of all required images (make -j4) with the > > kernel having been built based on android-msm-2.6.32, to be > > installed on a Nexus One, and I'm getting: > > > error: out/target/product/passion/boot.img is too large (2439168 > > > [2703360 - 270336]) > > > Anyone run into this, and/or know how to get past this error? > > > -- > > unsubscribe: > > [email protected]<android-kernel%2bunsubscr...@googlegroups.com> > > website:http://groups.google.com/group/android-kernel > > -- > ____________________________________ > > Sungwook Jung > Email: [email protected] > Home:http://rhap.eeya.net,http://www.cyworld.com/wwlww -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
