How to transplant android 4.4.2 to SAMA5D3X board

AT91EB40A, EB55, EB42 Evaluation Boards , AT91RM9200-DK, RM3400-DK will be the focus of the discussions: hardware guidance, embedded software, use,...

Moderator: nferre

Posts: 6
Joined: Fri Aug 12, 2016 5:17 am

How to transplant android 4.4.2 to SAMA5D3X board

Wed Jul 05, 2017 5:17 am

We use a Atmel SAMA5D3X evaluation platform MYD-SAMA5D3X to specify the way to transplant android 4.4.2 to SAMA5D3X board.

Step1: obtaining android original codes
1 $ mkdir android4sam_v4.4
2 $ cd android4sam_v4.4
3 $ repo init -u git:// -b android4sam_v4.4
4 $ repo sync

Step2: configuring android
1 $ . build/
2 $ lunch sama5d3-eng
3 $ make

Step3: generating android image
1 $ mkubi_image -b sama5d3

If things goes smoothly with you, system_ubifs-SAMA5D3-ANDROID-4.4.2_r2.img and userdata_ubifs-SAMA5D3-ANDROID-4.4.2_r2.img will be generated under current catalogue. Unfortunately, if there are any problems, please refer to the details on make_android_ubifs.log

Step4: bruning the development board
Copy the img file which was generated above into one of the burned mirror Android-image's catalogue, amend and burn the control file flash_all.tcl:


## Files to load

set bootstrapFile "boot.bin"

set ubootFile "u-boot.bin"

set kernelFile "uImage"

append dtbFile $variant_name $board_suffix ".dtb"

set rootfsFile "rootfs.ubi"

set ubootEnvFile "ubootEnv.bin"

set systemfsFile "system_ubifs-SAMA5D3-ANDROID-4.4.2_r2.img"

set datafsFile "userdata_ubifs-SAMA5D3-ANDROID-4.4.2_r2.img"

if {! [file exists $dtbFile]} {

puts "-E- === Unknown $variant_name + board $board_suffix combination ==="



## NandFlash Mapping

set bootStrapAddr 0x00000000

set ubootAddr 0x00040000

set ubootEnvAddr 0x000c0000

set dtbAddr 0x00180000

set kernelAddr 0x00200000

set systemfsAddr 0x01000000

set datafsAddr 0x0A000000



puts "-I- === Enable trimffs ==="

NANDFLASH::NandSetTrimffs 1

puts "-I- === Load the android system file system ==="

send_file {NandFlash} "$systemfsFile" $systemfsAddr 0

puts "-I- === Load the android data file system ==="

send_file {NandFlash} "$datafsFile" $datafsAddr 0

puts "-I- === DONE. ==="

Step5: firing android

Please remember to start-up android after burned and amend uboot environment variables
1 U-Boot> setenv filesys_env 'ubi.mtd=1 ubi.mtd=2 root=ubi0:system rootfstype=ubifs init=/init androidboot.hardware=sama5-ek androidboot.console=ttyS0'
2 U-Boot> setenv nand_args 'run bootargs_defaults
3 U-Boot> setenv bootargs ${bootargs} no_console_suspend mtdparts=atmel_nand:8M(bootstrap/uboot/kernel)ro,144M(system),80M(userdata) ${filesys_env}'
4 U-Boot> saveenv
5 U-Boot> boot

Return to “Evaluation and Development Boards”

Who is online

Users browsing this forum: Baidu [Spider] and 1 guest