Adaptation/GUID-7B9D4E46-6AF9-5B77-9BE3-8B1DFAC588BD.dita
changeset 15 307f4279f433
equal deleted inserted replaced
14:578be2adaf3e 15:307f4279f433
       
     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 concept
       
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
       
    12 <concept id="GUID-7B9D4E46-6AF9-5B77-9BE3-8B1DFAC588BD" xml:lang="en"><title>Set Up</title><shortdesc>Set up the source code and project files for an implementation
       
    13 of the USB client controller.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
       
    14 <p>This topic describes how to set up the source code and project
       
    15 files for an implementation of the USB client controller. </p>
       
    16 <p>Another more complicated example is implemented in the OMAP/H4
       
    17 platform. This platform has two USB device controllers. The code shows
       
    18 how two UDCs can be supported in the same source and build tree. The
       
    19 second controller (Fibula) is a High speed USB 2.0 compatible device
       
    20 controller, the code demonstrates how to support a USB 2.0 UDC and
       
    21 one or more USB 2.0 Client Devices. See the code in <filepath>...\omap-hrp\...</filepath>. </p>
       
    22 <p>The suggested steps are as follows: </p>
       
    23 <ol id="GUID-4850DC56-9ABA-5B34-8C5B-A314D0DB08B8">
       
    24 <li id="GUID-883110DC-0314-590C-B8F9-0A0663615445"><p>Decide where
       
    25 to put the source and header files for the platform-specific layer
       
    26 . Normally the USB device controller is part of the ASSP, and you
       
    27 would put the source files in the ASSP directory. For an external
       
    28 USB device controller, you would use the Variant directory instead. </p> </li>
       
    29 <li id="GUID-BB60E177-D816-5EE1-BF93-A9DF4CB1BE86"><p>Implement the
       
    30 platform-specific Layer within your chosen source and header files. </p> <p>If you have a header file with a name in the shape of <filepath>ASSP.h</filepath>, then you will put USB Device Controller register
       
    31 definitions and register bit definitions here. </p> </li>
       
    32 <li id="GUID-01DDD063-64F5-57EF-A404-965127E612E2"><p>Define the <filepath>.mmp</filepath> file for the USB client controller (the PDD), and
       
    33 put this into your chosen directory. Remember that the platform-specific
       
    34 layer is just <i>part</i> of the USB client controller, and the <filepath>.mmp</filepath> file needs to contain a list of <i>all</i> source
       
    35 files that need to be compiled. </p> </li>
       
    36 <li id="GUID-337F3E69-68C6-5A44-9406-59AFCA681F4E"><p>Add the name
       
    37 of the <filepath>.mmp</filepath> file (without the file extension)
       
    38 to your ASSP's <filepath>.inf</filepath> file in the <codeph>PRJ_MMPFILES</codeph> section. This must be in the same directory. This tells the <filepath>abld</filepath> tool about the existence of the <filepath>.mmp</filepath> file. </p> </li>
       
    39 </ol>
       
    40 </conbody></concept>