1 <?xml version="1.0" encoding="utf-8"?>

     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->

     3 <!-- This component and the accompanying materials are made available under the terms of the License 

     4 "Eclipse Public License v1.0" which accompanies this distribution, 

     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->

     6 <!-- Initial Contributors:

     7     Nokia Corporation - initial contribution.

     8 Contributors: 

     9 -->

    10 <!DOCTYPE task

    11   PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">

    12 <task id="GUID-092F414B-2279-4ADB-970F-75DAB8A80BD7" xml:lang="en"><title>SDIO Testing Guide</title><shortdesc>How to run unit tests of the SDIO platform-specific layer.</shortdesc><prolog><metadata><keywords/></metadata></prolog><taskbody>

    13 <prereq id="GUID-A029444C-0BF1-4D78-88EF-48AFBC35606B">       <p>Before

    14 running this test, you must do the following:<ul>

    15 <li><p>Port the SDIO Controller for your platform (see <xref href="GUID-9BBDFF77-5E2C-4E13-BEB3-716CC80B3375.dita">SDIO Implementation

    16 Guide</xref>)</p></li>

    17 <li><p>Build the test ROM.</p></li>

    18 <li><p>Boot the device with the test ROM.</p></li>

    19 </ul></p>     </prereq>

    20 <context id="GUID-88D222F5-0078-42E9-B1AF-67C32056EDBE"> <p>After

    21 you have ported the SDIO Controller on your platform, you can test

    22 it using the provided unit test application, SDIOTest. </p><p>The

    23 test application runs in a text shell and is made of two parts:<ul>

    24 <li><p>The test program, <filepath>sdiotest.exe</filepath> tests the

    25 Controller in isolation, at the interface level.</p></li>

    26 <li><p>The test driver,  <filepath>d_sdioif.ldd</filepath> uses the SDIO API, which is a kernel-side interface.</p> </li>

    27 </ul></p><p>The source code of the test application is in <filepath>/e32utils/sdio/source/</filepath>.</p><p>You must build <filepath>d_sdioif.ldd</filepath> for the appropriate platform and <filepath>sdiotest.exe</filepath> for the appropriate CPU architecture.</p><p>To include the two test components in a ROM, specify the <filepath>sdiotests.iby</filepath> file in your command line when building

    28 the image, such as in the following example:<codeblock xml:space="preserve">rom.bat -v h4hrp -i armv5 --symbol –t sdiotests.iby -m USE_SDIO_SD_MMC</codeblock></p><p>The SDIOTest utility is not an automated test: it performs

    29 various unitary operations which can be used to validate the behavior

    30 of the SDIO Controller. First, you request an operation by pressing

    31 the corresponding key on the command line. Then, you compare the resulting

    32 display with the data expected from the card. </p><p>The following

    33 steps provide an example of how to test your port.</p>     </context>

    34 <steps id="GUID-4DD07DEC-6017-4237-BE46-1D69E5FBD744-GENID-1-2-1-10-1-5-1-9-1-1-8-1-7-1-3-3">

    35 <step id="GUID-A295D44C-B646-4C27-842F-E11828BD2C6B"><cmd>Run the

    36 SDIOTest application.</cmd>

    37 </step>

    38 <step id="GUID-9A69E5AD-E938-4092-A8C2-CB65C37C8962-GENID-1-2-1-10-1-5-1-9-1-1-8-1-7-1-3-3-2"><cmd>Power up

    39 the stack by pressing the <userinput>P</userinput> key.</cmd>

    40 <stepresult><p>The stack must report that no card is present.</p></stepresult>

    41 </step>

    42 <step id="GUID-7F13CFE3-7B78-42EF-8BEA-682435B5F228"><cmd>Insert a

    43 card and power it up.</cmd>

    44 <stepresult><p>The stack must report that a card is present. </p></stepresult>

    45 </step>

    46 <step id="GUID-5FB0E930-1590-44FF-8C44-4DD842065C5E"><cmd>Read the

    47 card information by pressing the <userinput>I</userinput> key.</cmd>

    48 <stepresult><p>The data returned by the stack must match the data

    49 sheet you have for the card.</p></stepresult>

    50 </step>

    51 <step id="GUID-6798C237-7567-4BC8-9D69-358871167864"><cmd>Read the

    52 common control registers by pressing the <userinput>R</userinput> key.</cmd>

    53 <stepresult><p>The values must match the expected card data.</p></stepresult>

    54 </step>

    55 <step id="GUID-39001CA5-47E5-4340-B70C-13C4AD2A0266"><cmd>Read the

    56 common configuration by pressing the <userinput>C</userinput> key.</cmd>

    57 <stepresult><p>The values must match the expected card data.</p></stepresult>

    58 </step>

    59 <step id="GUID-CF489FD9-D291-4FFB-9FC7-F1EB5C80416F"><cmd>Read information

    60 about the I/O function by pressing the <userinput>F</userinput> key.</cmd>

    61 <stepresult><p>The data returned by the stack must match the I/O specifications

    62 of the card.</p></stepresult>

    63 </step>

    64 <step id="GUID-EB45AEEA-6EEA-4B9E-B0C4-A2BF66252812"><cmd>Quit the

    65 test by pressing the <userinput>Q</userinput> key.</cmd>

    66 </step>

    67 </steps>

    68 </taskbody></task>