User's Guide for NXP i.mx 8M Development Kit for Amazon AVS

Transcription

1 User's Guide Rev. 2, Document Number: IMX8MAVSUG 01/2019 User's Guide for NXP i.mx 8M Development Kit for Amazon AVS 1. Introduction The NXP i.mx 8M Development Kit for Amazon Alexa Voice Service (AVS) enables its wide customer base to easily integrate Alexa into their next generation design based on i.mx processors. The development kit consists of a 2-Mic array and the Pico i.mx 8M development kit, both optimized to deliver a low cost but flexible design to enable fast development to production. To enable customers to deliver a high-quality audio experience we have partnered with DSP Concepts for audio algorithms including echo cancellation, beamforming, and noise reduction to be delivered in software. This results in a single chip solution, lowering overall design cost, while ensuring customers to have the support and expertise needed to deliver a highquality user experience in a short development time. Contents 1. Introduction What s in the kit Amazon account setup Hardware setup Flash the board Install Alexa SDK Running sample AVS App Download MRM packages Testing MRM Enable auto start of Alexa sample Testing audio Testing audio with DSPC Testing Audio without DSPC (or before executing setupavs.sh) References Support Key terms Speaker references Ordering information and web links NXP B.V.

2 What s in the kit This user s guide provides step-by-step instructions for setting up the development kit and accessing and testing Amazon AVS including account, hardware and software setup. When finished, you will have a fully functioning prototype with Alexa built-in that uses the TechNexion Voice Hat 2-Mic Development Kit as an audio front end, and the PICO-PI-IMX8M development board as the processor handling the Alexa wake word recognition and interface to Amazon AVS. The NXP i.mx 8M Development Kit for Amazon AVS is available on and 2. What s in the kit Figure 1. NXP i.mx 8M development kit for Amazon AVS components NOTE Antistatic precautions are recommended for assembling the kit. 2

3 Amazon account setup Figure 2. NXP i.mx 8M Development Kit with connected TechNexion Hat In addition to the kit, you will also require: 1. A windows PC with internet connection and a USB port. 2. USB 5 V power adaptor (or use an USB port capable of sourcing power from a PC). Some PC s may not provide enough power to the board and will re-boot. If this occurs please use a 5V charger current instead. 3. Download the serial-to-usb drivers for serial debugging found here. 4. Multi-Room Music (MRM) feature enables music to be played and controlled across multiple, compatible Alexa devices at the same time. In order to test MRM, you will need a second voice kit or a MRM-enabled Alexa device. NOTE ON SPEAKERS The speakers provided in the kit are for initial prototyping only. For best Acoustic Echo Cancellation (AEC) and Barge-in performance of the voice input system, low distortion audio reproduction is important. High quality speakers are recommended and for space restrained applications, single transducer configurations perform better than multiple transducers with a cross-over network. Go to speaker references section for recommendations. 3

4 Amazon account setup 3. Amazon account setup To setup a developer account with Amazon, please perform the following steps. 1. Create a free developer account at developer.amazon.com. You can review the AVS Terms and Agreements here. Create Alexa Voice Service (AVS) project, as shown in Figure 3. Figure 3. Create Amazon account 2. Follow the steps as explained at Profile#product-information to register your product and create a device and security profile. After entering in the Security Profile and Security Profile description sections, make sure to select Other devices and platforms, as shown in Figure 4. Enter in the Client ID section and select Generate ID. 4

5 Amazon account setup Figure 4. Generate client ID NOTE When prompted for the Client ID, make sure to use the Client ID from the Other devices and platforms section. 3. On the Products page, click Manage and you can view your product details, as shown in Figure 5. Figure 5. Product page When done, the product profile is as shown in Figure 6 to Figure 9. 5

6 Amazon account setup Figure 6. Product Details Information I Figure 7. Product Details Information II 6

7 Amazon account setup Figure 8. Product Details Security Profile I 7

8 Hardware setup Figure 9. Product Details Security Profile II 8

9 Hardware setup 4. Hardware setup This section will describe how to connect the Voice Hat board to the PICO-PI-IMX8M board. 1. Remove the jumpers on J11 on the Pico-Pi baseboard, as shown in Figure 10. Figure 10. J11 on Pico-Pi baseboard 2. Change J2 jumpers to allow the board to boot the preloaded Linux image from emmc, as shown in Figure 11. Figure 11. J2 on Pico-Pi baseboard 3. Verify the pin headers and jumper settings on the back of the audio hat, as shown in Figure 12 and Figure 13. 9

10 Hardware setup Figure 12. Back of Voice HAT (header settings) Figure 13. Back of Voice HAT (switch settings from 1 to 8: ) 4. If using Wifi, connect the antennae to the antennae connector located on the top left of the SOM 5. Install the pin extenders on the Pico-Pi base board. 6. Plug the audio hat into the pin extenders on the Pico-Pi board, as shown in Figure 14 Figure 14. Audio hat plugged into the pico-pi board 10 User's Guide for NXP i.mx 8M Development Kit for Amazon AVS, User's Guide, Rev. 0, 11/2018

11 Flash the board Steps: 1. Plug in the USB-Micro cable into the PC and the Pico-Pi board for serial debug 2. Plug in the USB-C cable into the Pico-Pi board and PC for power 3. Connect the speakers to the audio hat s speaker connectors Figure 15. Hardware connections on the Voice Kit Figure 16. Dev kit plugged-in User's Guide for NXP i.mx 8M Development Kit for Amazon AVS, User's Guide, Rev. 0, 01/

12 Flash the board 5. Flash the board The NXP i.mx 8M Development Kit for Amazon AVS comes pre-loaded with a Yocto Linux image, requiring the user to run the scripts to build and run the sample AVS app. Please check for the latest version of software at microcontrollers/arm-based-processors-and-mcus/i.mx-applications-processors/i.mx-8- processors/i.mx-8m-development-kit-for-amazon-alexa-voice-service:far-field-voice- SERVICES. If the board does not contain an image or if the software is not up-to-date with the latest release, then you can download the image from nxp.com/xxx and flash the board by following the steps described in this section. If you do not wish to flash the image but use the pre-loaded image, skip section 5 Flash the board and go to section 6 Install Alexa SDK. NOTE The image is configured for Pico-8M with 1 GB DDR. Flashing the image on any variant of Pico-8M (such as 2/3 GB) may cause the boot failure. All NXP i.mx 8M Development Kits for Amazon AVS are configured with the correct memory configuration. If you are using a Pico-8M board purchased through a different channel, please confirm the memory configuration before flashing the image. NOTE If needed, download the serial-to-usb drivers found here. 1. Change J2 jumpers to put the Pico-Pi in serial download mode, as shown in Figure 17. Figure 17. Change J2 jumpers 12

13 Flash the board 2. Connect the Pico-Pi to your Windows PC using the provided USB-A to USB-C cable for power. 3. Connect the Pico-Pi to your Windows PC using the provided USB micro cable for serial download. 4. Download the latest manufacturing tool, pico-imx8m_mfgtool-xxxxx.zip, from ftp://ftp.technexion.net/development_resources/development_tools/installer/. 5. Extract the zip file to your Windows PC. 6. Navigate to mfgtools-without-rootfs_for_all_ddr\mfgtools-without-rootfs\mfgtools. 7. Double click the mfgtool2-wand_pi_8m-attach_emmc_as_usb_mass_storage.vbs to run the VBScript, as shown in Figure 18. Figure 18. Run VBScript 8. Click the Start button and wait for the progress bar to 100%, as shown in Figure 19. Figure 19. Progress of running VBScript 9. Download the demo image package from microcontrollers/arm-based-processors-and-mcus/i.mx-applications-processors/i.mx-8- processors/i.mx-8m-development-kit-for-amazon-alexa-voice-service:far-field-voice- SERVICES and extract the compressed image file. 10. Download and install Win32 Disk Imager from Use the Win32 Disk Imager to flash the extracted image to the board, as show in Figure

14 Install Alexa SDK Figure 20. Write operation NOTE If Win32 Disk Imager pops up a warning about hardware corruption, just ignore it and proceed. 12. After a successful write, disconnect the USB-C cable and change J2 jumpers back to allow the board to boot from emmc, as shown in Figure 21. Figure 21. J2 jumpers 13. Reconnect the USB-C cable to the Pico-Pi board to boot into the newly-installed image. 14

15 Install Alexa SDK 6. Install Alexa SDK This section describes how to access and test the Amazon sample AVS application. 1. Power on the board. Make sure that everything is connected before the system boots up. See Section 4 Hardware setup. 2. Open a serial console (Putty or Tera Term) on your PC and select the board s COM port number enumerated by the host system. NOTE The USB-serial chip on i.mx 8M enumerates two serial ports. Check both ports for a prompt. If needed, download the serial-to-usb drivers here. Use values shown in Figure 22 in the Port Settings section. Figure 22. Port Settings An NXP welcome prompt pops up, as shown in Figure

16 Install Alexa SDK Figure 23. NXP Welcome display massage 3. On the serial console, press Enter to see the login splash and then login using credential as root. Figure 24. Login as root The first time you boot the image, after login you will be asked to accept the NXP EULA. Please read and accept the NXP License Agreement. 16

17 Install Alexa SDK Figure 25. NXP EULA Acceptance 17

18 Install Alexa SDK 4. Enable Wi-Fi, log in, and connect to the Wi-Fi network with your SSID and password. Run start_wifi.sh with SSID and password as parameters../start_wifi.sh SSID password NOTE You only need to pass the SSID and PASSWORD as arguments the first time you register/connect to a Wi-Fi network. Next time you can run wifisetup.sh without any arguments to connect to the latest Wi-Fi network you have registered. Figure 26. Connecting to Wi-Fi network log NOTE Use quotation marks if your SSID or password has spaces, as shown in Figure 26. Check whether you have obtained a valid IP address from your Wi-Fi network. Use ifconfig to check your IP address. 18

19 Install Alexa SDK Figure 27. Check IP address 5. Alexa Multi-Room Music (MRM) is a feature that enables music to be played and controlled across multiple, compatible Alexa devices at the same time. If you wish to enable this feature, go to Section 8 Download MRM packages to download the required MRM packages. NOTE You will need an additional kit or an MRM enabled Alexa device to test MRM in Section 9 Testing MRM. If you wish to test the audio before downloading the Alexa SDK, see Section 11 Testing audio. 6. We are ready to start the installation of the Alexa SDK now. Go to /home/root/alexa_sdk directory and run the setupavs.sh script to start. Change to the Alexa_SDK directory and run the setupavs.sh script. cd ~/Alexa_SDK./setupAVS.sh NOTE You need to run the setupavs.sh again if credentials is reset or changed. The setupavs script will guide you to the Alexa SDK installation on your Pico 8M board. The first time when you run setupavs.sh, it will display as follows: You already have an AVS configuration setup on place... What do you want to do? Start over the whole AVS setup... 1 Just set new AVS Credentials... 2 Calibrate speakers... 3 Type the number of your selection and press Enter... 19

20 Install Alexa SDK Enter 1 for Type the number of your selection and press Enter... then it will ask whether you want to install MRM and DSPC SW. Do you want to install/enable MRM (Multi Room Music) [Y/N]? Do you want to install/enable DSPC SW (Recommended) [Y/N]? Select Y if you want to install MRM and Y if you want to enable DSPC software (recommended). MRM is for enabling the Multi-Room-Music functionality on Alexa_SDK. Use of MRM and other Amazon software is subject to license terms from Amazon, which can be found in the Appendices to the NXP Software License Agreement and any additional terms provided with the delivery of the Amazon software. The DSPC Software is the Audio Front End for (Acoustic Echo Cancelation, Beamforming, and so on) used for the Pico8M + VoiceHat kit. Figure 28. Run the setupavs.sh script If you have enabled MRM, the setupavs.sh script will use the two copied packages to install the MRM library and apply the patch to the Alexa_SDK. A successful installation message pops up, as shown in 29. Figure 29. Successful MRM installation 20

21 Install Alexa SDK If you have enabled the DSPC SW, the Audio Weaver libraries will be downloaded (from github) and installed. Since this package is downloaded by the script, you need to read and accept the DSPC license, so this can be installed. 21

22 Install Alexa SDK Figure 30. DSPC installation by setupavs.sh script The license will be displayed on the console. Press the Space or Enter to scroll down. Enter Y to accept the DSPC license. Do you accept this DSPC license agreement?[y/n]: Y Figure 31. Accepting DSPC license 22

23 Install Alexa SDK Everything is now installed and ready for building the Alexa SDK. To build the Alexa SDK, please perform the following steps. a) A configuration (cmake type) messages is displayed before the compilation begins, as shown in Figure 32. Figure 32. Configuring the build for MRM and DSPC b) If it is the first time that the Alexa SDK is compiled in your Pico 8M, the compilation process may take about 45 min. Figure 33. Compiling Alexa SDK c) Make sure that the 100% of the build is reached, as shown in Figure 33. Figure 34. Build of Alexa SDK successfully completed d) Set your AVS credentials before starting and running the Alexa Sample App. 7. Find your AVS credentials created in Section 3 Amazon account setup. 23

24 Running sample AVS app Figure 35. Check your product and Amazon IDs NOTE When prompted for the Client ID, make sure to use the Client ID from Other devices and platforms. Figure 36. Check your client ID 24

25 Running sample AVS app Enter your Product ID, Client ID, Serial number and Amazon ID, and choose locale. You can use the same ProducID and ClientID for several devices as long as you use a different Serial number for each device. Serial number can be any alphanumeric combination you choose, but needs to be unique for each device. Figure 37. Enter your AVS credentials 25

26 Running sample AVS app Finally, a speaker calibration needs to be performed. This is MANDATORY, if you skip this you will be not able to listen any audio trough the speakers. Ensure BOTH of the speakers are connected before starting the calibration. Once you are ready press Y to start the calibration. Figure 38. Speaker Calibration If the calibration succeeds you should be able to see a Calibration succeed message. You are now ready to start the Alexa Sample App. Figure 39. Alexa SDK installation successfully completed After successfully configuring Alexa for the first time, if you want to automatically start Alexa after boot without any interaction on the console, you can enable the Auto start mode. See Section 10 Enable auto start of Alexa sample. 26

27 Running sample AVS app 7. Running sample AVS app 1. To run the Alexa sample app, go to the Alexa_SDK directory and execute the runalexasampleapp.sh script, as shown in Figure 40. cd ~/Alexa_SDK./runAlexaSampleApp.sh Figure 40. Run Alexa sample app 2. The first time running the Alexa sample app, you need to authenticate the credentials set in Step 1, as shown in Figure 41. Look for the authentication code and copy it. Figure 41. Look for your authentication code 3. On your PC, open the browser, go to and register your code. You might be asked to sign in with your Amazon developer account (if not signed in yet), as shown in Figure 42. Figure 42. Register your authentication code 27

28 Running sample AVS app 4. Click Allow and the authentication is done, as shown in Figure 43. NOTE The authentication is only performed once per setup or when you change your AVS credentials. Figure 43. Allow authentication 5. Now the Alexa sample app is running, as shown in Figure 44. Figure 44. AVS sample app running 6. A connecting message pops up after the authentication is admitted, as shown in 45. Figure 45. Connecting message 28

29 Download MRM packages 7. If you have enabled MRM, some related log activities occur if there are other Echo or MRM capable devices in the same network, as shown in 46. Figure 46. Logs for MRM activity 29

30 Download MRM packages 8. Download MRM packages When the Alexa SDK is installed on the Pico 8M and two MRM packages are downloaded and placed into the ~/Alexa_SDK/mrm_packages directory on the Pico 8M, MRM can be enabled. The two MRM packages are: MRM Patch for C++ Client SDK File: avs_client_sdk_mrm_patch.1.1.tar.gz Description: Patch to Alexa SDK Source Code to enable MRM MRM SDK for NXP imx 8M File: wha_sdk_nxp-imx8_2018_08_07_12_48_55.tar Description: Library binary for the MRM protocol These two MRM packages are available at: MX8M-DEV-KIT. Sign in to your NXP account or create a new one if you do not have one. You will be asked to accept a license agreement. Figure 47. NXP MRM License Agreement 30

31 Download MRM packages Download the avs_client_sdk_mrm_patch.1.1.tar.gz and the wha_sdk_nxpimx8_2018_08_07_12_48_55.tar to a local directory on your PC. Now we need to copy these packages from your PC to the Pico 8M board. You can use scp or a USB stick to copy these two MRM packages into the ~/Alexa_SDK/mrm_packages directory onto the Pico 8M. Here it is shown how to do it using Drag and Drop using TeraTerm (SCP). Open a new Tera Term window and open a new connection, as shown in Figure 48. Figure 48. Open a new Tera term connection Use the IP address you got with ifconfig (illustrated on previous steps) to open an ssh connection with the Pico8M board and log in as root, as shown in Figure 49 and Figure

32 Download MRM packages Figure 49. Connect by ssh using the Pico 8M IP address Figure 50. Login on Pico 8M as root 32

33

34 Download MRM packages With TeraTerm you can drag and drop (one by one) the files. You only need to specify the destination patch on the popup window and click SCP, as shown in Figure 51 and Figure 52. Figure 51. Drag and drop tarball packages Figure 52. Set destination path 32

35 Testing MRM 1. Drag and drop both packages (one by one), and the transfer is in progress, as shown in Figure 53. Figure 53. Wait got transfer to be completed To make sure both packages were correctly copied, use the ls command to list the content of the mrm_packages directory. ls ~/Alexa_SDK/mrm_packages Figure 54. List copied MRM packages 33

36 Testing MRM 9. Testing MRM To create MRM group/cluster with Android/IOS app, you need to use the Android or IOS Amazon Alexa app to create a cluster of devices to exercise MRM to download the Amazon Alexa app for your download store. Figure 55. Home on Amazon Alexa app 34

37 Testing MRM To test MRM, please perform the following steps. 1. Check whether the app version is or later. Open the Alexa app, click the Settings, and go to the About Alexa app section, as shown in Figure 56 and Figure 57.Your version should be at least , otherwise you may not be able to see 3 rd party devices (like the Pico 8M) listed for MRM. Figure 56. Go to About Alexa App section 35

38 Testing MRM Figure 57. Check for App version 36

39 Testing MRM 2. Create a new MRM group. a) Click the Settings and go to the Multi-Room-Music section, as shown in Figure 58 and Figure 59. Figure 58. Go to settings 37

40 Testing MRM Figure 59. Go to Multi-Room Music section 38

41 Testing MRM b) Click Create New Group and select one of the names already listed or create a new name for your group. As an example, we use the Everywhere group, as shown in Figure 60 and Figure 61. Figure 60. Click on Create New group 39

42 Testing MRM Figure 61. Selecting Everywhere group 40

43 Testing MRM c) You can see all available devices listed, including the Pico 8M board (if the Alexa Sample App is running), as shown in Figure 62. Figure 62. See your MRM capable devices listed 41

44 Testing MRM d) Select the devices you want to create the cluster and click the Save button. As an example, we select 3 echo Dots and the Pico Pi 8M to form our Everywhere group, as shown in Figure 63. Figure 63. Select devices to form MRM groups 42

45 Enable auto start of Alexa sample e) Wait for the connection to establish, as shown in Figure 64. f) Now you are ready to test MRM. Figure 64. Wait for devices to connect 3. Command Alexa to play on your MRM group. a) Start an utterance, like Alexa. b) Play music on Everywhere. c) Now the devices on the group start playing same music. 43

46 Enable auto start of Alexa sample 10. Enable auto start of Alexa sample When the Wi-Fi is enabled, the setupavs.sh is running, the Alexa Sample is successfully started for the first time, you can enable the auto start mode. With the auto start mode ON, the Alexa Sample can start automatically as the board is powered ON. 1. Make sure that your Wi-Fi setup is already recorded once you have run the script first time. cd ~/Alexa_SDK./wifiSetup.sh <SSID> <PASS> After the reboot, you will be able to connect to the same Wi-Fi network by just running the script without parameters. cd ~/Alexa_SDK./wifiSetup.sh 2. Make sure that the Alexa is already functional and the authentication code has already been setup. If Alexa is responsive with OK, you can run the Alexa Sample app and try utterances. cd ~/Alexa_SDK./runAlexaSampleApp.sh 3. Enable the auto start mode. Run the EnableAutoStart.sh script to enable the Alexa to run as a service on the background at boot. After rebooting the board, the Alexa Sample app will start as a background service process. cd ~/Alexa_SDK./Scripts/EnableAutoStart.sh Reboot Figure 65. Enable auto start After the reboot, the LEDs blink for about three seconds and then stay OFF, which means Alexa is successfully running and ready to response. However, if you see the LEDs stay blinking all the time, then it means Alexa fails to start. One of the reason may be there is not enough time to wait for the Wi-Fi to connect. To solve it, you can edit the runalexaautostart.sh script and increase the sleep time after the wifisetup.sh., as shown in Figure 66. cd ~/Alexa_SDK/Scripts/ vi runalexaautostart.sh 44

47 Testing audio Figure 66. Modify auto start script 45

48 Testing audio 11. Testing audio Before running the Alexa SDK, you need to test the audio function. Depending on the configurations, you need to select a particular asound.conf to install. The TFA Amplifier (on the VoiceHat board) used to drive the speaker, requires a one-time speaker calibration process. If you want to play Audio before running the setupavs.sh (for getting Alexa SDK installed), you will need to perform the calibration by running the run_calibrate_once.sh script on the /home/root/tfa98xx directory. It is mandatory to have BOTH speakers connected before you run the scripts, otherwise the calibration might fail or you might be not able to listen to audio on the speaker when connected. 46

49 Testing audio Figure 67. Speaker calibration script Testing audio with DSPC If you are using a DSPC, an Audio Front process should be running, so that both the playback stream and recording stream are correctly routed to its destination. 1. Replace the asound.conf with the DSPC. NOTE This step is optional. If you are sure to install DSPC during setupavs.sh, you can omit this step. 47

50 Testing audio cp -v /etc/asound.conf /etc/asound.conf.backup cp -v /etc/asound.conf.dspc /etc/asound.conf 2. Start the Audio front-end process. cd ~/afe_process/ pkill wakemsq8v2 nice -n -20./wakemsq8v & 3. Test the arecord. NOTE We kill the wakemsgq8va process, just to make sure the afe process is explicitly initialized again. arecord -V stereo mytest.wav You can see some activities on the recording bar. 4. Test the playback. aplay mytest.wav 5. Return to the original asound.conf (only in case you did Step 1). cp -v /etc/asound.conf.backup /etc/asound.conf 48

51 References Testing Audio without DSPC (or before executing setupavs.sh) If you have not run the setupavs.sh yet or you have selected not to install DSPC, please test the audio with the following steps. 1. Replace the asound.conf with regular asound.conf. cp -v /etc/asound.conf /etc/asound.conf.backup cp -v /etc/asound.conf.regular /etc/asound.conf 2. Make sure the DSP AFE process is not running. pkill wakemsq8v2 3. Test the arecord. arecord -V stereo mytest.wav You can see some activities on the recording bar. 4. Test the playback. aplay mytest.wav 5. Return to the original asound.conf (only in case you did Step 1). cp -v /etc/asound.conf.backup /etc/asound.conf 49

52 References 12. References Support This kit will be supported by NXP via the i.mx Community - When posting a question, please make sure you specify that the question is related to the NXP i.mx 8M Development Kit for Amazon AVS by stating this in the title of the question Key terms Audioweaver BootBomb Speaker references Recommended external speakers: Mackie CR4. NOTE For these speakers, you need to buy connector cables and connector housing that fit the audio hat. Voice HAT compatible connection cable and connector housing: Ordering information and web links The NXP i.mx 8M Development Kit for Amazon AVS is available at: Software image is available at: 50

53 How to Reach Us: Home Page: nxp.com Web Support: nxp.com/support Information in this document is provided solely to enable system and software implementers to use NXP products. There are no express or implied copyright licenses granted hereunder to design or fabricate any integrated circuits based on the information in this document. NXP reserves the right to make changes without further notice to any products herein. NXP makes no warranty, representation, or guarantee regarding the suitability of its products for any particular purpose, nor does NXP assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequential or incidental damages. Typical parameters that may be provided in NXP data sheets and/or specifications can and do vary in different applications, and actual performance may vary over time. All operating parameters, including typicals, must be validated for each customer application by customer's technical experts. NXP does not convey any license under its patent rights nor the rights of others. NXP sells products pursuant to standard terms and conditions of sale, which can be found at the following address: nxp.com/salestermsandconditions. While NXP has implemented advanced security features, all products may be subject to unidentified vulnerabilities. Customers are responsible for the design and operation of their applications and products to reduce the effect of these vulnerabilities on customer s applications and products, and NXP accepts no liability for any vulnerability that is discovered. Customers should implement appropriate design and operating safeguards to minimize the risks associated with their applications and products. NXP, the NXP logo, Freescale, and the Freescale logo are trademarks of NXP B.V. All other product or service names are the property of their respective owners. All rights reserved NXP B.V. Document Number: IMX8MAVSUG Rev. 0 11/2018