Changes

Jump to: navigation, search

Android Development Environment (DACU)

1,003 bytes added, 13:09, 20 July 2012
no edit summary
=== 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(http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Android_GingerBread_2_3_4_DevKit_2_1/index_FDS.html), which provides, among other things, the Linux kernel version 2.6.32 source code and a Android 2.3.4 "Gingerbread" demo pre-packaged root file systemsource code.
Once The porting on Dacu consisted in: * patching the TI Android kernel is built, source tree with the system must be configured to boot from network, installing on the host machine a tftp and a nfs server. Please refer to [...] Dacu/Lizard modifications* adding kernel support 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) capacitive touchscreen controller and export via NFS the directory where buttons* rebuilding the root file system archive has been previously uncompressed., adding some demo and benchmark applications
=== Running Android ===
A few more steps are required before launching ==== From internal flash ==== The Dacu system is provided with a pre-programmed Android environment. When started (please refer to [[Dacu#Quick_start | Dacu Quick Start]]), the bootloader loads the Android: kernel and mounts the default root file system retrieving these components from the U-Boot consoleflash. For further information on the boot process, configure all please refer to [http://elinux.org/Android_Booting Android Booting]. ==== From the environment variables network ==== In some cases (using in particular during the setenv and saveenv commandsdevelopment phase) it's required to allow boot the system loading different kernel images or root file systems. You can do this by setting up Dacu to boot load the kernel and root file sustem from the network, using tftp and nfs protocols. Please refer to [...] for instruction on how to install a tftp and nfs servers on the host environment. In particularWhen the TFTP and NFS services are properly configured, add copy the kernel image to the following variablestftp directory (es:/tftpboot/dacu/android/uImage) and export via NFS the directory where the root file system archive has been previously uncompressed.
nfsandrargs=setenv bootargs init=/init rw The software package provided with Dacu includes the kernel binary image and a compressed archive containing the root=/dev/nfs nfsroot=${serverip}:${rootpath} mem=256M noinitrd androidbootfile system, so you can use the default components to set up the host machine.console=ttyS2 vram=${vram}
vram=24MA few more steps are required before launching Android: from the U-Boot console, you should stop the default boot procedure and launch the following command:
<pre>Enter the run net_andr_nfs=tftp ${buf} ${bootfile}; run nfsandrargs addip addcons; bootm ${buf}command.</pre>
Enter the run net_andr_nfs command. The console should report the following boot messages:
[...]
 
For more information on booting from network, please refer to [[Booting_Linux_Kernel#Configuration_net_nfs Configuration net_nfs]]

Navigation menu