📄 testing_the_uclinux_kernel.html
字号:
</li><li class="level1"><div class="li"> <strong>Serial driver test over UART port1</strong></div><ul><li class="level2"><div class="li">For the board that has the second UART port,it is also needed to see if it works right.</div></li><li class="level2"><div class="li">The test method is pretty much like the way to test the first UART port. </div></li></ul></li><li class="level1"><div class="li"> <strong>DPMC driver test</strong></div><ul><li class="level2"><div class="li"> Dynamic power managent controller test aims to see if this driver can change the VCO frequency, SCLK, CCLK, switch between different Modes, and change the Voltage successfully. Three points are selected: VCO 500M,SCLK 100M,CCLK 500M; VCO 300M,SCLK 100M,CCLK 300M; VCO 200M,SCLK 80M,CCLK 200M. The transition includes from Fullon to Active Mode and back, Fullon to Sleep Mode, back to Fullon, and then to Active Mode.</div></li><li class="level2"><div class="li"> Select the test case for dpmc : <pre class="code">under Customize Kernel Settings== Select Device Drivers == == Select Character devices == Enable Blackfin Power Management Support under Customize Vendor/User Settings== Select Blackfin test programs == Enable DPMC test program</pre></div></li></ul></li><li class="level1"><div class="li"> <strong>Pflags driver test</strong></div><ul><li class="level2"><div class="li"> Programmable flags test verifies the registers by writing different values to them to see if they can turn on and off the LED1 on STAMP board as expected. And it can also be checked by issue command: cat /proc/driver/pflags on target board shell to see the detailed information. If both are right, the case passes, otherwise it fails.</div></li><li class="level2"><div class="li"> Make the kernel configuraion like this:<pre class="code">under Customize Kernel Settings== Select Device Drivers == == Select Character devices == Enable Blackfin BF53x Programmable Flags Driver under Customize Vendor/User Settings== Select Blackfin test programs == Enable PFLAGS test program</pre></div></li></ul></li><li class="level1"><div class="li"> <strong>RTC test</strong></div><ul><li class="level2"><div class="li"> Real time conntroller tests to see if this device can be correctly read time for 6 times, set new RTC time, alarm time, and wait for the alarm ring. Then also a stop watch test and epoch reading. If all the cases run right, this test passes, otherwise it fails.</div></li><li class="level2"><div class="li"> Select the RTC test case when build the kernel:<pre class="code">under Customize Vendor/User Settings== Select Blackfin test programs == Enable RTC test program</pre></div></li></ul></li><li class="level1"><div class="li"> <strong>Timer tick test</strong></div><ul><li class="level2"><div class="li"> To check if the timer interrupt take place as required.</div></li><li class="level2"><div class="li"> There are three timer frequencies:100HZ, 250 HZ and 1000 HZ that can be selected. Selecting 100Hz means the timer would tick about 100 times every second. For 250HZ, 250 timer interrupts would happen. For 1000hz, about 1000 timer interrupts occur in each second.</div></li><li class="level2"><div class="li"> Select the following item when build the kernel:<pre class="code">under Customize kernel Settings== Select Blackfin Proccessor Options == == Select Clock Settings == == Select Timer frequency 100 HZ( 250 HZ or 1000 HZ)== </pre></div></li></ul></li><li class="level1"><div class="li"> <strong>I2C driver over TWI port(or GPIO) - Keypad, LCD</strong></div><ul><li class="level2"><div class="li"> To implement Keypad and LCD solution through I2C driver.</div></li><li class="level2"><div class="li"> The detailed info about keypad is at<a href="http://docs.blackfin.uclinux.org/doku.php?id=blackfin_twi_keypad_driver&s=twi" class="urlextern" title="http://docs.blackfin.uclinux.org/doku.php?id=blackfin_twi_keypad_driver&s=twi" rel="nofollow">the I2C Keypad doc</a>.</div></li><li class="level2"><div class="li"> The detailed info about LCD can check <a href="http://docs.blackfin.uclinux.org/doku.php?id=blackfin_twi_lcd_hd44780_based_driver&s=twi" class="urlextern" title="http://docs.blackfin.uclinux.org/doku.php?id=blackfin_twi_lcd_hd44780_based_driver&s=twi" rel="nofollow"> the I2C LCD doc</a>.</div></li></ul></li><li class="level1"><div class="li"> <strong>Joystick</strong><pre class="code">under Customize kernel Settings== Select Blackfin Processor Options == == Select BF537 Specific Configuration == --- PORT F/G Selection Select BF537/6/4 default GPIO PFx PORTG== Select Device Drivers == == Select I2C support == Enable I2C support Enable I2C device interface == Select I2C Hardware Bus support == Enable Blackfin TWI I2C support == Select Input device support == Enable Generic input layer (needed for keyboard,mouse,...) Disable Mouse interface Enable Joystick interface Enable Event interface Disable Keyboards Disable Mouse == Select Joysticks == Enable Analog Device AD7142 Joystick supportunder Customize Vendor/User Settings== Select Blackfin test programs == Enable input event device test</pre></div></li><li class="level1"><div class="li"> <strong> NOR Flash MTD driver test(JFFS2 FS)</strong></div><ul><li class="level2"><div class="li"> To check if the kernel supports the mtd device driver.</div></li><li class="level2"><div class="li"> Firstly erase the /dev/mtd2 device, copy the jffs2 image made from /rootfs to it, then mount the content of this device to another inode of the ram file system, e.g. /mnt. Finally compare the test file under /rootfs with that under /mnt. If they are the same, the case passes, otherwise it fails.</div></li><li class="level2"><div class="li"> When doing configuration, the kernel setting is the same as the way to enable the jffs2 filesystem. Details are in:<a href="http://docs.blackfin.uclinux.org/doku.php?id=enabling_jffs2" class="urlextern" title="http://docs.blackfin.uclinux.org/doku.php?id=enabling_jffs2" rel="nofollow">enable_jffs2</a>. As to the user settings, need more selection:<pre class="code">== Flash Tools == Select mtd-utils Enable eraseall Enable mkfs.jffs2</pre><p> These tools will be used in the test case.</p></div></li></ul></li><li class="level1"><div class="li"> <strong> NAND Flash MTD driver test(YAFFS)</strong></div><ul><li class="level2"><div class="li"> Build the uclinux kernel to support yaffs file system on nand flash:<pre class="code">under Customize Kernel Settings== Select Device Drivers == == Select Memory Technology Devices (MTD) == == Select NAND Flash Device Drivers == Enable NAND Device Support Enable NAND Flash device for BF537 STAMP board== Select File systems == == Select Miscellaneous filesystems == Enable YAFFS2 file system support</pre></div></li></ul></li><li class="level1"><div class="li"> <strong>ADSPI test(Net Scope,Net Awg)</strong></div><ul><li class="level2"><div class="li">It is a manual test to see if the ADC SPI card can acquire anolog signal from the environment and convert it to digital signal correctly. The sampled data then is formed into a picture and sent to the web browser through TCP/IP network. From the output of the web browser, we can tell if the ADC SPI works right.</div></li><li class="level2"><div class="li"> Build the uclinux kernel with ADC SPI driver support and ndso applications.:<pre class="code">under Customize Kernel Settings== Select Device Drivers == == Select Character devices == Enable Blackfin BF53x ADSP SPI ADC support under Customize Vendor/User Settings== Select Library Configuration == Enable Build libZ Enable Build libpng == Select Blackfin app programs== Enable Networked Software Defined Storage Oscilloscope or Enable Networked Arbitrary Waveform Generator (Please select only one of them and disable the other)</pre><p> Build this kernel and use it to boot the target board, configure the Ethernet card at kernel prompt:</p><pre class="code">#ifconfig eth0 10.100.4.50.</pre><p> Then starting the application :</p><pre class="code"> #ndso &. </pre><p> Open the web browser on host system, such as Mozilla, Firefox, <acronym title="Internet Explorer">IE</acronym>. Enter in the <acronym title="Uniform Resource Locator">URL</acronym> target ip address: </p><pre class="code"> http://10.100.4.50.</pre><p> Hit the <code>Acquire</code> button on the left, the picture sampled by the ADC converter can now been seen.</p></div></li></ul></li><li class="level1"><div class="li"> <strong>IDE device test - CD ROM,harddisk</strong></div><ul><li class="level2"><div class="li"> Support ide interfaced CD ROM and harddisk running on STAMP board.</div></li><li class="level2"><div class="li"> Please refer to the page for details <a href="http://docs.blackfin.uclinux.org/doku.php?id=blackfin_ide_ata_atapi_pio_mode_driver&s=ide" class="urlextern" title="http://docs.blackfin.uclinux.org/doku.php?id=blackfin_ide_ata_atapi_pio_mode_driver&s=ide" rel="nofollow">the IDE card doc</a>.</div></li></ul></li><li class="level1"><div class="li"> <strong>CF Memory card test</strong></div><ul><li class="level2"><div class="li"> Support CF Memory card in true IDE mode to be read/written by STAMP board.</div></li><li class="level2"><div class="li"> Please refer to the page for details <a href="http://docs.blackfin.uclinux.org/doku.php?id=compactflash_ide_ata_nand_flash_-_interface_card/" class="urlextern" title="http://docs.blackfin.uclinux.org/doku.php?id=compactflash_ide_ata_nand_flash_-_interface_card/" rel="nofollow">the CF card doc</a>.</div></li></ul></li><li class="level1"><div class="li"> <strong>802.11 wireless card test</strong></div><ul><li class="level2"><div class="li"> Support wireless ethernet card on STAMP board, which can have connection with wireless AP and do communication.</div></li><li class="level2"><div class="li"> Please refer to the page for details <a href="http://docs.blackfin.uclinux.org/doku.php?id=blackfin_802.11_wlan_-_orinoco_based_driver/" class="urlextern" title="http://docs.blackfin.uclinux.org/doku.php?id=blackfin_802.11_wlan_-_orinoco_based_driver/" rel="nofollow">the wireless card doc</a>.</div></li></ul></li><li class="level1"><div class="li"> <strong>USB host devices - memory stick,network(isp 1362,sl811)</strong></div><ul><li class="level2"><div class="li"> To expand usb port on stamp board. Details at:<a href="http://docs.blackfin.uclinux.org/doku.php?id=usb_add-on_card&s=usb" class="urlextern" title="http://docs.blackfin.uclinux.org/doku.php?id=usb_add-on_card&s=usb" rel="nofollow"> the usb add-on card</a>.</div></li></ul></li><li class="level1"><div class="li"> <strong>USB client device (network)</strong></div><ul><li class="level2"><div class="li"> To enable the second ethernet port through usb connection. Details at: <a href="http://docs.blackfin.uclinux.org/doku.php?id=blackfin_usb-lan_extender" class="urlextern" title="http://docs.blackfin.uclinux.org/doku.php?id=blackfin_usb-lan_extender" rel="nofollow">the usb-lan extender</a>. </div></li></ul></li><li class="level1"><div class="li"> <strong>Blue tooth</strong> </div></li><li class="level1"><div class="li"> <strong>Can bus test</strong> </div><ul><li class="level2"><div class="li"> To transmit the data between two target boards through can bus.</div></li><li class="level2"><div class="li"> It needs the target board running at a higher frequency: 625 MHZ CCLK and 125 MHZ SCLK.<pre class="code">under Customize Vendor/User Settings== Select Miscellaneous Application== Enable can4linux examples </pre></div></li><li class="level2"><div class="li"> After starting the kernel, do “modprobe can”, it would say can.ko is used and inserted. Receive data on one machine and send on the other one.<pre class="code">Machine one: can_send 10 01 02 03 04 05 06 07 08Machine two: receiveReceived with ret=1: 1408.437347 id=10 len=8 msg= 01 02 03 04 05 06 07 00 flags=0x00</pre></div></li></ul></li></ol></div><!-- SECTION [4855-18743] --><h3><a name="kernel_function_test" id="kernel_function_test">Kernel Function test</a></h3><div class="level3">
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -