SPRACO0 August   2019 AM6526 , AM6528 , AM6546 , AM6548

 

  1.   Enabling Android Automotive on Your TI Development Board
    1.     Trademarks
    2. 1  Introduction
    3. 2  Implementation
      1. 2.1 Prerequisites
      2. 2.2 Software Changes
    4. 3  Deploy Instructions
      1. 3.1 Build Instructions
      2. 3.2 Boot Instructions
    5. 4  Testing
      1. 4.1 Prerequisites/Setup for Automotive Testing
        1. 4.1.1 Compatibility Test Suite (CTS)
        2. 4.1.2 Vendor Test Suite (VTS)
      2. 4.2 Automotive Testing
        1. 4.2.1 Compatibility Test Suite (CTS)
        2. 4.2.2 Vendor Test Suite (VTS)
    6. 5  Open Source
    7. 6  Extending to a New Platform
    8. 7  Known Bugs
    9. 8  Future Work
    10. 9  FAQ
    11. 10 References

4.1.1 Compatibility Test Suite (CTS)

  • Runs on your desktop and executes a series of test cases on the connected device(s).
  • The intent is to reveal incompatibilities or malfunctions, ensure API compatibility and Android Compatibility Definition Document (CDD) compliance while developing the automotive configuration and additional related software components (Overview of CTS).
  1. Desktop machine setup:
    1. Ensure the latest versions of both Android Debug Bridge (adb) and Android Asset Packaging Tool (AAPT) are installed and those tools’ location(s) are added to the system path of your machine:
      2. $ sudo apt-get install adb aapt

      NOTE

      The SDK should already come with adb and aapt so the above command will either update/upgrade them or return the message:

      • “aapt is already the newest version <version_number>”
      • “adb is already the newest version <version_number>”
    2. Download the CTS packages matching your devices’ Android version and the Application Binary Interfaces (ABIs) your devices support.
    3. Unzip the CTS packages inside of ~/ti-processor-sdk-android-<board>-<version>/board-support/emmc_files:
      4. $ cd ~/ti-processor-sdk-android-<board>-<version>/board-support/emmc_files $ unzip ~/Downloads/android-cts-<version>.zip .
    4. You may need to override the ro.product.first_api_level property in order to ensure upgrade requirements are applied.
      1. Find the valid override values on Codenames, Tags, and Build Numbers.
      2. The following would be done inside the relative device.mk file:
      5. PRODUCT_PROPERTY_OVERRIDES += ro.product.first_api_level=<valid_override_value>