imx515编译脚本
来源:互联网 发布:国外旅游景点推荐 知乎 编辑:程序博客网 时间:2024/06/05 14:25
#!/bin/sh
ANDROID_PATH= /opt/imx515/source/myandroid
# Build Uboot Images
cd $/opt/imx515/source/myandroid/bootable/bootloader/uboot-imx
export ARCH=arm
export CROSS_COMPILE=$/opt/imx515/source/myandroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin
#Command to build for i.MX51 BBG board is:
make distclean
make mx51_bbg_android_config
make
#"u-boot.bin" is generated if you have a successful build
#Build Kernel Image
export PATH=$/opt/imx515/source/myandroid/myandroid/bootable/bootloader/uboot-imx/tools:$PATH
cd $/opt/imx515/source/myandroid/kernel_imx
echo $ARCH && echo $CROSS_COMPILE
export CROSS_COMPILE=$/opt/imx515/source/myandroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
make imx5_android_defconfig
make uImage
#Generate uImage to be loaded by u-boot
cd $/opt/imx515/source/myandroid/kernel_imx/arch/arm/boot
$/opt/imx515/source/myandroid/bootable/bootloader/uboot-imx/tools/mkimage -A arm -O linux -T kernel -C none -a 0x90008000 -e 0x90008000 -n "Android Linux Kernel" -d ./zImage ./uImage
# During boot, when uboot try to load above "uImage", it will know to load it (without image head added by mkimage tool) into 0x90008000 or 0x70008000 (specified by "-a"), and then jump to 0x90008000 or 0x70008000 (specified by "-e") to execute it. "-C none" means no compression when generating "uImage". This is because the original zImage is already a compressed one.
#Build Android Image
cd $/opt/imx515/source/myandroid
export CROSS_COMPILE=$/opt/imx515/source/myandroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
make PRODUCT-imx51_bbg-eng 2>&1 | tee build_imx51_bbg_android.log
#For i.MX51 BBG build, the following outputs are generated as default under myandroid/out/target/product/imx51_bbg
#Above three folders can be used to create your Android file system for NFS mounting, i.e. root/ > /, system/ > /system, data/ > /data
# recovery/: root file system when booting in "recovery" mode. Not directly used.
# ramdisk.img: Ramdisk image generated from "root/". Not directly used.
# system.img: EXT4 image generated from "system/". Can be programmed to "SYSTEM" partition on SD card with "dd"
# userdata.img: EXT4 image generated from "data/".
# recovery.img: EXT4 image generated from "recovery/". Can be programmed to "RECOVERY" partition on SD card with "dd"
cd $/opt/imx515/source/myandroid/out/target/product/imx51_bbg
$/opt/imx515/source/myandroid/bootable/bootloader/uboot-imx/tools/mkimage -A arm -O linux -T ramdisk -C none -a 0x90308000 -n "Android Root Filesystem" -d ./ramdisk.img ./uramdisk.img
ANDROID_PATH= /opt/imx515/source/myandroid
# Build Uboot Images
cd $/opt/imx515/source/myandroid/bootable/bootloader/uboot-imx
export ARCH=arm
export CROSS_COMPILE=$/opt/imx515/source/myandroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin
#Command to build for i.MX51 BBG board is:
make distclean
make mx51_bbg_android_config
make
#"u-boot.bin" is generated if you have a successful build
#Build Kernel Image
export PATH=$/opt/imx515/source/myandroid/myandroid/bootable/bootloader/uboot-imx/tools:$PATH
cd $/opt/imx515/source/myandroid/kernel_imx
echo $ARCH && echo $CROSS_COMPILE
export CROSS_COMPILE=$/opt/imx515/source/myandroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
make imx5_android_defconfig
make uImage
#Generate uImage to be loaded by u-boot
cd $/opt/imx515/source/myandroid/kernel_imx/arch/arm/boot
$/opt/imx515/source/myandroid/bootable/bootloader/uboot-imx/tools/mkimage -A arm -O linux -T kernel -C none -a 0x90008000 -e 0x90008000 -n "Android Linux Kernel" -d ./zImage ./uImage
# During boot, when uboot try to load above "uImage", it will know to load it (without image head added by mkimage tool) into 0x90008000 or 0x70008000 (specified by "-a"), and then jump to 0x90008000 or 0x70008000 (specified by "-e") to execute it. "-C none" means no compression when generating "uImage". This is because the original zImage is already a compressed one.
#Build Android Image
cd $/opt/imx515/source/myandroid
export CROSS_COMPILE=$/opt/imx515/source/myandroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
make PRODUCT-imx51_bbg-eng 2>&1 | tee build_imx51_bbg_android.log
#For i.MX51 BBG build, the following outputs are generated as default under myandroid/out/target/product/imx51_bbg
#Above three folders can be used to create your Android file system for NFS mounting, i.e. root/ > /, system/ > /system, data/ > /data
# recovery/: root file system when booting in "recovery" mode. Not directly used.
# ramdisk.img: Ramdisk image generated from "root/". Not directly used.
# system.img: EXT4 image generated from "system/". Can be programmed to "SYSTEM" partition on SD card with "dd"
# userdata.img: EXT4 image generated from "data/".
# recovery.img: EXT4 image generated from "recovery/". Can be programmed to "RECOVERY" partition on SD card with "dd"
cd $/opt/imx515/source/myandroid/out/target/product/imx51_bbg
$/opt/imx515/source/myandroid/bootable/bootloader/uboot-imx/tools/mkimage -A arm -O linux -T ramdisk -C none -a 0x90308000 -n "Android Root Filesystem" -d ./ramdisk.img ./uramdisk.img
- imx515编译脚本
- imx515 开发板Android源代码编译过程
- imx515 开发板Android源代码编译过程
- imx515 开发板Android源代码编译过程
- imx515 开发板Android源代码编译过程
- imx515 uboot 改变控制台
- 编译脚本
- 编译脚本
- IMX515中的TF卡分区
- ant 脚本编译
- FORM的编译脚本
- automake编译脚本
- ant编译脚本
- 自动编译脚本
- 编译MTK6516脚本
- 学习Ant编译脚本
- UDK 脚本编译运行
- shc脚本编译工具
- Android GSM驱动模块详细分析(二)request流程
- sybase函数用法之DateAdd
- UIActivityIndicatorView的两种形式
- Linux 用户(user)和用户组(group)管理概述
- html5 JS跨域通信
- imx515编译脚本
- JAVA的StringBuffer类
- firefox不支持web font字体文件的跨域加载
- 各种操作系统下清空dns缓存方法
- 简单说说正则中(.*),(.+?)的区别
- sybase 移植参考
- 成员变量和局部变量有什么区别?
- 程序员技术练级攻略 --陈皓
- IE 下使用firebug