world leader in high performance signal processing
Trace: » manual_test

How to build workspace

  • Make the dir: eg:~/workspace/src/kernel
  • Get the files:
         git clone git://10.99.22.20/git/buildroot kernel
         git submodule init
         git config submodule.testsuites.url git://10.99.22.20/buildroot_test
         git config submodule.linux/linux-kernel.url git://10.99.22.20/linux-kernel
         git submodule update
  • Checkout the right branch:using “git tag -l”to show all branch,”git checkout -b XXX XXX”to create branch, “git branch”to show the current branch,and “git pull” to update the code.The commands of “git checkout .” and “git status” is also useful.

How to setup toolchain

  • To create the dir /opt/uClinux/ by command 'mkdir -p /opt/uClinux', and run 'chmod 777 uClinux' to give all permissions.
  • Log on to regression machine (for example 10.99.29.60) to get the toolchain in usage from its /opt/uClinux folder.
  • Before make the uImage ,you should export PATH=/opt/uClinux/bfin-uclinux/bin:/opt/uClinux/bfin-elf/bin:/opt/uClinux/bfin-linux-uclibc/bin:$PATH
  • The following commands are also useful:ssh -l test XX.XX.XX.XX;scp test@xx.xx.xx.xx:/files ~/;scp ~/files test@xx.xx.xx.xx:~/. If you want to reference the previous release logs,please download the files in 10.99.22.20/home/test/release/.
  • You can also refer to the wiki of https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing. All the build uImage scripts and test scripes are in the file of “testsuites”.

Manual test

Before running the following specific cases from testsuites, please adjust your param setting according to your machine environment.

common/kernel_config.exp:

set src_root /your/kernel/source/code/directly 

If your are running the case on regression machine, please remember do:

export BOARD_CONFIG=BOARD_CONFIG(for example BF537-STAMP-XXX) 

AD1836 audio driver

  • The test will need to be done on the boards of BF533-STAMP,BF537-STAMP and BF609-EZKIT.
  • First refer to “Device driver test”—1.Audio driver test over SPORT(AD1836) in https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing.
  • Need a module of ad1836 http://docs.blackfin.uclinux.org/doku.php?id=hw:cards:ad1836a.(BF609-EZKIT have a special extension board).The module should be connect to the SPORT0 on the board .Need two audio cables, connect the board's audio input to PC's audio output and the board's audio output to PC's audio input.Using PC to provide sounds to board by palying a file of audiotest.mp3.
          testsuites/audio$  cd /workspace/kernal/testsuites/audio/
          testsuites/audio$  ./build_audio_kernel.exp BF537-STAMP audio_ad1836(to build uImage)
          testsuites/audio$  ./audio_data_test.exp BF537-STAMP audio_ad1836
          testsuites/audio$  ./audio_test.exp BF537-STAMP audio_ad1836
  • If we can hear the sound from the board, and the sound also have some changes,the test will pass,or there have some bugs.

AD1938 audio driver

  • The test will need to be done on the board of BF537-STAMP.
  • Refer to AD1836 audio driver.
          testsuites/audio$  cd /workspace/kernal/testsuites/audio/
          testsuites/audio$  ./build_audio_kernel.exp BF537-STAMP audio_ad1938(to build uImage)
          testsuites/audio$  ./audio_data_test.exp BF537-STAMP audio_ad1938
          testsuites/audio$  ./audio_test.exp BF537-STAMP audio_ad1938 
          
  • If we can hear the sound from the board, and the sound also have some changes,the test will pass,or there have some bugs.

ADAU1761

  • The test will need to be done on the board of BF609-EZKIT.
  • Refer to AD1836 audio driver.
  • Connect Audio EI3 Extender Board to P1A port on BF609-EZKIT,On Audio EI3 Extender Board, J4 is Line-in and J2 is headphone.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/audio$ ./build_audio_kernel.exp BF609-EZKIT audio_adau1761
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/audio$ ./audio_data_test.exp BF609-EZKIT audio_adau1761
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/audio$ ./audio_test.exp BF609-EZKIT audio_adau1761
        
  • If we can hear the sound from the board, and the sound also have some changes,the test will pass,or there have some bugs.

Audio ssm2603(2602)

  • The test will need to be done on the boards of BF537-STAMP and BF527-EZKIT.
  • Refer to AD1836 audio driver.
  • When run scripts for BF527-EZKIT ,please use BF527-EZKIT-V2 to replace BF527-EZKIT.
     
          testsuites/audio$  cd /workspace/kernal/testsuites/audio/
          testsuites/audio$  ./build_audio_kernel.exp BF527-EZKIT-V2 audio_ssm2603(to build uImage)
          testsuites/audio$  ./audio_data_test.exp BF527-EZKIT-V2 audio_ssm2603
          testsuites/audio$   ./audio_test.exp BF527-EZKIT-V2 audio_ssm2603 
  • If we can hear the sound from the board, and the sound also have some changes,the test will pass,or there have some bugs.

ADV7393 video output driver

  • Only Bf537-STAMP should be tested.
  • Hardware and connection refer to “13.Video driver test - ADV7393”in https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing.
  • Compiling uImage
          testsuites/video_adv7393$ ls
              build_video_adv7393_kernel.exp  video_adv7393_test.exp
          testsuites/video_adv7393$ ./build_video_adv7393_kernel.exp BF537-STAMP
          (After download the uImage to the board)
          testsuites/video_adv7393$ ./video_adv7393_test.exp BF537-STAMP
           
  • If you can see the image on the TV,the test will be pass.

AD7183b video input driver

  • Only Bf561-EZKIT should be tested.
  • Need a DVD outputing image,and TV seeing the image to ensure the DVD out normally.Connect composite output to to BF561-EZKIT AVIN5 port ,refer to “55.ADV7183 video decoder” https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing.
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/video_decoder$ ./build_video_decoder_kernel.exp BF561-EZKIT
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/video_decoder$ ./video_decoder_test.exp BF561-EZKIT
          
  • Use software of pYUV to open video_decoder_adv7183.yuv,if the picture is the same as the DVD ,then the test pass

ADV7842 video decoder driver

  • Only Bf609-EZKIT should be tested.
  • Hardware and how to connect ,refer”54.V4L2 Video Capture Driver - Camera”https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing.
  • This test have three formats(720p60(HD), NTSC and PAL),so you need test three times.
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/video_decoder$ ./build_video_decoder_kernel.exp BF609-EZKIT
            (to NTSC and PAL formats)     
           stsuites/video_decoder$ ./video_decoder_test.exp BF609-EZKIT composite 
            (to 720p60(HD) format)     
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/video_decoder$ ./video_decoder_test.exp BF609-EZKIT hdmi
            
  • Use software of pYUV to open file of *.yuv,if the picture is the same as the DVD ,then the test pass.

ADV7511 video encoder driver

  • Only Bf609-EZKIT should be tested.
  • Refer to “56.V4L2 Video Display Driver”https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing.
  • Connect ADV7511 adapter board to BF609-EZKIT P3A connector. Only HD format is support for ADV7511, so connect HDMI wire card to TV to display captured HD yuv file (720p).
            test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/video_encoder$ ./build_video_encoder_kernel.exp BF609-EZKIT
            test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/video_encoder$ ./video_encoder_test.exp BF609-EZKIT  
  • IF you can see a normal image on the TV,the test pass.

ADP8860/8870 Backlight Driver

  • Only Bf537-STAMP should be tested.
  • Special board,refer”60.ADP8860”https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing.
            test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/adp8860$ ./build_adp8860_kernel.exp BF537-STAMP
            test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/adp8860$ ./adp8860_test.exp BF537-STAMP  
  • IF you see the LED on the board change its bright,the test pass.

Bluetooth usb

  • BF537-STAMP,BF548-EZKIT and BF609-EZKIT need to be tested.
  • To use bluetooth protocal on stamp board via usb port.Refer to “39.Bluetooth (usb)“https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing.
            test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/bluetooth$ ./build_bluetooth_kernel.exp BF537-STAMP
            test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/bluetooth$ ./bluetooth_test.exp BF537-STAMP 
  • If it could communation(Ping: 00:15:83:44:C2:E7),the test pass.

Bluetooth ALSA

  • BF537-STAMP and BF609-EZKIT need to be tested.
  • To use bluetooth protocal on stamp board via usb port,and need a bluetooth earphone.Refer to “40.Bluetooth ALSA”https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing.
            test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/bluetoothalsa$ ./build_bluetoothalsa_kernel.exp BF609-EZKIT
       (after download uImage)
            test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/bluetoothalsa$ rcp test.wav root@10.100.4.50:/
       (open minicom)
            root:/> hciconfig hci0 up
       (open earphone,and matched pattern)                                                         
            root:/> hcitool scan                                                            
            Scanning ...                                                                    
            30:F9:ED:E1:9E:A9       DR-BT140Q                                       
            00:07:80:89:8F:0E       n/a                                             
            root:/> vi /etc/asound.conf
    
            pcm.bluetooth {
                 type bluetooth
                 device "30:F9:ED:E1:9E:A9"        
          }  (here is not space, it is a "Tab") 
            root:/> /etc/init.d/S30dbus start &
            root:/> bluetoothd &
            root:/> agent 0000 &
            root:/>export BTADAPTER=`dbus-send --system --dest=org.bluez --print-reply / org.bluez.Manager.DefaultAdapter | tail -n 1 | sed 's/^.*"\(.*\)".*$/\1/'` 
            root:/> dbus-send --system --print-reply --dest=org.bluez $BTADAPTER org.bluez.Adapter.CreateDevice string:30:F9:ED:E1:9E:A9 
            root:/>dbus-send --system --print-reply --dest=org.bluez $BTADAPTER/dev_30_F9_ED_E1_9E_A9 org.bluez.Audio.Connect 
            root:/> ls
            bin       etc       lib       proc      sbin      sys       tmp       var
            dev       init      mnt       root      srv       test.wav  usr
            root:/> aplay -D bluetooth test.wav   
  • If you hear song playing in the bluetooth earphone,test pass.

Camera Mt9M114

  • Only Bf609-EZKIT should be tested.
  • It needs an adapter board from P1A slot to PPI port,connect Aptina MT9M114 board(P9 connector) to BF609-EZKIT P1A connector via Aptina camera adapter board(J2 connector).
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/camera$ ./build_camera_kernel.exp BF609-EZKIT camera_mt9m114
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/camera$ ./camera_test.exp BF609-EZKIT camera_mt9m114  
  • If the camera_mt9m114.avi catched by board can play normally,the test pass.

Camera vs6624

  • BF537-STAMP and BF609-EZKIT need to be tested.
  • Connect STAMP_PPI port in the CMOS Camera card(VS6624) to PPI port in BF537-STAMP.
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/camera$ ./build_camera_kernel.exp BF537-STAMP camera_vs6624
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/camera$ ./camera_test.exp BF537-STAMP camera_vs6624  
  • If the camera_vs6624.avi catched by board can play normally,the test pass.

Direct fb

  • BF537-STAMP,BF548-EZKIT,BF527-EZKIT-V2 and BF609-EZKIT should be tested.
  • Every board should have itself LCD.
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/directfb$ ./build_directfb_kernel.exp BF527-EZKIT-V2
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/directfb$ ./directfb_test.exp BF527-EZKIT-V2 
  • If you can see some pictures playing in turns on the board'LCD,the test pass.

Common PPI driver

  • Only Bf537-STAMP should be tested.
  • Special board,Refer to 2013trunklog.
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/bfinppi$ ./build_bfinppi_kernel.exp BF537-STAMP
           root:/> version 
           root:/> ppitest m  
        (change another board)
           root:/> ppitest s  
  • If the sl ave output is right, the test pass.

Linphone ad1836

  • Only on board of BF533-STAMP and BF537-STAMP.
  • Use PC instead of a phone,and the board as another phone,there are communication by internet.PC paly music as someone talking,the board can hear,exchange each others, there can work normally.Everyone should insert a earphone.
  • Download and install software of Linphone from http://www.linphone.org/?lang=us.
  • Refer to https://docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:linphone.
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/linphone$ ./build_linphone_kernel.exp BF533-STAMP audio_ad1836
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/linphone$ ./build_linphone_kernel.exp BF533-STAMP audio_ad1836 
  • Play music on the PC, if hearing song form board'earphone,next.
  • Play music on the board, if hearing song form PC'earphone,the test pass.

Linphone adau1761

  • Only on board of BF609-EZKIT.
  • Use PC instead of a phone,and the board as another phone,there are communication by internet.PC paly music as someone talking,the board can hear,exchange each others, there can work normally.Everyone should insert a earphone.
  • Download and install software of Linphone from http://www.linphone.org/?lang=us.
  • Refer to https://docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:linphone.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/linphone$ ./build_linphone_kernel.exp BF609-EZKIT audio_adau1761
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/linphone$ ./build_linphone_kernel.exp BF609-EZKIT audio_adau1761 
  • Play music on the PC, if hearing song form board'earphone,next.
  • Play music on the board, if hearing song form PC'earphone,the test pass.

Mplayer

  • BF548-EZKIT,BF527-EZKIT-V2 and Bf609-EZKIT should do this test.
  • Every board should itself LCD,and connect it to the board.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/mplayer$ ./build_mplayer_kernel.exp BF548-EZKIT
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/mplayer$ ./mplayer_test.exp BF548-EZKIT 
    • If you can see a cartoon film playing on the board'LCD,the test pass.

Multichannel audio ALSA test

  • Only BF537-STAMP should be tested.
  • It needs test on ad1836 and ad1938.
  • The test seems like “AD1836 audio driver” and “AD1938 audio driver” ,only difference is that it have three output channeles,so if you can hear sound from three channneles,the test pass.
     
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/multichannel$ ./build_multichannel_kernel.exp BF537-STAMP audio_ad1836
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/multichannel$ ./multichannel_test.exp BF537-STAMP audio_ad1836
        

Power with ad1836

  • BF533-STAMP and BF537-STAMP need be tested.
  • The hardware should be connected like “AD1836 audio driver”,the test have two modeles--mem and standby.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/power_audio$ ./build_power_audio_kernel.exp BF537-STAMP audio_ad1836
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/power_audio$ ./power_audio_test.exp BF537-STAMP audio_ad1836 
        
  • If the board can into sleep, and wakeup by sound from PC,the test pass.

Power with ad1938

  • Only BF537-STAMP should be test.
  • Refer to “Power with ad1836”

Power with adau1761

  • Only BF609-EZKIT should be test.
  • Refer to “Power with ad1836”

Power with ssm2603(2602)

  • BF537-STAMP and BF527-EZKIT-V2 should be test.
  • Refer to “Power with ad1836”

Power with adv7393

  • Only BF537-STAMP should be test.
  • Refer to “Power with ad1836”

Power with tftlcd

  • BF537-STAMP BF548-EZKIT BF527-EZKIT-V2 and BF609-EZKIT should be test.
  • The test need the board's LCD,and it also has two modeles--mem and standby.
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/power_tftlcd$ ./build_power_tftlcd_kernel.exp BF537-STAMP
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/power_tftlcd$ ./power_tftlcd_test.exp BF537-STAMP  
  • IF you can see a image on the LCD , the board can into sleep, and it can wakeup by LCD(image on the LCD),the test pass.

Power wakeup by usb Power wakeup by usb

  • Only BF609-EZKIT should be tested.
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/usb_wakeup$ ./build_usb_wakeup_kernel.exp BF609-EZKIT
        (open minicom)
           root:/> echo mem >/sys/power/state (into mem sleep)
        (plug in a usb device , such as U disk)
        
  • If the board can wakeup ,the test pass.(more times test).

Qt

  • BF548-EZKIT and BF609-EZKIT should be test.
  • The test need the board's LCD.
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/qt$ ./build_qt_kernel.exp BF609-EZKIT
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/qt$ ./qt_test.exp BF609-EZKIT 
  • If you can see a movie palying on the board'LCD, the test pass.

TFT LCD xxx driver

  • LQ035—BF537-STAMP LQ043—BF548-EZKIT T350—BF527-EZKIT-V2 nl8048—BF609-EZKIT
  • Connect the LCD to the board .
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/tftlcd$ ./build_tftlcd_kernel.exp BF537-STAMP
           test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/tftlcd$ ./tftlcd_test.exp BF537-STAMP 
  • If you can see a image palying on the board'LCD, the test pass.

Touchscreen over PPI

  • Only BF526-EZBRD should be tested.
  • This test needs “BFL LCD lq035”
        (The hardware setup)
        ##############################################################
        # Hardware settings for landscape LCD EZ-EXTENDER(Rev 1.1/1.3)
        ##############################################################
        # JP1: OFF
        # JP2: 1 & 2 installed
        # JP3: 5 & 6 installed
        # JP5: 1 & 2 installed
        # JP6: OFF
        # JP7: OFF
        # JP8: All OFF
        # JP9: ON
        # JP10: 1 & 2 installed
        # JP11: 3 & 4 installed
        # JP12: OFF
        # JP13: 2 & 3 installed
        ##############################################################
    
        #########################################
        # Hardware settings for BF526-EZBRD
        #########################################
        # SW11: ALL OFF
        # SW12: ON, ON, OFF, ON
        # SW13: OFF, OFF, OFF, ON
        # SW14: OFF, ON, OFF, ON
        # SW20: OFF, ON, OFF, OFF, OFF, OFF
        # SW21: ON, ON, all others OFF
        # JP2:  OFF
        # JP3:  OFF (UART ENBL: 1&2 on by default)
        # JP5:  OFF (LED ENBL:  1&2 on by default)
        ##########################################
    
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/touchscreen$ ./build_touchscreen_kernel.exp BF526-EZBRD
       (download the uImage)
          test@test-OptiPlex-390:/$telnet 10.100.4.50
          root:~> version
          root:~> dmesg
          root:~> video_test
          root:~> event_test /dev/input/event0
       (press the screen of LCD)
  • If there are some codes appearing when press the screen,the test pass.

USB camera test

  • BF548-EZKIT and BF609-EZKIT should be tested.
  • Refer to “54.V4L2 Video Capture Driver - Camera” https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing.
         test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/usb_camera$ ./build_usb_camera_kernel.exp BF609-EZKIT
         test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/usb_camera$ ./usb_camera_test.exp BF609-EZKIT
       
  • You will get a file of usb_camera.mp4, open it,and if it the picture is nornal when playing,the test pass.

Usb otg test

  • BF548-EZKIT BF527-EZKIT-V2 and BF609-EZKIT should be tested.
  • There are two modeles--dma and pio.The board'usb work as host,plug in the USB disk;The board'usb work as device,so it needs PC to work as host.It also needs a usb line,one head of the line is 'A' to connect U disk , another is 'B' to connect the PC.
     test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/usbotg$ ./build_usbotg_kernel.exp BF609-EZKIT dma
     (download the uImage and open minicom) 
  • Plug in the U disk, if the board can identify the U disk.After plug in the PC,and the board can work and appear some message, the test pass.

Sdio wifi

ADP5588 ADP5520

   (ADP5588)
      test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/adp5588_qwerty$ ./build_adp5588_qwerty_kernel.exp BF537-STAMP
      test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/adp5588_qwerty$ ./adp5588_qwerty_test.exp BF537-STAMP
   (ADP5520)
      test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/adp5520$ ./build_adp5520_kernel.exp BF537-STAMP
      test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/adp5520$ ./adp5520_test.exp BF537-STAMP
    
  • According the tips,press the button,if the test script run successfully,the test pass.

Camera frame capture driver over PPI

  • BF533-STAMP and BF537-STAMP should be tested.
  • Connect the camera to the board's PPI.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/ppifcd$ ./build_ppifcd_kernel.exp BF537-STAMP
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/ppifcd$ ./ppifcd_test.exp BF537-STAMP  
  • If the picture of “ppifcd.bmp” can open ,and the picture is normal,the test pass.

Can bus driver

  • BF537-STAMP BF548-EZKIT and BF609-EZKIT should be tested.
  • This test needs two same boardes,and connected by a telephone line.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/canbus$ ./build_canbus_kernel.exp BF537-STAMP
       (open minicom)
          root:/> ifconfig can0 down
          root:/> ifconfig can0 up
          root:/> candump can0
       (Switch to the machine sending data through can bus)
          root:/> ifconfig can0 down
          root:/> ifconfig can0 up
          root:/> cansend can0 123#AABBCCDD
          root:/> cansend can0 12345678#1122334455667788
          root:/> cangen can0  
       (On the machine receiving data, more information refer 2013trunk) 
  • Change the roles, if the slave can receive the data,the test pass.

Capacitor adc AD714x

  • Only BF537-STAMP should be tested.
  • This test needs AD7142 and AD7147,the hardware connection refers to “25.Capacitance Touch” https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/cap_touch$ ./build_cap_touch_kernel.exp BF537-STAMP
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/cap_touch$ ./cap_touch_test.exp BF537-STAMP 
  • According the tips, press the capacitive touch area,if you can receive feedback information,the test pass.

CoreB DSP framework

  • Only BF609-EZKIT should be tested.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/icc$ ./build_icc_resource_kernel.exp BF609-EZKIT
       (download the uImage, and open the minicom)
          root:/> cd /bin
          root:/bin> ./icc_loader -l icc
          root:/bin> ./icc_loader -e icc_resource 
  • If you see the led is lighted, the test pass.

CTS/RTS

  • Only BF537-STAMP should be tested.
  • Refer to “43.hardware flow controll RTS/CTS test” https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing
          ------------
          SW4 to be [on on on off]
          ---------------
          minicom -s
          Serial port setup
          F - Hardware Flow Control: Yes 
          ------------------
          root:/> cd bin/
          root:/bin>  rtscts_test ttyBF0 -t
          root:/bin> cat /proc/kallsyms
          -------------------------------------
          switch the SW4.3 to off, it would withhold the message from outputing. Switch back to on, printing resumes. 
          ------------------------------------  
  • The test phenomena refer to the log of 2013trunk.

DSA

  • Only BF518F-EZBRD should be tested.
  • This test needs BF518 which has two internetes.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/dsa$ ./build_dsa_kernel.exp BF518F-EZBRD
          (download the uImage ,and open the minicom)
          root:/> ifconfig eth0 0.0.0.0 up
          root:/> ifconfig eth1 10.100.4.50 up
          root:/> ifconfig eth2 192.168.1.2 down 
          root:/> cp bin/busybox srv/ftp/
          (turn to PC)
          test@test-OptiPlex-3010:~/workspace/src/kernel$ ping -c 10 10.100.4.50
          test@test-OptiPlex-3010:~/workspace/src/kernel$ ping -c 10 192.168.1.2
          test@test-OptiPlex-3010:~/workspace/src/kernel$ traceroute 10.100.4.50
          test@test-OptiPlex-3010:~/workspace/src/kernel$ traceroute 192.168.1.2
          test@test-OptiPlex-3010:~/workspace/src/kernel$ ftp 10.100.4.50
          ftp> get busybox
          ftp> put busybox
          ftp> exit
          test@test-OptiPlex-3010:~/workspace/src/kernel$ ls busybox
          (turn to board)
          root:/>  ifconfig eth2 192.168.1.2 down
          root:/> cp bin/busybox srv/ftp/
          root:/> ifconfig eth2 192.168.1.2 up
          (turn to PC)
          test@test-OptiPlex-390:~$ sudo ifconfig eth0 192.168.1.3
          test@test-OptiPlex-3010:~/workspace/src/kernel$ ping -c 10 192.168.1.2
          test@test-OptiPlex-3010:~/workspace/src/kernel$ ping -c 10 10.100.4.50
          test@test-OptiPlex-3010:~/workspace/src/kernel$ traceroute 192.168.1.2
          test@test-OptiPlex-3010:~/workspace/src/kernel$ traceroute 10.100.4.50
          test@test-OptiPlex-3010:~/workspace/src/kernel$ ftp 192.168.1.2
          ftp> get busybox
          ftp> put busybox
          ftp> bye
          test@test-OptiPlex-3010:~/workspace/src/kernel$ ls busybox  
  • Refer the log of 2013trunk,if there are the same,test pass.

Generic GPIO driver

  • BF533-STAMP BF537-STAMP BF548-EZKIT BF527-EZKIT-V2 and BF609-EZKIT should be tested.
  • The hardware setup: SW5: on on on on for bf537 stamp board and bf548 ezkit board.SW13: on xx off off off off for bf527 ezkit board.Refer to “19.Generic gpio test” https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing/dsa.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/generic_gpio$ ./build_generic_gpio_kernel.exp BF533-STAMP
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/generic_gpio$ ./generic_gpio_test.exp BF533-STAMP 
  • According to the prompt, press the button, and check the message .If the value in the message is right,the test pass.More information refer to 2013trunk.

I2C Keypad and LCD driver over TWI port or GPIO

  • BF533-STAMP BF537-STAMP BF548-EZKIT BF527-EZKIT-V2 and BF609-EZKIT should be tested.
  • The hardware setup :
          BF533-STAMP: JP1 set 15-16
          BF537-STAMP: JP1 set 15-16
          BF609-EZKIT: JP1 set 15-16
          BF548-EZKIT: JP1 set 9-10
          BF527-EZKIT: JP1 set 9-10
          For BF527 board jumper “STAMP_ENABLE” must be shorted to turn on the TWI signal. It's JP7 on 2.x board and JP3 on 1.x board 
  • The Keypad don't need to test.The LCD hardware refer to https://docs.blackfin.uclinux.org/doku.php?id=blackfin_twi_lcd_hd44780_based_driver.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/i2ctwi$ ./build_i2ctwi_lcd_kernel.exp BF537-STAMP
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/i2ctwi$ ./i2ctwi_lcd_test.exp BF537-STAMP 
  • If you can see some message show on the LCD ,the test pass.

Ieee 1588 ptp

  • Only BF518F-EZBRD should be tested.
  • This test needs two same boardes,one work as master,another work as slave.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/ptp$ ./build_ptp_kernel.exp  BF518F-EZBRD
       (download the uImage, and open the minicom,connect the two boardes by a network cable)
       (The master)
          root:/>  ifconfig
          root:/> date
          root:/> date -s 2013.04.02-15:54
          root:/> date 
          root:/>   testptp -g
          root:/> testptp -s
          root:/>   testptp -g
          root:/> ptp4l -i eth0 -q -v
       (change another,the slave)
          root:/> ifconfig eth0 10.100.4.51
          root:/> ping 10.100.4.50
          root:/> ptp4l -i eth0 -q -v -s
          root:/> date
          root:/> phc2sys -s /dev/ptp0
          root:/> date                         
  • If the date of slave is the same as the master's,the test pass.

Keypad

  • Only BF548-EZKIT should be tested.
  • Connect the 4×4 keypad into the keypad interface.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/keypad$ ./build_keypad_kernel.exp BF548-EZKIT
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/keypad$ ./keypad_test.exp BF548-EZKIT 
  • According the prompt,press the button.If the script can finish successfully,the test pass.

NAND Flash MTD driver

  • BF548-EZKIT BF527-EZKIT-V2 and BF526-EZBRD should be tested.
  • On BF527-EZKIT board, switch SW1: [off off on off], SW11: [x x x on]. On BF526-EZBRD board, SW12: [off off on off], SW13: [x x x on].
      test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/nand$ ./build_nand_kernel.exp BF548-EZKIT
      test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/nand$ ./nand_test.exp BF548-EZKIT 
  • If the script can finish successfully,the test pass.

Pfbutton driver

  • BF533-STAMP BF537-STAMP and BF609-EZKIT should be tested.
  • Refer to “20.Pfbutton driver test” https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/pfbutton$ ./build_pfbutton_kernel.exp BF537-STAMP
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/pfbutton$ ./pfbutton_test.exp BF537-STAMP 
  • According the prompt,press the button,if the board can receive the message,the test pass.

Rotary input device driver

      test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/rotary$ ./build_rotary_kernel.exp BF518-EZKIT
      test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/rotary$ ./rotary_test.exp BF518-EZKIT 
  • Turn the switch(BF548 is sw3,BF527 is sw3,BF609 is sw9) to simulate the displacement change, if the message on the board is changing,the test pass.

NDSO AWG

   (NDSO)
      test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/spiadc$ ./build_ndso_kernel.exp BF537-STAMP
   (download the uImage and open minicom)
      root:/> ifconfig  eth0 10.100.4.50
      root:/> thttpd
   (Open the web browser on host system, such as Mozilla, Firefox, IE. Enter in the URL target ip address: http://10.100.4.50)
   (Hit Acquire button on the left, the picture sampled by the ADC converter can now be seen on website)
   (If the peak of the wave is about 3V,the test pass.)  
   (AWG)
      test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/spiadc$ ./build_awg_kernel.exp BF537-STAMP
   (download the uImage and open minicom)
      root:/> ifconfig eth0 10.100.4.50                                                                                         
      root:/> thttpd
   (Open the web browser on host system, such as Mozilla, Firefox, IE. Enter in the URL target ip address: http://10.100.4.50)
   (Connect oscilloscope to the board,to output waveform by creating on website)
   (If you can see the same waveform as on the website,the test pass.)  

Touchscreen

  • There are two kinds of ports for touchscreen connection: SPI port for BF537-STAMP/BF527-EZKIT/BF609-EZKIT; PPI port for BF548-EZKIT.
  • Hardware setup and connection refer to “48.Touchscreen” https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:testing.
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/touchscreen$ ./build_touchscreen_kernel.exp BF548-EZKIT
          test@test-OptiPlex-3010:~/workspace/src/kernel/testsuites/touchscreen$ ./touchscreen_test.exp BF548-EZKIT  
  • Touch the screen when run the script of touchscreen_test.exp,if the board can show the message of press location, the test pass.