Test environment [Development board model]: MY-IMX6-EK140P-6Y-512M-4G [Kernel version]: Linux-4.1.15 [File system]: L4115-fsl-image-gui-myimx6a7.tar.bz2 Interface identification diagramNetwork port test (ETH1) [Test description]: The development board is used to send ICMP packets to the PC for testing [Interface identification]: ETH1 [Interface silk screen]: P10 [System interface]: eth0 Test operation Configure the computer wired network card IP to 192.168.137.99. Use an Ethernet cable to connect the ETH1 of the development board and the computer. Configure the network port of the development board: =====> Input command: ifconfig eth1 down ifconfig eth0 192.168.137.81=====> Output information: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not readyfec 2188000.ethernet eth0: Link is Up - 100Mbps/Full - flow control offIPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Test ETH1 (eth0): =====> Input command: ping 192.168.137.99 -c 2 -w 4 =====> Output information: PING 192.168.137.99 (192.168.137.99) 56(84) bytes of data.64 bytes from 192.168.137.99: icmp_seq=1 ttl=64 time=0.685 ms64 bytes from 192.168.137.99: icmp_seq=2 ttl=64 time=0.374 ms --- 192.168.137.99 ping statistics ---2 packets transmitted, 2 received, 0% packet loss, time 999msrtt min/avg/max/mdev = 0.374/0.529/0.685/0.157 ms Test Result “0% packet loss” means the test passed. Network port test (ETH2) [Test description]: Use the development board to send ICMP packets to the PC for testing [Interface identification]: ETH2 [Interface silk screen]: P8 [System interface]: eth1 Test operation Note: Check the jumper cap on the "silk screen P5" to ensure that it is connected. Configure the computer wired network card IP to 192.168.137.99. Use an Ethernet cable to connect the development board's ETH2 and the computer. Configure the network port of the development board =====> Input command:ifconfig eth0 downifconfig eth1 192.168.137.82 =====> Output information:IPv6: ADDRCONF(NETDEV_UP): eth1: link is not readyfec 20b4000.ethernet eth1: Link is Up - 100Mbps/Full - flow control offIPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Test ETH2 (eth1): =====> Input command:ping 192.168.137.99 -c 2 -w 4 =====> Output information:PING 192.168.137.99 (192.168.137.99) 56(84) bytes of data.64 bytes from 192.168.137.99: icmp_seq=1 ttl=64 time=0.705 ms64 bytes from 192.168.137.99: icmp_seq=2 ttl=64 time=0.386 ms--- 192.168.137.99 ping statistics ---2 packets transmitted, 2 received, 0% packet loss, time 999msrtt min/avg/max/mdev = 0.386/0.545/0.705/0.161 msTest Result “0% packet loss” means the test passed. USB Test [Test Description]: Test by plugging and unplugging a USB storage device (U disk) [Interface Identification]: USB HOST [Interface Silkscreen]: P20 Test Method Insert a USB device into the USB interface on the bottom board, and the system will output information similar to the following: usb 1-1.4: new high-speed USB device number 4 using ci_hdrc usb-storage 1-1.4:1.0: USB Mass Storage device detected scsi host0: usb-storage 1-1.4:1.0 scsi 0:0:0:0: Direct-Access Mass Storage Device 1.00 PQ: 0 ANSI: 0 CCS sd 0:0:0:0: [sda] 7716864 512-byte logical blocks: (3.95 GB/3.67 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] No Caching mode page found sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sda2 sd 0:0:0:0: [sda] Attached SCSI removable disk Unplug the USB device from the backplane, the system will output information similar to the following: usb 1-1.4:USB disconnect, device number 4 Test result When the USB storage device is plugged in or out, the system outputs similar information as above, which means it is normal. SD interface test [Test description]: Test by inserting and identifying the TF card [Interface logo]: SD [Interface silk screen]: P13 Test method Power off the development board and install the TF card into the SD interface. Check the driver output information in the kernel =====> Input command: dmesg | grep mmc0 =====> Output information: mmc0: SDHCI controller on 2190000.usdhc [2190000.usdhc] using ADMA mmc0: host does not support reading read-only switch, assuming write-enable mmc0: new high speed SDHC card at address 1234 mmcblk0: mmc0:1234 SA04G 3.67 GiB Check the system's SD interface device =====> Input command: ls /dev/mmcblk0* =====> Output information: /dev/mmcblk0 ...Test results If the system outputs information similar to the above when the SD storage device is plugged in or out, it indicates normal. Standard GPIO test [Test description]: Control the output level of GPIO [Interface identification]: SPI/I2C/GPIO [Interface silk screen]: P21 [System interface]: /sys/class/gpio/ GPIO output low level test Configure P21:35 to output low level: =====> Input command: OUT_IO_OUT_NUM=4 echo ${OUT_IO_OUT_NUM} > /sys/class/gpio/export echo "out" > /sys/class/gpio/gpio${OUT_IO_OUT_NUM}/direction echo 0 > /sys/class/gpio/gpio${OUT_IO_OUT_NUM}/value Use a multimeter to test pin P21:35. If the voltage is 0V, it means OK GPIO output high level test Configure P21:36 to output high level: =====> Input command: OUT_IO_OUT_NUM=3 echo ${OUT_IO_OUT_NUM} > /sys/class/gpio/exportecho "out" > /sys/class/gpio/gpio${OUT_IO_OUT_NUM}/direction echo 1 > /sys/class/gpio/gpio${OUT_IO_OUT_NUM}/value Use a multimeter to test pin P21:36. The voltage is 3.3V, which means OK Others The command to control GPIO to output low level: =====> Input command: echo 0 > /sys/class/gpio/gpio${OUT_IO_OUT_NUM}/value The command to control GPIO to output high level: =====> Input command: echo 1 > /sys/class/gpio/gpio${OUT_IO_OUT_NUM}/value Other available GPIOs: P21:33,34,23; the corresponding IO numbers are: 2,1,110 GPIO-LED test (led-heartbeat) [Test description]: Observe the LED implemented as led-heartbeat [Interface identification]: LED [Interface silkscreen]: D12 [System interface]: /sys/class/leds/Heartbeat/ Test operation No operation is required Test result After the system starts, you can see that D12 flashes regularly, which means it should be functioning normally. GPIO-LED test (led-timer) [Test description]: Control the on and off time of led-timer (LED) [Interface identification]: LED [Interface silk screen]: D8 [System interface]: /sys/class/leds/led-timer/ Test operation Change the off time: =====> Input command: echo 1000 > /sys/class/leds/led-timer/delay_off Change the on time: =====> Input command: echo 2000 > /sys/class/leds/led-timer/delay_on Test results After executing the above two instructions, it is found that the corresponding LED is on for 2 seconds and off for 1 second. GPIO-LED Test (led-default) [Test Description]: Control the on/off state of led-default (LED) [Interface Identification]: LED [Interface Silkscreen]: D11 [System Interface]: /sys/class/leds/led-timer/ Test OperationDescription: After the system starts, the default state is always on. Make D11 off: =====> Input command: echo 0 > /sys/class/leds/default/brightness Make D11 always on: =====> Input command: echo 1 > /sys/class/leds/default/brightness Test Result After executing the command, it is found that the state of the corresponding LED changes with the function of the command. 100000000 > /sys/class/pwm/$PWM_DEV/pwm0/periodecho 100000000 > /sys/class/pwm/$PWM_DEV/pwm0/duty_cycleecho 1 > /sys/class/pwm/$PWM_DEV/pwm0/enable 100000000 > /sys/class/pwm/$PWM_DEV/pwm0/periodecho 100000000 > /sys/class/pwm/$PWM_DEV/pwm0/duty_cycleecho 1 > /sys/class/pwm/$PWM_DEV/pwm0/enable 100000000 > /sys/class/pwm/$PWM_DEV/pwm0/enable 100000000 > /sys/class/pwm/$PWM_DEV/pwm0/duty_cycle It can be seen that the corresponding LED flashes once in 1 second (1000000000 nanoseconds) (the duration of the high level is 100000000 nanoseconds = 0.> /sys/class/pwm/$PWM_DEV/pwm0/period echo 100000000 > /sys/class/pwm/$PWM_DEV/pwm0/duty_cycle echo 1 > /sys/class/pwm/$PWM_DEV/pwm0/enable Test Result You can hear the buzzer sound once in 1 second (1000000000 nanoseconds) (the high level duration is 100000000 nanoseconds = 0.1 second). Serial port test (UART2) [Test description]: Use the serial port self-transmitting and self-receiving mode to test [Interface identification]: SPI/I2C/GPIO [Interface location]: P21:27,28 [System equipment]: /dev/ttymxc1 Test operation Short the sending and receiving pins of serial port 2 (pins 27 and 28 of P21) Execute test instructions: =====> Input instruction:/my-demo/linux-4.1.15/MY_SERIAL_TEST_L4115_MYIMX6A7.out /dev/ttymxc1 "www.myzr.com.cn" =====> Output information: Starting send data...finish Starting receive data: ASCII: 0x77 Character: w ASCII: 0x77 Character: w ASCII: 0x77 Character: w ASCII: 0x2e Character: . ASCII: 0x6d Character: m ASCII: 0x79 Character: y ASCII: 0x7a Character: z ASCII: 0x72 Character: r ASCII: 0x2e Character: . ASCII: 0x63 Character: c ASCII: 0x6f Character: o ASCII: 0x6d Character: m ASCII: 0x2e Character: . ASCII: 0x63 Character: c ASCII: 0x6e Character: n ASCII: 0x0 Character: Test Result After executing the test command, if the application outputs information similar to the above, it is normal. Serial port test (UART3) [Test description]: Use the serial port self-transmitting and self-receiving mode to test [Interface identification]: SPI/I2C/GPIO [Interface location]: P21:25,26 [System device]: /dev/ttymxc2 Test command Short the sending and receiving pins of serial port 2 (pins 25 and 26 of P21) Execute test instructions: =====> Input command:/my-demo/linux-4.1.15/MY_SERIAL_TEST_L4115_MYIMX6A7.out /dev/ttymxc2 "www.myzr.com.cn" =====> Output information: Starting send data...finish Starting receive data: ASCII: 0x77 Character: w ASCII: 0x77 Character: w ASCII: 0x77 Character: w ASCII: 0x2e Character: . ASCII: 0x6d Character: m ASCII: 0x79 Character: y ASCII: 0x7a Character: z ASCII: 0x72 Character: r ASCII: 0x2e Character: . ASCII: 0x63 Character: c ASCII: 0x6f Character: o ASCII: 0x6d Character: m ASCII: 0x2e Character: . ASCII: 0x63 Character: c ASCII: 0x6e Character: n ASCII: 0x0 Character: Test Result After executing the test command, the application outputs similar information as above, which means it is normal. CAN Test 【Test Description】: Use CAN1 to send and CAN0 to receive. [Interface Identification]: CAN1 (corresponding to can0 in the system); CAN2 (corresponding to can1 in the system) [Interface Silkscreen]: CAN1 P7:1,2; CAN2 P9:1,2 Test Preparation Connect CAN_L (P7:1) of CAN1 with CAN_L (P9:1) of CAN2. Connect CAN_H (P7:2) of CAN1 with CAN_H (P9:2) of CAN2. Test command Configure CAN1 (can0): =====> Input command: ip link set can0 up type can bitrate 125000 =====> Output information: flexcan 2090000.can can0: writing ctrl=0x0e312005IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready Configure CAN2 (can1): =====> Input command: ip link set can1 up type can bitrate 125000 =====> Output information: flexcan 2094000.can can1: writing ctrl=0x0e312005IPv6: ADDRCONF(NETDEV_CHANGE): can1: link becomes ready CAN1 (can0) background reception: =====> Input command: candump can0 & =====> Output information: [1] 589 CAN2 (can1) sends data: =====> Input command:cansend can1 1F334455#1122334455667788 =====> Output information: can0 1F334455 [8] 11 22 33 44 55 66 77 88 SPI test (ECSPI1) [Test description]: Use the self-transmitting and self-receiving method to test. [Interface identification]: SPI/I2C/GPIO [Interface silk screen]: P21: 3,4 [System device]: /dev/spidev0.0 Test operation Short-circuit pins 3 and 4 of P21. Execute test instructions =====> Input command: /my-demo/linux-4.1.15/MY_SPIDEV_TEST_L4115_MYIMX6A7.out -D /dev/spidev0.0 =====> Output information: spi mode: 0 bits per word: 8 max speed: 500000 Hz (500 KHz) FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF DE AD BE EF BA AD F0 0D Test results After executing the test instructions, the application outputs similar information as above, which is normal. SPI test (ECSPI2) 【Test description】: Use the self-transmitting and self-receiving method to test. [Interface identification]: SPI/I2C/GPIO [Interface silkscreen]: P21: 9,10 [System device]: /dev/spidev1.0 Test operation Short-circuit pins 9 and 10 of P21. Execute test instructions =====> Input command: /my-demo/linux-4.1.15/MY_SPIDEV_TEST_L4115_MYIMX6A7.out -D /dev/spidev1.0 =====> Output information: spi mode: 0 bits per word: 8 max speed: 500000 Hz (500 KHz) FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF DE AD BE EF BA AD F0 0DTest results After executing the test instructions, the application outputs similar information as above, which is normal. Watchdog timeout reset test 【Test description】: Turn on the watchdog and wait for the watchdog to time out and generate a reset. [Interface identification]: None [Interface silk screen]: None [System device]: /dev/watchdog Test operation Run the watchdog program: =====> Input command: /unit_tests/wdt_driver_test.out 10 15 1 =====> Output information: Starting wdt_driver (timeout: 10, sleep: 15, test: write) Trying to set timeout value=10 seconds The actual timeout was set to 10 seconds Now reading back -- The timeout is 10 seconds Test result After running the test command for 10 seconds, WatchDog times out and the system is reset. You will see system restart output similar to the following in the terminal: U-Boot 2016.03-svn270 (Oct 08 2018 - 16:52:53 +0800)CPU: Freescale i.MX6ULL rev1.0 528 MHz (running at 396 MHz)CPU: Industrial temperature grade (-40C to 105C) at 51CReset cause: WDOGBoard: MYIMX6EK140P-6Y Watchdog feeding test [Test description]: Turn on the watchdog and feed the application. [Interface identification]: None [Interface silk screen]: None [System device]: /dev/watchdog Test operation Run the watchdog program and set the timeout to 4 seconds and the dog feeding interval to 2 seconds: =====> Input command: /unit_tests/wdt_driver_test.out 4 2 1 & =====> Output information: [1] 831Starting wdt_driver (timeout: 4, sleep: 2, test: write)Trying to set timeout value=4 secondsThe actual timeout was set to 4 secondsNow reading back -- The timeout is 4 secondsTest result The system is working normally, indicating that the dog feeding function is normal. RTC Test [Test Description]: Read and set the time, and check whether the time is correct after powering off and restarting [Interface Identifier]: None [Interface Silkscreen]: None [System Device]: /sys/class/rtc/rtc0/ Test Operation 1. Power off and restart the device to check the current system time and hardware time: =====> Input command: date =====> Output information: Wed Sep 19 17:39:19 UTC 2018 2. View the current RTC chip clock: =====> Input command: hwclock =====> Output information: Wed Sep 19 17:40:05 2018 0.000000 seconds 3. Set the system clock and synchronize it to the RTC chip =====> Input command: date -s "2018-09-21 12:34:56" =====> Output information: Fri Sep 21 12:34:56 UTC 2018 4. Write the system clock to the hardware clock =====> Input command: hwclock -w Test results 1. Power off and restart the evaluation board to view the current system clock and hardware clock =====> Input command: date =====> Output information: Fri Sep 21 12:36:02 UTC 2018 2. View the current RTC chip clock =====> Input command: hwclock =====> Output information: Fri Sep 21 12:36:12 2018 0.000000 seconds You can see that the time we get is basically the same as the set time. wakealarm wakeup test [Test description]: Set the wakealarm event, then put the system to sleep and wait for the wakealarm event to wake it up. [Interface identification]: None [Interface silk screen]: None [System equipment]: such as /sys/class/rtc/rtc1/wakealarm Test operation 1. Set rtc1 to generate a wakealarm event after 10 seconds=====> Input command: echo +10 > /sys/class/rtc/rtc1/wakealarm 2. Put the device to sleep=====> Input command: echo mem > /sys/power/state=====> Output information: PM: Syncing filesystems ... done. Freezing user space processes ... (elapsed 0.007 seconds) done. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Suspending console(s) (use no_console_suspend to debug)Test results 1. You can see that all LEDs of the development board except the power indicator are off. 2. The status of the LED in 10 is restored, and the system outputs information similar to the following: PM: suspend of devices complete after 708.601 msecsPM: suspend devices took 0.710 secondsPM: late suspend of devices complete after 2.543 msecsPM: noirq suspend of devices complete after 2.410 msecsDisabling non-boot CPUs ...PM: noirq resume of devices complete after 1.494 msecsPM: early resume of devices complete after 1.571 msecsPM: resume of devices complete after 223.182 msecsPM: resume devices took 0.230 secondsRestarting tasks ... done. Audio playback test 【Test Description】: Verify the audio playback function of the evaluation board by playing audio files. [Interface Identification]: HP/MIC [Interface Silkscreen]: P12 [System Device]: wm8960-audio Test Operation Plug the earphone into the "HP/MIC" port of the development board. Execute the test command: =====> Input command: aplay /unit_tests/audio8k16S.wav =====> Output information: Playing WAVE '/unit_tests/audio8k16S.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Stereo Test Result After executing the above test command, you can hear the sound output by the audio device. Audio Recording Test [Test Description]: Verify the audio recording function of the evaluation board by recording and playing the recording file. [Interface identification]: HP/MIC [Interface silk screen]: P12 [System device]: wm8960-audio Test operation 1. Plug the headset with MIC into the "HP/MIC" port of the development board. 2. Execute the recording command: =====> Input command: arecord -d 5 -f S16_LE -t wav foobar.wav =====> Output information: Recording WAVE 'foobar.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono 3. Play the recording =====> Input command: aplay foobar.wav =====> Output information: Playing WAVE 'foobar.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono Test result After executing the above test command, you can hear the playing recording. WIFI module RTL8188EUS (optional) test [Test description]: After WIFI is connected to the AP, the development board sends ICMP messages to the external network to verify that the connection is normal. [Interface logo]: WIFI, WIFI_ANT [Interface silk screen]: U20, E2 [System device]: wlan0 Test operation 1. Make sure that the WIFI module is attached to the "WIFI" logo, otherwise there is no need to test. 2. Connect the WIFI antenna to the interface marked with "WIFI_ANT". 3. Generate a WPA PSK file for the SSID Command format: wpa_passphrase494 msecsPM: early resume of devices complete after 1.571 msecsPM: resume of devices complete after 223.182 msecsPM: resume devices took 0.230 secondsRestarting tasks ... done. Audio playback test [Test description]: Verify the audio playback function of the evaluation board by playing audio files. [Interface logo]: HP/MIC [Interface silk screen]: P12 [System device]: wm8960-audio Test operation Plug the earphone into the "HP/MIC" port of the development board. Execute the test command: =====> Input command: aplay /unit_tests/audio8k16S.wav =====> Output information: Playing WAVE '/unit_tests/audio8k16S.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Stereo Test results After executing the above test command, you can hear the sound output by the audio device. Audio recording test [Test description]: Verify the audio recording function of the evaluation board by recording and playing the recording file. [Interface logo]: HP/MIC [Interface silk screen]: P12 [System device]: wm8960-audio Test operation 1. Plug the headset with MIC into the "HP/MIC" port of the development board. 2. Execute the recording command: =====> Input command: arecord -d 5 -f S16_LE -t wav foobar.wav =====> Output information: Recording WAVE 'foobar.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono 3. Play the recording =====> Input command: aplay foobar.wav =====> Output information: Playing WAVE 'foobar.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, MonoTest results After executing the above test command, you can hear the played recording. WIFI module RTL8188EUS (optional) test [Test description]: After WIFI is connected to the AP, the development board sends ICMP packets to the external network to verify that the connection is normal. [Interface Identification]: WIFI, WIFI_ANT [Interface Silk Screen]: U20, E2 [System Device]: wlan0 Test Operation 1. Make sure that the WIFI module is attached to the "WIFI" logo, otherwise no test is required. 2. Connect the WIFI antenna to the interface marked with "WIFI_ANT". 3. Generate a WPA PSK file for the SSID Command format: wpa_passphrase494 msecsPM: early resume of devices complete after 1.571 msecsPM: resume of devices complete after 223.182 msecsPM: resume devices took 0.230 secondsRestarting tasks ... done. Audio playback test [Test description]: Verify the audio playback function of the evaluation board by playing audio files. [Interface logo]: HP/MIC [Interface silk screen]: P12 [System device]: wm8960-audio Test operation Plug the earphone into the "HP/MIC" port of the development board. Execute the test command: =====> Input command: aplay /unit_tests/audio8k16S.wav =====> Output information: Playing WAVE '/unit_tests/audio8k16S.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Stereo Test results After executing the above test command, you can hear the sound output by the audio device. Audio recording test [Test description]: Verify the audio recording function of the evaluation board by recording and playing the recording file. [Interface logo]: HP/MIC [Interface silk screen]: P12 [System device]: wm8960-audio Test operation 1. Plug the headset with MIC into the "HP/MIC" port of the development board. 2. Execute the recording command: =====> Input command: arecord -d 5 -f S16_LE -t wav foobar.wav =====> Output information: Recording WAVE 'foobar.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono 3. Play the recording =====> Input command: aplay foobar.wav =====> Output information: Playing WAVE 'foobar.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, MonoTest results After executing the above test command, you can hear the played recording. WIFI module RTL8188EUS (optional) test [Test description]: After WIFI is connected to the AP, the development board sends ICMP packets to the external network to verify that the connection is normal. [Interface Identification]: WIFI, WIFI_ANT [Interface Silk Screen]: U20, E2 [System Device]: wlan0 Test Operation 1. Make sure that the WIFI module is attached to the "WIFI" logo, otherwise no test is required. 2. Connect the WIFI antenna to the interface marked with "WIFI_ANT". 3. Generate a WPA PSK file for the SSID Command format: wpa_passphrase[passphrase] =====> Input command: wpa_passphrase MYZR-OPEN Myzr2012 > /etc/wpa_supplicant.confpkill wpa_supplicant 4. Connect=====> Input command: wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf=====> Output information: Successfully initialized wpa_supplicantrfkill: Cannot open RFKILL control device==> rtl8188e_iol_efuse_patchIPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready==> rtl8188e_iol_efuse_patchIPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready 5. Get IP =====> Input command: udhcpc 114.215.177.38): 56 data bytes 64 bytes from 192.168.124.113 (14.215.177.38): 56 data bytes 64 bytes from 192.168.124.113 (14.215.177.38): 56 data bytes 64 bytes from 192.168.124.113 (14.215.177.38): 56 data bytes 64 bytes from 192.168.124.113 (14.215.177.38): 56 data bytes 64 bytes from 192.168.124.113 (14.215.177.38): 56 data bytes 64 bytes from 192.168.124.113 (14.215.177.38): 56 data bytes 64 bytes from 14.215.177.38: seq=0 ttl=49 time=15.753 ms64 bytes from 14.215.177.38: seq=1 ttl=49 time=11.835 ms--- www.baidu.com ping statistics ---2 packets transmitted, 2 packets received, 0% packet lossround-trip min/avg/max = 11.835/13.794/15.753 msTest result "0% packet loss" means the WIFI connection is normal. 4G module EC20 (optional) test [Test description]: After the 4G connection is successful, the development board sends ICMP packets to the external network to verify that the connection is normal. [Interface Identification]: 3G/4G [Interface Silkscreen]: P19 [System Device]: eth2 Test Operation 1. Power off the development board, connect the 4G module, connect the antenna, insert the SIM card, and then start the evaluation board. 2. Use the command to connect to the network: =====> Input command:/my-demo/linux-4.1.15/MY_EC20_QuectelCM_L4115_MYIMX6A7.out &=====> Output information: [1] 607[09-21_13:36:14:352] WCDMA<E_QConnectManager_Linux&Android_V1.1.34[09-21_13:36:14:353] /my-demo/linux-4.1.15/MY_EC20_QuectelCM_L4115_MYIMX6A7.out profile[1] = (null)/(null)/(null)/0, pincode = (null)[09-21_13:36:14:356] Find /sys/bus/usb/devices/1-1.2 idVendor=2c7c idProduct=0125[09-21_13:36:14:356] Find /sys/bus/usb/devices/1-1.2:1.4/net/eth2[09-21_13:36:14:356] Find usbnet_adapter = eth2[09-21_13:36:14:356] Find /sys/ bus/usb/devices/1-1.2:1.4/GobiQMI/qcqmi2[09-21_13:36:14:357] Find qmichannel = /dev/qcqmi2[09-21_13:36:14:403] Get clientWDS = 7[09-21_13:36:14:435] Get clientDMS = 8[09-21_13:36:14:467] Get clientNAS = 9[09-21_13:36:14:499] Get clientUIM = 10[09-21_13:36:14:532] Get clientWDA = 11[09-21_13:36:14:563] requestBaseBandVersion EC20CEFAR02A10M 4G[09-21_13:36:14:659] requestGetSIMStatus SIMStatus: SIM_READY[09-21_13:36:14:692] requestGetProfile[1] cmnet///0[09-21_13:36:14:724] requestRegistrationState2 MCC: 460, MNC: 0, PS: Attached, DataCap: LTE[09-21_13:36:14:755] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED[09-21_13:36:14:819] requestRegistrationState2 MCC: 460, MNC: 0, PS: Attached, DataCap: LTE[09-21_13:36:16:036] requestSetupDataCall WdsConnectionIPv4Handle: 0x87756f40[09-21_13:36:16:132] requestQueryDataCall IPv4ConnectionStatus: CONNECTED[09-21_13:36:16:163] ifconfig eth2 up[09-21_13:36:16:193] busybox udhcpc -f -n -q -t 5 -i eth2[09-21_13:36:16:211] udhcpc (v1.24.1) started[09-21_13:36:16:318] Sending discover...[09-21_13:36:16:378] Sending select for 10.151.159.101...[09-21_13:36:16:438] Lease of 10.151.159.101 obtained, lease time 7200[09-21_13:36:16:522] /etc/udhcpc.d/50default: Adding DNS 221.179.38.7[09-21_13:36:16:522] /etc/udhcpc.d/50default: Adding DNS 120.196.165.7 3. Test connection=====> Input command: ping -I eth2 www.baidu.com -c 2 -w 4=====> Output information: PING www.baidu.com (14.215.177.38): 56 data bytes64 bytes from 14.215.177.38: seq=0 ttl=49 time=15.753 ms64 bytes from 14.215.177.38: seq=1 ttl=49 time=11.835 ms--- www.baidu.com ping statistics ---2 packets transmitted, 2 packets received, 0% packet lossround-trip min/avg/max = 11.835/13.794/15.753 msTest Result "0% packet loss" means the WIFI connection is normal. Display screen (optional) test [Test description]: Observe the display screen during system startup to determine whether the display function is normal [Interface identification]: RGB [Interface silk screen]: P3 [System device]: /dev/fb0 Test operation Connect the display screen to the development board, power on, and observe the display screen during the development board startup. Test results During the system startup, you can see the Linux Penguin and OpenEmbedded startup screens. FXLS8471 (optional) test [Test description]: Confirm that the function is normal by reading the sensor data under the system [Interface identification]: Accelerometer [Interface silk screen]: U18 [System device]: /sys/class/misc/FreescaleAccelerometer/ Test operation 1. Enable the sensor =====> Input command: echo 1 > /sys/class/misc/FreescaleAccelerometer/enable =====> Output information: mma enable setting actived 2. Check the sensor data ======> Input command: cat /sys/class/misc/FreescaleAccelerometer/data =====> Output information: -384,136,16384Test result After executing the above command, the system will output the sensor data, which means it is normal. FXAS2100 (optional) test [Test description]: Confirm that the function is normal by reading the sensor data under the system [Interface logo]: Gyroscope [Interface silk screen]: U19 [System device]: /dev/input/eventX Test operation 1. Enable the sensor =====> Input command: echo 1 > /sys/class/misc/FreescaleGyroscope/enable =====> Output information: misc FreescaleGyroscope: mma enable setting active 2. Run evtest program: =====> Input command: evtest =====> Output information: No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: fxas2100x/dev/input/event1: 20cc000.snvs:snvs-powerkey/dev/input/event2: FreescaleAccelerometer/dev/input/event3: mag3110Select the device event number [0-3]: 3. Select the corresponding device, here fxas2100 corresponds to event0, so we enter 0: =====> Input command: 0=====> Output information: Event: time 1538485645.829802, type 3 (EV_ABS), code 0 (ABS_X), value -3Event: time 1538485645.829802, type 3 (EV_ABS), code 1 (ABS_Y), value 13Event: time 1538485645.829802, type 3 (EV_ABS), code 2 (ABS_Z), value 4Event: time 1538485645.829802, -------------- SYN_REPORT ------------Test results After executing the above command, the value output by the system is the sensor data. -------------------------------------------------------------------------------- --------------------------------------------------------------------------------com[/url] ping statistics ---2 packets transmitted, 2 packets received, 0% packet lossround-trip min/avg/max = 11.835/13.794/15.753 msTest results "0% packet loss" indicates that the WIFI connection is normal. Display screen (optional) test [Test description]: Observe the display of the display screen during system startup to determine whether the display function is normal [Interface logo]: RGB [Interface silk screen]: P3 [System device]: /dev/fb0 Test operation Connect the display screen to the development board, power on, and observe the display screen during the development board startup. Test results During the system startup, you can see the Linux Penguin and OpenEmbedded startup screens. FXLS8471 (optional) test [Test description]: Confirm that the function is normal by reading the sensor data under the system [Interface identification]: Accelerometer [Interface silk screen]: U18 [System device]: /sys/class/misc/FreescaleAccelerometer/ Test operation 1. Enable the sensor =====> Input command: echo 1 > /sys/class/misc/FreescaleAccelerometer/enable =====> Output information: mma enable setting actived 2. Check the sensor data ======> Input command: cat /sys/class/misc/FreescaleAccelerometer/data =====> Output information: -384,136,16384Test result After executing the above command, the system will output the sensor data, which means it is normal. FXAS2100 (optional) test [Test description]: Confirm that the function is normal by reading the sensor data under the system [Interface logo]: Gyroscope [Interface silk screen]: U19 [System device]: /dev/input/eventX Test operation 1. Enable the sensor =====> Input command: echo 1 > /sys/class/misc/FreescaleGyroscope/enable =====> Output information: misc FreescaleGyroscope: mma enable setting active 2. Run evtest program: =====> Input command: evtest =====> Output information: No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: fxas2100x/dev/input/event1: 20cc000.snvs:snvs-powerkey/dev/input/event2: FreescaleAccelerometer/dev/input/event3: mag3110Select the device event number [0-3]: 3. Select the corresponding device, here fxas2100 corresponds to event0, so we enter 0: =====> Input command: 0=====> Output information: Event: time 1538485645.829802, type 3 (EV_ABS), code 0 (ABS_X), value -3Event: time 1538485645.829802, type 3 (EV_ABS), code 1 (ABS_Y), value 13Event: time 1538485645.829802, type 3 (EV_ABS), code 2 (ABS_Z), value 4Event: time 1538485645.829802, -------------- SYN_REPORT ------------Test results After executing the above command, the value output by the system is the sensor data. -------------------------------------------------------------------------------- --------------------------------------------------------------------------------com[/url] ping statistics ---2 packets transmitted, 2 packets received, 0% packet lossround-trip min/avg/max = 11.835/13.794/15.753 msTest results "0% packet loss" indicates that the WIFI connection is normal. Display screen (optional) test [Test description]: Observe the display of the display screen during system startup to determine whether the display function is normal [Interface logo]: RGB [Interface silk screen]: P3 [System device]: /dev/fb0 Test operation Connect the display screen to the development board, power on, and observe the display screen during the development board startup. Test results During the system startup, you can see the Linux Penguin and OpenEmbedded startup screens. FXLS8471 (optional) test [Test description]: Confirm that the function is normal by reading the sensor data under the system [Interface identification]: Accelerometer [Interface silk screen]: U18 [System device]: /sys/class/misc/FreescaleAccelerometer/ Test operation 1. Enable the sensor =====> Input command: echo 1 > /sys/class/misc/FreescaleAccelerometer/enable =====> Output information: mma enable setting actived 2. Check the sensor data ======> Input command: cat /sys/class/misc/FreescaleAccelerometer/data =====> Output information: -384,136,16384Test result After executing the above command, the system will output the sensor data, which means it is normal. FXAS2100 (optional) test [Test description]: Confirm that the function is normal by reading the sensor data under the system [Interface logo]: Gyroscope [Interface silk screen]: U19 [System device]: /dev/input/eventX Test operation 1. Enable the sensor =====> Input command: echo 1 > /sys/class/misc/FreescaleGyroscope/enable =====> Output information: misc FreescaleGyroscope: mma enable setting active 2. Run evtest program: =====> Input command: evtest =====> Output information: No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: fxas2100x/dev/input/event1: 20cc000.snvs:snvs-powerkey/dev/input/event2: FreescaleAccelerometer/dev/input/event3: mag3110Select the device event number [0-3]: 3. Select the corresponding device, here fxas2100 corresponds to event0, so we enter 0: =====> Input command: 0=====> Output information: Event: time 1538485645.829802, type 3 (EV_ABS), code 0 (ABS_X), value -3Event: time 1538485645.829802, type 3 (EV_ABS), code 1 (ABS_Y), value 13Event: time 1538485645.829802, type 3 (EV_ABS), code 2 (ABS_Z), value 4Event: time 1538485645.829802, -------------- SYN_REPORT ------------Test results After executing the above command, the value output by the system is the sensor data. -------------------------------------------------------------------------------- --------------------------------------------------------------------------------echo 1 > /sys/class/misc/FreescaleGyroscope/enable =====> Output information: misc FreescaleGyroscope: mma enable setting active 2. Run the evtest program: =====> Input command: evtest =====> Output information: No device specified, trying to scan all of /dev/input/event*Available devices:/dev/input/event0: fxas2100x/dev/input/event1: 20cc000.snvs:snvs-powerkey/dev/input/event2: FreescaleAccelerometer/dev/input/event3: mag3110Select the device event number [0-3]: 3. Select the corresponding device, here fxas2100 corresponds to event0, so we enter 0: =====> Input command: 0=====> Output information: Event: time 1538485645.829802, type 3 (EV_ABS), code 0 (ABS_X), value -3Event: time 1538485645.829802, type 3 (EV_ABS), code 1 (ABS_Y), value 13Event: time 1538485645.829802, type 3 (EV_ABS), code 2 (ABS_Z), value 4Event: time 1538485645.829802, -------------- SYN_REPORT ------------Test results After executing the above instructions, the value output by the system is the sensor data. -------------------------------------------------------------------------------- --------------------------------------------------------------------------------echo 1 > /sys/class/misc/FreescaleGyroscope/enable =====> Output information: misc FreescaleGyroscope: mma enable setting active 2. Run the evtest program: =====> Input command: evtest =====> Output information: No device specified, trying to scan all of /dev/input/event*Available devices:/dev/input/event0: fxas2100x/dev/input/event1: 20cc000.snvs:snvs-powerkey/dev/input/event2: FreescaleAccelerometer/dev/input/event3: mag3110Select the device event number [0-3]: 3. Select the corresponding device, here fxas2100 corresponds to event0, so we enter 0: =====> Input command: 0=====> Output information: Event: time 1538485645.829802, type 3 (EV_ABS), code 0 (ABS_X), value -3Event: time 1538485645.829802, type 3 (EV_ABS), code 1 (ABS_Y), value 13Event: time 1538485645.829802, type 3 (EV_ABS), code 2 (ABS_Z), value 4Event: time 1538485645.829802, -------------- SYN_REPORT ------------Test results After executing the above instructions, the value output by the system is the sensor data. -------------------------------------------------------------------------------- --------------------------------------------------------------------------------
提升卡
变色卡
千斤顶
京公网安备 11010802033920号
