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.

DRA72: Automotive Android comments and questions

Part Number: DRA72

I have been following the instructions on "6AO.1.1 Application Notes"  page

Since it requires Ubuntu 14.04 and none of my 5 Linux sytems are that I installed it using VirtualBox on Arch Linux

I give it 8 CPU, 16G of RAM and 1TB of disk space so that should be enough

I had a few issues with your instructions which are missing a few items to be able to compile Android.

It gives an error about a dtc too old and once the compiler is installed it gives some mysterious error which after a search on google the solution found is to install the missing lib

sudo apt-get install device-tree-compiler
sudo apt-get install liblz4-tool

Then for some weird reasons it refuses to use the installed OracleJava so I switch to Open Java which it doesn't like because it wants 1.8

Since 1.8 is not available I have to install a ppa version this way :

sudo add-apt-repository ppa:openjdk-r/ppa
sudo apt-get update
sudo apt-get install openjdk-8-jdk
sudo update-alternatives --config java
sudo update-alternatives --config javac

It might be a good idea to update your instructions.

Now to my question,

All I am doing this weekend is getting TI Android to work on one of my Beagleboard X15 but the ultimate goal is to use it on a producttion board where I work.

The problem I have with your instructions about the installation is that it requires to use the micro USB port, not a problem on the Beableboard X15 but on the production board we have 2 USB host only port.

We do have a serial debug port.

What would be an alternative way to install android on the system? We have 64M of qspi and 4G of emmc to use.

I did get a few errors which don't seem to be fatal, how do I get rid of those errors?

[231/1002] including ./external/libdrm/Android.mk ...
external/libdrm/libkms/Android.mk:23: warning: invalid GPU drivers: omapdrm
[249/1002] including ./external/mesa3d/Android.mk ...
./external/mesa3d/Android.mk:52: warning: invalid GPU drivers: omapdrm

Michel Catudal

  • Hi Michel,

    can you clarify on which device you want to run 6AO.1.1 - is it Beagleboard X15 or DRA7x board?

    Regards,
    Yordan
  • Yordan,

    The current target is a DRA726, I am just using the Beagleboard X15 for tests because I don't have to change as much on u-boot and the kernel. The differences with the TI EVM are not as  big as those with our design with the DRA726.

    I've use TI Industrial EVM, Beagleboard X15 Rev A and B1 before we had DRA726 hardware. I created yocto based on the Automotive yocto 3.04 on those.

    We had a few TI EVM that got zapped and I managed to convert the Beagleboard X15 at the time to use the LCD from the EVM after a few modifications to the device tree.

    Another target is a custom board that uses a DRA7x A15 double core.

    I have one question on this Android, I read that for the Beaglebone the last version that has support for SGX uses kernel 3,2,

    From what I found on the weekend both the TI and Linaro android support one of the latest Android that uses kernel 4.4, does the support for  SGX work on those?

    Michel Catudal

  • beagleboard x15 rev c(community reference platform) and AM572x GPEVM is upstreamed to AOSP.

    instructions at wiki.linaro.org/.../BeagleBoard-X15

    wiki should have instructions for oreo and master based on 4.14 kernel.

    x15 boots with emmc and 4GB is sufficient for processor SDK android and upstream feature and sw product purpose.

    the mentioned baseline uses DDK 1.17 (uses SGX 544).
  • x15 revc is not compatible with dra72.

    please check on device tree definition in uboot and kernel and add the delta to enable revb.
    this should be easy to do but we never got to validate reva or revb