7 Nokia Corporation - initial contribution. |
7 Nokia Corporation - initial contribution. |
8 Contributors: |
8 Contributors: |
9 --> |
9 --> |
10 <!DOCTYPE concept |
10 <!DOCTYPE concept |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
12 <concept id="GUID-180973A1-5C0A-5A85-82CC-E6B739A7F207" xml:lang="en"><title>Validation</title><shortdesc>Describes the test code to validate a port of the MMC Controller.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
12 <concept id="GUID-180973A1-5C0A-5A85-82CC-E6B739A7F207" xml:lang="en"><title>Platform |
|
13 Specific Layer Validation</title><shortdesc>Describes the test code to validate a port of the MMC Controller.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
13 <p>There are three stages involved in testing a port of the MultiMediaCard |
14 <p>There are three stages involved in testing a port of the MultiMediaCard |
14 controller. The first stage tests the controller in isolation; subsequent |
15 controller. The first stage tests the controller in isolation; subsequent |
15 stages test an additional area of functionality. </p> |
16 stages test an additional area of functionality. </p> |
16 <p>All three stages involve text shell based test programs and test drivers, |
17 <p>All three stages involve text shell based test programs and test drivers, |
17 and therefore these tests can be run by just building a text shell ROM. You |
18 and therefore these tests can be run by just building a text shell ROM. You |
71 local media sub-system, in effect accessing the card as a local drive. This |
72 local media sub-system, in effect accessing the card as a local drive. This |
72 requires a kernel side test driver <filepath>D_DRVIF.LDD</filepath> as well |
73 requires a kernel side test driver <filepath>D_DRVIF.LDD</filepath> as well |
73 as the test program itself. </p> <p>This is not a 'go/no-go' type test, but |
74 as the test program itself. </p> <p>This is not a 'go/no-go' type test, but |
74 is a test utility that can perform a small variety of operations. These are |
75 is a test utility that can perform a small variety of operations. These are |
75 selected a simple interactive way by pressing appropriate keys. It is used |
76 selected a simple interactive way by pressing appropriate keys. It is used |
76 to test that card initialisation and single block read and write requests |
77 to test that card initialization and single block read and write requests |
77 are performed successfully. </p> </li> |
78 are performed successfully. </p> </li> |
78 <li id="GUID-BCCDA1BB-7205-5C0D-A0CC-607E44196624"><p> <filepath>T_ATADRV.EXE</filepath> tests |
79 <li id="GUID-BCCDA1BB-7205-5C0D-A0CC-607E44196624"><p> <filepath>T_ATADRV.EXE</filepath> tests |
79 that card initialisation and simple read and write requests succeed. It also |
80 that card initialization and simple read and write requests succeed. It also |
80 tests multi-block read/write operations, format requests, accessing the device |
81 tests multi-block read/write operations, format requests, accessing the device |
81 following a media change event, and a machine power down event. </p> <p>This |
82 following a media change event, and a machine power down event. </p> <p>This |
82 is a 'go/no-go' type test. If this test succeeds, you can have fairly high |
83 is a 'go/no-go' type test. If this test succeeds, you can have fairly high |
83 confidence that the F32 test suite will run successfully. </p> </li> |
84 confidence that the F32 test suite will run successfully. </p> </li> |
84 </ol> <table id="GUID-D29E7820-6241-5B6E-B242-4B7037BA7344"> |
85 </ol> <table id="GUID-D29E7820-6241-5B6E-B242-4B7037BA7344"> |