📄 testing_the_uboot.html
字号:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head> <title></title> <link rel="stylesheet" media="screen" type="text/css" href="./style.css" /> <link rel="stylesheet" media="screen" type="text/css" href="./design.css" /> <link rel="stylesheet" media="print" type="text/css" href="./print.css" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /></head><body><a href=start.html>start</a></br><div class="toc"><div class="tocheader toctoggle" id="toc__header">Table of Contents</div><div id="toc__inside"><ul class="toc"><li class="level1"><div class="li"><span class="li"><a href="#testing_uboot" class="toc">Testing Uboot</a></span></div><ul class="toc"><li class="level2"><div class="li"><span class="li"><a href="#purpose" class="toc">Purpose</a></span></div></li><li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div><ul class="toc"><li class="level3"><div class="li"><span class="li"><a href="#basic_command_tests" class="toc">Basic Command Tests</a></span></div></li><li class="level3"><div class="li"><span class="li"><a href="#added_feature_tests" class="toc">Added Feature Tests</a></span></div></li><li class="level3"><div class="li"><span class="li"><a href="#manual_test" class="toc">Manual test</a></span></div></li></ul></li><li class="level2"><div class="li"><span class="li"><a href="#environment" class="toc">Environment</a></span></div><ul class="toc"><li class="level3"><div class="li"><span class="li"><a href="#target_configuration" class="toc">Target Configuration</a></span></div></li><li class="level3"><div class="li"><span class="li"><a href="#host_configuration" class="toc">Host Configuration</a></span></div></li></ul></li><li class="level2"><div class="li"><span class="li"><a href="#uboot_test_steps" class="toc">Uboot test steps</a></span></div></li><li class="level2"><div class="li"><span class="li"><a href="#criteria" class="toc">Criteria</a></span></div></li><li class="level2"><div class="li"><span class="li"><a href="#problem_reporting_and_tracking" class="toc">Problem reporting and tracking</a></span></div></li><li class="level2"><div class="li"><span class="li"><a href="#limitations" class="toc">Limitations</a></span></div></li></ul></li></ul></div></div><h1><a name="testing_uboot" id="testing_uboot">Testing Uboot</a></h1><div class="level1"></div><!-- SECTION [1-28] --><h2><a name="purpose" id="purpose">Purpose</a></h2><div class="level2"><p> The purpose of testing U-Boot is to ensure the release is stable and robust, which can be used to initialize the target board and boot it into the uClinux kernel.</p></div><!-- SECTION [29-214] --><h2><a name="overview" id="overview">Overview</a></h2><div class="level2"><p> To test the Das U-boot, a host system and Blackfin target are required. The host system is where the U-Boot source code is downloaded and built. The Blackfin target enables tests to be run on the processor ensuring that the U-Boot binary can initialize the board properly before the uClinux kernel has been booted up. For now, there are four types of target boards available: STAMP board with Blackfin 533 chip, STAMP board with Blackfin 537 chip, EZKIT board with BF533 and EZKIT board with BF561. These four boards are covered in this test. Since there is some difference between them, the way to test the uboot also differs accordingly. And since Blackfin 534 is only one ethernet port less than the Blackfin 537 chip, the test for BF534 can be emulated by running on BF537 board. There is one case for BF537 to test if it can boot the kernel uImage through the serial port successfully.</p><p>The uboot test is taken at various system clock and core clock to ensue U-Boot support the boards at all the working frequencies well. The working range for both BF533 board and BF537 board is 30~120Mhz System Clock and 30~600Mhz Core Clock. For each board, four combinations of CSLK and SCLK are selected.<br/> </p><ul><li class="level1"><div class="li">stamp BF533 board: 552 Mhz 110 Mhz, 552Mhz 36 Mhz, 398 Mhz 79 Mhz, 99Mhz 49Mhz. <br/> </div></li><li class="level1"><div class="li">stamp BF537 board: 550 Mhz 110 Mhz, 500Mhz 50 Mhz, 500 Mhz 100 Mhz, 100Mhz 50Mhz. <br/> </div></li><li class="level1"><div class="li">ezkit BF561 board: 600 Mhz 120 Mhz, 600Mhz 60 Mhz, 660 Mhz 132 Mhz, 150Mhz 75Mhz. <br/> </div></li><li class="level1"><div class="li">ezkit BF533 board: 648 Mhz 129 Mhz, 594Mhz 59 Mhz, 594 Mhz 118 Mhz, 108Mhz 54Mhz. <br/> </div></li></ul><p>After download the U-Boot source code, change the CSLK and SCLK value in the stamp.h/bf537.h/ezkit561.h/ezkit533.h head file by redefine CONFIG_VCO_MULT, CONFIG_CCLK_DIV, and CONFIG_SCLK_DIV. Then build a u-boot.bin, flash it onto the board and do all the test cases to see if they can pass. When finished, it comes to the next combination of CSLK and SCLK, and go through the whole process all over again. The same apply to the left points. </p><p>And while running the test cases, to ensure that cache settings (either data cache or instruction cache) does not negativily effect any of the tests, all the tests will be executed 4 times on BF533 board(0.3 silicon) ,BF537 board(0.2 silicon) and BF561 EZKIT board(not BF533 EZKIT board) - with:</p><ul><li class="level1"><div class="li"> instruction cache off, data cache off</div></li><li class="level1"><div class="li"> instruction cache on, data cache off</div></li><li class="level1"><div class="li"> instruction cache off, data cache on</div></li><li class="level1"><div class="li"> instruction cache on, data cache on</div></li></ul><p> Since the U-Boot tests will load an elf uClinux image and uImage, it is necessary to have a known working uClinux kernel under <code>/tftpboot</code> on the host system.</p></div><!-- SECTION [215-2864] --><h3><a name="basic_command_tests" id="basic_command_tests">Basic Command Tests</a></h3><div class="level3"><p> U-Boot provides a set of commands to operate the resources, such as RAM, FLASH, serial port, and ethernet, on the board before the kernel is executed. The below tests attempt to ensure that all the features of U-Boot are working. </p><ol><li class="level1"><div class="li"> <strong>test countdown time period</strong></div><ul><li class="level2"><div class="li">It calculates the intermediate time between the 3rd and 2nd second when countdown in rebooting. Then the result is compared with 1 second. If the difference is less than 0.1, the case passes, otherwise it fails.</div></li></ul></li><li class="level1"><div class="li"><strong>version command</strong></div><ul><li class="level2"><div class="li"> Input the version command at the U-Boot prompt. If it can display the U-Boot version, it passes, otherwise it fails.</div></li></ul></li><li class="level1"><div class="li"> <strong>echo</strong></div><ul><li class="level2"><div class="li"> Input echo command followed by one sentence. If the output is the same as the sentence entered, the case passes, otherwise it fails.</div></li></ul></li><li class="level1"><div class="li"> <strong>help date</strong></div><ul><li class="level2"><div class="li"> Input this command to see if the help information is shown correctly. If the output is like 鈥淸MMDDhhmm]鈥⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -