查看“MY-IMX6-EK314 Linux-3.0.35 Test Manual”的源代码

<div>

= '''Preparation before test''' =
----
1）Please refer to"Connection of the evaluation board to the computer"in 《MY-IMX6-EK314 booting manual》 for the connection.<br>
	
2）Please refer to"booting of the evaluation board to the computer"in 《MY-IMX6-EK314 booting manual》 for the booting.<br>
	
= '''Test item''' =
----
== '''Lan port test''' ==
MY-I.MX6 evalution board support dual lan port(1 100M network port and 1 Gigabit network port)<br>
===  Test instruction ===
* The first ethernet lan port is “U12”on front view of base board，the second one is “P1”on front view of base board.<br>

=== Test method ===
1）	Test the first ethernet lan port<br>
* Connect lan line：connect “U12”on evaluation board with computer lan port through network<br>
* set computer IP：set computer lan port IP as 192.168.18.18<br>
[[File:MY-IMX6-EK314 L3035_2.1.2.1.png]]<br>
* Set the evaluation board IP：<br>
::$ ifconfig eth0 192.168.18.36　　　　		　	＃ configure the eth0<br>
* run test command ：<br>
::$ ifconfig eth1 down			　　　　		　	＃ eth1 to be shut down<br>
::$ ping 192.168.18.18 -c 2 -w 4	　　　　		　＃ send ICMP to HOST<br>
* Observe test result：system will output following information：：<br>
--- 192.168.18.18 ping statistics ---<br>

2 packets transmitted, 2 packets received, 0% packet loss

* Test result：“0% packet loss”represent test passing<br>
* reference symbols<br>
[[File:MY-IMX6-EK314 L3035_2.1.2.2.png]]<br>
2）Test the second ethernet lan port<br>
* connect lan line：take out lan line from the first lan port then plug in “P1”on evaluation board，another end of lan line is kept in connection with lan port of computer.<br>
* Set computer IP：set computer lan port IP as 192.168.18.18（if the setting was already done then go direclty into next step）.<br>
* Set the second lan port IP：<br>
::$ ifconfig eth1 192.168.18.27	　　　　		　＃ configure the eth1<br>
After the setting system will output working condition of the second lan port, as below：<br>
smsc95xx 1-1.1:1.0 eth1: link up, 100Mbps, full-duplex, lpa 0x4DE1<br>
*Run test command：<br>
::$ ifconfig eth0 down		　　　　				　＃ eth0 to be shut down<br>
::$ ping 192.168.18.18 -c 2 -w 4			　　　　　＃ send ICMP to HOST<br>
* Observe test result：system will output the following message：<br>
--- 192.168.18.18 ping statistics ---

2packets transmitted, 2 packets received, 0% packet loss

* Test result：“0% packet loss”represent test passing.<br>
* reference symbols<br>
[[File:MY-IMX6-EK314 L3035_2.1.2.3.png]]<br>
== '''USB Test''' ==
=== Test instruction ===
MY-IMX6-EK314evaluation board has two USB HOST ports，in“J2”in base board。<br>
===  Test  method ===
1）	Start test<br>
plug USB device in USB port in base board，system will output the following message：<br>
::usb *-*.*: new high speed USB device number * using fsl-ehci<br>
……<br>
2）	Test end<br>
Take out USB device from the base board，system will output the following message：<br>
::usb *-*.*: USB disconnect, device number *<br>
===  reference symbols ===
[[File:MY-IMX6-EK314 L3035_2.2.3.1.png]]<br>
== '''SD card interface test''' ==
===  Test instruction  ===
SD card interface is in“SD3”in rear view of base board。<br>
===  Start test ===
1）Insert device in SD card slot<br>
Insert SD card in SD card port in base board, system will output following message(see attached image),e.g.SD port is normal：<br>
::mmc*: new high speed SD card at address ****<br>
::mmcblk*: mmcx:xxxx SA**G *.**GiB<br>
::mmcblk*: p*<br>
2）Pop-up device from SD card slot<br>
Press again SD card in SD card slot，base board will pop-up SD card。system will output following message(see attached image),e.g.function of SD card port pop-up is normal：<br>
::mmc*: card **** removed<br>
3）	End test<br>
Take out SD card after SD card pop-up,to end the test.<br>

===  reference symbols ===
[[File:MY-IMX6-EK314 L3035_2.3.3.1.png]]<br>

== '''Audio and video test''' ==
=== Test instruction  ===
This test is to verify the function of video & audio of evaluation board by playing vocal video.br>
===  Test  method ===
1）Prepare test<br>
Connect audio output device to audio element in front view of base board,audio element is “J20”in front view of base board，silkscreened as“HP”.<br>
2）Execute test<br>
Play a video with gplay，commanded as below：<br>
＃ aplay /unit_tests/audio8k16S.wav<br>
The above command will play a file designated by command with aplay.<br>
3）Test result<br>
You can see the vedeo played on display screen of evaluation board and hear the voices outputed by audio device.<br>
===  reference symbols ===
[[File:MY-IMX6-EK314 L3035_2.4.3.1.png]]<br>
== '''Video test''' ==
===  Test instruction  ===
This test is performed by playing the video verification board's audio video feature.<br>
===  Test  method ===
To play a video using gplay, the sample commands are as follows:<br>
＃ gplay /unit_tests/akiyo.mp4<br>
The above command will use the file specified in the gplay play command.<br>
* Test Results<br>
:After executing the above test command, you will see a video image of approximately 1 second on the evaluation board display.<br>
===  reference symbols ===
[[File:MY-IMX6-EK314 L3035_2.5.3.1.png]]<br>
== '''GPIO Test''' ==
=== Test instruction  ===
On the U14 on the front of the MY-IMX6-EK314 backplane, there are 33 GPIOs, one of which acts as a GPIO-LED.<br>
The CPU of the GPIO-LED uses the pin "EIM_D22" and is connected to the "U14:30 pin" on the backplane.<br>
Tip: The GPIO-LED test requires a multimeter. Users without a multimeter can skip to the next test.<br>
=== GPIO-LED（GPIO）Test ===
GPIO's Test method is as follows：<br>
::$ echo 1 > /sys/class/leds/user_led/brightness<br>
Test the U14:30 pin with a multimeter, and you can see that the pin is high level.<br>
::$ echo 0 > /sys/class/leds/user_led/brightness<br>
Test the U14:30 pin with a multimeter, and you can see that the pin is low level<br>
=== Universal GPIO testing ===
Here we take EIM_D21 as an example. Through the schematic we can see that EIM_D21 is finally connected to U14:29.<br>
1）Calculate the serial number of the GPIO<br>
*According to the chip manual, we can find that EIM_D21 PAD can be configured as GPIO3_IO21<br>
*IMX6 GPIO sequence number is calculated as: (where group - 1) * 32 + sequence number, so the pin value of PIO3_IO21 is (3 – 1) * 32 + 21 = 85. <br>
2）Set the IO Number of the GPIO to be tested<br>
::$ IO_NUMBER=85<br>
3）Export GPIO<br>
::$ echo ::${IO_NUMBER} > /sys/class/gpio/export<br>
4）Set the GPIO direction <br>
::$ echo out > /sys/class/gpio/gpio::${IO_NUMBER}/direction<br>
5）Control output <br>
::$ echo 1 > /sys/class/gpio/gpio::${IO_NUMBER}/value<br>
Using the multimeter to test the corresponding pin of IO_NUMBER, you can see that the pin is high level.<br>
::$ echo 0 > /sys/class/gpio/gpio::${IO_NUMBER}/value<br>
Using the multimeter to test the corresponding pin of IO_NUMBER, you can see that the pin is low level<br>
== '''key test''' ==
===  Test instruction  ===
：Here are 4 keys on MY-IMX6-EK314 evaluation board，three of them are custom function keys（SW2：VOL-，SW3: VOL+，SW4: Sleep Wake），and one reset key（SW5：nRE）.test program key_test can test these 3 function keys.<br>

===  Test  method ===
1）Execute test program<br>
press command in terminalto run test program，example as below：<br>
::$ /app_test/key_test<br>
2）proceed with interactive test<br>
press separately SW4、SW3、SW2，system will output corresponding message as below：<br>
key*** Pressed<br>
key*** Released<br>
Message of“key*** Pressed”is outputed with press of key，message of“key*** Released”is outputed with release of key.<br>
3）End test<br>
press “Ctrl”+“C”on computer to send the test program for keys.<br>
Note：press SW1（system will reset and reboot）.<br>
===  reference symbols ===
[[File:MY-IMX6-EK314 L3035_2.7.3.1.png]]<br>
== '''Serial port test''' ==
There are 5 serial ports in MY-IMX6-EK314，4 are user serial ports（in “J12”in front view of base board，silkscreened as“UART”），one is debug serial port（in “P3”in front view of base board，Silk screen is DEBUG）。<br>
===  Test instruction  ===
Instruction of system device file：：<br>
*Device file for debug serial port in the system is ttymxc0，device file for user serial port are ttymxc1、ttymxc2、ttymxc3、ttymxc4.<br>
Instruction for transceiver pin of serial ports and their corresponding device file：<br>
* UART2：send 9，receive 10，ttymxc1 <br>
* UART3：send 13，receive 14，ttymxc2 <br>
* UART4：send 15，receive 17，ttymxc3 <br>
* UART5：send 16，receive 18，ttymxc4 <br>
Tips：transceiver pins of serial port are listed here,but please refer to schematic for definition of all pins of serial port.<br>
=== Serial port test===
1）Test instruction <br>
* Test method instruction：<br>
Adopt method of self-sending & self-receiving of serial port.<br>
*Test result instruction：<br>
The test program sends a string to the serial port and outputs the string received by the serial port.<br>
2）Enter the test program directory<br>
::$ cd /app_test<br>
3）UART2 Test<br>
* Prepare test<br>
Short connect sending pin and receiving pin of serial port 2（no.9 and no.10 pin of J12）.<br>
* Execute test command<br>
::$ ./uart_test /dev/ttymxc1 "www.myzr.com.cn"<br>
* Test result reference symbols<br>
[[File:MY-IMX6-EK314 L3035_2.8.2.1.png]]<br>
4）UART3 Test <br>
* Prepare test<br>
Short connect sending pin and receiving pin of serial port 3（no.12 and no.13 pin of J12）.<br>
* Execute test command<br>
::$ ./uart_test /dev/ttymxc2 "www.myzr.com.cn"<br>
5）UART4 Test<br>
* Prepare test<br>
Short connect sending pin and receiving pin of serial port 4（no.15 and no.17 pin of J1）.<br>
* Execute test command<br>
::$ ./uart_test /dev/ttymxc3 "www.myzr.com.cn"<br>
* Test result figured <br>
[[File:MY-IMX6-EK314 L3035_2.8.2.2.png]]<br>
6）UART5 Test<br>
* Prepare test<br>
Short connect sending pin and receiving pin of serial port 5（no.16 and no.18 pin of J1）。<br>
* Execute test command<br>
::$ ./uart_test /dev/ttymxc4 "www.myzr.com.cn"<br>
* Test result figured<br>
[[File:MY-IMX6-EK314 L3035_2.8.2.3.png]]<br>
== '''RS232 Serial port test''' ==
=== Test instruction  ===
The MY-IMX6-EK314 evaluation panel leads out an RS232 interface through serial port 4, located at the "P2" position (DB9 seat) on the front of the bottom panel.<br>
=== Test  method ===
1）Prepare test<br>
Short connect sending pin and receiving pin of RS232（no.2 and no.3 pin of P2）.<br>
2）Execute test command<br>
::$ ./uart_test /dev/ttymxc3 "www.myzr.com.cn"<br>
Note: since RS232 is introduced through UART4, the test can also follow the method of UART4<br>
3）Test result figured<br>
[[File:MY-IMX6-EK314 L3035_2.9.2.1.png]]<br>

== '''RTC Test''' ==
===  Test instruction  ===
:Due to restrictions in transportation，MY-IMX6-EK314 evaluation board doesn't contatin battery in delivery,before RTC test please prepare button cell to install on “BT1”in rear view of base board（beside silkscreened name of“RTC”）.<br>
	
===  Test  method ===
1）power off then reboot device,to check the time of system and hardware.<br>
:Command to check clock of current system as below：<br>
::$ date <br>
Message outputed by system as below：<br>
Thu Jan  1 00:00:12 UTC 1970<br>
:Command to check clock of RTC chip as below：<br>
::$ hwclock	<br>
Message outputed by system as below：<br>
Tue Nov 30 00:00:00 1999  0.000000 seconds<br>
2）Set system clock and synchronously set to RTC chip<br>
:Command to set system clock are with below reference：<br>
::$ date -s "2015-09-02 12:34:56" <br>
:Command to write system clock into hardware as below：<br>
::$ hwclock –w <br>
3）Power off and reboot evaluation board，to check current system clock and hardware clock<br>
:Please refer to step 1<br>
4）Test result<br>
It will be a newly-set clock after execution until step 3 <br>
=== Reference symbols ===
Below image is screenshots for step1 and step 2 in the test<br>
[[File:MY-IMX6-EK314 L3035_2.10.3.1.png]]<br>
Below image is the screenshots for step3 in the test<br>
[[File:MY-IMX6-EK314 L3035_2.10.3.2.png]]<br>
== '''WatchDog Test''' ==
=== Test instruction  ===
WatchDog consists of 2 items: one is reset test and the other is dog feeding test.<br>
===  Reset test ===
1）Test instruction <br>
Reset test will boot WatchDog，but doesn't feed dog，the system will reset after a timeout.<br>
2）Execute test<br>
::$ /unit_tests/wdt_driver_test.out 10 15 1<br>
3）Test result<br>
Wait for 10 seconds after running of test command，WatchDog timeout，system is resetted。you can see message outputed by system rebooting on terminal.<br>
[[File:MY-IMX6-EK314 L3035_2.11.2.1.png]]<br>
=== Dog feeding test ===
1）Test instruction <br>
The dog feeding test will start the WatchDog and feed the dog once every 2 seconds. The system will not reset due to the timeout of the WatchDog.<br>
2）Execute test<br>
* Booting WatchDog<br>
::$ /unit_tests/wdt_driver_test.out 4 2 1 &<br>
* View current time<br>
::$ date<br>
3）Verification<br>
* View current time<br>
After a few minutes, the system is still not reset.Let's look at the current time.<br>
::$ date<br>
* Stop feeding the dog<br>
At this time, we terminate the Watchdog test program, so there is no program to feed the dog, and the system will reset within the timeout (here is 4 seconds).<br>
::$ ps | grep "/unit_tests/wdt_driver_test.out"<br>
3195root   　　   1464 S  　　  /unit_tests/wdt_driver_test.out 4 2 1<br>
As you can see, the pid of wdt_driver_test.out is 3195. Next, we terminate the process of 3195: <br>
::$ kill 3195<br>
[[File:MY-IMX6-EK314 L3035_2.11.3.1.png]]<br>

== '''SPI Test''' ==
There are a group of SPI ports on MY-IMX6-EK314，located on“J13”，silkscreened as “SPI”。<br>
=== Test instruction  ===
SPI1 is used for SPI Nor Flash.Here we test SPI2.<br>
MISO pin and MOSI pin of SPI port will be used for the test。SMISO pin of SPI port is “no.7 of J13”on the base board，and MOSI pin is “no.11 of J13”.<br>

=== Test method ===
Adopt way of SPI self-sending（output）self-receiving（input）.<br>
1）Prepare test<br>
Short connect MISO pin and MISO pin of SPI port，e.g.short connect pin no.7 and pin no.11 of J13 on the base board.<br>
2）Execute test<br>
::$ /app_test/spi_test -D /dev/spidev1.0<br>
3）Test result<br>
If SPI is normal，you can see on terminal the following charaters：<br>
::FF FF FF FF FF FF <br>
::40 00 00 00 00 95 <br>
::FF FF FF FF FF FF <br>
::FF FF FF FF FF FF <br>
::FF FF FF FF FF FF <br>
::DE AD BE EF BA AD <br>
::F0 0D<br>

=== Figured ===
[[File:MY-IMX6-EK314 L3035_2.12.3.1.png]]<br>

== '''CAN interface test''' ==
=== Test instruction  ===
Oscilloscope will be used for CAN test，please skip this step for users who don't have oscilloscope。<br>
=== Test  method ===
1）Configuration CAN0<br>
:Instanced example as below：<br>
::$ ip link set can0 up type can bitrate 250000 <br>
2）Configuration of link for oscilloscope<br>
Connect CH1 and CH2 with “R83”of evaluation board（the green stand on topside on front view of base board）。<br>
Configure oscilloscope（for users who don't know how to use oscilloscope ,please ask hardware engineers for assistance ）.<br>
3）Execute test command<br>
::$ /app_test/client_test <br>
4）Test result<br>
When exectue the test command,you can see a waving change on oscilloscope <br>
=== Figured ===
[[File:MY-IMX6-EK314 L3035_2.13.3.1.png]]<br>
== '''PCIE interface test''' ==
=== Test instruction  ===
System is already added with drivers for PCI port，in booting system will check out devices on PCI-E interface<br>
=== Test  method ===
Reset system，observe the message outputed by system booting <br>
1）PCI-E driving program output messages<br>
In the course of system booting, if there is outputed message as below,e.g PCI-E interface load is normal：：<br>
iMX6 PCIe PCIe RC mode imx_pcie_pltfm_probe entering.<br>
PCIE: imx_pcie_pltfm_probe start link up. <br>
2）Message outputed without link of PCI-E device<br>
In the course of system booting，it there is not a valid device linked with PCI-E interface，system will prompt“link down!”on PCI-E port，something as below：<br>
link up failed, DB_R0:0x00801600, DB_R1:0x08200000!<br>
IMX PCIe port: link down! <br>
3）Message outputed when there is a valid PCI-E device linked（here take Intel 4965AGN as an example）<br>
In the course of system booting，if PCI-E port detect a valid device and the device module is normal，system will prompt“link up”on PCI-E port，as below：<br>
IMX PCIe port: link up.<br>
4）Linux test command：<br>
::$ lspci<br>
If a valid PCI-E device is inserted on PCI-E port,information related to the module will be gained with lspci，something like this（what is linked is Intel 4965AGN in this case）：<br>
::00:00.0 Class 0604: 16c3:abcd<br>
::01:00.0 Class 0280: 8086:4229<br>
If there is not device linked with PCI-E port，lspci system won't output any message。<br>
=== Figured ===
Following figure is message outputed by system without a link with PCI-E device.<br>
[[File:MY-IMX6-EK314 L3035_2.14.3.1.png]]<br>
The following figure is message ouputed by system with a link to Intel 4965AGN<br>
[[File:MY-IMX6-EK314 L3035_2.14.3.2.png]]<br>
Following figure is message by use of lspci after entering system on the condition of a link with Intel 4965AGN<br>
[[File:MY-IMX6-EK314 L3035_2.14.3.3.png]]<br>
	
== '''WIFI Test''' ==
=== Test instruction  ===
Model no. of WIFI chip ussed for MY-I.MX6 evaluation board is RTL8188EUS。<br>
=== Test  method ===
1）Load WIFI module driver<br>
Instanced command as below：<br>
::$ insmod /lib/modules/wifi/wlan.ko<br>
2）Generate WIFI config file<br>
Refered command as below：<br>
::$ wpa_passphrase MYZR_TP-LINK myzrd2302 > /etc/wpa_supplicant.conf<br>
Both name and password of WIFI designated by this command are “MYZR_TP-LINK myzrd2302”，need to replace with your own linkable WIFI name and password<br>
3）Link WIFI network<br>
Instanced command as below：<br>
::$ wpa_supplicant -B –c /etc/wpa_supplicant.conf -iwlan0<br>
4）Automaically gain IP<br>
Instanced command as below：<br>
::$ udhcpc -i wlan0<br>
Note：need to ensure a DHCP function opened for WIFI network in use。<br>
5）Test WIFI network link<br>
Instanced command as below：<br>
::$ ping -I wlan0 www.baidu.com -c 2<br>
6）Test result<br>
Execute step 5 if ok, e.g. WIFI module is normal to work.<br>
	
== '''IPU Test''' ==
=== Test instruction  ===
The whole IPU test will take over ten minutes 。<br>
=== Test  method ===
1）Execute test<br>
enter directory where test program is located（must enter directory where test program is locased for a normal test script）<br>
::$ cd /unit_tests/<br>
execute test script<br>
::$ ./autorun-ipu.sh<br>
2）Test result<br>
In the whole test process，you can see a constant change of content on the display screen。<br>
After test is over，you can see on terminal the following message：<br>
autorun-ipu.sh: Exiting PASS<br>
<br>

＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝test stop at Wed Sep 2 16:08:55 UTC 2015 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝

=== Figured===
[[File:MY-IMX6-EK314 L3035_2.16.3.1.png]]<br>
<br>
[[File:MY-IMX6-EK314 L3035_2.16.3.2.png]]<br>

== '''GPU test''' ==
=== Test instruction  ===
Verify GPU function.<br>
=== Test  method ===
* Execute test command<br>
::$ cd /opt/viv_samples/vdk/ && ./tutorial3 -f 100<br>
::$ cd /opt/viv_samples/vdk/ && ./tutorial4_es20 -f 100<br>
::$ cd /opt/viv_samples/tiger/ &&./tiger<br>
* Test process<br>
When executing the test command, you can see that the display is changing.For more information, please refer to /unit_test/gpu.sh<br>
=== Figured ===
[[File:MY-IMX6-EK314 L3035_2.17.3.1.png]]<br>

== '''VPU test''' ==
=== Test instruction  ===
In the test,vedio file will be decoded with VPU and outputed to the display device.<br>
=== Test  method ===
* Execute test<br>
enter directory where test program is located（must enter directory where test program is locased for a normal test script）<br>
::$ cd /unit_tests/<br>
* Execute test script<br>
::$ ./autorun-vpu.sh<br>
* Test process <br>
In the whole test process，you can see the vedio decoded by VPU on the display screen.<br>
=== Figured ===
[[File:MY-IMX6-EK314 L3035_2.18.3.1.png]]<br>

= '''Reveal function test''' =
----
*Special notes:
<pre>
When  u-boot  version u-boot-2016.03 svn315 and above
      Kernel  version Linux -3.0.35 svn31 and above
                      Linux -3.14.52 svn369 and above
                      Linux -3.14.52 svn368 and above
      Burning tool MfgTool-MYIMX6A9-L* svn181 and above 
</pre>
Please refer to 《[[My-IMX6-A9 series: display functional tests|[MY-IMX6-A9 series: display functional tests]]》my-imx6-a9 series: display function test for testing

*In general, it is tested as follows:
Instruction：need to re-boot system to enter u-boot command line for each reveal function test，enter command and press Enter key<br>
Example as below：<br>
== '''Single screen display''' ==
Instruction：enter command and press Enter key，observe the displayed content on screen in the course of system booting，Linux Logo can be seen.<br>
=== LVDS1 ===
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=ldb,LDB-1024X600,if=RGB666; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
=== LVDS0 ===
Enter u-boot command line，enter the following commands and press Enter key：<br>
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=ldb,LDB-1024X600,if=RGB666 ldb=sin0; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
=== HDMI ===
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
Tips：there is not reveal of Linux Logo on screen for HDMI display in booting。vedio can be played with gplay command after entering system，vedio transfered can be seen on display screen<br>
Example for vedio playing command as below：<br>
::$ gplay /unit_tests/akiyo.mp4<br>
=== RGB ===
Setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=lcd,SEIKO-WVGA,if=RGB24; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
== '''Dual screens synchronous display''' ==
Instruction：enter command and press Enter key，Linux Logo is displayed on the two screens in kernel booting，and other operations to screen is also displayed on the two screens.<br>
=== LVDS1+LVDS0 synchronous display ===
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=ldb,LDB-1024X600,if=RGB666 ldb=dul0 video=mxcfb1:dev=ldb,LDB-1024X600,if=RGB666; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
== '''dual screen asynchronous display''' ==
=== Test commands probably to be used ===
* Turn on backlight of  main display screen<br>
::$ echo 0 > /sys/class/graphics/fb0/blank<br>
* Turn on backlight of the second display screen<br>
::$ echo 0 > /sys/class/graphics/fb2/blank<br>
* Play the designated vedio file to vedio device（here video17 is related to main screen）<br>
::$ gst-launch playbin2 uri=file:///unit_tests/akiyo.mp4 \<br>
video-sink="mfw_v4lsink device=/dev/video17"<br>
* Play the designated vedio file to vedio device（here video18 is related to the second screen）.<br>
::$ gst-launch playbin2 uri=file:///unit_tests/akiyo.mp4 \<br>
video-sink="mfw_v4lsink device=/dev/video18"<br>
=== Test method instruction ===
1）Enter u-boot command line and enter commands then press Enter key and wait until booting is over<br>
Example as below：<br>
2）Execute command turn on backlight of corresponding display screen<br>
Example as below：<br>
3）Execute vedio playing command to play the vedio to display screen<br>
Example as below：<br>
Instruction：in the mode of dual screen asynchronous display ，the backlight defaut of the second screen is closed after system boot，so need to execute step2）.<br>
=== LVDS1 as main screen ===
:*LVDS1+LVDS0 dual screen asynchronous display<br>
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=ldb,LDB-1024X600,if=RGB666 video=mxcfb1:dev=ldb,LDB-1024X600,if=RGB666; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
:* LVDS1+RGB dual screen asynchronous display<br>
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=ldb,LDB-1024X600,if=RGB666 video=mxcfb1:dev=lcd, SEIKO-WVGA,if=RGB24; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
:*  LVDS1+HDMI dual screen asynchronous display<br>
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=ldb,LDB-1024X600,if=RGB666 video=mxcfb1:dev=hdmi,1920x1080M@60,if=RGB24; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
=== LVDS0 as main screen ===
:* LVDS0+LVDS1 dual screen asynchronous display：<br>
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=ldb,LDB-1024X600,if=RGB666 ldb=sep0 video=mxcfb1:dev=ldb,LDB-1024X600,if=RGB666; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
:* LVDS0+RGB dual screen asynchronous display<br>
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=ldb,LDB-1024X600,if=RGB666 ldb=sin0 video=mxcfb1:dev=lcd,SEIKO-WVGA,if=RGB24; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
:* LVDS0+HDMI dual screen asynchronous display<br>
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=ldb,LDB-1024X600,if=RGB666 ldb=sin0 video=mxcfb1:dev=hdmi,1920x1080M@60,if=RGB24; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
=== RGB as main screen ===
:* RGB+LVDS1 dual screen asynchronous display：<br>
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=lcd,SEIKO-WVGA,if=RGB24 video=mxcfb1:dev=ldb,LDB-1024X600,if=RGB666; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
:* RGB+LVDS0 dual screen asynchronous display：<br>
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=lcd,SEIKO-WVGA,if=RGB24 video=mxcfb1:dev=ldb,LDB-1024X600,if=RGB666 ldb=sin0; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
=== HDMI as main screen ===
:* HDMI+LVDS1 dual screen asynchronous display<br>
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb1:dev=ldb,LDB-1024X600,if=RGB666; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
:* HDMI+LVDS0 dual screen asynchronous display<br>
setenv bootargs console=ttymxc0,115200 ip=none root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb1:dev=ldb,LDB-1024X600,if=RGB666 ldb=sin0; mmc dev 2; mmc read 0x10800000 0x800 0x2000; bootm<br>
</div>