6AM.1.0 Release Notes


 * NOTE: This is the last Linux kernel 3.14.x based Android release, next releases would be on Linux kernel version 4.4.x
 * Refer to 6AM.1.0_Application_Notes section for stable fixes releases

= Introduction =

These Release Notes provide instructions for both,
 * Testing the release using a pre-built binary image which can be loaded onto eMMC on EVM board
 * Rebuilding the Android binary image from the Android sources

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

NOTE: Same set of software binaries work for both J6 and J6 Eco EVMs, only the device tree file (.dtb) is different for different EVMs. Refer to 6AM.1.0_Application_Notes for more details

Release Features
Following new features are enabled/tested for J6 and J6 Eco in this release:
 * Boot: fastboot, QSPI/NOR + emmc boot, SD card boot, Single stage bootloader, USB peripheral boot, IPU loading in u-boot
 * Connectivity: USB2.0/USB3.0 Host, Gadget and dual-role, Dual Ethernet, SD card detect, eMMC HS200 mode, DCAN
 * Power: AVS0, MPU DVFS, ABB
 * Thermal: Governors implemented for MPU (On Die), Monitoring implemented for all on chip sensors
 * Video: 1080p60 MP4/H264/MP2 Playback, H264 Video Encode (F2F)
 * Audio: MP3/AAC playback, stereo audio out on McASP, 5.1 Audio on HDMI, Downmix to Stereo on McASP when disconnected, Aux-In, ARM<->DSP Audio Routing
 * Display: SGX accelerated UI and touch, DRM/KMS, ION/GEM, HDMI A/V out, GC320, HDMI hot plug detect
 * Camera: TVP5158 Analog camera(JAMR3), VIP: YUYV/RGB888 format capture, NV12 capture, Interlaced capture, VPE: color conversion, v4L2 M2M, scalar, DEI, RGB565 and alpha channel support
 * Radio: HD 1.5 Radio Library (ARM/DSP rendering) and DAB Radio support
 * IPC: IPC Late attach and error recovery during late attach. Added support to avoid /dev/mem access by using UIO driver and misc driver for hwspinlock user interface
 * WiLink8Q: WLAN - Wi-Fi/Wi-Fi Direct/SoftAP (R8.4 Version), BT - A2DP Sink, AVRCP, HFP (using Cybercomm stack)
 * Secure boot: Validated in this release on HS device and M-Shield DK Lite v4.4.1 (available in CDDS Only). Customers needing access to the M-Shield DK Lite package should contact their TI representatives
 * Reference Implementation: IPU1 based RVC, FPDlink as primary display

Release Limitations
In this release:
 * J6/J6 Eco
 * DSS: DSS acceleration is not supported with full fps
 * Video: MPEG2 decode not fully functional
 * Video: Artifacts seen in some MPEG2 playback, fix available in 6AM.1.0_Application_Notes
 * Platform: Warm reset is not supported on DRA7xx because of silicon errata. Current implementation of Android recovery mode relies on warm reset and hence broken. We are looking at alternate way to support recovery mode
 * Camera: Frame drops observed in camera preview (Camera app)
 * J6 Eco
 * Platform: IODelay configuration for J6 Eco Rev 2.0 and Ethernet support for Rev-C EVM not added yet

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

=Rebuilding Android from Sources=

Build PC setup
You need a 64 bit Ubuntu machine for building Android file system.


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

Follow instructions from official Android page here for setting up the packages required for building Android.


 * Proxy/Firewall

If you are behind proxy/firewall, workaround it using the instructions in. For installing repo make sure you also export https_proxy environment variable.


 * 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


 * 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.


 * A note on Host binaries of Marshmallow

Host binaries like simg2img, make_exr4fs etc.. that are built in Android M needs shared libraries now. You might see errors like below when trying to use those binaries simg2img: error while loading shared libraries: libc++.so: cannot open shared object file: No such file or directory To resolve it, export your LD_LIBRARY_PATH to include the libraries. Point it to either the daily build or the folder from your build system export LD_LIBRARY_PATH=${MYDROID}/out/host/linux-x86/lib64/ or export LD_LIBRARY_PATH=


 * Build Quirk

If you have the following build failure Error occurred during initialization of VM Incompatible minimum and maximum heap sizes specified

increase java heap size as the following in your host bash script _JAVA_OPTIONS: -Xms1024M -Xmx1024M

Android Filesystem Sources
You can get the Android source for this release by doing: cd mkdir -p 6AM.1.0 cd 6AM.1.0 export YOUR_PATH=$PWD mkdir -p mydroid; cd mydroid export MYDROID=$PWD repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b 6AM.x -m RLS_6AM.1.0.xml repo sync

TI Hardware Accelerated Graphics and MultiMedia Binaries
Multimedia (DCE) and accelerated graphics binaries are part of Android file system build

U-Boot Sources
cd ${YOUR_PATH} git clone git://git.omapzoom.org/repo/u-boot.git cd u-boot git checkout 6AM.1.0

Kernel & Driver Sources
cd ${YOUR_PATH} mkdir kernel git clone git://git.omapzoom.org/kernel/omap.git kernel/android-3.14 cd kernel/android-3.14 git checkout android-3.14-6AM.1.0

Setting up build environment
From your work directory (6AM.1.0 folder): export YOUR_PATH=$PWD export MYDROID=${YOUR_PATH}/mydroid export PATH=$PATH:${MYDROID}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/ export CROSS_COMPILE=${MYDROID}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-

Building U-boot sources
Instructions for building x-loader and bootloader

cd ${YOUR_PATH}/u-boot export CROSS_COMPILE=${MYDROID}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi- export ARCH=arm make distclean make dra7xx_evm_android_config make

Building Kernel
Instructions for building kernel and device tree

cd ${YOUR_PATH}/kernel/android-3.14 export CROSS_COMPILE=${MYDROID}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi- export ARCH=arm make mrproper ./ti_config_fragments/android_config.sh make uImage LOADADDR=0x80008000 make dtbs

Note: If you are making changes to kernel defconfig and need to rebuild SGX kernel module, refer here

Building Android Filesystem (AFS)
Instructions for building Android file system. Note that Building Lollipop code base needs Java7

cd $MYDROID . build/envsetup.sh lunch full_jacinto6evm-userdebug make -j2 clean make -j2

Building WiLink WLAN Driver
Instructions for building TI WiLink (Wl18xx) WLAN driver

export ARCH=arm export CROSS_COMPILE=${MYDROID}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi- export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.14 export KLIB=${KERNEL_DIR} export KLIB_BUILD=${KERNEL_DIR} cd ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/ make defconfig-wl18xx make

Rebuild Android Filesystem (AFS) to include kernel and WLAN driver
Copy Kernel Image (This step is for making your kernel to be part of boot.img) cd $MYDROID cp -v ${YOUR_PATH}/kernel/android-3.14/arch/arm/boot/zImage device/ti/jacinto6evm/kernel

Copy WLAN Driver (This step is for making wlan driver modules to be part of system.img) cd $OUT/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/wl18xx/wl18xx.ko. cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wlcore/wlcore.ko. cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wlcore/wlcore_sdio.ko.

Rebuild AFS to generate update images cd $MYDROID . build/envsetup.sh lunch full_jacinto6evm-userdebug rm out/target/product/jacinto6evm/*.img rm out/target/product/jacinto6evm/obj/PACKAGING/systemimage_intermediates/system.img make -j2

Preparing eMMC binaries/images
cd $YOUR_PATH mkdir emmc_files cp -v ${MYDROID}/out/target/product/jacinto6evm/*img emmc_files cp -v ${MYDROID}/device/ti/jacinto6evm/fastboot.sh emmc_files cp -v ${MYDROID}/out/host/linux-x86/bin/{simg2img,make_ext4fs,mkbootimg,fastboot,adb} emmc_files cp -v ${MYDROID}/out/host/linux-x86/lib64/{libc++.so,libcutils.so,liblog.so,libselinux.so} build/emmc cp -v ${YOUR_PATH}/kernel/android-3.14/arch/arm/boot/zImage emmc_files/kernel cp -v ${YOUR_PATH}/kernel/android-3.14/arch/arm/boot/dts/dra7*.dtb emmc_files cp -v ${YOUR_PATH}/u-boot/MLO emmc_files/GP_MLO cp -v ${YOUR_PATH}/u-boot/MLO emmc_files/ cp -v ${YOUR_PATH}/u-boot/u-boot.img emmc_files

=Flashing eMMC images=

The default setup is to flash MLO and u-boot.img to QSPI and remaining binaries (kernel, dtb file and AFS) to emmc.
 * Instructions are same for J6 and J6 Eco EVM
 * For more info on partitions and flashing refer to "QSPI NOR/eMMC partitions" Application note.

DIP Switch settings
Required DIP switch settings: This configuration corresponds to the following device boot order: SD &rArr; QSPI_1

Flashing procedure
Hit any key to stop autoboot: 3 U-Boot# fastboot cd $YOUR_PATH/emmc_files sudo ./fastboot.sh
 * Copy u-boot.img and MLO files to an SD card (boot partition) and then boot the target board from this external SD card.
 * Connect a USB cable from the Linux PC to the USB3.0 port on board
 * Power on the board and stop the board at u-boot prompt by interrupting with key press
 * Put the board in fastboot mode by typing in fastboot command
 * On the Linux PC which has the emmc images run the fastboot.sh script to flash the binaries
 * NOTE: After the flashing is done, remove the external SD card and reboot the board.

U-Boot# env default -a U-Boot# saveenv
 * If you see errors like "Unknown command 'nand' - try 'help'" when booting, execute below commands on u-boot prompt. This generally happens if you have used GLSDK binaries on this board

=Application notes/Additional Info= 6AM.1.0_Application_Notes

Refer to Application notes page for more info on features of this release, additional boot options, etc...