Panda5AJ.1.3 Release Notes

= Introduction =

This software release has been developed and verified in the following software and hardware environment.

OS Kernel: Linux® 3.4 Android:  Android JellyBean 4.1.1 Toolchain: Andriod linux-x86 toolchain arm-eabi-4.4.3 Reference hardware platforms: TI OMAP5 5432 uEVM ES1.0 (Panda5) Build Host OS: Ubuntu Daily Build OMAP5 uEVM Version: OMAP5_JB_panda5_master_ build 100  NOTE: This release is not forward compatible with OMAP5432 ES2.0 silicon


 * uEVMs built with ES1.0 Silicon are labeled UEVM5432x-00-yy-zz
 * uEVMs built with ES2.0 Silicon are labeled UEVM5432x-02-yy-zz

=Prebuilt release image= The release image can be obtained from here. After you download the binaries, follow the flashing instruction from "Flashing eMMC image" section.

=Build PC setup=

You would need a 64bit machine for building Android file system. You must have sudo permissions on the PC for installing packages


 * Install Pre-requisite packages for building the Android File System

The following commands will install the correct packages to your PC:

Ubuntu 10.04 sudo apt-get install git-core flex bison gperf libesd0-dev zip libwxgtk2.6-dev zlib1g-dev build-essential tofrodos x-dev sudo apt-get install lib32readline5-dev libstdc++6 lib32z1 lib32z1-dev ia32-libs g++-multilib libx11-dev libncurses5-dev

Ubuntu 12.04 sudo apt-get install git-core flex bison gperf libesd0-dev zip libwxgtk2.8-dev zlib1g-dev build-essential tofrodos sudo apt-get install lib32readline6-dev libstdc++6 lib32z1 lib32z1-dev ia32-libs g++-multilib libx11-dev libncurses5-dev


 * Install Java SE 6 JDK from Oracle

http://www.oracle.com/technetwork/java/javase/downloads/index.html


 * Install latest repo tool

mkdir ~/bin -p sudo apt-get install curl curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo chmod a+x ~/bin/repo export PATH=~/bin:$PATH

If you do not have sudo rights to your machine, contact your System Administrator for assistance.


 * Tool Chain for building Kernel and Drivers

The Kernel and Driver sources are built using the Android linux-x86 toolchain for ARM GNU/Linux version. This tool chain can be obtained when you pull the Android code based on the released manifest that will be given.


 * Proxy/Firewall

If you are behind proxy/firewall, workaround it using the instructions in

=Downloading Release Software=

Android Filesystem Sources
Note: You should export environment variable "https_proxy", since Android repo initialization downloads repo tree from Google server over https connection.

export https_proxy=

You can get the Android source for this release by doing: cd mkdir -p 5AJ.1.3 cd 5AJ.1.3 export YOUR_PATH=`pwd` mkdir -p mydroid; cd mydroid export MYDROID=`pwd` git config --global url."http://".insteadOf https:// repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b 5AJ.x -m RLS_5AJ.1.3.xml repo sync
 * 1) Use http instead of https in git

Kernel & Driver Sources
To clone kernel source from scratch do: cd ${YOUR_PATH} mkdir kernel git clone git://git.omapzoom.org/kernel/omap.git kernel/android-3.4 cd kernel/android-3.4 git checkout ba84518df1c32908b1188a73bf015d69e2f321e1

UsbBoot Sources
cd ${YOUR_PATH} git clone git://git.omapzoom.org/repo/omapboot.git usbboot cd usbboot git checkout 71f4037a947416a6d40b5cae28180d65512d701c

=Build Instructions=

Setting up build environment
From your work directory (5AJ.1.3 folder): export YOUR_PATH=`pwd` export MYDROID=${YOUR_PATH}/mydroid export PATH=$PATH:${MYDROID}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/ mkdir $MYDROID/logs export CROSS_COMPILE=${MYDROID}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-

Building usbboot
This is for creating the emmc boot

cd ${YOUR_PATH}/usbboot git clean -fdx export TOOLCHAIN=${MYDROID}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- make MACH=omap5 BOARD=omap5uevm clean make MACH=omap5 BOARD=omap5uevm CROSS_COMPILE=${HOME}/.jenkins/workspace/OMAP5_AFS/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-

Building Kernel
To create kernel uImage you need to add "mkimage" directory path to your "PATH" environment variable: cd ${YOUR_PATH}/kernel/android-3.4 make -j$(cat /proc/cpuinfo |grep ^proc|wc -l) ARCH=arm CROSS_COMPILE=arm-eabi- mrproper make -j$(cat /proc/cpuinfo |grep ^proc|wc -l) ARCH=arm CROSS_COMPILE=arm-eabi- android_omap_defconfig make -j$(cat /proc/cpuinfo |grep ^proc|wc -l) ARCH=arm CROSS_COMPILE=arm-eabi- uImage modules

Building Android Filesystem (AFS)
cd $MYDROID . build/envsetup.sh lunch 17 #(specific lunch target: full_omap5panda-userdebug) make -j $(egrep '^processor' /proc/cpuinfo | wc -l) clean make -j $(egrep '^processor' /proc/cpuinfo | wc -l)

Building TI WLAN & Blueti Drivers
When building the wifi drivers and the new blue tooth blueti drivers you will also need to also have the CROSS_COMPILE also set as listed above in Setting up the Build

Environment.

Wifi Drivers export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.4 export ARCH=arm export KLIB=${KERNEL_DIR} export KLIB_BUILD=${KERNEL_DIR} cd ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/ make -j4 clean make -j4

Blueti Drivers export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.4 export ARCH=arm export KLIB=${KERNEL_DIR} export KLIB_BUILD=${KERNEL_DIR} cd ${MYDROID}/hardware/ti/wpan/bluetooth-compat/ make -j4 clean make -j4

Ducati and Graphics instruction
Download the pre-built graphics and ducati binaries for this release from here. Place them in appropriate location in AFS output.

cd ${YOUR_PATH} mkdir sgx_ducati cd sgx_ducati


 * 1) Download the ducati and graphics tar balls in sgx_ducati folder

tar -xvf ducati.tgz cp -v ducati/ducati-m3-core0.xem3 ${MYDROID}/out/target/product/panda5/system/vendor/firmware/

tar -xvf sgx.tgz cp -vrf sgx/* ${MYDROID}/out/target/product/panda5/

=Preparing Android binaries= Officially this release supports emmc boot. For the emmc the system image file must have the sgx and ducati binary included, the document

OPBU_Linux_panda5AJ_1_2_Release_Notes.doc contain details on other components that can also be added to the AFS as done for sgx and ducati. It is recommended to read the

document before building your final image.

Rebuild Android Filesystem (AFS) to include the Wifi, Ducati & SGX binaries
Wifi & BT kernel modules: export KERNEL=${YOUR_PATH}/kernel/android-3.4 export BOARD_TYPE="panda5" cd $MYDROID/out/target/product/$BOARD_TYPE mkdir -p system/lib/modules; cd system/lib/modules cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/compat/compat.ko. cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/net/wireless/cfg80211.ko. cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/net/mac80211/mac80211.ko. cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wl12xx/wl12xx.ko. cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wl18xx/wl18xx.ko. cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wl1251/wl1251.ko. cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wlcore/wlcore*.ko. cp -fp ${MYDROID}/hardware/ti/wpan/bluetooth-compat/net/bluetooth/bnep/bnep.ko. cp -fp ${MYDROID}/hardware/ti/wpan/bluetooth-compat/net/bluetooth/rfcomm/rfcomm.ko. cp -fp ${MYDROID}/hardware/ti/wpan/bluetooth-compat/net/bluetooth/bluetooth.ko. cp -fp ${MYDROID}/hardware/ti/wpan/bluetooth-compat/net/bluetooth/hidp/hidp.ko. cp -fp ${MYDROID}/hardware/ti/wpan/bluetooth-compat/drivers/bluetooth/btwilink.ko.

cd $MYDROID . build/envsetup.sh lunch 17 cp -v ${YOUR_PATH}/kernel/android-3.4/arch/arm/boot/zImage device/ti/${BOARD_TYPE}/kernel for i in $(ls out/target/product/panda5/*img); do rm -vf $i; done make -j $(egrep '^processor' /proc/cpuinfo | wc -l)

Preparing eMMC binaries/images
cd $YOUR_PATH mkdir emmc_files cp -v ${MYDROID}/out/target/product/panda5/*img emmc_files cp -v ${MYDROID}/device/ti/omap5sevm/boot/fastboot.sh emmc_files cp -v ${MYDROID}/out/host/linux-x86/bin/{simg2img,make_ext4fs,mkbootimg,fastboot,adb} emmc_files cp -v ${YOUR_PATH}/kernel/android-3.4/arch/arm/boot/zImage emmc_files/kernel cp -v ${YOUR_PATH}/usbboot/out/omap5uevm/MLO emmc_files/omap5uevm_GP_ES1.0_MLO cp -v ${YOUR_PATH}/usbboot/out/omap5uevm/usbboot emmc_files cp -v ${YOUR_PATH}/usbboot/out/omap5uevm/iboot.ift emmc_files # for a GP device

Flashing eMMC images
This is done using usbboot to put the PANDA5 board (OMAP5) in fastboot mode with the steps given below:

Required switch settings on the Panda5 board to enable eMMC boot. (S6 on the back of the board) 3    2    1     0   OFF OFF OFF OFF

1. Connect your USB3 cable from the target to your flashing station, the power supply, & the micro usb cable using a terminal or screen (for screen the command is: screen /dev/ttyUSB0 115200)

2. Make sure the board is powered OFF

3. Start usbbboot in fastboot mode:

sudo ./usbboot -f When running this command you will see: usbboot -f: starting in fastboot mode waiting for device...

4. Power up your board

From the terminal you should see something similar to this saying the device is in fastboot mode: r1Texas Instruments Inc Bootloader 1.1.0-jenkins-OMAP5_usbboot-102^0 Build Info: Apr 20 2012 - 05:01:26 Entering fastboot mode... From the command prompt where you ran the usbboot command you should see something similar to this below: reading ASIC ID   CHIP: 5430 IDEN: cfd7d499ed40beab470795a5cfbc5707807b4b6a MPKH: 351edf8f4d739d50f7449a6d3d3d983d6220974836f039c752dae7226bb19955 CRC0: 06e92275 CRC1: 3894aaf5 device is ED/HD (EMU/HS) sending 2ndstage to target... f0030002 waiting for 2ndstage response...   received 2ndstage response...

5. Run your fastboot.sh script sudo ./fastboot.sh      This will flash the binaries into the emmc on the Panda board.

6. Now reset the board and let it boot up.