REX-RED Community Android 4.3

Size: px

Start display at page:

Download "REX-RED Community Android 4.3"

Norma Moody
5 years ago
Views:

1 REX-RED Community Android 4.3 Build Guide REXNOS CO.,Ltd

2 Document Information Version 1.1 File Name REX5260 Android 4.3 Build Guide.doc Date May 20, 2014 Status Working Revision History Date Version Update Descriptions Editor JUNE 5, 2014 V1.0 First Edition Chapman Yoo JUNE 18, 2014 V1.1 Download Source from Git Server Chapman Yoo Copyright 2

3 Table of Contents 1. Introduction System Requirements Required build package Required build environment Release S/W Sources Toolchain Installation Toolchain install step Toolchain Path in Build Shell Set-up Android Development Environment Install Android JDK Set up USB Configuration add Android Tools Path Update USB Driver Download Sources from Git Server Pre-Condition Download U-boot Source Download JB Kernel Source Download Android Jelly Bean Platform Source Build Images at Jelly Bean Build U-boot image Build JB Kernel image Build Android Jelly Bean Platform image Update Sources from git server Update U-Boot Source Update Kernel Source Update Android Platform Source Flash Process Copyright 3

4 6.1 REX-RED Community Board Compositions Pre-Condition for Download Process SD Fusing Process fastboot mode on REX-RED Board Flashing the kernel and Android platform images Flash only Kernel image Flash only ramdisk image Flash only system image ADB Usage Example Audio.so file update on Target Board Copyright 4

5 1. Introduction This document has intended to provide detailed instruction for the installation of Android 4.3 on the Samsung Exynos5260 Application Processor based development REX5260 board. REX5260 Board supports Android JB 4.3.x and SD/MMC as the booting device. This document covers installing, building, and flashing the images of the bootloader, kernel, and Android platform to those flash memory devices. Chapter 2 describes how to set up an Android platform development environment. Chapter 3 describes how to download the bootloader, kernel, and Android platform from rexnos git server. Chapter 4 describes how to build the bootloader, kernel, and Android 4.3 platform. Chapter 5 describes how to update sources from git server Chapter 6 describes how to flash the images into REX-RED target board. Chapter 7 describes how to use adb and show example for audio file update on REX-RED Community target board. Copyright 5

6 2. System Requirements 2.1 Required build package Required build environment Development OS Ubuntu Bit x86 or Newer Version (Notice: For Android Jelly Bean(4.3.x), a 64-bit environment is required) Refer to Compiler u-boot: arm-eabi kernel: arm-eabi-4.6 Android: arm-eabi-4.6 Booting Device emmc 5.0 / SD Card Release S/W Sources (refer U-boot u-boot (gcc 4.4.3) Kernel linux (gcc 4.6) Android Platform rex5260_android-4.3 (gcc 4.6) Copyright 6

7 2.1.3 Toolchain Installation The cross-compile toolchain is required to build the kernel and platform of Android. The toolchain for Android 4.3 is provided in the Android platform source. That toolchain is in the directory of the Android platform source and can be found in the sub-directory prebuilt/gcc/linux-x86/arm/arm-eabi-4.6/ Another cross-compile toolchain, arm-eabi-4.4.3, is required to build the U-BOOT. It is recommended that you first copy to root in /opt/toolchains and set the path in as the environment variable Toolchain install step a. Go to /opt/toolchains/ directory to download toolchain arm-eabi $ cd /opt/toolchains/ b. Run the command git clone rex:rex/tools/arm/toolchain/arm-eabi git Download arm-eabi u-boot toolchain /opt/toolchain$ git clone rex:rex/tools/arm/toolchain/arm-eabi git Cloning into 'arm-eabi-4.4.3'... remote: Counting objects: 389, done. remote: Compressing objects: 100% (271/271), done. remote: Total 389 (delta 75), reused 389 (delta 75) Receiving objects: 100% (389/389), MiB MiB/s, done. Resolving deltas: 100% (75/75), done. Checking connectivity... done c. change mod toolchains $chmod 777 R /opt/toolchains/arm-eabi-4.4.3/ d. add the path of toolchain in.bashrc $ vi ~/.bashrc Copyright 7

8 export ARCH=arm export CROSS_COMPILE=/opt/toolchains/arm-eabi-4.4.3/bin/arm-eabi- e. run.bashrc by using the follow command $ source ~/.bashrc Toolchain Path in Build Shell For the reference a)u-boot build.sh b) kernel build.sh Copyright 8

Refer to the follow links to the homepage and download packages Refer to Android SDK : http://developer.android.

9 c)platform build.sh 2.2 Set-up Android Development Environment Install Android JDK The Android Developer homepage provides packages to set up an Android development environment. Refer to the follow links to the homepage and download packages Refer to Android SDK : a. Click Download the SDK b. Select bit according to your PC system type and then Download the SDK ADT Bundle for Windows Copyright 9

If you don t know exactly your PC s system type, go to Control Panel -> All control Panel Items -> System c. Unzip the downloaded bundle file For example : adt-bundle-windows-x86-20140321.

10 If you don t know exactly your PC s system type, go to Control Panel -> All control Panel Items -> System c. Unzip the downloaded bundle file For example : adt-bundle-windows-x zip d. Execute SDK Manager.exe in adt-bundle-windows-x / If unzipped the Android SDK Bundle file, you can see SDK Manager.exe as like under picture Copyright 10

11 e. Select Android SDK Tools f. Select Google USB Driver and then click Install 3 Packages Copyright 11

12 g. Select Accept License and then click Install Set up USB Configuration If install done, you can see usb_driver, xxx/sdk/extras/google/, directory. Copyright 12

13 Modify usb-driver, android_winusb.inf as shown following picture and update driver on the windows OS. Check ADB USB Hardware IDs at Device Manager Device Manager right mouse into select Properties right mouse Android xxx to select properties and go to Details select Hardware Ids at Property You can see Values (Notice: Exactly Values depend on your PC) USB\VID_18D1&PID_xxxx&REV_xxxx&MI_xx USB\VID_18D1&PID_xxxx&MI_xx Ex) USB\VID_18D1&PID_4E26&REV_0233&MI_01 USB\VID_18D1&PID_4E26&MI_01 Copyright 13

$Add the value of Hardware Ids into android_winusb.inf file according to the Value of Hardware Ids -. android_winusb.inf exist at \sdk\extras\google\usb_driver\ [Google.$

14 Add the value of Hardware Ids into android_winusb.inf file according to the Value of Hardware Ids -. android_winusb.inf exist at \sdk\extras\google\usb_driver\ [Google.NTx86] ; Samsung SMDK %SingleBootLoaderInterface% = USB_Install, USB\VID_xxxx&PID_xxxx Ex)%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E26& MI_01 %CompositeAdbInterface% = USB_Install, USB\VID_xxxx&PID_xxxx&xxxx Ex)%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E26&REV_0233&MI_01 [Google.NTamd64] ; Samsung SMDK %SingleBootLoaderInterface% = USB_Install, USB\VID_xxxx&PID_xxxx Copyright 14

$Ex)%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E26& MI_01 %CompositeAdbInterface% = USB_Install, USB\VID_xxxx&PID_xxxx&xxxx Ex)%CompositeAdbInterface% = USB_Install,$

15 Ex)%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E26& MI_01 %CompositeAdbInterface% = USB_Install, USB\VID_xxxx&PID_xxxx&xxxx Ex)%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E26&REV_0233&MI_ add Android Tools Path Add Fastboot path at Environment Variables Go to Control Panel System Properties Advanced and then Select Environment Variables Copyright 15

$D:\Android_SDK\sdk\platform-tools add platform-tools like this ;D:\Android_SDK\sdk\platform-tools Refer to following picture Copyright http://www.$

16 Double Click Path to modify android tools path Add the platform-tools path Example: If downloaded android sdk and installed successfully at D:\Android_SDK\sdk\platform-tools add platform-tools like this ;D:\Android_SDK\sdk\platform-tools Refer to following picture Copyright 16

17 Select OK in Environment Variables Select OK in Advanced Copyright 17

18 Copyright 18

19 2.2.4 Update USB Driver Connect USB Cable with REX5260 Target Board and Power Cable Plug-In and then Press Power Button for a while Copyright 19

20 Go to Device Manager in your PC You can see Fully Android on REX5260 in Other devices Right mouse on Fully Android on REX5260 and select Properties Refer to following picture Copyright 20

21 Select Update Driver in Full Android on REX5260 Properties Refer to following picture Copyright 21

22 Select Browse my computer for drier software Copyright 22

23 Browse usb_driver in your PC and Select Include subfolders And then Click Next Refer to following picture Select Install this driver software anyway Copyright 23

Android Composite ADB Interface or Android ADB

24 If Successfully Updated USB Driver, you can see following picture And REX5260 Board may recognize Android Composite ADB Interface or Android ADB Interface in Android Device Copyright 24

25 Copyright 25

26 3. Download Sources from Git Server 3.1 Pre-Condition Make the directory of download all source files, rex5260. Make rex5260 Directory $ mkdir rex5260 $ cd rex5260 rex5260$ Go to And download setup_git_rex.sh files at rex5260 Directory Copyright 26

27 Run setup_git_rex.sh file to get permission key Run setup_git_rex.sh rex5260$ ls setup_git_rex.sh rex5260$./setup_git_rex.sh - Simplified Your Life With an SSH Config File - Added Pre-shared RSA Key! All Done. rex5260$ Download following required source files in the rex5260 directory Caution: U-BOOT, KERENL, and Android PLAFORM should be installed in the same parent directory. Required source files: Notice : Kernel & Android Platform have both version, Jelly Bean and KitKat U-boot : u-boot Kernel : linux Android Platform : rex5260_android-4.3 Copyright 27

28 All commands in this chapter are entered on the shell prompt after the Ubuntu prompt. 3.2 Download U-boot Source Run following command to get U-BOOT source code git clone rex:rex/red/u-boot.git if you done, you can find u-boot/ directory download the U-BOOT source code from git server rex5260$ git clone rex:rex/red/u-boot.git Cloning into 'u-boot'... remote: Counting objects: 7969, done. remote: Compressing objects: 100% (5525/5525), done. remote: Total 7969 (delta 2302), reused 7969 (delta 2302) Receiving objects: 100% (7969/7969), MiB MiB/s, done. Resolving deltas: 100% (2302/2302), done. Checking connectivity... done rex5260$ 3.3 Download JB Kernel Source Run following command to get Kernel source code git clone rex:rex/red/kernel/linux git if you done, you can find linux / directory download the kernel source code from git server rex5260$ git clone rex:rex/red/kernel/linux git Cloning into 'linux '... remote: Counting objects: 42199, done. remote: Compressing objects: 100% (38414/38414), done. remote: Total (delta 3453), reused (delta 3340) Receiving objects: 100% (42199/42199), MiB MiB/s, done. Resolving deltas: 100% (3453/3453), done. Copyright 28

29 Checking connectivity... done Checking out files: 100% (40004/40004), done. rex5260$ 3.4 Download Android Jelly Bean Platform Source Run the following command to install curl sudo apt-get install curl Install curl rex5260$ sudo apt-get install curl Run the following commands to download repo tool and setup permission curl > ~/bin/repo chmod +x ~/bin/repo Download repo tool and setup permission rex5260$ curl > ~/bin/repo % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed :--:-- --:--:-- --:--: rex5260$ chmod +x ~/bin/repo rex5260$ Run following command to get Android Platform source code ~/bin/repo init -u git@rexred.org:rex/red/rex5260_android-4.3/manifest.git ~/bin/repo sync download the Android Platform source code from git server rex5260$ ~/bin/repo init -u git@rexred.org:rex/red/rex5260_android-4.3/manifest.git rex5260$ ~/bin/repo sync Copyright 29

4. Build Images at Jelly Bean Note : Jelly Bean Kernel Source and Android have to have same parent directory Jelly Bean Platform Source should Like this $ cd rex5260 / rex5260$ ls u-boot linux-3.4.39 rex5260_android-4.

sh Build U-BOOT source code $ cd rex5260/u-boot rex5260/u-boot $./build.sh Check that u-boot.bin has been created in u-boot directory. If u-boot should be built successfully Check that xyref5260-spl.

30 4. Build Images at Jelly Bean Note : Jelly Bean Kernel Source and Android have to have same parent directory Jelly Bean Platform Source should Like this $ cd rex5260 / rex5260$ ls u-boot linux rex5260_android Build U-boot image Go to the directory where U-boot source code is downloaded : rex5260/u-boot. Build the u-boot image, u-boot.bin, using execute the shell script build.sh Build U-BOOT source code $ cd rex5260/u-boot rex5260/u-boot $./build.sh Check that u-boot.bin has been created in u-boot directory. If u-boot should be built successfully Check that xyref5260-spl.bin has been created in u-boot/spl directory. If u-boot should be built successfully Note : The cross compiler toolchain for the u-boot is arm-eabi it is different from the cross compiler used to build the Android kernel and platform. Copyright 30

31 Refer to u-boot cross compiler at u-boot /build.sh u-boot /build.sh CROSS_COMPILE_PATH="/opt/toolchains/arm-eabi-4.4.3/bin/arm-eabi-" 4.2 Build JB Kernel image Go to the directory where kernel source code is downloaded: linux / Run make distclean command $ cd linux / linux $ make distclean Run make rex5260_defconfig command $ cd linux / linux $ make rex5260_defconfig # # configuration written to.config # if you don t have modification about kernel configuration, it s step can be skipped. If not, Run menuconfig to set the kernel configuration, $ cd linux / linux $ make menuconfig Copyright 31

32 Select Load an Alternate Configuration File Copyright 32

Loading kernel configuration arch/arm/configs/rex5260_defconfig Save as.config file in linux-3.4.

33 Loading kernel configuration arch/arm/configs/rex5260_defconfig Save as.config file in linux directory after setting kernel configuration Build the kernel image, zimage, using execute the shell script build.sh as shown like this Build Kernel source code $ cd linux linux $./build.sh Copyright 33

Refer to kernel cross compiler at linux-3.4.39/build.sh linux-3.4.39/build.sh KERNEL_CROSS_COMPILE_PATH="/opt/toolchains/arm-eabi-4.6/bin/arm-eabi-" Check that linux-3.4.39/arch/arm/boot/zimage has been created under the kernel directory 4.

34 Refer to kernel cross compiler at linux /build.sh linux /build.sh KERNEL_CROSS_COMPILE_PATH="/opt/toolchains/arm-eabi-4.6/bin/arm-eabi-" Check that linux /arch/arm/boot/zimage has been created under the kernel directory 4.3 Build Android Jelly Bean Platform image Android 4.3 platform creates two images, the ramdisk image, and the system image Building step : Go to the directory where Android platform source is downloaded: rex5260_android-4.3/ Build the required images for the Android platform using the shell script build.sh Build Android Platform source code $ cd rex5260_android-4.3 rex5260_android-4.3$./build.sh rex5260 platform Copyright 34

35 Check that system.img and ramdisk.img have been created in the rex5260_android-4.3/out/target/product/rex5260/ directory Note : To make system.img successfully, the kernel image should be built before building Android platform Refer to Android Platform cross compiler at rex5260_android-4.3/build.sh rex5260_android-4.3/build.sh ROOT_DIR=$(pwd) OUT_DIR="$ROOT_DIR/out/target/product/$PRODUCT_BOARD" OUT_HOSTBIN_DIR="$ROOT_DIR/vendor/samsung_slsi/script" KERNEL_CROSS_COMPILE_PATH="$ROOT_DIR/prebuilts/gcc/linux-x86/arm/armeabi-4.6/bin/arm-eabi-" Copyright 35

36 5. Update Sources from git server After run git pull command in shell, if you find under comments at u-boot, linux and rex5260_android-4.3 rex_5260/xxxxxx$ git pull You are not currently on a branch. Please specify which branch you want to merge with. See git-pull(1) for details. git pull <remote> <branch> rex_5260/xxxxxx$ Run git checkout master and then try git pull one more time rex_5260/xxxxxx$ git checkout master rex_5260/xxxxxx$ git pull Please refer to for using useful git command. -. git branch -. git log -. git show 5.1 Update U-Boot Source Go to rex_5260/u-boot Run git pull command If source already up-to-date, shows Already up-to-date. rex_5260$ cd u-boot rex_5260/u-boot$ git pull Already up-to-date. rex_5260/u-boot$ Copyright 36

5.2 Update Kernel Source Go to rex_5260/linux-3.4.39 Run git pull command a) There is update source rex_5260$ cd linux-3.4.39 rex_5260/linux-3.4.39$ git pull remote: Counting objects: 21, done.

37 5.2 Update Kernel Source Go to rex_5260/linux Run git pull command a) There is update source rex_5260$ cd linux rex_5260/linux $ git pull remote: Counting objects: 21, done. remote: Compressing objects: 100% (11/11), done. remote: Total 11 (delta 10), reused 0 (delta 0) Unpacking objects: 100% (11/11), done. From git.rexred.org:rex/red/kernel/linux cc a70a04 master -> origin/master Updating 3cc a70a04 Fast-forward arch/arm/mach-exynos/setup-disp-clock.c 2 +- drivers/video/backlight/tc358764_mipi_lcd.c drivers/video/s5p_mipi_dsi.c files changed, 8 insertions(+), 23 deletions(-) rex_5260/linux $ b) If source already up-to-date, shows Already up-to-date. rex_5260/linux $ rex_5260/linux $ git pull Already up-to-date. rex_5260/linux $ 5.3 Update Android Platform Source Go to rex_5260/rex5260_android-4.3 Run git pull command Copyright 37

38 rex_5260$ cd rex5260_android-4.3 rex_5260/rex5260_android-4.3$ git pull Already up-to-date. rex_5260/rex5260_android-4.3$ Copyright 38

39 6. Flash Process 6.1 REX-RED Community Board Compositions Front Compositions Rear Compositions Copyright 39

40 6.2 Pre-Condition for Download Process Connection Guide to download images Copyright 40

41 Copy SD Fusing all Images into Micro SD Card SD Fusing images : -. E5260_nbl1_for_Espresso_board_ bin -. sd_fusing.sh -. sd_fusing command.txt -. tzsw.bin -. u-boot.bin -. xyref5260-spl.bin Connect USB to Serial Port to get debug message between PC and REX-RED Board The condition of serial communication: Port: COM# ( the number depends on Device Manager, Ports(COM & LPT)) Serial Baud Rate: , Data: 8bit, Parity: None Stop: 1bit, Flow Control: None Copyright 41

board, you can check the messages on the serial terminal window.

42 6.3 SD Fusing Process Power Cable Extract Insert SD Card Set SD Booting Mode SD Booting Mode While booting up the REX5260 target board, you can check the messages on the serial terminal window. Power Cable Plug-In Press Power Button for a while Copyright 42

43 Enter the command shell environment by hitting any key in 3 seconds. When the message, Hit any key to stop autoboot: # is printed on the serial terminal window Please refer to under picture As shown under picture, you can see SDMMC Booting In Checking Boot Mode: SDMMC U-boot command shell for SDMMC Type the following command to erase all images and data in the boot and user Copyright 43

44 partitions XYREF5260 # emmc partion XYREF5260 # mmc erase boot XYREF5260 # mmc erase user Copyright 44

45 [Caution: When you execute this command, all data in the boot partition and the user partition are erased.] XYREF5260 # fdisk -c Type the below command to download the bootloader on the EMMC from SD Card XYREF5260 # emmc open 1 XYREF5260 # movi read fwbl XYREF5260 # movi write zero fwbl XYREF5260 # movi read bl XYREF5260 # movi write zero bl XYREF5260 # movi read u-boot XYREF5260 # movi write zero u-boot XYREF5260 # movi read tzsw XYREF5260 # movi write zero tzsw XYREF5260 # emmc close 1 Copyright 45

46 Power Cable Extract Extract SD Card Change Booting Mode into emmc Booting Mode emmc Booting Mode Copyright 46

47 Power Cable Plug-In Press Power Button for a while Enter the command shell environment by hitting any key in 3 seconds. When the message, Hit any key to stop autoboot : # is printed on the serial terminal window When you can see Checking Boot Mode.EMMC during boot up, it means that emmc written successfully. [Notice: If not, try to write emmc one more by means of SD Booting Mode fully] Copyright 47

48 Type the below commands on bootloader for partition format XYREF5260 # fatformat mmc 0:1 Copyright 48

49 XYREF5260 # ext3format mmc 0:2 XYREF5260 # ext3format mmc 0:3 XYREF5260 # ext3format mmc 0:4 Copyright 49

50 6.4 fastboot mode on REX-RED Board Enter into the fastboot mode to download images Notice: fastboot mode should execute on emmc boot mode Power Cable Extract Power Cable Plug-In Press Power Button for a while (or press Reset Button which exist last right side of Power Button) Enter the command shell environment by hitting any key in 3 seconds. When the message, Hit any key to stop autoboot : # is printed on the serial terminal window Type fastboot command to download images and enter into fastboot mode XYREF5260 # fastboot Copyright 50

51 6.5 Flashing the kernel and Android platform images Enter into fastboot mode cmd to use DOS Prompt Shell Copyright 51

Copy all images into directory where fastboot file exist (we already added Android Tools Path in 2.2.3 clause, so fastboot command works anywhere) E5260_nbl1_for_Espresso_board_140124.

52 Copy all images into directory where fastboot file exist (we already added Android Tools Path in clause, so fastboot command works anywhere) E5260_nbl1_for_Espresso_board_ bin, xyref5260-spl.bin, tzsw.bin images are distributed separately via Samsung S.LSI.CSE Team and There are in site which provided by REXNOS -.U-BOOT images : u-boot.bin, xyref5260-spl.bin -.Android Kernel image : zimage -.Android Platform images : ramdisk.img, system.img Copyright 52

53 Go to directory which have images for download Example C: > cd d: Android rexnos sd_fusing> Flash kernel image d: Android rexnos sd_fusing> fastboot flash kernel zimage Flash ramdisk image d: Android rexnos sd_fusing> fastboot flash ramdisk ramdisk.img Flash system image d: Android rexnos sd_fusing> fastboot flash system system.img Copyright 53

54 6.6 Flash only Kernel image Check whether the boot mode is emmc or not. If not, you have to select emmc boot mode emmc Booting Mode Power Cable Extract Power Cable Plug-In Press Power Button for a while (or press Reset Button which exist last right side of Power Button) Enter the command shell environment by hitting any key in 3 seconds. When the message, Hit any key to stop autoboot : # is printed on the serial terminal window Type fastboot command to download images and enter into fastboot mode XYREF5260 # fastboot Copyright 54

55 cmd to use DOS Prompt Shell Copyright 55

56 Type under command in Dos shell d: Android rexnos sd_fusing> fastboot flash kernel zimage 6.7 Flash only ramdisk image Check whether the boot mode is emmc or not. If not, you have to select emmc boot mode emmc Booting Mode Power Cable Extract Power Cable Plug-In Press Power Button for a while (or press Reset Button which exist right side of Power Button) Enter the command shell environment by hitting any key in 3 seconds. When the Copyright 56

57 message, Hit any key to stop autoboot : # is printed on the serial terminal window Type fastboot command to download images and enter into fastboot mode XYREF5260 # fastboot cmd to use DOS Prompt Shell Type under command in Dos shell d: Android rexnos sd_fusing> fastboot flash ramdisk ramdisk.img Copyright 57

58 6.8 Flash only system image Check whether the boot mode is emmc or not. If not, you have to select emmc boot mode emmc Booting Mode Power Cable Extract Power Cable Plug-In Press Power Button for a while (or press Reset Button which exist last right side of Power Button) Enter the command shell environment by hitting any key in 3 seconds. When the message, Hit any key to stop autoboot : # is printed on the serial terminal window Type fastboot command to download images and enter into fastboot mode XYREF5260 # fastboot cmd to use DOS Prompt Shell Copyright 58

59 Type under command in Dos shell d: Android rexnos sd_fusing> fastboot flash system system.img Copyright 59

60 7. ADB Usage Example 7.1 Audio.so file update on Target Board cmd to use DOS Prompt Shell Go to directory platform-tools where Android SDK installed and you can see adb.exe and fastboot.exe For example: d: Android_SDK sdk platform-tools Copy audio so file which you want to apply into platform-tools directory Example: d: Android_SDK sdk platform-tools> cp out/target/product/rex5260/system/ lib/hw/audio.primary.rex5260.so. Connect USB Cable between PC and REX-RED Board Copyright 60

Type the following command to connect adb between PC and REX-RED d: Android_SDK sdk platform-tools>adb root d: Android_SDK sdk platform-tools>adb remount d: Android_SDK

61 Type the following command to connect adb between PC and REX-RED d: Android_SDK sdk platform-tools>adb root d: Android_SDK sdk platform-tools>adb remount d: Android_SDK sdk platform-tools>adb push audio.primary.rex5260.so /system/lib/audio.primary.rex5260.so d: Android_SDK sdk platform-tools>adb reboot Copyright 61

Download Method for. MV 7420 Android 5.1

Download Method for. MV 7420 Android 5.1 Download Method for MV 7420 Android 5.1 MICROVISION Co., Ltd www.microvision-kit.com Document Information Version 1.0 File Name Download Method for MV7420 Android 5.1.doc Date 2015. 09. 21 Satus Working