6AJ.1.2 Application Notes

Back to 6AJ.1.2_Release_Notes

Poly Fix Silicon Identification

 * Box Identification:
 * Locate (D) Date Code information
 * The Date Code is listed in YYWW format.
 * Material with date codes of 1327 or later are manufactured with the corrected poly slot reticle


 * Device Level Identification:
 * There is a unique 7-character code (YMLLLLS) symbolized on the top of every component
 * YM in the code corresponds to the Year and Month of assembly
 * Units with lot trace code of 37LLLLS or later have been manufactured with the corrected poly slot reticle.


 * Programmatic Identification:
 * The test program revision is programmed as part of the die ID revision register.
 * Register to read is 0x4AE0C20C and The FT revision is found in bits [15:8]
 * If the value is 5 or more, it is poly fixed material

QSPI NOR/eMMC partitions
In this release, the xloader and boorloader goes into QSPI and rest of the images go in to eMMC partitions. The table below summarizes the partition info

Syntax for fastboot flash command is fastboot flash

To update kernel (zImage) alone, flash the zimage partition fastboot flash zimage 

To update ramdisk.img alone, you will have to create boot.img file and flash it. Steps to create boot.img file below cd $YOUR_PATH/emmc_files mkbootimg --kernel  --ramdisk  --ramdisk_offset 0x01f00000 --base 0x80000000 --output boot.img

Note: To update MLO and u-boot.img in SPI, follow commands below. They have to be flashed together.

fastboot oem spi fastboot flash xloader  fastboot flash bootloader 

Re-Building SGX kernel module
Some changes made to kernel defconfig can causes prebuilt SGX kernel module to not load [   8.354095] pvrsrvkm_sgx544_116: disagrees about version of symbol thermal_cooling_device_register [   8.363616] pvrsrvkm_sgx544_116: Unknown symbol thermal_cooling_device_register (err -22) [   8.372467] pvrsrvkm_sgx544_116: disagrees about version of symbol thermal_zone_bind_cooling_device [   8.382049] pvrsrvkm_sgx544_116: Unknown symbol thermal_zone_bind_cooling_device (err -22) [   8.390869] pvrsrvkm_sgx544_116: disagrees about version of symbol pid_task [   8.398254] pvrsrvkm_sgx544_116: Unknown symbol pid_task (err -22) ..

Follow the instructions below for rebuilding SGX module

cd ${MYDROID}/device/ti/proprietary-open/jacinto6/sgx_src/eurasia_km/eurasiacon/build/linux2/omap4430_android export KERNELDIR=${YOUR_PATH}/kernel/android-3.8 export CROSS_COMPILE=${MYDROID}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- export ARCH=arm make TARGET_PRODUCT="omap5sevm" BUILD=release TARGET_SGX=544es2

SGX module will be present at ${MYDROID}/device/ti/proprietary-open/jacinto6/sgx_src/eurasia_km/eurasiacon/binary2_544_116_omap4430_android_release/target/pvrsrvkm_sgx544_116.ko or ${MYDROID}/out/target/product/jacinto6evm/target/kbuild/pvrsrvkm_sgx544_116.ko

Push this file to /system/lib/modules/ location on the target and reboot the board.

Audio
Below is some information about what input/output connectors in VayuEVM can be used for audio and what type of accessories can be connected.

NOTE: Audio devices can be assigned to listening zones through the Settings -> Sound -> Audio Zone Configuration.

WiLink8Q
J2: WLAN/BT 2.4Ghz J3: WLAN 5Ghz J8: BT 2.4 Ghz
 * You will need a COM8 WiLink8Q hardware module
 * EVM H/W Mod:
 * If you have DRA7xx-EVM boards less than REV-E, you need a mod to get 32KHz clock to COM8 module. Refer here for more details
 * If you have DRA7xx-EVM boards less than REV-F, you need a mod to test BT HFP. Refer here for more details
 * SW5 USERCONFIG DIP Switch: Make sure you have the correct DIP switch as mentioned in Flashing section
 * Antenna connector details for COM8 module
 * Bluetooth: All Bluetooth profiles were tested using Cybercom bluego solution, contact Cybercom for getting access to their solution.

NOTE: Don't use Cybercom App and Android stock Bluetooth (Settings &rArr; Wireless & Metworks &rArr; Bluetooth) together

Ethernet
shell@android:/$ su shell@android:/# netcfg eth0 up # to bring up the interface shell@android:/# netcfg eth0 dhcp # to get IP address from DHCP server shell@android:/# netcfg eth0 down # to bring down the interface
 * Use following commands for enabling Ethernet (eth0/eth1) in Android.


 * Android by default only supports one instance of Ethernet at frameowrk, and eth1 is the instance used by Android UI (Browser, etc..)

HDMI

 * In this release, DDC block in HDMI is used to read the EDID info
 * Following hardware modification is needed to be done on Jacinto6 EVM REV-Dx boards for HDMI to be functional (Rev-E and later boards don't need this)
 * • Mod is needed on RU108 module
 * • Lines 3B1 and 3B2 need to be shorted for HPD interrupt line to be connected all times
 * • Lines 4B1 and 4B2 need to be shorted for CEC interrupt line to be connected all times
 * • Refer to image here for details

Disable HDMI
In order to disable/remove HDMI from the system, apply the below kernel patch, rebuild and flash kernel. The patch below is to disable HDMI in kernel defconfig cd ${YOUR_PATH} git fetch http://review.omapzoom.org/kernel/omap refs/changes/37/34337/1 && git cherry-pick FETCH_HEAD

USB Super Speed

 * USB1 port on EVM is Super speed capable and is validated in both host mode and gadget mode.
 * By default the USB1 port is set to be in gadget mode. To change USB1 port to be in host mode, apply the below patch in kernel, rebuild kernel and flash the updated dtb file

cd ${YOUR_PATH}/kernel/android-3.8 git fetch http://review.omapzoom.org/kernel/omap refs/changes/83/34283/1 && git cherry-pick FETCH_HEAD

DCAN
DCAN1_RX should be connected by populating R611 (0Ω) cd ${MYDROID}/external git clone https://git.gitorious.org/linux-can/can-utils.git
 * H/W Mod: For excercising the external interface of DCAN1 (can0) on the DRA7xx EVM, the following board modification is required:
 * Test Tools: Follow instructions below to get can-utils tool

Multi Display
Two multi display configurations are supported in this release  Primary LCD + HDMI panel  Default configuration  Primary FPD Link + HDMI panel  Make sure you don't have JAMR board on your EVM</li> Requires kernel changes and u-boot changes for switching to this configuration </li> cd ${YOUR_PATH}/kernel/android-3.8 git fetch http://review.omapzoom.org/kernel/omap refs/changes/70/34270/2 && git cherry-pick FETCH_HEAD git fetch http://review.omapzoom.org/kernel/omap refs/changes/81/34281/1 && git cherry-pick FETCH_HEAD
 * 1) Kernel change to disable early IPU camera
 * 1) Kernel change to make FPD Link primary display

cd ${YOUR_PATH}/u-boot git fetch http://review.omapzoom.org/repo/u-boot refs/changes/69/34269/2 && git cherry-pick FETCH_HEAD Rebuild and flash kernel and u-boot components</li> </ul> </ol>
 * 1) U-boot change to disable early IPU camera

VIP Single Instance

 * In this release OV10635 sensor was tested by attaching it to the vision board
 * Sensor sits on i2c 2 bus at address and is currently set for 8-bit YUV422 format
 * H/W setup to test sensor functionality:
 * Attach vision board to the Vayu EVM.
 * Switch settings on vision board must be configured [0-7] as Off On Off On Off On Off on
 * Connect OV10635 sensor to the vision board
 * If you launch Camera App after Android boot, then an instance of VIP is created on MPU side (A15)
 * If you have the hardware connected at boot time, then an instance of VIP is created in M4 side and you will see a auto preview from camera sensor during boot.

IPC

 * Linux kernel rpmsg example (rpmsg<->BIOS RPMessage): http://processors.wiki.ti.com/index.php/RPMsg_Kernel_Client_Application
 * Benchmarking: http://processors.wiki.ti.com/index.php/IPC_BenchMarking

Boot Options
Default flashing instructions and script are meant for two stage bootloader (MLO & u-boot) with MLO and u-boot loading from QSPI and remaining content flashed to emmc. Instructions below are for other options enabled in this release.

SD card boot
SD Card Boot Information

USB Peripheral boot
This mode is for flashing a fresh new board, which has no MLO or u-boot present on SPI or eMMC (To avoid SD card)

SYSBOOT [0-15] OFF OFF OFF OFF ON OFF OFF OFF   ON OFF OFF OFF OFF OFF OFF OFF ON cd $YOUR_PATH/emmc_files sudo ./usbboot-stand-alone -s ./u-boot-spl.bin
 * Disconnect the power supply from the board
 * CHange DIP switch as below, this configuration corresponds to the following device boot order: USB
 * Connect micro USB cable from Linux PC to USB3.0 port on EVM
 * Execute the following command on Linux PC

reading ASIC ID CHIP: 5641 rom minor version: 01 IDEN: 0000000000000000000000000000000000000000 MPKH: 0000000000000000000000000000000000000000000000000000000000000000 CRC0: af96e165 CRC1: 00000000 device is GP sending 2ndstage to target... SYSBOOT [0-15] OFF ON ON OFF OFF OFF OFF OFF   ON OFF OFF OFF OFF OFF OFF OFF ON
 * Power on or reset the board
 * At this point DRA7xx communicates with host machine, u-boot-spl will be transferred into DRA7xx internal memory and board will boot automatically and enter into fastboot mode
 * Change the DIP switch now for regular boot (SD &rArr; QSPI_1)
 * Now you can run the fastboot.sh script or fastboot commands to flash the board.

Single stage bootloader
To enable the early boot flow, configure the DRA7xx board to boot in QSPI_1 production boot mode by setting the sys_boot dip switches as follows: SYSBOOT [0-15] OFF ON ON OFF ON ON OFF OFF   ON OFF OFF OFF OFF OFF OFF OFF ON

Then power cycle the board. At boot when early boot mode is detected, SPL will load and boot necessary OS images into memory directly, bypassing u-boot load and execution.

If the SPL finds the required partitions/images, it will boot to the kernel; otherwise it falls back to regular flow of loading u-boot which allows user to flash partitions as needed.

All eMMC option
If you don't want to use QSPI NOR and want everything to be flashed to emmc and boot from emmc, follow instructions below.

echo "Setting target for bootloader to SPI" ${FASTBOOT} oem spi
 * Remove following lines from fastboot.sh script before flashing

SYSBOOT [0-15] OFF ON OFF OFF OFF ON OFF OFF   ON OFF OFF OFF OFF OFF OFF OFF ON
 * Required DIP switch settings after flashing: This configuration corresponds to the following device boot order: SD &rArr; eMMC