~~NOCACHE~~
===== How-to =====

===== Boot loader =====

==== Barebox ====

The TQMa6x modules are mainlined in barebox featuring device tree and SPL support.

<WRAP round important>Please note that TQ systems uses U-Boot for testing and verification. In case
of differences in pin and clock configuration etc. please contact our technical support.</WRAP>
==== U-Boot ====

For details on using U-Boot see [[http://www.denx.de/wiki/view/DULG/UBootCommandLineInterface | U-Boot Command Line Interface]]


=== Booting ===

The default environment is configured to try booting from SD / eMMC card and fall back to booting from net. You can set the environment variable bootcmd, to force either booting from net or from eMMC / SD card:

<code>
TQMa6Q[MBa6x] U-Boot > setenv bootcmd run netboot
TQMa6Q[MBa6x] U-Boot > setenv bootcmd run mmcboot
</code>

=== Update ===

The TQMa6 U-Boot boot loader support update of

  * boot loader
  * kernel
  * devicetree
  * root FS (only for root FS that fits into the RAM)
	 
You can use the update scripts from the U-Boot environment for update:

  * run update_kernel (Linux kernel update)
  * run update_uboot (boot loader update) 
  * run update_fdt (Device Tree update) 


=== Devicetree fit image BSP Rev.0109 ===

== update to fit image ==

With BSP Rev.0109 fdt fit image was introduced, this image contains all devicetree blob files in one file.To select a specific configuration environment variable **fitfdt_part**
By defailt U-Boot is configured for single devicetree. When fdt fit image should be used then U-Boot must be configured and updated as follows:

    - set environment variable **fdt_type** from **single** to **fit**\\ <code>setenv fdt_type fit</code>
    - set environment variable **fitfdt_file** from **imx6q-mba6x.dtb** to **mba6-image-dtb.itb**\\  <code>setenv fdt_file mba6-image-dtb.itb</code>
    - save environment settings\\  <code>saveenv</code>
    - set environment variable **autoload** to **no**\\  <code>setenv autoload no</code>setenv   
    - set ip address manually or get the network configuration via dhcp 
    - set environment variable **serverip** to the ip address where your TFTP server is running\\  <code>setenv serverip xxx.xxx.xxx.xxx</code>     
    - run fdt update <code>run update_fdt</code> 

== using fit image ==


These scripts load the files from the configured tftp server. You need a working network connection.

To update parts of the U-Boot environment or the Device Tree during development you can use also the U-Boot tftp command.	

===== Using different boot media =====

==== Preface ====

<WRAP round important>Switching boot sources is only possible if the BOOT_MODE fuses are not programmed. If configured for "Boot from eFuses" but fuses are not programmed, the boot loader will not be able to determine the boot source. </WRAP>

To enable boot device selection BOOT_MODE has to be set to "Internal Boot". This can be done using DIP switch 
S5 on MBa6x:

^ BOOT_MODE         ^ S5-1 ^ S5-2 ^
| Boot from eFuses  |  0   |  0   |
| Serial Downloader |  0   |  1   |
| Internal Boot     |  1   |  0   |
==== NFS ====

To boot the MBa6x from network you need a working boot loader in SD card or eMMC which is able to get the kernel image over tftp and to provide the kernel with commandline settings for NFS. Depending on the boot loader location the board has to be configured to load the boot loader. See [[.how_to#sd-card|SD card]] and [[.how_to#emmc|eMMC]]. You have to provide the images via tftp and nfs and to configure the boot loader to work with your tftp-server and your nfs-server 

=== U-Boot ===

To enable NFS Boot you have to set the following environment variables (static IP):

  * ipaddr: static IP address of MBa6x
  * serverip: static IP of TFTP / NFS server

To boot type the following command:

<code>
TQMa6Q[MBa6x] U-Boot > run netboot
</code>
==== eMMC ====

To initialize the eMMC with an newly created image follow the instructions below:

  * Use [[.how_to#sd-card|SD card]] boot
  * on your development host add an additional ext3 partition to the SD card
  * copy the uboot_tqma6<q|s>_hd.img file to this partition
  * insert the SD card in MBa6x and boot
  * copy the image to the eMMC using the following commands:    

  root@tqm:~ mount /dev/mmcblk0p4 /mnt
  root@tqm:~ cd /mnt
  root@tqm:/mnt dd if=uboot_tqma6<q|s>_hd.img of=/dev/mmcblk1 bs=1M conv=fsync
  root@tqm:/mnt poweroff

  * remove SD card
  * configure for eMMC boot (see table)

You can also establish an workflow using the Freescale Manufacturing tool.

To boot the MBa6x from an initialized eMMC you have to set DIP switches:

^ DIP  ^ S1  ^ S2  ^ S4 ^
| 1 |  0  |  0  | x  |
| 2 |  1  |  1  | x  |
| 3 |  1  |  0  | x  |
| 4 |  0  |  1  | x  |
| 5 |  0  |  0  | x  |
| 6 |  x  |  0  | x  |
| 7 |  x  |  0  | x  |
| 8 |  x  |  0  | x  |

Power up the MBa6x. 

To boot from eMMC type the following command:

<code>
TQMa6Q[MBa6x] U-Boot > run mmcboot
</code>

To update U-Boot on eMMC you can use workflow:

  * copy U-Boot image to your TFTP Server
  * set U-Boot env uboot to the file name of your U-Boot image
  * use the Macro on U-Boot prompt:

<code>
TQMa6Q[MBa6x] U-Boot > run update_uboot
</code>

<WRAP round tip>You need to use the imx-image not the plain binary image of U-Boot. Image must be written to Sector 2 (1024 Bytes offset) of the eMMC.</WRAP>

==== SD Card ====

Copy the complete system image to an SD card to boot the module via SD card.

<code bash>
$ dd if=platform-MBa6x/images/uboot_tqma6<q|s>_hd.img of=/dev/sd<n> bs=4M conv=fsync
</code>

<WRAP round tip>You have to use the raw device of the SD card not a partition!</WRAP>

To boot the MBa6x from a previously generated SD Card you have to set DIP switches:

^ DIP  ^ S1  ^ S2  ^ S4 ^
| 1 |  0  |  0  | x  |
| 2 |  1  |  0  | x  |
| 3 |  0  |  1  | x  |
| 4 |  1  |  0  | x  |
| 5 |  0  |  1  | x  |
| 6 |  0  |  x  | x  |
| 7 |  0  |  0  | x  |
| 8 |  0  |  0  | x  |

Insert the SD card in X9 of MBa6x and power up the MBa6x.

To boot from eMMC type the following command:

<code>
TQMa6Q[MBa6x] U-Boot > run mmcboot
</code>

<WRAP round tip>You need to use the imx-image not the plain binary image of U-Boot. Image must be written to Sector 2 (1024 Bytes offset) of the SD-card.</WRAP>


==== SPI-NOR ====

Starting with BSP REV.0104 the U-Boot for SPI is built within the BSP. The following configuration is needed to build U-Boot images which stores the environment in SPI-NOR:

  * TQMa6S: TQMa6S_MBa6x_SPI
  * TQMa6Q/D: TQMa6Q_MBa6x_SPI

To boot the MBa6x from SPI NOR on TQMa6x configure DIP switches as followed:

^ DIP  ^ S1  ^ S2  ^ S4 ^
| 1    |  0  |  x  | x  |
| 2    |  0  |  x  | 0  |
| 3    |  1  |  x  | 0  |
| 4    |  1  |  x  | 1  |
| 5    |  x  |  x  | 1  |
| 6    |  x  |  x  | 0  |
| 7    |  x  |  x  | 0  |
| 8    |  x  |  x  | 0  |


<WRAP round tip>You need to use the imx-image, not the plain binary image of U-Boot. Image must be written to 1024 bytes offset from start of flash.</WRAP>


==== SATA ====

<WRAP round important>under construction</WRAP>

===== Change Device Tree =====

The hardware is configured using Device Tree. The Device Tree files for TQMa6x / MBa6x are located in //platform-MBa6x/build-target/linux-<version>/arch/arm/boot/dts/imx6....dts<i>// after the prepare step of the kernel package.

Documentation of Device Tree for your kernel version can be found in the kernel tree under Documentation/devicetree

<WRAP round important>**Attention:** Changes in the build directory are not saved. You need to create a patch to make the changes permanent.</WRAP>

<WRAP round important>**Attention:** Changes of the Device Tree must be compiled. To do this enter the following commands:</WRAP>

<code sh>
$ ptxdist drop dtc extract
$ ptxdist go
$ ptxdist images
</code>

If you only want to update the kernel image you also need to transfer the resulting Device Tree blob to your device. It has to be copied to your tftp directory:

<code sh>
$ cp platform-MBa6x/images/imx6<variant>-mba6x.dtb <your tftp dir>
</code>

And can then be loaded to the device. After saving and resetting the new Device Tree will be used.

**U-Boot**

<code sh>
TQMa6S[MBa6x] > printenv fdt_file
</code>

Check name if settings and file name are correct

<code sh>
TQMa6S[MBa6x] > run update_fdt
</code>

===== Load / Change / Save the Device Tree under U-Boot =====

With "fdt" command under U-Boot we can edit the Devicetree

1) Load the fdt from mmc in to RAM
<code> mmc dev ${mmcdev}; mmc read ${fdt_addr} ${fdt_start} ${fdt_size}; </code>
2) Set your $fdt_addr as fdt address for the fdt command
<code> fdt addr ${fdt_addr}</code>
3) Resize the fdt to "+4k" 
<code> fdt resize </code> 

4) Identify your tree in the Device Tree 
<code> fdt print - recursive print of your path (e.g / -> Prints the whole Devicetree. /soc -> everything under "/soc")
 fdt list - Prints only the Top level of path (e.g / -> Lists only the "First" Level. /soc -> Prints the First level of all devices under "/soc"  </code>

5) Change values of properties
<code> fdt set "your path" "your property" "your value" e.g:
fdt set /display@0 status okay </code>

6) Write the changed Device Tree from RAM to mmc
<code> 'mmc dev ${mmcdev}; mmc write ${fdt_addr} ${fdt_start} ${fdt_size};' </code>
<WRAP round tip>For testing purpose only. For bigger changes, please compile the Devicetree</WRAP>
===== Change / adapt display type =====

<WRAP round tip>Configuration of display type and display support depends on the kernel version used
since the drivers are at least partly in staging.</WRAP>

When displays or display settings are altered the device tree has to be modified.
See [[en:arm:tqma6x:linux:how_to#change_device_tree|here]] how to change device tree.

==== Configure HDMI ====

Beginning with **Linux 3.16-rc5** (BSP REV.0104) a devicetree with special settings for HDMI is compiled.

<WRAP round tip>Correct working of the HDMI driver depends on the function of the HPD signal of the Monitor.</WRAP>


==== Configure parallel display ====

<WRAP round important>under construction</WRAP>

Beginning with **Linux 3.16-rc5** (BSP REV.0104) a devicetree with special settings for parallel display is compiled.
To change the display type, you need to change the default timing and - in case timing is not supplied yet - the 
correct display timing has to be entered in device tree.




==== Configure LVDS ====

To use LVDS display with frame buffer support, make sure to disable other displays in the device tree (set the status property of the node to "disabled").

To enable the LVDS output you have to 

  * enable the LDB and the LBD port(s) in arch/arm/boot/dts/imx6qdl-mba6x.dtsi
  * configure video timing for your display

Timing examples:

**Sharp lq085y3lg13**

<code>
                       lq085y3lg13 { /* needs fsl,data-width = <18> */
                                 clock-frequency = <26200000 26600000 27000000>;
                                 hactive = <800>;
                                 vactive = <480>;
                                 hfront-porch = <10>;
                                 hback-porch = <0>;
                                 hsync-len = <255>; /* FIXME: typ < 256!!*/
                                 vback-porch = <0>;
                                 vfront-porch = <2>; /* move 2 lines up */
                                 vsync-len = <40 45 50>;
                                 de-active = <1>;
                                 hsync-active = <0>;
                                 vsync-active = <0>;
                         };
</code>

**AUO auo-g156-xw01**

<code>
                         auo-g156-xw01 {
                                 clock-frequency = <60000000 76000000 90000000>;
                                 hactive = <1366>;
                                 vactive = <768>;
                                 hfront-porch = <10>;
                                 hback-porch = <10>;
                                 hsync-len = <80 200 570>;
                                 vback-porch = <100>;
                                 vfront-porch = <10>;
                                 vsync-len = <10 38 120>;
                                 de-active = <1>;
                                 hsync-active = <0>;
                                 vsync-active = <0>;
                         };
</code>

**CHIMEI g104-x1**

<code>
                        chimei-g104-x1 {
                                 clock-frequency = <55000000 65000000 75000000>;
                                 hactive = <1024>;
                                 vactive = <768>;
                                 hfront-porch = <75>;
                                 hback-porch = <10>;
                                 hsync-len = <76 255 776>; /* FIXME: typ < 256!*/
                                 vback-porch = <100>;
                                 vfront-porch = <10>;
                                 vsync-len = <2 38 182>;
                                 de-active = <1>;
                                 hsync-active = <0>;
                                 vsync-active = <0>;
                         };
</code>

**CHIMEI g070y2-l01**

<code>
                         chimei-g070y2-l01 {
                                 clock-frequency = <27000000 29500000 33000000>;
                                 hactive = <800>;
                                 vactive = <480>;
                                 hfront-porch = <0>;
                                 hback-porch = <0>;
                                 hsync-len = <130 192 290>;
                                 vback-porch = <0>;
                                 vfront-porch = <2>;
                                 vsync-len = <10 20 70>;
                                 de-active = <1>;
                                 hsync-active = <0>;
                                 vsync-active = <0>;
                         };
</code>
                         
===== Compile kernel / boot loader outside of the BSP =====

<WRAP round important>  
  * TQ System GmbH development and testing is done under the documented environment. Please consider to use the same environment for testing if you think there are issues. 
  * BSP consists of boot loader, kernel, root FS **and** plumbing for patching, configuration and building images.
</WRAP>

==== The big picture ====

Changes to mainline sources of Linux kernel and boot loader are provided in the form of patch series. These series are located inside patches directory of the BSP. These directories are either directly under the BSP root or at the same location as the platformconfig file for your hardware platform.

The series file describes the order how patches have to be applied. Please note that the patch series are against the documented versions of the boot loader or kernel.

<WRAP round tip>If the first patch in the series is a tar.bz2 blob that means this will be a patch that raises the patchlevel from the base version to the bugfix version (for instance from Linux 3.2 mainline to Linux 3.2.20 stable)</WRAP>

==== Configuration ====

Configuration info is located at the following places:

  * Linux: kernel configuration file is named kernelconfig.x.y and is located at the same location as the platformconfig file for your hardware platform.
  * barebox: kernel configuration file is named barebox-<version>.config and is located at the same location as the platformconfig file for your hardware platform. The same applies for changes to the barebox default environment. 
  * U-Boot: U-Boot configuration string can be found in the PTXdist hardware configuration settings. Currently the following configurations are supported:
    * TQMa6Q_MBa6x_MMC
    * TQMa6Q_MBa6x_SPI
    * TQMa6S_MBa6x_MMC
    * TQMa6S_MBa6x_SPI

==== Tools ====

The following list is a selection of tools that are able to work with patch series:

  * stg (Stacked git)
  * quilt
  * git quiltimport (from the git-sh extension) 

Read manual pages how to use the tools.

==== Steps ====

  * Get sources of the versions to build
  * Apply patches from BSP
  * Configure packages using the configuration from the BSP
  * Build


===== Setup the Ethernet devices under U-Boot =====

==== USB-ETH ====
1) Start to detect USB device
 <code> usb start </code>

2) To use it under U-Boot you have to change the active Ethernet device
<code> setenv ethact sms0 </code>
<WRAP round tip>Available Ethernet devices are "sms0"(X12) and "FEC"(X11) </WRAP>

<WRAP round info>if no link activity shown in U-Boot see [[en:arm:tqma6x:linux:known_issues#u-boot|Known Issues]] </WRAP>

===== Using the CAN Interface =====
==== Configuration of canX on MBa6x (BSP Rev.0100)====
To configure the CAN interface use the canconfig command.

SYNTAX: 
<code>
root@MBa6x:/dev canconfig
usage:
        canconfig <dev> bitrate { BR } [sample-point { SP }]
                BR := <bitrate in Hz>
                SP := <sample-point {0...0.999}> (optional)
        canconfig <dev> bittiming [ VALs ]
                VALs := <tq | prop-seg | phase-seg1 | phase-seg2 | sjw>
                tq <time quantum in ns>
                prop-seg <no. in tq>
                phase-seg1 <no. in tq>
                phase-seg2 <no. in tq
                sjw <no. in tq> (optional)
        canconfig <dev> restart-ms { RESTART-MS }
                RESTART-MS := <autorestart interval in ms>
        canconfig <dev> ctrlmode { CTRLMODE }
                CTRLMODE := <[loopback | listen-only | triple-sampling | berr-reporting] [on|off]>
        canconfig <dev> {ACTION}
                ACTION := <[start|stop|restart]>
        canconfig <dev> clockfreq
        canconfig <dev> bittiming-constants
        canconfig <dev> berr-counter

</code>

To configure the CAN0 interface with a bitrate of 125000 
<code>root@MBa6x: canconfig can0 bitrate 125000
root@MBa6x:/ ifconfig can0 up
root@MBa6x:/ ifconfig can0
t@MBa6x:/ ifconfig can0
can0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          UP RUNNING NOARP  MTU:16  Metric:1
          RX packets:11 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:142

</code>

----

=====  WEIM bus =====
<WRAP round info 60%>
The term "wireless" does not imply that the WEIM is literally an interface
without wires. It simply means that this module was originally designed for
wireless and mobile applications that use low-power technology.

The actual devices are instantiated from the child nodes of a WEIM node.
</WRAP>

==== Device tree documentation ==== 
=== Required properties: ===



**- compatible:**\\            
Should contain one of the following:\\  
"fsl,imx1-weim"\\  
"fsl,imx27-weim"\\  
"fsl,imx51-weim"\\  
"fsl,imx50-weim"\\  
"fsl,imx6q-weim"\\  
**- reg:**\\                   
A resource specifier for the register space\\  
(see the example below)\\  
**- clocks: **\\               
the clock, see the example below.\\  
**- #address-cells:**\\        
Must be set to 2 to allow memory address translation\\ 
**- #size-cells:**\\           
Must be set to 1 to allow CS address passing\\ 
**- ranges:**\\                
Must be set up to reflect the memory layout with fourinteger values for each chip-select line in use:\\  
<cs-number> 0 <physical address of mapping> <size>

=== Optional properties: ===

**- fsl,weim-cs-gpr:**\\     
For "fsl,imx50-weim" and "fsl,imx6q-weim" type of devices, it should be the phandle to the system General Purpose Register controller that contains WEIM CS GPR register, e.g. IOMUXC_GPR1 on i.MX6Q.  IOMUXC_GPR1[11:0] should be set up as one of the following 4 possible values depending on the CS space configuration.


 
                              
^  IOMUXC_GPR1 [11:0]]  ^  CS0  ^  CS1  ^  CS2  ^  CS3  ^
^  05  |  128M  |  0M  |  0M  |  0M  |                               
^  033  |  64M  |  64M  |  0M  |  0M  |
^  0113  |  64M  |  32M  |  32M  |  0M  |
^  01111  |  32M  |  32M  |  32M  |  32M  |
In case that the property is absent, the reset value or what bootloader sets up in IOMUXC_GPR1[11:0] will be used.


<WRAP round important 50%> Timing property for child nodes. It is mandatory, not optional.</WRAP>


**- fsl,weim-cs-timing:**\\    
The timing array, contains timing values for the child node. We can get the CS index from the child node's "reg" property. The number of registers depends on the selected chip.\\  
  
For i.MX35 ("fsl,imx27-weim") there are three registers: CSCRxU, CSCRxL, CSCRxA.\\  
For i.MX53 ("fsl,imx50-weim") and i.MX6Q("fsl,imx6q-weim")and i.MX6DL("fsl,imx6q-weim") and there are six registers: CSxGCR1, CSxGCR2, CSxRCR1, CSxRCR2, CSxWCR1, CSxWCR2.\\  


==== Example for WEIM Bus ==== 
  * Example code for Linux 3.14
  * Customized pinmuxing
  * Customized timing  
  * For Linux 3.16<wrap hi> fsl,weim-cs-gpr = <&gpr>;</wrap> must be added
  * Line 15 <wrap hi><mainboard-name></wrap> must be customized
  * Line 18 <wrap hi>Mainboard xyz</wrap> must be customized 
  * Line 19 <wrap hi>mainboard</wrap> must be costumized
=== Device tree example ===
<code>

12 /dts-v1/;
13
14 #include "imx6dl-tqma6s.dtsi"
15 #include "imx6qdl-<mainboard-name>.dtsi"
16
17 / {
18         model = "TQ TQMa6S on Mainnboard xyz";
19         compatible = "tq,mainboard", "tq,tqma6s", "fsl,imx6dl";
20
…
215 &iomuxc {
…
454         weim {
455                 pinctrl_weim_1: weim-grp1 {
456                         fsl,pins = <
457 /* (PAD_CTL_DSE_80ohm | PAD_CTL_HYS | PAD_CTL_SPEED_MED) */
458 #define PAD_CTL_EIM_ADDR 0x00010098
459 /* (PAD_CTL_DSE_80ohm | PAD_CTL_HYS | PAD_CTL_SPEED_MED | PAD_CTL_PKE) */
460 #define PAD_CTL_EIM_DATA 0x00011098
461 /* (PAD_CTL_DSE_80ohm | PAD_CTL_HYS | PAD_CTL_SPEED_MED | PAD_CTL_PUS_100K_UP) */
462 #define PAD_CTL_EIM_CTRL 0x0001b098
463 /* (PAD_CTL_DSE_80ohm | PAD_CTL_HYS | PAD_CTL_SPEED_MED) */
464 #define PAD_CTL_EIM_RW  0x00010098
465                                 MX6QDL_PAD_EIM_DA0__EIM_AD00 PAD_CTL_EIM_ADDR
466                                 MX6QDL_PAD_EIM_DA1__EIM_AD01 PAD_CTL_EIM_ADDR
467                                 MX6QDL_PAD_EIM_DA2__EIM_AD02 PAD_CTL_EIM_ADDR
468                                 MX6QDL_PAD_EIM_DA3__EIM_AD03 PAD_CTL_EIM_ADDR
469                                 MX6QDL_PAD_EIM_DA4__EIM_AD04 PAD_CTL_EIM_ADDR
470                                 MX6QDL_PAD_EIM_DA5__EIM_AD05 PAD_CTL_EIM_ADDR
471                                 MX6QDL_PAD_EIM_DA6__EIM_AD06 PAD_CTL_EIM_ADDR
472                                 MX6QDL_PAD_EIM_DA7__EIM_AD07 PAD_CTL_EIM_ADDR
473                                 MX6QDL_PAD_EIM_DA8__EIM_AD08 PAD_CTL_EIM_ADDR
474                                 MX6QDL_PAD_EIM_DA9__EIM_AD09 PAD_CTL_EIM_ADDR
475                                 MX6QDL_PAD_EIM_DA10__EIM_AD10 PAD_CTL_EIM_ADDR
476                                 MX6QDL_PAD_EIM_DA11__EIM_AD11 PAD_CTL_EIM_ADDR
477                                 MX6QDL_PAD_EIM_DA12__EIM_AD12 PAD_CTL_EIM_ADDR
478                                 MX6QDL_PAD_EIM_DA13__EIM_AD13 PAD_CTL_EIM_ADDR
479                                 MX6QDL_PAD_EIM_DA14__EIM_AD14 PAD_CTL_EIM_ADDR
480                                 MX6QDL_PAD_EIM_DA15__EIM_AD15 PAD_CTL_EIM_ADDR
481                                 MX6QDL_PAD_EIM_A16__EIM_ADDR16 PAD_CTL_EIM_ADDR
482                                 MX6QDL_PAD_EIM_A17__EIM_ADDR17 PAD_CTL_EIM_ADDR
483                                 MX6QDL_PAD_EIM_A18__EIM_ADDR18 PAD_CTL_EIM_ADDR
484                                 MX6QDL_PAD_EIM_CS0__EIM_CS0_B PAD_CTL_EIM_CTRL
485                                 MX6QDL_PAD_EIM_OE__EIM_OE_B PAD_CTL_EIM_CTRL
486                                 MX6QDL_PAD_EIM_RW__EIM_RW PAD_CTL_EIM_RW
487                                 MX6QDL_PAD_CSI0_DATA_EN__EIM_DATA00 PAD_CTL_EIM_DATA
488                                 MX6QDL_PAD_CSI0_VSYNC__EIM_DATA01 PAD_CTL_EIM_DATA
489                                 MX6QDL_PAD_CSI0_DAT4__EIM_DATA02 PAD_CTL_EIM_DATA
490                                 MX6QDL_PAD_CSI0_DAT5__EIM_DATA03 PAD_CTL_EIM_DATA
491                                 MX6QDL_PAD_CSI0_DAT6__EIM_DATA04 PAD_CTL_EIM_DATA
492                                 MX6QDL_PAD_CSI0_DAT7__EIM_DATA05 PAD_CTL_EIM_DATA
493                                 MX6QDL_PAD_CSI0_DAT8__EIM_DATA06 PAD_CTL_EIM_DATA
494                                 MX6QDL_PAD_CSI0_DAT9__EIM_DATA07 PAD_CTL_EIM_DATA
495                         >;
496                 };
497         };
498 };
…
&weim {
</code>
=== Example Code for TQMa6S ===
<code>
597         pinctrl-names = "default";
598         pinctrl-0 = <&pinctrl_weim_1>;
599         /* <cs-number> 0 <physical address of mapping> <size> */
600         ranges = <0 0 0x08000000 0x08000000>;
601         #address-cells = <2>;
602         #size-cells = <1>;
603         status = "okay";
604
605         sram@0,0 {
606                 compatible = "tq,sram";
607                 #address-cells = <1>;
608                 #size-cells = <1>;
609                 reg = <0 0 0x0080000>;
610                 bank-width = <1>;
611                 /* optimized settings for device at CS0 */
612                 /* CSxGCR1, CSxGCR2, CSxRCR1, CSxRCR2, CSxWCR1, CSxWCR2 */
613                 /*
614                  * timing for SRAM: we have 8 Bit data and 19 Bit
615                  * address
616                  */
617                 fsl,weim-cs-timing = <
618                         0x60240001 0x00001000 0x07f11101
619                         0x00000000 0x0f249241 0x00000000
620                 >;
621         };
622 };
</code>

----

===== Configure and use PWM Backlight =====

<WRAP round info 60%>
the following information is based on Linux kernel 3.16
</WRAP>

  * Pins (GPIO,PWM) must be configured
  * The power-supply property could refer to a logical always-on device
  * Required Kernel configuration:
    - PWM support
    - PWM backlight support
    - regulator support

==== Device tree documentation ==== 
=== Required properties: === 

 - **compatible:**"pwm-backlight"\\
 - **pwms:** OF device-tree PWM specification (see PWM binding[0])\\
 
 - **brightness-levels:** Array of distinct brightness levels. Typically these are in the range from 0 to 255, but any 
 range starting at 0 will do. The actual brightness level (PWM duty cycle) will be interpolated from these values. 
 0 means a 0% duty cycle (darkest/off), while the last value in the array represents a 100% duty cycle (brightest).
 
 - **default-brightness-level:** the default brightness level (index into the array defined by the "brightness-levels" property)
 
 - **power-supply:** regulator for supply voltage

=== Optional properties: ===

 - **pwm-names:** a list of names for the PWM devices specified in the\\
 "pwms" property (see PWM binding[0])\\
 
 - **enable-gpios:** contains a single GPIO specifier for the GPIO which enables\\
 and disables the backlight (see GPIO binding[1])\\

 [0]: Documentation/devicetree/bindings/pwm/pwm.txt\\
 [1]: Documentation/devicetree/bindings/gpio/gpio.txt
   
=== Device tree example TQMa6x / MBa6x (BSP0104/Linux kernel 3.16) ===
<code>
51         backlight_ldb: backlight@0 {
52                 compatible = "pwm-backlight";
53                 pwms = <&pwm1 0 62500>;
54
55                 brightness-levels = <0 96 128 160 192 224 255>;
56                 default-brightness-level = <5>;
57
58                 power-supply = <&vcc3v3>;
59                 enable-gpios = <&gpio4 5 GPIO_ACTIVE_HIGH>;
60
61         };
…
152         regulators {
153                 compatible = "simple-bus";
154                 #address-cells = <1>;
155                 #size-cells = <0>;
…
175                 vcc3v3: regulator@2 {
176                         compatible = "regulator-fixed";
177                         reg = <2>;
178                         regulator-name = "vcc3v3";
179                         regulator-min-microvolt = <3300000>;
180                         regulator-max-microvolt = <3300000>;
181                 };
…
336 &iomuxc {
337         pinctrl-names = "default";
338         pinctrl-0 = <&pinctrl_hog>;
…
445         hog {
446                 pinctrl_hog: hoggrp-1 {
447                         fsl,pins = <
…
451                                 MX6QDL_PAD_GPIO_19__GPIO4_IO05 0x80000000 /* LCD.BLT_EN */
…
486                         >;
487                 };
488         };
…
637 };

530         pwm1 {
531                 pinctrl_pwm1_mba6x: pwm1grp-mba6x-1 {
532                         fsl,pins = <
533                                 /* 100 k PD, DSE 120 OHM, SPPEED LO */
534                                 MX6QDL_PAD_GPIO_9__PWM1_OUT 0x00003050
535                         >;
536                 };
537         };
…
732 &pwm1 {
733         status = "okay";
734         pinctrl-names = "default";
735         pinctrl-0 = <&pinctrl_pwm1_mba6x>;
736 };
…
</code>

===== TQMa6x serial downloader =====

<WRAP round important> You have to set the Starterkit to boot-mode "serial downloader", please see [[en:arm:tqma6x:mba6x:dip_switches|MBa6x DIP switch settings]]
</WRAP>
<WRAP round info>
We recommend to use Ubuntu 14.04 64bit for the imx-usb tool
</WRAP>


Starting with TQMa6x-BSP-REV.0109 we deliver a Linux tool to upload U-Boot into the TQMa6X RAM from your development host and start it.
After building the BSP the tool is located under \\   
**.../TQMa6x-BSP-REV.0109/platform-MBa6x/packages/h-imx_usb_loader-master**\\  

You have to apply the following steps before you can start to work with the tool:

  * Copy the content of folder .../TQMa6x-BSP-REV.0109/platform-MBa6x/packages/h-imx_usb_loader-master/usr/etc/ to /etc 
  * Copy the content of folder .../TQMa6x-BSP-REV.0109/platform-MBa6x/packages/h-imx_usb_loader-master/usr/bin/ to /bin
 
==== Usage of serial downloader tool ==== 

  - Set Starterkit to boot-mode "serial downloader", please see [[en:arm:tqma6x:mba6x:dip_switches|MBa6x DIP switch settings]]
  - Connect Starterkit connector X8 (Micro USB cable provided with the Starterkit) to your host
  - Connect Starterkit connector X15 (RS232) to your host
  - Power up Starterkit
  - Please check that Linux recognized a new USB device, see output of command **dmesg | grep -i usb**. You should see something like the following :<code>usb 1-1: Manufacturer: Freescale SemiConductor Inc 
hid-generic 0003:15A2:0054.0002: hiddev0,hidraw1: USB HID v1.10 Device [Freescale SemiConductor Inc  SE Blank ARIK] on usb-0000:02:03.0-1/input0
</code>
  - Open a serial terminal on your host e.g. TeraTerm
  - Open a Linux terminal and naviagate to folder "images" in the BSP dirctory\\  e.g. **/home/embedded/TQMa6x-BSP-REV.0109/platform-MBa6x/images**\\   
  - Start the serial downloader **imx_usb** as super user with the desired U-Boot as parameter <WRAP round important>Keep in mind to select a U-Boot that is corresponding to your module, please see [[intern:arm:tqma6x:linux:deployment|]]</WRAP>e.g.<code>embedded@ubuntu:~/workspace/TQMa6x-BSP-REV.0109/platform-MBa6x/images$ sudo imx_usb u-boot-TQMa6Q_MBa6x.imx</code>host console output after starting the serial downloader<code>config file </etc/imx-loader.d/imx_usb.conf>
vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf
vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf
vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf
vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf
vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf
vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf
vid=0x066f pid=0x37ff file_name=linux_gadget.conf
config file </etc/imx-loader.d/mx6_usb_work.conf>
parse /etc/imx-loader.d/mx6_usb_work.conf
15a2:0054(mx6_qsb) bConfigurationValue =1
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename u-boot-TQMa6Q_MBa6x.imx
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 2
jump_addr 0x00000000
== end work item
main dcd length 308
sub dcd length 304

loading binary file(u-boot-TQMa6Q_MBa6x.imx) to 4fbff400, skip=0, fsize=5cc00 type=aa

<<<379904, 379904 bytes>>>
succeeded (status 0x88888888)
jumping to 0x4fbff400
</code>
  - Now you can see the U-Boot messages in the serial terminal programm

Next steps are:\\
  * write U-Boot from tftp to eMMC, see [[en:arm:tqma6x:linux:deployment#updating_existing_firmware_over_ethernet|Updating existing firmware over ethernet]]  
  * write kernel image from tftp to eMMC, see [[en:arm:tqma6x:linux:deployment#updating_existing_firmware_over_ethernet|Updating existing firmware over ethernet]]