Skip to content
Branch: master
Find file History
Pull request Compare This branch is even with 1.5.
MuniSakkuru Version 1.5.0 aac-sdk
The Alexa Automotive Core (AAC) SDK is for automotive OEMs to integrate Alexa directly into vehicles.

**v1.5.0**

* v1.5.0 released on 2019-03-06

**Enhancements**

* Added a C++ sample application to demonstrate use cases that the Alexa Auto SDK supports. Read more about the C++ Sample App [here](./samples/cpp/README.md).
* Released the code for the AGL Alexa Voice Agent, a binding for Automotive Grade Linux powered by Alexa Auto SDK v1.5. The software is shipped as a standard AGL binding that exposes an API for speech recognition using the Alexa Voice Service. Please refer to the [AGL Alexa Voice Agent documentation](./platforms/agl/alexa-voiceagent-service/README.md) for instructions to build, install, and test the binding on an R-Car M3 board.
* Added support for runtime selection of the AmazonLite wake word locale. The AmazonLite locale will automatically switch when the AVS locale is switched.
* Added support for optionally logging and uploading Alexa Auto SDK metrics to the Amazon cloud. Voice request metrics, for example, include start and end timestamps of user and Alexa speech and UPL between the request and Alexa’s response. Please contact your SA or Partner Manager for details or to request this package for Android.
* Added support for an optional platform interface `EqualizerController`. The Equalizer Controller enables Alexa voice control of device audio equalizer settings by making gain adjustments to three frequency bands (“BASS”, “MIDRANGE”, and/or “TREBLE”).
* Added an optional Code-Based Linking (CBL) authorization implementation in the Engine. With the new `cbl` module, the Engine handles acquiring access tokens. A `CBL` platform implementation should be registered with the Engine in place of an `AuthProvider` implementation to use this method for authorization.
* Improved the usage and deployment of the Local Voice Engine extension on Android. Please contact your SA or Partner Manager for more information.
* Updated the vehicle information configuration API to include a vehicle identifier. An `aace.vehicle.info.vehicleIdentifier` property of vehicle configuration is now available through the existing `VehicleConfiguration`.

**Resolved Issues**

* Fixed an issue where barging in while many unprocessed Speak directives are queued could cause SpeechSynthesizer to become unresponsive or crash
* Added an `EXPECTING` state to the `AlexaClient DialogState` to accommodate multi-turn for hold-to-talk interactions. When more user input is required during an interaction, tap-to-talk interactions will transition directly from `EXPECTING` to `LISTENING` whereas hold-to-talk will remain in the `EXPECTING` state until listening is manually triggered.
* Fixed an issue where the Android Sample App could get stuck in a loop of INVALID_REQUEST_EXCEPTION errors being thrown repeatedly after MACCAndroidClient reported an error. Note: To fix this, the C++ `ExternalMediaAdapter::getState` method signature changed to allow the implementation to say whether the state it provides is valid. This change is not backward compatible.
* Fixed an issue where the Android Sample App created a syslog sink and logged VERBOSE in release builds. Note: As part of the fix, the default Engine logger sink id changed from *console* to *default*. Existing calls to `LoggerConfiguration::createLoggerRuleConfig` with sink id `"console"` should be changed to sink id `"default"`.

**Known Issues**

* The Alexa Auto SDK Engine becomes unresponsive if it receives a ```Play``` directive during shutdown. However, since shutdown is triggered when car ignition is turned off, there is no direct customer impact expected.
* When a timer sounds during an Alexa-to-Alexa call, uttering "stop" ends the call, not the timer.
* Multiple automotive devices using the same account at the same time can access contacts from phones paired across those devices.
Latest commit 798ead5 Mar 6, 2019
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
hosttools
meta-aac-builder Version 1.5.0 aac-sdk Mar 6, 2019
meta-aac-ubuntu Version 1.3.0 aac-sdk Nov 21, 2018
meta-aac Version 1.5.0 aac-sdk Mar 6, 2019
scripts Version 1.5.0 aac-sdk Mar 6, 2019
.gitignore
README.md Version 1.5.0 aac-sdk Mar 6, 2019
build.sh Version 1.5.0 aac-sdk Mar 6, 2019

README.md

Building the Alexa Auto SDK

This directory contains a collection of software which is required to build the Alexa Auto SDK software components for various target platforms.

Overview

The Alexa Auto SDK Builder is based on OpenEmbedded that provides a simple way to cross compile all the Alexa Auto SDK software components for various target platforms. Recommended for developers who wants to use platforms such as Android and QNX.

For target platforms already based on OpenEmbedded infrastructure, such as Yocto/Poky, you can use OE generated SDK or alternatively you may use meta-aac layer to build and install Alexa Auto SDK into your system. See Alexa Auto SDK OE layer below for meta-aac layer usage.

Quick Start

Run the build process as follows (where AAC_SDK_HOME is the location you've installed the AAC SDK.):

$ ${AAC_SDK_HOME}/builder/build.sh (oe) <args>

Alexa Auto SDK Builder

Developers who want to build the complete Alexa Auto SDK software for various cross targets can use OpenEmbedded based building system Alexa Auto SDK Builder.

Getting Started

The Alexa Auto SDK Builder can be run either natively on a Linux host or in a Docker environment.

macOS users can run the Alexa Auto SDK Builder using Docker for Mac; see Builder setup in a Docker environment below.

Note: For QNX targets, you must install the QNX 7.0 SDP within your host.

Builder setup on a desktop Linux host

To run the Alexa Auto SDK Builder natively, please follow the guide below. Ubuntu 16.04 LTS was tested and is recommended as the Linux host environment.

Set up OpenEmbedded/BitBake

First you will need to set up OpenEmbedded-Core.

The following example will install OpenEmbedded-Core and BitBake under your home directory. Note that the variable OE_CORE_PATH must be pointed at the OpenEmbedded-Core source directory.

$ cd ~
$ git clone git://git.openembedded.org/openembedded-core oe-core -b rocko
$ cd oe-core
$ git clone git://git.openembedded.org/bitbake -b 1.36
$ export OE_CORE_PATH=$(pwd)

The minimum requirements to run OpenEmbedded on an Ubuntu Linux host are as follows:

$ apt-get install chrpath diffstat gawk texinfo \
python python3 wget unzip build-essential cpio \
git-core libssl-dev quilt cmake \
libsqlite3-dev libarchive-dev python3-dev \
libdb-dev libpopt-dev

Note: For Linux targets, you must install libssl-dev as well.

$ apt-get install libssl-dev

Builder setup in a Docker environment

To use Builder on macOS hosts, Docker CE for Mac must be installed according to its official guide.

Upon first run, Builder will build the Docker image aac/ubuntu-base:<revision> and create a dedicated Docker volume buildervolume for running the Alexa Auto SDK Builder in your Docker environment. This might take up to an hour to complete.

IMPORTANT NOTE on macOS: If you are trying to build for QNX targets with macOS host, QNX 7.0.0 SDP must be installed within Case-Sensitive file system, with additional Linux tools installation. You may need to use external drive for installation since your system file system is NOT Case-Sensitive by default.

Running Builder

To run the Alexa Auto SDK Builder, invoke the following command. This will generate a complete target installation image. (where AAC_SDK_HOME is the location you've installed the Alexa Auto SDK.)

$ ${AAC_SDK_HOME}/builder/build.sh oe [options]

Note: The first run might take up to an hour to complete while OpenEmbedded generates all necessary toolchains internally.

The following options are available:

  • -h,--help to show full available options.
  • -t,--target <target> to specify cross compilation target. Defaults to native. See the table below for the details.
  • -b,--build-dir <directory> option to specify the working directory for a build. Defaults to ${AAC_SDK_HOME}/builder/build. This option will be ignored when running inside the Docker environment.
  • -g,--debug option to build with debugging options.
  • -c,--clean option to clean build. If the OE recipe name is specified with --package option, the only specified recipe will be cleaned.
  • (Android target only) --android-api <integer> option to explicitly specify Android API level. Defaults to 22.
  • (QNX7 target only) --qnx7sdp-path <path> option to specify QNX 7.0.0 SDP installation (in host). If you run Builder within Docker environment, host QNX SDP tools are always used. So make sure you have installed Linux tools within SDP even if your host is macOS.

The following build targets are available:

Platform Name -t value
Generic Linux native
Android ARMv7a androidarm
Android ARMv8a androidarm64
Android x86 androidx86
Android x86-64 androidx86-64
QNX AArch64 qnx7arm64
QNX x86-64 qnx7x86-64

(Preview) For all other targets/toolchains, please refer to the files meta-aac-builder/conf/machine/*.conf. Those targets are provided by default for Poky based Linux systems:

Note: Using Builder to build the Alexa Auto SDK for macOS targets is not currently supported.

Platform Name -t value
AGL AArch64 aglarm64
(Preview) Poky Linux ARMv7a (+NEON) pokyarm
(Preview) Poky Linux AArch64 pokyarm64

For example, to build all the Alexa Auto SDK modules and their dependencies for an Android ARMv7a target, run the following command:

$ ${AAC_SDK_HOME}/builder/build.sh oe -t androidarm

Install image

After successfully building the image, the output directory deploy/ will be generated under the ${AAC_SDK_HOME}/builder/ directory.

Within the output directory, you will find the tar.gz archive aac-image-minimal-<target>.tar.gz. You may upload this image to your actual target hardware.

aac-image-minimal contains the following build artifacts:

  • /opt/AAC/bin/: cURL binaries with ngHTTP2 enabled
  • /opt/AAC/include/: All dev headers for all dependencies.
  • /opt/AAC/lib/: All shared libraries, including AVS Device SDK, cURL, ngHTTP2.
  • /opt/AAC/share/: CMake files for building external Alexa Auto SDK modules.

If you've built the native target image, then you may install them directly on your Linux PC.

Note: If you've built the image with the -g option, you will find an extra tar.gz archive aac-image-minimal-<target>-dbg.tar.gz, which contains debug symbols for later GDB use.

Note: These binaries use the Alexa Auto SDK C++ API, and cannot be used for Android targets without the Alexa Auto SDK Engine for Android package (JNI API).

Clean build

To build cleanly, following command will remove all caches.

$ ./build.sh oe --clean

Tip: The build.sh script typically performs a clean build. In most situations there is no need for a more thorough clean. When the --clean option is used, the Docker image used for building is purged. Purging the Docker image may cause the next build to take up to an hour to complete because the Docker image is reconstructed.

Build with mbedtls

On some Android Samsung devices, OpenSSL caused the Alexa Auto sample app to terminate. Follow the steps below to use mbedtls.

$ echo "PACKAGECONFIG_pn-curl = \"mbedtls nghttp2\"" >> ${HOME}/aac-extra.conf
$ ${AAC_SDK_HOME}/builder/build.sh oe <options> ${HOME}/aac-extra.conf

Alexa Auto SDK OE layer

Developers who want to integrate Alexa Auto SDK software into existing OpenEmbedded based system can use Alexa Auto SDK OE layer a.k.a meta-aac, without using Alexa Auto SDK Builder.

Note: For Android and QNX targets should use Alexa Auto SDK Builder. This method may require advanced OpenEmbedded system administration skills.

The recommended and tested platform is Poky Linux 2.4 (rocko).

Adding layers and module recipes

You need to add the following OE layers into your setup.

  • Alexa Auto SDK OE layer: ${AAC_SDK_HOME}/builder/meta-aac

Additionally, you may need to add the individual Alexa Auto SDK module recipes by adding them to BBFILES. To add all SDK modules, you can simply add the following line to your bblayers.conf:

Note that ${AAC_SDK_HOME} needs to be interpreted as the actual full path.

BBFILES += "${AAC_SDK_HOME}/modules/*/*.bb"

cURL with ngHTTP2

The curl package must be configured with the nghttp2 feature enabled. The meta-aac layer defines a default PACKAGECONFIG for curl but if your system has its own definition, you need to modify PACKAGECONFIG to include nghttp2.

Note that we provide the default nghttp2 recipe within the meta-aac layer, but you may use other alternatives.

You can’t perform that action at this time.