This shows you the differences between two versions of the page.
tutorials:ct1:installation:a20_a20-add_custom_plan_board_android_configuration [2014/10/28 11:29] parker h |
tutorials:ct1:installation:a20_a20-add_custom_plan_board_android_configuration [2014/10/28 11:35] (current) parker h |
||
---|---|---|---|
Line 62: | Line 62: | ||
==== 4.2 AndroidProducts.mk ==== | ==== 4.2 AndroidProducts.mk ==== | ||
+ | There is only a word: | ||
+ | |||
+ | PRODUCT_MAKEFILES := \ | ||
+ | $(LOCAL_DIR)/sugar_ref001.mk | ||
+ | |||
+ | "Sugar_ref001. Mk" which is what is said above files, so also want to replace their scheme of the file name. | ||
+ | |||
==== 4.3 BoardConfig.mk ==== | ==== 4.3 BoardConfig.mk ==== | ||
+ | |||
+ | This file is generally defines the Wifi and some other configuration variables. | ||
+ | In the same way, and initiative under the file name the name of the related words have to change their plans. | ||
==== 4.4 init.sun7i.rc ==== | ==== 4.4 init.sun7i.rc ==== | ||
+ | |||
+ | The script will be invoked in the android system startup, function is related to plan do the driving load and service initialization, some customers customized service, can also be loaded in the "init. Sun7i.rc" . | ||
==== 4.5 initlogo.rle ==== | ==== 4.5 initlogo.rle ==== | ||
+ | |||
+ | Custom boot log pictures, the default is 720 p pictures, pictures can use | ||
+ | "lichee/tools/tools_win/LogoGen.Zip" small tool to generate. | ||
==== 4.6 needfix.rle ==== | ==== 4.6 needfix.rle ==== | ||
+ | |||
+ | Boot file system self-check repair interface logo image, as large as initlogo, also can use "lichee/tools/tools_win/LogoGen.Zip "small tool to generate. | ||
==== 4.7 recovery.fstab ==== | ==== 4.7 recovery.fstab ==== | ||
+ | |||
+ | This file is defined in the 'recovery' stage partitions or equipment corresponds to the mount point, general default to the male version of the partition. | ||
==== 4.8 sun7i-ir.kl ==== | ==== 4.8 sun7i-ir.kl ==== | ||
+ | |||
+ | In view of the remote control button mapping value configuration. | ||
==== 4.9 vendorsetup.sh ==== | ==== 4.9 vendorsetup.sh ==== | ||
+ | |||
+ | It’s content is usually as below | ||
+ | |||
+ | add_lunch_combo sugar_ref001-eng | ||
+ | |||
+ | 'lunch' at compile time after you will see' sugar_xxx eng' this option, if it is modified to : | ||
+ | |||
+ | add_lunch_combo sugar_ref001-user | ||
+ | |||
+ | 'lunch' at compile time after you will see' sugar_xxx user' this option.The difference between the two lies in the eng version for engineering development, by default, the adb's open and open root privileges, and user version don't open the default adb and do not open the root permissions. | ||
+ | Release the firmware usually to compile the user mode, which can improve the safety of the system. | ||
==== 4.10 vold.fstab ==== | ==== 4.10 vold.fstab ==== | ||
+ | |||
+ | Here is on storage devices (such as an SD card, nandflash, usb, sata) definition.When just creating a custom solution directory can not change, when need to customize the board mounted in the storage unit to modify again. | ||
==== 4.11 package.sh ==== | ==== 4.11 package.sh ==== | ||
+ | |||
+ | The package will be invoked script, In the case of sugar - ref001 content as follows: | ||
+ | |||
+ | #!/bin/bash | ||
+ | DEBUG="uart0" | ||
+ | SIGMODE="none" | ||
+ | | ||
+ | if [ "$1" = "-d" -o "$2" = "-d" ]; then | ||
+ | echo "----------debug version, have card0 printf-----------" | ||
+ | DEBUG="card0"; | ||
+ | else | ||
+ | echo "----------realse version, have uart0 printf-----------" | ||
+ | fi | ||
+ | | ||
+ | cd $PACKAGE | ||
+ | ./pack -c sun7i -p android -b sugar-ref001 -d ${DEBUG} -s ${SIGMODE} | ||
+ | cd - | ||
+ | |||
+ | when transplant need to change the 'sugar - ref001' to their project name, and name and lichee/tools/pack_brandy/one/sun7i/configs/android scheme configuration directory name should be consistent, otherwise the package' pack 'complains, the script now supports three parameters, two commonly used: | ||
+ | |||
+ | pack:Package produce firmware | ||
+ | pack -d:Packaged produce serial port information from SD/TF card slot output into the firmware. | ||