This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

FAQ on EVM and software(Linux/Android)

This FAQ is meant to address common issues seen for EVM and SW. This post will be updated, so if you are seeing an issue, please take a look at this forum for possible solutions.

1.Which documents should I refer for Android, Linux and EVM


Tools folder:

SW Folder:

Linux Download Page:

Android Download Page:

Getting started Videos:

2. Where I can get documentation supporting the release?

EVM System reference manual and quick start up guide is available at Tools folder (

TRM/DM for the device is available on OMAP5432 product page (

3.Where can I buy cables for the EVM?


Micro USB cable ( 1 is used for Android ADB and flashing the EVM, 1 is used for the UART to USB debugging output) --> 2x

Micro HDMI Cable ( used for LCD monitor output) -->

Power supply -->


1.What if you’re behind a firewall?

Ans) Below are the things which needs to be done when behind a fire wall, Exporting the https_proxy variable with a suitable value. The git config settings has to be done by following the link

2.Selecting proper target for the “lunch” Command.

Ans) While executing the “lunch” command please check carefully before entering the correct number for the desired target as mentioned in the release notes.


1.What if the proxy settings are not set before running the script?

Ans) If you missed it, you can add the file in SD card,

  • Connect your SD card to your host machine via SD card reader.
  • Mount the rootfs partition typically /dev/sdX2 (where X might be different on different systems).
  • Add the resolv.conf to etc directory of rootfs partition.
  • Unmount and insert it in board and boot.

Once the this setting is done and when you run the script it starts installing all the required packages on its own.

2.This kernel error keeps showing up it while running the board "omap_hsmmc 480ad000.mmc: vmmc regulator missing".

Ans) This is a known issue which will be fixed soon.

3. What are the performance limitations on the current release?

Ans) Power and Thermal management is not implemented, so default frequency for the ARM® Cortex-A15 processors is limited to 800MHz for each core (instead of 1.5Ghz).  The power and thermal management will be implemented in a future release to enable full performance evaluation of the ARM® Cortex-A15 cores. 

4. Are there details about the release?

Ans) The FAQ is available here: