|
/***** www.9tripod.com ********************************************************************/
/***** huangdongchao *******************************************************************/
/***** 20150428 ************************************************************************/
20150428:Initial update
1.
Images information:
Bootloader:
| \
├── 2ndboot.bin ---- |
├── nsih ------ | => ubootpak.bin
├── u-boot.bin --- /
Kernel:
| \
├── ramdisk.img -- | => boot.img
└── zImage ------- /
Filesystem:
└── system.img --------------------- /
Tools:
├── s5p4418-sdmmc.sh -- For burnning ubootpak.bin to external booting SDCARD
/*******************************************************************************************/
2.
How to compile:
1)bootloader(ubootpak.bin)
./build.sh -u
2)kernel
./build.sh -k
3)system(boot.img, systme.img, userdata.img, cache.img)
./build.sh -s
4)build all once
./build.sh -a
or
./build.sh
Notice:
before compile, to run: ./build.sh -h
for some references.
/*******************************************************************************************/
3.
fastboot update function:
BOOTLOADER:
fastboot flash ubootpak ubootpak.bin
or
fastboot flash 2ndboot 2ndboot.bin
fastboot flash bootloader u-boot.bin
BOOT IMAGE:
fastboot flash boot boot.img
FILESYSTEM:
fastboot flash system system.img
USERDATA:
fastboot flash userdata userdata.img
CACHE:
fastboot flash cache cache.img
/*******************************************************************************************/
4.
SD card update function:
Case 1: when emmc(inand) is not empty
1)to be ready one SD card, create a folder "x4418-android" in sd card root directory.
2)cp the images: ubootpak.bin boot.img system.img userdata.img cache.img, to x4418-android.
3)in folder x4418-android,create file "env.txt",it is used to configure which images to be updated.
eg:
ubootpak=1
boot=1
system=1
userdata=0
cache=0
'1' means 'to be updated'
'0' means 'do not be updated'
so above information means:to update ubootpak.bin boot.img system.img, do not update userdata.img cache.img
Notice:
when env.txt is not existent, or it is empty, it will be to update ubootpak.bin boot.img system.img default.
Case 2: when emmc(inand) is empty; we need to make a booting sd card.
1)use tools gparted to partition SD card: front space reserved 128MB; other format fat32 filesystem.
2)run:sudo mkfs.vfat /dev/sdb1 (or sdc1,sde1),to format sd card to FAT32.
3)write ubootpak into sd card.
To run: sudo ./s5p4418-sdmmc.sh /dev/sdb ubootpak.bin
4)create a folder "x4418-android" in sd card root directory.
3)cp the images: ubootpak.bin boot.img system.img userdata.img cache.img, to x4418-android.
4)in folder x4418-android,create file "env.txt",it is used to configure which images to be updated.
eg:
ubootpak=1
boot=1
system=1
userdata=0
cache=0
'1' means 'to be updated'
'0' means 'do not be updated'
so above information means:to update ubootpak.bin boot.img system.img, do not update userdata.img cache.img
Notice:
when env.txt is not existent, or it is empty, it will be to update ubootpak.bin boot.img system.img default.
/*******************************************************************************************/
5.
CPU boot up order:
SD0 --> eMMC(SD2) --> USB
when sd card has been writen ubootpak.bin and be inserted into SD0, cpu boot up from SD card.
or, it will boot up from eMMC.
or, if eMMC is empty, it will boot up form USB.
|
|