R58的编译步骤f1选项v1.1版本

2017/3/16 16:38

请严重注意:

编译全志R58的Android6.0.1的系统和其它系统有两个不同:

1、在执行pack打包之前,必须执行verity_data_init,否则f1选项编译的系统会打包失败!

2、在执行pack打包之前,必须编译uboot,否则系统起不来/没有显示。

3、octopus_perf-eng不是适配SC5806开发板的。

一、系统编译:

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig$ cat android_r58m_wyb_20170314split.tar.gza* > android.tar.gz

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig$ tar zxvf lichee_r58m_wyb_20170308.tar.gz

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig$ tar zxvf android.tar.gz

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig$ cd lichee/

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/lichee$ ./build.sh config

Welcome to mkscript setup progress

All available chips:

0. sun50iw1p1

1. sun8iw10p1

2. sun8iw1p1

3. sun8iw3p1

4. sun8iw5p1

5. sun8iw6p1

6. sun8iw7p1

7. sun8iw8p1

8. sun8iw9p1

9. sun9iw1p1

Choice: 5

All available platforms:

0. android

1. dragonboard

2. linux

3. camdroid

4. secureandroid

Choice: 0

All available kernel:

0. linux-3.10

1. linux-3.4

Choice: 1

All available boards:

0. eagle-p83

1. f1

2. fpga

3. perf1_v1_0

4. perf2_v1_0

5. perf3_v1_0

6. qc

Choice: 1

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/lichee$

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/lichee$ ./build.sh

if [ -z /home/wwt/r58m_orig/lichee/linux-3.4/output/lib/modules/3.4.39 ]; then \

cp -u sgx544/android/kernel_mode/eurasia_km/eurasiacon/binary2_sunxi_android_release/target/pvrsrvkm.ko /kernel_mode/linux-3.4; \

fi

make:离开目录“/home/wwt/r58m_orig/lichee/linux-3.4/modules/gpu”

regenerate rootfs cpio

11281 块

12037 块

build_ramfs

Copy boot.img to output directory ...

Copy modules to target ...

sun8iw6p1 compile Kernel successful

INFO: build kernel OK.

INFO: build rootfs ...

INFO: skip make rootfs for android

INFO: build rootfs OK.

INFO: ----------------------------------------

INFO: build lichee OK.

INFO: ----------------------------------------

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/lichee$

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/lichee$ cd ../android/

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/android$ source build/envsetup.sh

including device/asus/deb/vendorsetup.sh

including device/asus/flo/vendorsetup.sh

including device/asus/fugu/vendorsetup.sh

including device/generic/mini-emulator-arm64/vendorsetup.sh

including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh

including device/generic/mini-emulator-mips/vendorsetup.sh

including device/generic/mini-emulator-x86_64/vendorsetup.sh

including device/generic/mini-emulator-x86/vendorsetup.sh

including device/htc/flounder/vendorsetup.sh

including device/lge/hammerhead/vendorsetup.sh

including device/moto/shamu/vendorsetup.sh

including device/softwinner/astar-d7/vendorsetup.sh

including device/softwinner/astar-h7/vendorsetup.sh

including device/softwinner/common/vendorsetup.sh

including device/softwinner/octopus-f1/vendorsetup.sh

including device/softwinner/octopus-perf/vendorsetup.sh

including device/softwinner/tulip-p1/vendorsetup.sh

including device/softwinner/tulip-p2/vendorsetup.sh

including sdk/bash_completion/adb.bash

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/android$ lunch

You're building on Linux

Lunch menu... pick a combo:

1. aosp_arm-eng

2. aosp_arm64-eng

3. aosp_mips-eng

4. aosp_mips64-eng

5. aosp_x86-eng

6. aosp_x86_64-eng

7. aosp_deb-userdebug

8. aosp_flo-userdebug

9. full_fugu-userdebug

10. aosp_fugu-userdebug

11. mini_emulator_arm64-userdebug

12. m_e_arm-userdebug

13. mini_emulator_mips-userdebug

14. mini_emulator_x86_64-userdebug

15. mini_emulator_x86-userdebug

16. aosp_flounder-userdebug

17. aosp_hammerhead-userdebug

18. aosp_hammerhead_fp-userdebug

19. aosp_shamu-userdebug

20. astar_d7-eng

21. astar_d7-user

22. astar_h7-eng

23. astar_h7-user

24. octopus_f1-eng

25. octopus_f1-user

26. octopus_perf-eng

27. octopus_perf-user

28. tulip_p1-eng

29. tulip_p1-user

30. tulip_p2-eng

31. tulip_p2-user

Which would you like? [aosp_arm-eng] 24

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=6.0.1

TARGET_PRODUCT=octopus_f1

TARGET_BUILD_VARIANT=eng

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

TARGET_CPU_VARIANT=cortex-a7

TARGET_2ND_ARCH=

TARGET_2ND_ARCH_VARIANT=

TARGET_2ND_CPU_VARIANT=

HOST_ARCH=x86_64

HOST_OS=linux

HOST_OS_EXTRA=Linux-3.13.0-24-generic-x86_64-with-Ubuntu-14.04-trusty

HOST_BUILD_TYPE=release

BUILD_ID=MMB29M

OUT_DIR=out

============================================

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/android$

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/android$ extract-bsp

/home/wwt/r58m_orig/android/device/softwinner/octopus-f1/bImage copied!

/home/wwt/r58m_orig/android/device/softwinner/octopus-f1/modules copied!

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/android$ make -j12

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/android$ verity_data_init

请严重注意,这个时候打包没有显示的!^_^必须编译uboot。(这个步骤可以跳过!)

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/android$ pack

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/android$ cd ../lichee/brandy/

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/lichee/brandy$

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/lichee/brandy$ ./build.sh -p sun8iw6p1

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/lichee/brandy$ cd -

/home/wwt/r58m_orig/android

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/android$ pack

二、内核的裁剪(可选):

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/lichee$ ./build.sh config

Welcome to mkscript setup progress

All available chips:

0. sun50iw1p1

1. sun8iw10p1

2. sun8iw1p1

3. sun8iw3p1

4. sun8iw5p1

5. sun8iw6p1

6. sun8iw7p1

7. sun8iw8p1

8. sun8iw9p1

9. sun9iw1p1

Choice: 5

All available platforms:

0. android

1. dragonboard

2. linux

3. camdroid

4. secureandroid

Choice: 0

All available kernel:

0. linux-3.10

1. linux-3.4

Choice: 1

All available boards:

0. eagle-p83

1. f1

2. fpga

3. perf1_v1_0

4. perf2_v1_0

5. perf3_v1_0

6. qc

Choice: 1

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/lichee$

1、打印等级调整

rootroot@cm-System-Product-Name:/home/wwt/r58m_orig/lichee/linux-3.4$ make ARCH=arm menuconfig

General setup  --->

(16) Kernel log buffer size (16 => 64KB, 17 => 128KB)

修改为:

(18) Kernel log buffer size (16 => 64KB, 17 => 128KB)

2、关闭Realtek的WIFI/BT。只使用AP6212等。(正基的模块,博通的芯片)

Device Drivers  --->

[*] Network device support  --->

[*]   Wireless LAN  --->

<M>   Broadcom FullMAC wireless cards support

(/system/vendor/modules/fw_bcmdhd.bin) Firmware path

(/system/vendor/modules/nvram.txt) NVRAM path

(/system/vendor/modules/config.txt) Config path

Enable Chip Interface (SDIO bus interface support)  --->

Interrupt type (Out-of-Band Interrupt)  --->

<M>   Realtek 8723B SDIO or SPI WiFi

<M>   Realtek 8723BS_VQ0 WiFi

修改为:

< >   Realtek 8723B SDIO or SPI WiFi

< >   Realtek 8723BS_VQ0 WiFi

3、关闭SELinux安全选项,方便调试

Security options  --->

[*] Security hooks for pathname based access control

(32768) Low address space for LSM to protect from user allocation

[*] NSA SELinux Support

[*]   NSA SELinux boot parameter

(1)     NSA SELinux boot parameter default value

[ ]   NSA SELinux runtime disable

[*]   NSA SELinux Development Support

[*]   NSA SELinux AVC Statistics

(1)   NSA SELinux checkreqprot default value

[ ]   NSA SELinux maximum supported policy format version

修改为:

[ ] NSA SELinux Support

4、打开USB摄像头驱动/UVC

Device Drivers  --->

<*> Multimedia support  --->

[*]   Video capture adapters  --->

[*]   V4L USB devices  --->

--- V4L USB devices

< >   USB Video Class (UVC)

修改为:

<M>   USB Video Class (UVC)

[*]     UVC input events device support

R58的编译步骤f1选项v1.1版本的更多相关文章

  1. Linux-编译器gcc/g++编译步骤

    gcc和g++现在是gnu中最主要和最流行的c&c++编译器.g++是c++的命令,以.cpp为主:对于c语言后缀名一般为.c,这时候命令换做gcc即可.编译器是根据gcc还是g++来确定是按 ...

  2. GCC编译命令常用选项

    GCC是GUN Compiler Collection的简称,除编译程序外,还包含其他相关工具.GCC可将高级语言编写的源代码构建成计算机直接执行的二进制代码.GCC是Linux平台下最常用的编译程序 ...

  3. 04全志R58平台编译内核需要选择的配置

    04全志R58平台编译内核需要选择的配置 2018/11/6 14:19 版本:V1.0 开发板:SC5806 1.系统编译:(略) 每次系统编译/内核的时候都需要选3次N: * * Xtables ...

  4. 本地编译全志R系列的步骤(Ubuntu16.04.4版本)

    本地编译全志R系列的步骤(Ubuntu16.04.4版本) 2018/6/14 9:32 版本:V1.0 0.获取全志R系列的Android源码包: 请通过渠道/代理商/方案公司获取全志R系列的And ...

  5. C语言编译步骤

    C语言编译步骤:   1.预处理(hello.i ):宏定义展开.条件编译等,同是将代码中的注释删除,这里并不会检查语法 2.编译(hello.s):检查语法,将预处理后文件编译生成汇编文件. 3.汇 ...

  6. Android 源码编译 步骤

    添加资源后编译步骤 1:lunch 112:mmm frameworks/base/core/res/生成Install: out/target/product/hammerhead/system/f ...

  7. zlib库VS2015编译步骤

    [点击这里下载zlib1.2.8源码](http://zlib.net/zlib128.zip) [点击这里下载zlib1.2.8编译动态库](http://zlib.net/zlib128-dll. ...

  8. Nginx的编译安装及选项

    编译安装Nginx1.安装常见的工具和库(GCC.PCRE.zlib.OpenSSL) Nginx是一个由C语言编写的,所以需要一个编译工具如GNU的GCC[root@www ~]# yum inst ...

  9. 腾讯开源项目phxpaxos的编译步骤

    #paxos的一般编译流程在项目文档<中文详细编译手册>里面已经有介绍,这里重点介绍一下编译samples目录下的代码: #我的环境是ubuntu; #设置paxos根目录 phx_dir ...

随机推荐

  1. hduoj2094产生冠军

     产生冠军 Time Limit: 1000/1000 MS (Java/Others)    Memory Limit: 32768/32768 K (Java/Others) Total Su ...

  2. 【iOS系列】- iOS吸附效果的实现 之 UICollectionView的使用全解

    [iOS系列]- iOS吸附效果的实现 之 UICollectionView的使用全解 UICollectionView可以做很多的布局,在iOS开发中较为重要,所以这里就以实例来讲解UICollec ...

  3. BZOJ 2243: [SDOI2011]染色 树链剖分+线段树区间合并

    2243: [SDOI2011]染色 Description 给定一棵有n个节点的无根树和m个操作,操作有2类: 1.将节点a到节点b路径上所有点都染成颜色c: 2.询问节点a到节点b路径上的颜色段数 ...

  4. HDU3488 Tour —— 二分图最大权匹配 KM算法

    题目链接:https://vjudge.net/problem/HDU-3488 Tour Time Limit: 3000/1000 MS (Java/Others)    Memory Limit ...

  5. vs2013/2015中scanf函数类似于error C4996: 'scanf': This function or variable may be unsafe的安全检查错误

    在使用vs2015时,遇到了scnaf函数安全性的问题,程序不能正常运行,错误如下: error C4996: 'scanf': This function or variable may be un ...

  6. AutoIT: 返回文件目录下所有的文件名,包括子文件

    _filelist("D:\Snagit 10") Func _filelist($searchdir) ;;;函数名(形参) $search = FileFindFirstFil ...

  7. bzoj 1014 火星人prefix —— splay+hash

    题目:https://www.lydsy.com/JudgeOnline/problem.php?id=1014 用 splay 维护字符串上不同位置的哈希值还是第一次... 具体就是每个节点作为位置 ...

  8. 【137】Photoshop相关功能

    1. photoshop中怎样批处理操作 图文教程 来源:http://www.jb51.net/photoshop/57784.html 不知道大家有没有接触过PS里面的批处理呢,当我们要完成数百张 ...

  9. 表单中的readOnly 和disabled

    readonly和Disabled是用在表单中的两个属性,它们都能够做到使用户不能够更改表单域中的内容.但是它们之间有着微小的差别,总结如下: disabled也可以禁用按钮和链接: <butt ...

  10. 2-6 Opencv模块组织结构

    https://opencv.org/releases.html https://sourceforge.net/projects/opencvlibrary/files/opencv-win/3.4 ...