Changes

Jump to: navigation, search

Android Development Environment (DACU)

1,641 bytes added, 10:28, 20 July 2012
no edit summary
# the Android/Linux kernel
# the Android root file system – this file system is mounted (that is, made available, attached) by the kernel during the boot process on the root directory (“/”).
 
 
=== Android porting on Dacu ===
 
Android relies on the Linux kernel version 2.6.x, so, like many other linux systems, booting it is straightforward once a working Linux kernel image and a pre-built root file system are available. A big help in getting these software components come from the Texas Instruments Android Development Kit for Sitara Devices, which provides, among other things, the Linux kernel version 2.6.32 source code and a Android 2.3.4 "Gingerbread" demo root file system.
 
Once the kernel is built, the system must be configured to boot from network, installing on the host machine a tftp and a nfs server. Please refer to [...] for instruction on how to setup the host environment. When the TFTP and NFS services are properly configured, copy the kernel image (arch/arm/boot/uImage) to the tftp directory (es: /tftpboot/lizard/android/uImage) and export via NFS the directory where the root file system archive TI_Android_Eclair_DevKit-V1/Filesystem/rootfs_am35x.tar.bz2) has been previously uncompressed.
 
 
=== Running Android ===
 
A few more steps are required before launching Android: from the U-Boot console, configure all the environment variables (using the setenv and saveenv commands) to allow the system to boot from network. In particular, add the following variables:
 
nfsandrargs=setenv bootargs init=/init rw root=/dev/nfs nfsroot=${serverip}:${rootpath} mem=256M noinitrd androidboot.console=ttyS2 vram=${vram}
 
vram=24M
 
net_andr_nfs=tftp ${buf} ${bootfile}; run nfsandrargs addip addcons; bootm ${buf}
 
Enter the run net_andr_nfs command. The console should report the following boot messages:
 
[...]
 
=== Useful Links ===

Navigation menu