====== Android BSP======
<alert type="info"> The Android image files are only available on request. Please contact [[Support@tq-group.com?subject=Android BSP Request|Support]]. </alert>

<panel type="primary" title="supported Features">
<grid>
<col sm="6">
^  Feature  ^  Description  ^
| Bootloader  |  u-boot  |
| Display support – HDMI  |  HDMI interface  |
| Display support – LVDS  |  dcss  |
| MIPI-DSI  |  Display interface  |
| Ethernet - SOC  |    |
| PWM  |    |
| SDIO interface (SD card/eMMC)  |  Boot from external SD card or internal eMMC  |
| Touch (i2c/USB)  |  Touch interface  |

</col>
<col sm="6">
^  Feature  ^  Description  ^
| USB 2.0/3.0 - SOC  |    |
| I2C |  100kHz and 400kHz  |
| GPIO  |  Output pins  |
| UART  |  w/o flow control  |
| SPI  |    |
| Audio  |    |
| CPU Power Management  |    |
| PCIe  |    |
</col>
</grid>
</panel>


<panel type="primary" title="Programming via UUU-Tool">

The Android image can be written via a UUU script on SD card and on eMMC of the module
==== UUU over Windows Preparation ====
  - Unpacking the image archive into a folder
  - Download uuu from [[https://github.com/NXPmicro/mfgtools/releases|GitHub]] and save it to the directory with the images.
  - open windows cmd with admin rights
  - use cd to go to the folder where the android files and scripts are located
  - start the UUU script using the command **uuu_imx_android_flash.bat** to get a overview of the available functions
==== Flash module ====
  - connect MBa8Mx via microUSB on X19
  - Set switch S9 to (1)OFF (2)OFF (3)ON (4)OFF (Serial downloader)
  - connect MBa8Mx with power
  - start flash process with the following command (LVDS, eMMC):

<code> uuu_imx_android_flash.bat -f imx8mq -c 7 -u 4g-dual -d dcss-lvds-tm070jvhg33 -e </code>
<alert type="warning" icon="fa fa-warning">currently there is no support for the lcdif-lvds-tm070jvhg33 devicetree!</alert>
++++ Options for script | 
<code>
 options:
  -h                displays this help message
  -f soc_name       flash android image file with soc_name
  -a                only flash image to slot_a
  -b                only flash image to slot_b
  -c card_size      optional setting: 14 / 28
                        If not set, use partition-table.img/partition-table-dual.img (default)
                        If set to 14, use partition-table-14GB.img for 16GB SD card
                        If set to 28, use partition-table-28GB.img/partition-table-28GB-dual.img for 32GB SD card
                    Make sure the corresponding file exist for your platform
  -m                flash mcu image
  -u uboot_feature  flash uboot or spl&bootloader image with "uboot_feature" in their names
                        For Standard Android:
                            If the parameter after "-u" option contains the string of "dual", then spl&bootloader image will be flashed,
                            otherwise uboot image will be flashed
                        For Android Automative:
                            only dual bootloader feature is supported, by default spl&bootloader image will be flashed
                        Below table lists the legal value supported now based on the soc_name provided:
                          
                             soc_name       legal parameter after "-u"                                                                          
                   
                              imx8mq         dual trusty-dual mba8mx-uuu trusty-secure-unlock trusty                                             
                                             2g 2g-dual 2g-trusty-dual 2g-mba8mx-uuu 2g-trusty 2g-trusty-secure-unlock                           
                                             4g 4g-dual 4g-trusty-dual 4g-mba8mx-uuu 4g-trusty 4g-trusty-secure-unlock                           

  -d dtbo_feature   flash dtbo, vbmeta and recovery image file with "dtb_feature" in their names
                        If not set, default dtbo, vbmeta and recovery image will be flashed
                        Below table lists the legal value supported now based on the soc_name provided:
                           
                              imx8mq         hdmi dcss-lvds-tm070jvhg33 lcdif-lvds-tm070jvhg33  

  -e                erase user data after all image files being flashed
  -D directory      the directory of of images
                        No need to use this option if images are in current working directory
  -t target_dev     emmc or sd, emmc is default target_dev, make sure target device exist
  -p board          specify board for imx8mq, since more than one platform we maintain Android on use these chips
                        For imx8mq, this option is only used internally. No need for other users to use this option
                        For other chips, this option doesn't work
  -i                with this option used, after uboot for uuu loaded and executed to fastboot mode with target device chosen, this script will stop
                        This option is for users to manually flash the images to partitions they want to
  -daemon           after uuu script generated, uuu will be invoked with daemon mode. It is used for flash multi boards
  -dryrun           only generate the uuu script under /tmp direcbory but not flash images
  -super            do not generate super.img when flash the images with dynamic partition feature enabled.
                        Under the condition that dynamic partition feature are enabled:
                          if this option is not used, super.img will be generated under current working directory and flashed to the board.
                          if this option is used, make sure super.img already exists together with other images.
</code>
++++

</panel>