ReleaseNotes.txt

   1 Intel(R) Platform Innovation Framework for EFI
   2 EFI Development Kit 2.0 (EDK 2.0)
   3 Alpha Release
   4 2006-04-26
   5
   6 Copyright (c) 2006, Intel Corporation
   7
   8 This document provides updates to documentation, along with a description on
   9 how to install and build the Edk 2.0.
  10
  11 Package Contents
  12 ----------------
  13   ReleaseNote.txt- These release notes for the package.
  14   MdePkg         - A package containing Industry Standard headers and libraries
  15   Tools          - A package containing Build Specific tools which are designed
  16                    to help the developer create and modify drivers and
  17                    libraries
  18   EdkModulePkg   - A package containing reference drivers
  19   EdkFatBinPkg   - A package containing binary DXE drivers for the Fat 32 file
  20                    system
  21   EdkShellBinPkg - A package containing binary Shell applications and commands
  22   EdkNt32Pkg     - A package containing the NT32 Emulation platform reference
  23
  24 Note: MDE and MDK that appear in other documentation refer to the MdePkg and
  25 Tools packages.  These two packages are the minimum requirement for developing
  26 EDK 2.0 Packages.  It is also recommended that the top level files included
  27 with the EDK be downloaded in conjunction with these two packages.
  28
  29 Note: Documents have the following filenames:
  30   EDK 2.0 Module Development Environment Library Specification v0.50
  31       (MDE_Library_Spec_0_50.rtf)
  32   EDK 2.0 Build and Packaging Architecture Specification v0.50
  33       (Build_Packaging_Spec_0_50.rtf)
  34   EDK 2.0 Platform Configuration Database Infrastructure Description v0.51
  35       (PCD_Infrastructure_0_51.rtf)
  36   EDK 2.0 Module Surface Area v0.50
  37       (Module_Surface_Area_0_50.rtf)
  38   EDK 2.0 Module Development Environment (MDE) Package Specification v0.50
  39       (MDE_Package_Spec_0_50.rtf)
  40   EDK 2.0 C Coding Standards Specification v0.50
  41       (C_Coding_Standards_Specification_ 0_50.rtf)
  42
  43 Pre-Requisites
  44 --------------
  45 The following list of tools must be installed on the development workstation
  46 prior to using the Edk 2.0.
  47
  48 Compiler Tool Chain
  49       Microsoft* Visual Studio .NET 2003*  (http://www.microsoft.com)
  50     or
  51       GCC version 4.x or later (http://gcc.gnu.org)
  52
  53 Assembler Tool Chain
  54       Microsoft Macro Assembler, version 6.15 or later
  55     or
  56       GNU binutils 2.16.1 or later
  57
  58 Java Development Kit ( Java 5.0 or later)
  59       Sun* jdk-1.5.0_04 or later (http://java.sun.com)
  60     or
  61       Bea Systems* jrockit-25.2.0-jdk1.5.0_03 or later (http://www.bea.com)
  62
  63 Java Tools
  64     Apache-ANT, version 1.6.5 or later (http://ant.apache.org)
  65     Ant-contrib, version 1.0b2 or later
  66       (http://sourceforge.net/project/showfiles.php?group_id=36177)
  67     Saxon8, version 8.1.1
  68       (http://prdownloads.sourceforge.net/saxon/saxonb8-1-1.zip?download)
  69     XMLBeans, version 2.1.0 or later (http://xmlbeans.apache.org)
  70
  71 Other Tools
  72     TortoiseSVN version 1.3.3. (http://tortoisesvn.tigris.org/)
  73
  74 Optional Tools
  75 --------------
  76 Compiler Tool Chains:
  77     Intel C++ Compiler for Windows, ver. 9.0 or later (http://www.intel.com)
  78     Intel C Compiler for EFI Byte Code, ver. 1.2 or later
  79       (http://www.intel.com/cd/software/products/asmo-na/eng/compilers/efibc/index.htm)
  80     Microsoft Driver Development Kit, version 3790.1830 or later
  81       (http://www.microsoft.com/whdc/devtools/ddk/orderddkcd.mspx)
  82     Microsoft ACPI Source Language Assembler, Version 1.0.13NT or later
  83     Intel ACPI Component Architecture, version 20060113
  84
  85 -----------------------
  86 Notes On Required Tools (Source Control System)
  87 -----------------------
  88 The EDK 2.0 is being managed by the Subversion Source Control on Tianocore.org.
  89 This software package provides speed, security, and additional features. The
  90 recommended client is TortoiseSVN version 1.3.3.
  91  (Available at http://tortoisesvn.tigris.org/)
  92
  93 There are instructions for the use of Subversion Source Control on the
  94 Tianocore.org website, as part of the checkout procedures.
  95
  96 The URL of the EDK 2.0 repository is:
  97   https://edk2.tianocore.org/svn/edk2/trunk/edk2
  98
  99 -----------------------
 100 Notes On Documentation
 101 -----------------------
 102 The documents are being managed by the Subversion Source Control on
 103 Tianocore.org.  The document repository is "docs" and must be checked out
 104 separately from the EDK 2.0 source tree. Refer to the checkout procedures on
 105 the Tianocore.org website for EDK 2.0.
 106
 107 The URL of the document repository is:
 108   https://edk2.tianocore.org/svn/edk2/trunk/docs
 109
 110
 111 -----------------------
 112 Notes On Required Tools (MS Windows environment example)
 113 -----------------------
 114 Software Installation Order:
 115   After installing the compiler tools and your Subversion client, the following
 116   required tools should be installed in order:
 117     Java JDK, Apache-Ant, ant-contrib, xmlbeans, saxon8
 118
 119 Java Development Kit:
 120
 121    The Java Environment Variable must be set before attempting to build.
 122        i.e. For Sun JDK (see note below*):
 123               set JAVA_HOME=c:\ Java\jdk1.5.0_06
 124        i.e. For Bea Systems:
 125               set JAVA_HOME=c:\Program Files\Java\jrockit-R26.0.0-jdk1.5.0_04
 126
 127   *When using the Sun JDK5.0
 128     During installation, you should specify the install directory as C:\Java
 129     instead of C:\Program Files\(or some other drive letter.)  While installing
 130     to this non-standard location is not required. In use, it seems to work
 131     more reliably.
 132     For the JDK, the install path would be C:\Java\jdk1.5.0_06
 133     For the JRE, the install path would be C:\Java\jre1.5.0_06
 134     Alternatively, you can specify C:\sunjavajdk and C:\sunjavajre.
 135
 136     NOTE: You cannot combine the location for the JDK and the JRE, as the JRE
 137     install removes most of the binaries and libraries installed by the JDK
 138     install.
 139
 140 Java Tools:
 141     The Apache-ANT requires the ANT_HOME environment variable to be set before
 142     attempting to build:
 143          i.e.  set ANT_HOME=c:\<full path to where ant was installed>
 144
 145     The ant-contrib.jar file should be installed in the %ANT_HOME%\lib
 146     directory.
 147
 148     The XMLBeans, requires the XMLBEANS_HOME environment variable to be set
 149     before attempting to build:
 150          i.e. set XMLBEANS_HOME=C:\<full path to where xmlbeans  was installed>
 151
 152     The saxon8.jar file should be copied to the %XMLBEANS_HOME%\lib directory.
 153
 154    The Ant and XMLBean tools are required to be in the path.
 155      MS system example:
 156         set PATH=%PATH%;%ANT_HOME%\bin;%XMLBEANS_HOME%\bin
 157      Linux/OS X bash shell example:
 158         export PATH=$PATH:${ANT_HOME}/bin:${XMLBEANS_HOME}/bin
 159
 160 -------------------------------------------------------------------------------
 161 Quick Start
 162 -----------
 163 Edit the text file, msft_tools_def.txt, located in the Tools/Conf directory.
 164 This file contains the names of the compiler tool chains and the location of
 165 the compiler binaries.  It has been pre-populated with the standard location
 166 for the Microsoft tool chains and includes the standard location of the Intel C
 167 Compiler for EFI Byte Code (EBC)
 168
 169 Follow the instructions at https://edk2.tianocore.org/servlets/ProjectSource to
 170 checkout the entire EDK 2.0 source tree.
 171
 172 In a command window, change to the top level directory of the Edk 2.0 sources.
 173   Set the WORKSPACE environment variable, e.g.:
 174
 175     c:\> set WORKSPACE=C:\MyWork\Edk2.0
 176
 177 To test your tool chain setup and to build the Supplied Tools, execute:
 178     c:\MyWork\Edk2.0\> edksetup
 179
 180 (This command will be referred to as the setup command throughout the rest of
 181 this document.)
 182       NOTE: You should run the setup command at the start of every session.
 183             This configures the environment to include the TianoTools and the
 184             Java applications and libraries.
 185
 186 Once this is completed, you are ready to test the Build, by executing:
 187     c:\MyWork\Edk2.0\> ant
 188
 189 This command builds all of the packages, including the NT32 reference platform.
 190
 191 -------------------------
 192 Individual Package Builds
 193 -------------------------
 194 After running the setup command, you can build individual packages.
 195   In the command window, cd to the package that you want to build, and just
 196   type:
 197     c:\MyWork\Edk2.0\EdkNt32Pkg\> ant
 198
 199 The EdkNt32Pkg has a special target; "run" that will execute the Nt32 emulation
 200 platform under Microsoft Windows.
 201
 202 To exit the Nt32 emulation platform, you may type reset at the EFI Shell>
 203 command prompt.  Alternately, you may use the Graphical interface, Boot
 204 Maintenance Manager screen's Reset System command.
 205
 206 ------------------------
 207 Individual Module Builds
 208 ------------------------
 209 After running the setup command, you can build individual modules.
 210   In the command window, cd to the module that you want to build, and just
 211   type:
 212     c:\MyWork\Edk2.0\MdePkg\Library\BaseLib\> ant
 213
 214 -------------------------------------------------------------------------------
 215 A Word on Apache-ANT
 216 --------------------
 217 The Apache-ANT program is a build tool that uses XML-based project files.
 218 Similar to Makefiles, these project files may contain multiple targets.  Most
 219 build.xml files in Edk2.0 are auto-generated; any edits performed on the
 220 build.xml files will be overwritten the next time ant is executed.
 221
 222 Pre-defined targets in the build.xml files include:
 223     all      - This target builds binaries for defined architectures
 224     clean    - This target removes object files generated by commands
 225     cleanall - This target removes all generated files and directories.
 226
 227 A Word on GCC tool chain
 228 ------------------------
 229 You will find a script in the tree that will download, configure, compile, and
 230 install a gcc 4.0.2 tool chain for development. It has support for the ia32
 231 architecture.  It can be built and run on Cygwin, Linux, and many other POSIX
 232 compliant host environments. There are a few tools that you will need on your
 233 host computer in order to compile the tool chain. Among them are bash, gcc,
 234 gmake, curl (or wget).
 235
 236 -------------------------------------------------------------------------------
 237
 238 General Information:
 239 ===============================================================
 240 Mechanisms:
 241 ----------
 242 A brief overview:
 243
 244 A) Surface Area Package Description (SPD) file contains information about the
 245 modules that the package contains, including the location of all MSA files, and
 246 public library names and headers that might be provided by a module in the
 247 package.  Packages are defined by SPD files.  (Found in the root of the Package
 248 subdirectory (i.e. EdkNt32Pkg)) The SPD is further explained in the "Build
 249 Packaging Specification" document.
 250
 251 B) Module Surface Area Definition (MSA) files.  A description of a module's
 252 surface area, with all module specific default flags and features specified.
 253 Refer to the "Module Surface Area Architecture Specification" for additional
 254 details. The MSA is further explained in the "Build Packaging Specification"
 255 document.
 256
 257 C) Module Build Description (MDB). The "as-built" definition file that contains
 258 only the changes to the default flags defined in the MSA. The MSA and MDB are
 259 further explained in the "Build Packaging Specification" document.
 260
 261 D) Platform Configuration Database (PCD).  A platform database which contains a
 262 variety of current platform settings or directives by which a driver or
 263 application can interact with.  The PCD is defined by the PCD_Protocol (This is
 264 further explained in the "Platform Configuration Database Infrastructure
 265 Description" document.
 266
 267 E) Library Class.  A library class is a logical grouping of similar functions.
 268 When developing components, the module surface area declares the class of
 269 libraries that can be used by the component. The MBD file specifies the
 270 instance(s) of the library that will be used during compilation/linking. All
 271 library type modules must include header files in their distribution package,
 272 as well as their surface area and module build description files. Components,
 273 on the other hand, need only provide the binary and build description files
 274 when distributing BINARY packages.  The Library Classes are further explained
 275 in the "Build Packaging Specification" document.
 276
 277 =========================================================================
 278 The common operations by developers of new modules are:
 279 -------------------------------------------------------
 280
 281 1) How to manually create a new module in a package:
 282   - The module source code must first be created in an appropriate directory
 283     (under the package the module is to be a part of.)
 284   - An MSA file must be created, spelling out all aspects of the module.
 285   - The MSA must be added to the SPD for the package to include the module.
 286
 287 -----------------------------------------
 288 2) Add/Remove module(s) to/from a package:
 289
 290   - Setup environment as Build
 291   - Add a module to a package
 292      * Generate the module SurfaceArea description file and build description
 293        file
 294      * Run GenBuildFile.bat under <PackageDir> to generate an entrance
 295        build.xml for the module
 296      * Add a new <MsaFile> element under <MsaFiles> into
 297        <PackageDir>\<PackageName>.spd, using relative path to package
 298      * Add a new <ModuleSA> entry under each <TianoImage> into
 299        <PackageDir>\<PackageName>.fpd file
 300
 301    - Remove a module from a package
 302      * Comment out or remove corresponding <MsaFile> element under <MsaFiles>
 303        from <PackageDir>\<PackageName>.spd
 304      * Comment out or remove corresponding <ModuleSA> entry under each
 305        <TianoImage> from <PackageDir>\<PackageName>.fpd
 306
 307 -----------------------------------
 308 3) How to manually create a package:
 309   - Identify the modules that are to be members of the project.
 310   - Identify the Variables and Guids required in and of the Package (including
 311     consumption/production information).
 312   - Create an SPD file defining these modules and calling out their MSA files.
 313
 314 --------------------------------------
 315 4) Declare a new Protocol in a package:
 316   - This release requires manual editing of the SPD file, adding the protocol
 317     to the ProtocolDeclarations section of the file.
 318   - Add the Protocol .h file to the Include\Protocol directory.
 319   - Add an <Entry> to the <ProtocolDeclarations> element in the
 320     <PackageName>.spd file
 321      * Each line contains Protocol base name then the global variable name and
 322        then the hex value of the Protocol GUID.
 323
 324 Example Protocol Entries (NOTE: The Guid entry is a single line in the SPD file):
 325 <ProtocolDeclarations>
 326   <Entry Name="UnicodeCollation">
 327   <C_Name>gEfiUnicodeCollationProtocolGuid</C_Name>
 328   <Guid>{ 0x1d85cd7f, 0xf43d, 0x11d2, 0x9a, 0xc, 0x0, 0x90, 0x27,
 329     0x3f, 0xc1, 0x4d }</Guid>
 330   <Entry Name="UsbHc">
 331   <C_Name>gEfiUsbHcProtocolGuid</C_Name>
 332   <Guid>{ 0xf5089266, 0x1aa0, 0x4953, 0x97, 0xd8, 0x56, 0x2f, 0x8a,
 333     0x73, 0xb5, 0x19 }</Guid>
 334
 335 ---------------------------------
 336 5) Declare a new PPI in a package:
 337  - This release requires manual editing of the SPD file
 338   - Add the PPI .h file to the Include\Ppi directory.
 339   - Add an <Entry> to the package <PpiDeclarations> element in the
 340     <PackageName>.spd file
 341      * Each line contains PPI base name then the global variable name and then
 342        the hex value of the PPI GUID.
 343
 344 Example Ppi Entries (NOTE: The Guid entry is a single line in the SPD file):
 345 <PpiDeclarations>
 346   <Entry Name="NtPeiLoadFile">
 347     <C_Name>gNtPeiLoadFilePpiGuid</C_Name>
 348     <Guid>{ 0xfd0c65eb, 0x405, 0x4cd2, 0x8a, 0xee, 0xf4, 0x0, 0xef, 0x13,
 349       0xba, 0xc2 }</Guid>
 350   </Entry>
 351   <Entry Name="NtThunk">
 352     <C_Name>gPeiNtThunkPpiGuid</C_Name>
 353     <Guid>{ 0x98c281e5, 0xf906, 0x43dd, 0xa9, 0x2b, 0xb0, 0x3, 0xbf,
 354       0x27, 0x65, 0xda }</Guid>
 355   </Entry>
 356 </PpiDeclarations>
 357
 358
 359 ----------------------------------
 360 6) Declare a new GUID in a package:
 361   - This release requires manual editing of the SPD file to include the new
 362     Guid.  This is identical to adding a ProtocolDeclaration or PpiDeclaration
 363     element as described above.
 364
 365 ---------------------------------------
 366 7) Define a new PCD entry in a package:
 367   - This release requires manual editing of the SPD file to include the new
 368     PCD.  New Pcd entries are added to the PcdDefinitions section of the
 369     <PackageName>.spd file using the following example for the format:
 370     NOTE: The hex <Token> value must be unique.
 371
 372 <PcdDefinitions>
 373   <PcdEntry ItemType="FIXED_AT_BUILD">
 374     <C_Name>PcdMaximumUnicodeStringLength</C_Name>
 375     <Token>0x00000001</Token>
 376     <DatumType>UINT32</DatumType>
 377     <DefaultValue>1000000</DefaultValue>
 378   </PcdEntry>
 379 </PcdDefinition>
 380
 381 ------------------------------
 382 8) Declare a new Library Class:
 383   - This release requires manual editing of the SPD file to include the new
 384     Library Class.  New Library Class entries are added to the
 385     LibraryClassDeclarations seection of the <PackageName>.spd file using
 386     the following example for the format:
 387
 388 <LibraryClassDeclarations>
 389   <LibraryClassDeclaration>
 390     <LibraryClass>BaseLib</LibraryClass>
 391     <IncludeHeader>Include/Library/BaseLib.h</IncludeHeader>
 392   </LibraryClassDeclaration>
 393 </LibraryClassDeclarations>
 394
 395 --------------------------------------
 396 9) Add a library instance to a package:
 397   - This requires manual MSA and MBD file.
 398
 399 -----------------------------
 400 10) Add a module to a package:
 401   - This requires manual MSA and MBD editing
 402
 403
 404 =======================================================
 405 Notes:
 406 ------
 407 The EDK 2.0 represents significant changes in the structure of the EDK.
 408 Therefore it is very difficult to isolate all of the changes of this version of
 409 the EDK with the previous (EDK 1.0) version.
 410
 411 Of particular note:
 412
 413 1) EDK 2.0 contains new hardware feature support for the ICH SMBUS Libraries.
 414    These libraries are provided to make Memory Reference Code (MRC) development
 415    easier.
 416 2) The MDE Libraries - The MDE libraries represent significant changes in source
 417    (with only limited changes in functionality.)  These new libraries conform
 418    to the "MDE Library Specification".
 419 3) The Fat Binary and the EDK Shell Binary Packages are functionally identical
 420    to the EDK 1.0 version.
 421 4) The EDK tools directory has been expanded to include more tools and more
 422    tool functionality.
 423 5) The EDK NT32 section has been ported to the new build process, but
 424    functionally remains the same as the EDK 1.0 version.
 425 6) The Application "HelloWorld" has been ported to EDK 2.0 as well.
 426
 427 =======================================================
 428 Virus scanned by McAfee VirusScan Enterprise 8.0.0, Virus Definitions 4718, no
 429 virus detected.
 430