uboot ITP

Document Sample
uboot ITP Powered By Docstoc
					    iSoftTech




   uboot – BF535
Integration Test Plan
uboot - ITP                                                                               Revision: 1.1




 Edit History
 Revision     Date         Author            Description

 1.0          08th March   Bama S
              04
 1.1          15th March   Ganapathi         Updated the TFTP and DHCP Test cases
              04
 1.2          25th March   Ganapathi         Added some more test case as per the ADI feedback
              04
 1.3          1st April    Ganapathi         Added new network commands test for crossover cable
              04                             and Ethernet switch.
                                             Added test case for the command “iminfo”
                                             These test cases added as per ADI feedback




5/18/2012                              iSoftTech - Confidential & Proprietary              Page 2 of 28
uboot - ITP                                                                                  Revision: 1.1




                                     Proprietary Notice

The information and descriptions contained herein embody confidential and proprietary information,
which is the property of iSoftTech. Such information and descriptions may not be copied, reproduced,
disclosed to others, published or used, in whole or in part, for any purpose other than that for which it
is being made available without the express prior written permission of iSoftTech.




                                        Change Notice

     The information in this document has been carefully checked and is believed to be entirely
reliable. However, no responsibility is assumed for inaccuracies. Furthermore, iSoftTech reserves
the right to make changes without notice to any products or plan herein to improve reliability, function
or design.




5/18/2012                                iSoftTech - Confidential & Proprietary               Page 3 of 28
uboot - ITP                                                                                                                                           Revision: 1.1



                                                                Table of Contents
1.     Purpose .......................................................................................................................................................... 5
2.     Scope of this document .................................................................................................................................. 5
3.     Abbrevations .................................................................................................................................................. 5
4.     References...................................................................................................................................................... 5
5.     Test Strategy and Methodology ..................................................................................................................... 5
6.     Test Setup ...................................................................................................................................................... 5
7.     Automation .................................................................................................................................................... 6
8.     Test equipment required ................................................................................................................................ 6
9.     Test Cases ...................................................................................................................................................... 6
     9.1.      Uboot from flash .................................................................................................................................... 6
     9.2.      Console command test ........................................................................................................................... 6
       9.2.1.          OS loading commands ................................................................................................................... 6
       9.2.2.          U-boot up gradation commands ..................................................................................................... 8
       9.2.3.          Environment variable setting and access commands .................................................................... 10
       9.2.4.          Memory access commands ........................................................................................................... 12
       9.2.5.          Miscellaneous commands ............................................................................................................ 14
     9.3.      Network commands ............................................................................................................................. 18
       9.3.1.          PING test cases ............................................................................................................................ 18
       9.3.2.          TFTPBOOT test cases ................................................................................................................. 20
       9.3.3.          DHCP test cases ........................................................................................................................... 22
     9.4.      Auto boot test cases ............................................................................................................................. 23
10.         Sign Off Table ......................................................................................................................................... 28
11.         Review Notes ........................................................................................................................................... 28




5/18/2012                                                         iSoftTech - Confidential & Proprietary                                                Page 4 of 28
uboot - ITP                                                                              Revision: 1.1




1.       Purpose
uboot – BF535 is ported version of u-boot-1.0.0 and is ported to Blackfin (ADSP-BF535) - EZ-Kit.
This bootloader supports the following features.
     1. Auto boot.
     2. Support for OS loading commands (like boot, bootelf, bootp, loads, loadb).
     3. U-boot up gradation commands (like erase, cp, protect).
     4. Environment variables setting and access commands (like setenv, saveenv, printenv).
     5. Memory usage commands (like md, cmp, mw, nm and etc).
     6. Miscellaneous commands (like bdinfo, flinfo, echo, go and etc).
     7. Supports Network features – PING, TFTP and DHCP
     8. MAC address reading from EEPROM.
     9. Serial download of image.

2.       Scope of this document
This document lists all the Test Cases to be conducted for the Integrated Testing.

3.       Abbrevations
UUT            Unit Under Test

4.       References
     1. Requirement specification - BSP for EZ-Kit 535 + PT – LAN Card

5.       Test Strategy and Methodology
The following test cases are planned to tested as part of this project development
     1. uboot booting from flash
     2. Console commands testing
     3. Network features – PING, TFTP and DHCP
     4. Feature list of the u-boot.

6.       Test Setup
                                   Ethernet
       PC                Eth0                                  Eth0   EZ-Kit (UUT)
                                   Serial connection
                         RS232                         UART1
                                              TEST_SETUP 1




5/18/2012                                 iSoftTech - Confidential & Proprietary          Page 5 of 28
uboot - ITP                                                                           Revision: 1.1



7.      Automation
No automation is planned

8.      Test equipment required
              1.   PC running Linux.
              2.   EZ-Kit board.
              3.   Serial port connection.
              4.   Ethernet connection.

9.      Test Cases

9.1.    Uboot from flash
Test case Id               IT_1
Purpose                    To test uboot booting from flash
Test Setup                 TEST_SETUP 1

Pre-condition              Connect the power supply and connect EZ_kit UART1 console
                           with the host PC with Host baud rate 57600. Refer APPENDIX 1
                           for first time flash programming.
Test procedure             Switch on EZ-Kit. U-boot starts running from flash and gives the
                           serial console output.
Input                      None
parameter(s)
Expected                   Console prompt and uClinux loading complete
result(s)

9.2.    Console command test

9.2.1. OS loading commands
Test case Id               IT_2
Purpose                    To test following OS loading commands. These commands are
                           used to load the OS image from remote place (network or serial
                           port) or RAM.
                           boot     - boot default, i.e., run 'bootcmd'
                           bootelf - Boot from an ELF image in memory
                           loadb - load binary file over serial line (kermit mode)
Test Setup                 TEST_SETUP 1

Pre-condition              Connect the power supply and connect the EZ_Kit console



5/18/2012                                    iSoftTech - Confidential & Proprietary   Page 6 of 28
uboot - ITP                                                              Revision: 1.1


                 UART1 with the host PC.
Test procedure   boot - boot default. This command runs the bootcmd
                 environment settings. Type the command “boot”, see whether
                 booting is based on the environment setting in bootcmd.
                 Example : Say the Env variable
                 tftpboot = tftp 0x800000 linux.dxe; bootelf 0x800000
                 bootcmd = run tftpboot.
                 Then on tying boot, it invokes the tftpboot.


                 bootelf - Boot from an ELF image in memory. This command is
                 used to load the ELF image from the memory. After
                 downloading the image into RAM , type bootelf <image start
                 address> to load the image.
                 loadb - load binary file over serial line (kermit mode). This
                 command is used to load the binary image file through the serial
                 port.


Input            None
parameter(s)
Expected         All the above commands executed successfully
result(s)



Test case Id     IT_3
Purpose          To test uboot booting with Large ELF file.
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_kit UART1 console
                 with the host PC with Host baud rate 57600.
                 Place a Large ELF image file (less than 8MB) in the tftp server.
                 Refer APPENDIX 1 for first time flash programming.
Test procedure   Switch on EZ-Kit. U-boot starts running from flash and gives the
                 serial console output and automatically load the image from the
                 tftp server.
Input            None
parameter(s)
Expected         Large ELF image (size less than 8MB) loading completed
result(s)        successfully




5/18/2012                       iSoftTech - Confidential & Proprietary   Page 7 of 28
uboot - ITP                                                              Revision: 1.1



Test case Id     IT_4
Purpose          To test uboot booting with small ELF file.
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_kit UART1 console
                 with the host PC with Host baud rate 57600.
                 Place a small ELF image file in the tftp server.
                 Refer APPENDIX 1 for first time flash programming.
Test procedure   Switch on EZ-Kit. U-boot starts running from flash and gives the
                 serial console output and automatically load the image from the
                 tftp server.
Input            None
parameter(s)
Expected         Small ELF image loading completed successfully
result(s)

9.2.2. U-boot up gradation commands
Test case Id     IT_5
Purpose          To test following U-boot upgradation commands. These
                 commands are used to upgrade the u-boot in the flash through
                 u-boot.
                 erase - erase FLASH memory
                 cp     - memory copy
                 protect - enable or disable FLASH write protection
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_Kit Console UART1
                 with host PC.
Test procedure   erase - This command is used erase the FLASH memory. Using
                 this command individual sector or whole flash can be erased.
                 erase bank:sector – erase the particular sector in the flash.
                 cp     - This command is used to copy the memory.
                 protect – This command is used to write protect the flash
                 sector.
                 Follow the Test Sequence given in the APPENDIX 2 to perform
                 this test
Input            None
parameter(s)



5/18/2012                       iSoftTech - Confidential & Proprietary   Page 8 of 28
uboot - ITP                                                                Revision: 1.1



Expected         All the tests in the test procedure are successful.
result(s)



Test case Id     IT_6
Purpose          To test flash erase command for the following case.
                 i) erase N:SF-SL(flash bank N and SF-starting sector SL-ending
                 sector).
                 ii) erase bank N
                 iii) erase all
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_Kit Console UART1
                 with host PC.
Test procedure   i) erase N:SF-SL – erase the sector starting (SL) to sector
                 ending(SF) in the Bank N.
                 Example
                  erase 1:0-3 – erase sector 0 to 3 in the bank 1.
                 ii) erase bank N – erase the flash bank N.
                 iii) erase all – erase the all bank in the flash
Input            None
parameter(s)
Expected         Flash sectors erased successfully
result(s)



Test case Id     IT_7
Purpose          To test flash sectors protect command for the following case.
                 i) protect enable/disable N:SF-SL (flash bank N, SF=starting
                 sector, SL=ending sector)
                 ii) protect enable/disable bank N
                 iii) protect enable/disable all

Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_Kit Console UART1
                 with host PC.
Test procedure   i) protect enable/disable N:SF-SL – protect the sector starting
                 (SL) to sector ending(SF) in the Bank N.


5/18/2012                         iSoftTech - Confidential & Proprietary   Page 9 of 28
uboot - ITP                                                                    Revision: 1.1



                 Example
                  protect on 1:0-3 – protect sector 0 to 3 in the bank 1.
                  protect off 1:0-3 – unprotect sector 0 to 3 in the bank 1.


                 ii) protect enable/disable bank N – protect/unprotect the flash
                 bank N.
                 iii) protect enable/disable all – protect/unprotect the all bank in
                 the flash
Input            None
parameter(s)
Expected         Flash sectors protected/unprotected successfully
result(s)


Test case Id     IT_8
Purpose          To test cp command for the following cases
                 i) test cp.b, cp.w, cp for less number of data
                 i) test cp.b, cp.w, cp for large number of data


Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_Kit Console UART1
                 with host PC.
Test procedure   i) Use the cp command for byte, word and long word copy with
                 very less count (i.e count is 1).
                 ii) Use the cp command for byte, word and long word copy with
                 very large count.


Input            None
parameter(s)
Expected         cp command is copying small and large number of data
result(s)        successfully.

9.2.3. Environment variable setting and access commands
Test case Id     IT_9
Purpose          To test following environment variable setting commands. These
                 commands are used to set, edit and save environment variables
                 in the flash.



5/18/2012                       iSoftTech - Confidential & Proprietary         Page 10 of 28
uboot - ITP                                                                       Revision: 1.1



                 setenv - set environment variables
                 saveenv - save environment variables to persistent storage
                 printenv- print environment variables
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect the EZ_Kit console
                 UART1 with the host PC.
Test procedure   setenv - This command is used to add new environment
                 variables. Type setenv <variable name> <value>
                 example : setenv ipaddr 192.168.0.45
                 saveenv – This command is used to save the environment
                 variables to flash. Type saveenv to save the environment
                 variables.
                 printenv- This command is used to display the environment
                 variables. Type printenv
Input            None
parameter(s)
Expected         All the above commands are executed successfully
result(s)


Test case Id     IT_10
Purpose          To test following cases for the setenv command separately


Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect the EZ_Kit console
                 UART1 with the host PC.
Test procedure   i) Test deleting environment variables
                 example:
                   setenv <environment variable name>
                   setenv bootdelay - to delete the environment variable ‘bootdelay’.
                 ii) Test setting environment variables multiple times with
                 different values, checking that each time works correct
                 set a large number of environment variables: 50 test deleting
                 environment variables.
                 example:
                   setenv <environment variable name> <value>
                   setenv bootdelay 10.




5/18/2012                       iSoftTech - Confidential & Proprietary            Page 11 of 28
uboot - ITP                                                               Revision: 1.1



                 iii) set a large number of environment variables: 50


Input            None
parameter(s)
Expected         i) Environment variable deleted successfully
result(s)        ii) Environment variable’s value changed successfully.
                 iii) More than 50 environment variable created successfully.


Test case Id     IT_11
Purpose          To test following cases for the saveenv command separately


Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect the EZ_Kit console
                 UART1 with the host PC.
Test procedure   i) run saveenv with 5 environment variables, then delete all but
                 one, then run saveenv, then reset/reboot, then run printenv

                 ii) delete all environment variables, then reset/reboot, then run
                 printenv
Input            None
parameter(s)
Expected         All the above cases are executed successfully
result(s)

9.2.4. Memory access commands
Test case Id     IT_12
Purpose          To test following memory access commands. These commands
                 are used to compare, display, modify and etc in memory.
                 cmp     - memory compare
                 md      - memory display
                 mm      - memory modify (auto-incrementing)
                 mw      - memory write (fill)
                 nm      - memory modify (constant address)


Test Setup       TEST_SETUP 1




5/18/2012                       iSoftTech - Confidential & Proprietary    Page 12 of 28
uboot - ITP                                                             Revision: 1.1



Pre-condition    Connect the power supply and connect the EZ-Kit console
                 UART1 with host PC.
Test procedure   cmp - This command is used to compare portion of the
                 memory content.
                 example : cmp.w 0x10000 0x2000000 0x800
                 The above example compares the 0x800 words starting from the
                 locations specified in the command.
                 md     - This command is used to display the memory content.
                 example : md.w 0x10000 0x10
                 The above example displays the 0x800 words of the memory
                 content, starting from the location in the command. To quit press
                 CTRL+C


                 mm     - This command is used to modify the content of the of
                 the memory. The address for the consequent memory will be
                 incremented automatically.
                 example : mm.w 0x10000
                 The above example modify the content of memory from starting
                 address specified in the command the address will be
                 incremented automatically. To quit press CTRL+C.
                 mw      - This command is used to write specified value in the
                 specified location of the memory.
                 example : mw.w 0x10000 0x0 0x10
                 The above example writes the value 0 from starting address
                 (0x1000) specified in the command to next 0x10 words. To quit
                 press CTRL+C


                 nm     - This command is used to modify the content of
                 specified location(constant address) of the memory.
                 example : nm.w 0x10000
                 The above example modify the content of memory at address
                 specified in the command. To quit press CTRL+C
                 Note: For more help about these commands type “help
                 <command name>”.
Input            None
parameter(s)
Expected         All the above commands are executed successfully



5/18/2012                     iSoftTech - Confidential & Proprietary    Page 13 of 28
uboot - ITP                                                              Revision: 1.1


result(s)



Test case Id     IT_13
Purpose          To test mw command for the following cases
                 i) test mw.b, mw.w, mw for less number of data
                 i) test mw.b, mw.w, mw for large number of data


Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_Kit Console UART1
                 with host PC.
Test procedure   i) use the mw command for byte, word and long word write in
                 memory with very less count(i.e count is 1).
                 ii) Use the mw command for byte, word and long word write in
                 memory with very large count.


Input            None
parameter(s)
Expected         mw command is writing small and large number of data
result(s)        successfully.

9.2.5. Miscellaneous commands
Test case Id     IT_14
Purpose          To test following other commands in the u-boot. These
                 command are miscellaneous commands.
                 flinfo - print FLASH memory information
                 go      - start application at address 'addr'
                 help    - print online help
                 run     - run commands in an environment variable
                 version - print monitor version
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect the EZ-Kit console
                 UART1 with host PC.
Test procedure   flinfo - print FLASH memory information
                 go      - start application at address 'addr'



5/18/2012                       iSoftTech - Confidential & Proprietary   Page 14 of 28
uboot - ITP                                                              Revision: 1.1



                 help    - print online help
                 run     - run commands in an environment variable
                 version - print monitor version


                 Note: For more help about these commands type “help
                 command name>”.


Input            None
parameter(s)
Expected         All the above commands are executed successfully
result(s)



Test case Id     IT_15
Purpose          To test reset command.
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_Kit Console UART1
                 with host PC.
Test procedure   Test the reset command in the u-boot.
Input            None
parameter(s)
Expected         The board reset working successfully
result(s)


Test case Id     IT_16
Purpose          To test bdinfo command
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_Kit Console UART1
                 with host PC.
Test procedure   Use the bdinfo command to display the board details and ip
                 address details.
Input            None
parameter(s)
Expected         The board details displayed are correct.
result(s)



5/18/2012                       iSoftTech - Confidential & Proprietary   Page 15 of 28
uboot - ITP                                                                Revision: 1.1



Test case Id     IT_17
Purpose          To test coninfo command
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_Kit Console UART1
                 with host PC.
Test procedure   Use the coninfo command to display the console details (like
                 flags and in/out devices)
Input            None
parameter(s)
Expected         The console details displayed are correct.
result(s)



Test case Id     IT_18
Purpose          To test crc32 command
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_Kit Console UART1
                 with host PC.
Test procedure   Use the crc32 command to calculate the checksum.
Input            None
parameter(s)
Expected         The checksum calculated successfully
result(s)



Test case Id     IT_19
Purpose          To test iminfo command
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_Kit Console UART1
                 with host PC.
Test procedure   Use the iminfo command to show the image information (like
                 Image Name, Image Type, Data Size, Load Address, Entry
                 Point and etc.)
                 Example:
                         Iminfo




5/18/2012                         iSoftTech - Confidential & Proprietary   Page 16 of 28
uboot - ITP                                                              Revision: 1.1




Input            None
parameter(s)
Expected         The image information displayed successfully
result(s)




Test case Id     IT_20
Purpose          To test echo command
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_Kit Console UART1
                 with host PC.
Test procedure   Use the echo command to display the string in the u-boot
                 console. Use this command for very large string.
Input            None
parameter(s)
Expected         Echo command is working successfully.
result(s)
Test case Id     IT_21
Purpose          To test sleep command
Test Setup       TEST_SETUP 1

Pre-condition    Connect the power supply and connect EZ_Kit Console UART1
                 with host PC.
Test procedure   Use the sleep command to provide the delay in seconds.
                 Test sleep for very large arguments, possibly as an overnight
                 test.
Input            None
parameter(s)
Expected         Sleep command is working successfully.
result(s)



Test case Id     IT_22
Purpose          To test invalid command.



5/18/2012                       iSoftTech - Confidential & Proprietary   Page 17 of 28
uboot - ITP                                                                Revision: 1.1



Test Setup        TEST_SETUP 1

Pre-condition     Connect the power supply and connect EZ_Kit Console UART1
                  with host PC.
Test procedure    Type the invalid command in the prompt.
Input             None
parameter(s)
Expected          “Invalid command” displayed in the console.
result(s)



Test case Id      IT_23
Purpose           To test file size updated in the environment variable.
Test Setup        TEST_SETUP 1

Pre-condition     Connect the power supply and connect EZ_Kit Console UART1
                  with host PC.
Test procedure    Check the image file size after loading from the remote machine.
Input             None
parameter(s)
Expected          The file size is updated successfully
result(s)

9.3.    Network commands

9.3.1. PING test cases
Test case Id      IT_24
Purpose           Test Ping – the simple command
Test Setup        TEST_SETUP 1

Pre-condition     Configure the IP address by setting the environment variable
                  “ipaddr” and Ethernet address environment variable “ethaddr”.
                  Also set the server ipaddress and gateway env variables –
                  “serverip” and “gatewayip”
Test procedure    Ping from PC to UUT, and UUT to PC
Input             None
parameter(s)
Expected          Ping succeeds
result(s)



5/18/2012                        iSoftTech - Confidential & Proprietary    Page 18 of 28
uboot - ITP                                                              Revision: 1.1




Test case Id     IT_25

Purpose          To Test whether Ping replies are received without any missing
                 sequence number
Test Setup       TEST_SETUP 1

Pre-condition    Configure the IP address by setting the environment variable
                 “ipaddr” and Ethernet address environment variable “ethaddr”.
                 Also set the server ipaddress and gateway env variables –
                 “serverip” and “gatewayip”
Test procedure   Ping from PC to UUT and UUT to PC
                 Check for Ping replies on PC and UUT respectively
Input            None
parameter(s)
Expected         Ping replies should be displayed without any missing sequence
result(s)        number.


Test case Id     IT_26

Purpose          To Test whether ICMP destination unreachable message is
                 displayed when the ping application is run to some non-existed
                 machine in the remote network.
Test Setup       TEST_SETUP 1

Pre-condition    Configure the IP address by setting the environment variable
                 “ipaddr” and Ethernet address environment variable “ethaddr”.
                 Also set the server ipaddress and gateway env variables –
                 “serverip” and “gatewayip”
Test procedure   Ping from UUT to some non-existed machine in the remote
                 network.

                 Run tcpdump to capture ICMP error packet on the local
                 network.
Input            None
parameter(s)
Expected         ICMP destination unreachable error message should be
result(s)        generated by UUT and captured by tcpdump utility on the local
                 network.




5/18/2012                       iSoftTech - Confidential & Proprietary   Page 19 of 28
uboot - ITP                                                                        Revision: 1.1


9.3.2. TFTPBOOT test cases
Test case Id     IT_27
Purpose          To get the file to RAM, through tftpboot command
Test Setup       TEST_SETUP 1

Pre-condition    TFTP Server Configuration:

                 In the file /etc/xinetd.d/tftp set the following configurations
                 service tftp
                 {
                      disable = no
                      socket_type              = dgram
                      wait                = yes
                      user                = nobody
                      log_on_success              += USERID
                      log_on_failure           += USERID
                      server               = /usr/sbin/in.tftpd
                      server_args              = /tftpboot
                 }

                 Restart TFTP Server.
                 copy the linux.dxe into /tftpboot

                 TFTP Client Configuration:
                 Configure the IP address by setting the environment variable “ipaddr” and
                 Ethernet address environment variable “ethaddr”.
                 Also set the server ipaddress and gateway env variables – “serverip” and
                 “gatewayip”
Test procedure   Use the tftpboot command as follows
                 Tftpboot <load address> <remote file>
Input            None
parameter(s)
Expected         Loading complete
result(s)


Test case Id     IT_28
Purpose          To test the TFTP boot through the hub
Test Setup       TEST_SETUP 1

Pre-condition    Configure the tftp server and the client IP address as mentioned
                 in the test case IT_27
                 Type the command “run tftp_boot” to do this test.
Test procedure
Input            None



5/18/2012                         iSoftTech - Confidential & Proprietary           Page 20 of 28
uboot - ITP                                                              Revision: 1.1


parameter(s)
Expected         TFTP Loading complete.
result(s)


Test case Id     IT_29
Purpose          To test the TFTP boot through the Crossover cable.
Test Setup       TEST_SETUP 1

Pre-condition    Configure the tftp server and the client IP address as mentioned
                 in the test case IT_27
                 Type the command “run tftp_boot” to do this test.
Test procedure
Input            None
parameter(s)
Expected         TFTP Loading complete.
result(s)


Test case Id     IT_30
Purpose          To test the TFTP boot through the Ethernet switch
Test Setup       TEST_SETUP 1

Pre-condition    Configure the tftp server and the client IP address as mentioned
                 in the test case IT_27
                 Type the command “run tftp_boot” to do this test.
Test procedure
Input            None
parameter(s)
Expected         TFTP Loading complete.
result(s)


Test case Id     IT_31
Purpose          To test the network boot failure where the host stops sending
                 files.
Test Setup       TEST_SETUP 1

Pre-condition    Configure the tftp server and the client IP address as mentioned
                 in the test case IT_27
Test procedure   Run tftp_boot to load the image from the remote machine.
                 Remove the network cable. wait for 5minutes.Check whether the
                 loading stopped and nothing happened until the user
                 intervention.


5/18/2012                       iSoftTech - Confidential & Proprietary   Page 21 of 28
uboot - ITP                                                                 Revision: 1.1




Input            None
parameter(s)
Expected         Image Loading is not completed.
result(s)

9.3.3. DHCP test cases
Test case Id     IT_32
Purpose          To get IP from the DHCP server dynamically and load the image
                 from the remote machine using tftp.
Test Setup       TEST_SETUP 1

Pre-condition    Note : DHCP is used to assign the IP address and also to get
                 the boot parameters like boot file name. It then loads the image.
                 DHCP provides same functionality as bootp . Hence bootp
                 wouldnot be tested.
                 Test AutoBoot to boot the image from the DHCP Server. Refer
                 Test Case IT_12 for more details on Autoboot.
                 The System running DHCP Server should also run TFTP Server.
                 Refer Test Case IT_10 for TFTP Server Configuration.
                 DHCP Server Configuration:
                 In the /etc/dhcpd.conf file set the following parameter.
                 filename "/tftpboot/linux.dxe"
                 Restart the dhcp server
                 DHCP Client Configuration.
                 Configure the Ethernet address environment variable “ethaddr”.
Test procedure   Type the command “dhcp” to do this test.


Input            None
parameter(s)
Expected         Observe whether the following environment variables are
result(s)        updated due to DHCP
                 ipaddr, serverip, gatewayip, netmask.
                 TFTP Loading complete.


Test case Id     IT_33



5/18/2012                        iSoftTech - Confidential & Proprietary     Page 22 of 28
uboot - ITP                                                                        Revision: 1.1



Purpose            To test booting over the network where the server is many hops
                   away from the board under test
Test Setup         TEST_SETUP 1

Pre-condition      Have the server in one subnet and client in other subnet.
                   Interface these subnets through the routers with BOOTP/DHCP
                   relay agent.
Test procedure     Load the image from the remote machine in the different subnet.
Input              None
parameter(s)
Expected           Image Loading complete.
result(s)

9.4.    Auto boot test cases
Test case Id       IT_34
Purpose            To test auto boot feature
Test Setup         TEST_SETUP 1

Pre-condition      Connect the power supply and connect EZ_kit UART1 console
                   with the host PC.
Test procedure     Switch on EZ-Kit. U-boot starts running from flash and it will wait
                   for the user to press any key. If the user has not pressed any
                   key till the delay count to 0 then u-boot will download the image
                   from the remote place and loads the image automatically.
                   Autoboot also has to be tested for the following feature. By
                   varying the bootcmd as given below, booting through TFTP or
                   DHCP and TFTP should be possible.

                   Example :
                   Say :
                   bootcmd=run tftp_boot to boot through TFTP
                   bootcmd=run dhcp_boot to boot through DHCP and TFTP

                   Here:
                   tftp_boot=tftp 0x800000 linux.dxe ; bootelf 0x800000
                   dhcp_boot = dhcp ; bootelf 0x800000 ( load address for the DHCP cannot be
                                                           changed dynamically. It is fixed to
                                                            0x800000).



Input              None
parameter(s)
Expected           uClinux loading complete



5/18/2012                         iSoftTech - Confidential & Proprietary          Page 23 of 28
uboot - ITP                                            Revision: 1.1


result(s)




5/18/2012     iSoftTech - Confidential & Proprietary   Page 24 of 28
uboot - ITP                                                                                Revision: 1.1



                                           APPENDIX 1


uboot Flash Programming

    1. Load u-boot.hex file generated after building the uboot , into flash using the visualDSP
       flashprogrammer

    2. The following changes has to be done in the uClinux distribution to boot the uClinux through
       u-boot. This is because the u-boot runs in the location 0x1000.

         In the linker script
                   uClinux-dist/linux-2.4.x/arch/frionommu/platform/frio/ADI/ram.ld in

         the MEMORY section.

         ram       : ORIGIN = 0x1000,         LENGTH = 0x1000000
         change to
         ram         : ORIGIN = 0x20000,        LENGTH = 0xffffff

         And .text (.= 0x1000) section starting should be changed
         from .= 0x1000 to .= 0x20000.

    3.   Connect serial port with EZKit UART1.

    4.   Use the serial port terminal with the following settings in the host machine

         baud rate: 57600kbps
         Data: 8bit
         Parity: None
         Stop bit: 1

    5.   Power On EZKit. U-boot boots from flash and displays version details.




5/18/2012                                iSoftTech - Confidential & Proprietary           Page 25 of 28
uboot - ITP                                                                                    Revision: 1.1



                                           APPENDIX 2
u-boot upgradation procedure

    1. copy the bin file from the tftp server to RAM at 0x20000. Use the following command for this.

        tftp 0x20000 u-boot.bin

    2. The flash in the EZKit has two non-contiguous regions, both are used to program the uboot
       which is a two stage bootloader. Erase the flash before reprogramming. Use the following
       commands to erase the boot flash and application flash sectors.

        i) erase 1:0 - to erase sector 0 in the bank 1
        ii) erase 1:4 - to erase sector 4 in the bank 1
        iii) erase 1:5 - to erase sector 5 in the bank 1

    3. Overwrite the new u-boot code from the RAM at 0x20000.We need to overwrite both the boot
       flash and the application flash regions separately. The region of these flash as follows

        0x20000000 - 0x20008000 - boot flash.
        0x20020000 - 0x200A0000 - application flash.

        u-boot is compiled and linked as follows. It has two parts.

        First part of the u-boot is linked to run from the sector 0 in the boot flash. This has minimum
        CPU and RAM initialization. This also moves the second part of uboot from application flash
        to RAM and transfers control to uboot code in the RAM.

        The second part is linked to run from RAM but initially copied to application flash.

        The u-boot binary file have the data to overwrite both flash regions. First 0x1000 bytes forms
        the fist stage of uboot, copied to the boot flash region. Rest (u-boot.bin binary file size -
        0x1000) of the bytes form the second stage of uboot, copied to the application flash region.

        Use the following commands to overwrite u-boot

        i) cp.w 0x20000 0x20000000 0x800 - overwrite the first stage uboot in the boot flash. here the
        count 0x800, is number of words.

        ii) cp.w 0x21000 0x20020000 0xC55C - overwrite the second stage u-boot. here the count
        0xC55C, is number of words.

        Note: If the flash regions are contiguous then we can overwrite the flash with     single
        command.


    4. Compare the u-boot overwritten in the flash with source in the RAM use the following
       commands

        i) cmp.w 0x20000 0x20000000 0x800
        ii) cmp.w 0x21000 0x20020000 0xC55C
        iii) if there an mismatch then do the step 2 and 3 again.




5/18/2012                                iSoftTech - Confidential & Proprietary                Page 26 of 28
uboot - ITP                                                                                Revision: 1.1



                                            APPENDIX 3
Board configuration:

EZ-Kit settings:

        1. BMODE DIP switch setting

                   1 2 3
                   ON ON ON

                   While power on EZ-Kit , the boot sequence starts from the
                   Async bank 0 (0x20000000). For more details refer Table 4-10
                   Reset Vector address in ADSP-BF535 hardware reference manual.

        2. PLL SETUP switch settings

                   1 2 3 4 5 6 7 8 9 10 11 12
                   OFF OFF OFF OFF ON ON ON ON OFF ON ON ON

                   This is the peripheral clock settng for 120Mhz.
                   For more details refer PLL overview in ADSP-BF535
                   hardware reference manual.

        3. Jumper setting ( to enable audio, feature not part of uboot)
               JP1 - short 1-3 and short 2-4. To select MIC in.
               JP2 - short 2-3, To Enable audio codec.
               For more details refer ADSP-BF535_EZKit-lite.pdf

EZ-LAN settings:

        1. Jumper settings


        JP4 and JP5 - short, Connects UART1 of BF535 to connector,
        uboot uses UART1 for console output and ucLinux also uses UART1 for console.


        JP1 and JP3 - open, since u-boot/ uclinux doesn't use UART0, these jumpers left open.

        JP2        - Controls timer1, timer2 and timer3. Since u-boot doesn't use timer,
                     this left open.

        JP8 - MAC address from EEPROM, enable or disable. If 1-2 connected access is disabled.
        JP9    - connect 2-3 - SMC91c111 Write enable for the BF535
        JP10 - connect 2-3 - SMC91c111 Read enable for the BF535

        2. u-boot uses UART1 for console, the output is availble at CON1.

        pin1   - Tx
        pin3   - Rx
        Pin2&4 - Gnd




5/18/2012                                 iSoftTech - Confidential & Proprietary           Page 27 of 28
uboot - ITP                                                                            Revision: 1.1



10.     Sign Off Table
The following template may be used for the sign-off list. Departments/Representatives may be added
deleted on an as needed basis.
       Dept/Org              Representative          Approved Signature              Date
                            (Name/Job Title)
Authors/ Leads –
isofttech
PM – isofttech
Software Development
– Customer
Hardware
Development –
Customer
System Verification &
Integration – Customer



11.     Review Notes




5/18/2012                             iSoftTech - Confidential & Proprietary           Page 28 of 28

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:12
posted:5/19/2012
language:Latin
pages:28