DOCSLIB.ORG

Tool Installation for PMC-MC-X2/X4 with P2020 Series Processor

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Tool Installation for PMC-MC-X2/X4 with P2020 Series Processor DYNAMIC ENGINEERING 150 DuBois, Suite C Santa Cruz, CA 95060 (831) 457-8891 Fax (831) 457-4793 http://www.dyneng.com [email protected] Est. 1988 Tool installation for PMC-MC-X2/X4 with P2020 series processor This document contains information of proprietary interest to Dynamic Engineering. It has been supplied in confidence and the recipient, by accepting this material, agrees that the subject matter will not be copied or reproduced, in whole or in part, nor its contents revealed in any manner or to any person except to meet the purpose for which it was delivered. Dynamic Engineering has made every effort to ensure that this manual is accurate and complete. Still, the company reserves the right to make improvements or changes in the product described in this document at any time and without notice. Furthermore, Dynamic Engineering assumes no liability arising out of the application or use of the device described herein. Dynamic Engineering’s products are not authorized for use as critical components in life support devices or systems without the express written approval of the president of Dynamic Engineering. 6/22/2018 REV A2 Embedded Electronics Page 1 INTRODUCTION 3 DEVELOPMENT PLATFORM SETUP 3 CROSS PLATFORM DEVELOPMENT TOOLS SETUP 4 Build cross-development tools and images 7 Install toolchain on your development Host 7 Verify your installation 8 Verify development toolchain 9 Embedded Electronics Page 2 Introduction On the development board a minimized version of Linux 2.6.35 is installed. Linux minimal image is a Busy Box. Development tools are not a part of Busy Box environment. According to Linux traditions, native for the hardware platform development tools are part of full Linux image only. You cannot do development on a small, embedded platform with NXP’s P2020 CPU. Cross-platform development is typical Linux way for software development for embedded devices. It is necessary to install and build cross platform toolchain on the development host. Development platform setup The development desktop is Intel x86-64 based computer with Linux CentOS- 7.5.1804 with developer options installed. Standard development environment for that version of Linux comes with make tools version 3.82. That version has some bugs. Replace make 3.82 with make 4.1 procedure: cd /tmp wget http://ftp.gnu.org/gnu/make/make-4.1.tar.gz tar xvf make-4.1.tar.gz cd make-4.1/ ./configure make sudo make install rm -rf make-4.1.tar.gz make-4.1 After these few steps, the make files are installed in /usr/local/bin/make. => Skip if you already have installed make tools 4.1 or above. Embedded Electronics Page 3 Cross platform development tools setup P2020 is NXP’s popular communication processor with PowerPC Architecture. NXP has Linux SDK for Linux development for P2020 at https://www.nxp.com/support/developer-resources/run-time-software/linux- software-and-development-tools/linux-sdk-for-qoriq-processors:SDKLINUX You will need to register your name and email to download the SDK. Current SDK v.2.0 doesn’t support P2020 QorIQ processor and you will need to select Previous tab QorIQ Linux SDK v1.9 is the latest Linux development package for P2020 processor. Embedded Electronics Page 4 You need 3 packages only: Embedded Electronics Page 5 1. QorIQ SDK V1.9 PPCE500V2 CACHE.iso 2. QorIQ SDK V1.9 PPCE500V2 IMAGE.iso 3. QorIQ SDK V1.9 SOURCE.iso SDK Image has pre-built binaries. A good option to use them for reference. SDK Cache has pre-built binaries. T hey will save significant time for you if you install SDK Source and SDK cache into same folder. Mount SDK cache first and run ./install from the top folder. Don’t do anything else with SDK cache, please! You may unmount it after installation. Mount SDK source and run ./install. Choose same place when you have install SDK cache. Now you can follow QorIQ SDK 1.9 Documentation to prepare Host development environment, setup Poky to build images. Host development environment needs Python 2.7 or above. If you don’t have Python Procedure: $ wget https://www.python.org/ftp/python/2.7.6/Python-2.7.6.tar.xz [NOTE: Python 2.7.3 and python 2.7.5 can be used as well.] $ tar -xf Python-2.7.6.tar.xz $ cd Python-2.7.6 $ ./configure --prefix=/opt/python-2.7.6 $ make $ sudo make install Run export command [below] to ensure python 2.7.x is used for Yocto build. $ export PATH=/opt/python-2.7.6/bin:$PATH For a list of the Linux distributions tested by the Yocto Project community see SANITY_TESTED_DISTROS in poky/meta-yocto/conf/distro/poky.conf. The following is the detailed package list on the CentOS hosts: $ sudo yum install gawk make wget tar bzip2 gzip python unzip perl patch \ diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath socat SDL- devel xterm For the Fedora hosts: $ sudo yum install sudo yum install gawk make wget tar bzip2 gzip python unzip perl patch \ diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath \ Embedded Electronics Page 6 ccache perl-Data-Dumper perl-Text-ParseWords perl-Thread-Queue socat \ findutils which SDL-devel xterm For Ubuntu and Debian hosts: $ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \ build-essential chrpath socat libsdl1.2-dev xterm Extra packages are needed for Ubuntu-64b: $ sudo apt-get install lib32z1 lib32ncurses5 lib32bz2-1.0 ia32-libs lib32ncurses5- dev For OpenSUSE host: $ sudo zypper install python gcc gcc-c++ git chrpath make wget python-xml \ diffstat makeinfo python-curses patch socat libSDL-devel xterm To setup Poky execute a help command $ . ./fsl-setup-poky -h This command output provides a list of architectures to support by QorIQ SDK V1.9 Poky installation is $ . ./fsl-setup-env -m p2020rdb p2020rdb is a machine to support p2020 CPU. Build cross-development tools and images $ cd <sdk-install-dir>/build_p2020rdb $ bitbake <image-target> Where <image-target> is one of the following: • fsl-image-minimal : contains basic packages to boot up a board • fsl-image-core : contains common open source packages and FSL specific packages. • fsl-image-full : contains all packages in the full package list. • fsl-image-mfgtool : contains all the user space apps needed to deploy the fsl- image-mfgtool image to a USB stick, hard drive, or other large physical media. • fsl-image-virt : contains toolkit to interact with the virtualization capabilities of Linux • core-image-x11 : Freescale image with a very basic X11 image with a terminal • fsl-toolchain : the cross compiler binary package Select fsl-toolchain to build standalone toolchain only. Install toolchain on your development Host $ cd build_p2020rdb/tmp/deploy/sdk $ ./fsl-networking-eglibc-<host_arch>-<core>-toolchain-<release>.sh Embedded Electronics Page 7 The default installation path for standalone toolchain is /opt/fsl-qoriq/1.9/. The install folder can be specified during the installation procedure. Verify your installation $ echo $PATH you should see /opt/fsl-qoriq/1.9/ in the output list /opt/fsl-qoriq/1.9/sysroots/x86_64-fslsdk-linux/usr/bin:/opt/fsl- qoriq/1.9/sysroots/x86_64-fslsdk-linux/usr/bin/powerpc-fsl-linux- gnuspe:/home/alex/QorIQ-SDK-V1.9-20151210- yocto/sources/poky/scripts:/home/alex/QorIQ-SDK-V1.9-20151210- yocto/sources/poky/bitbake/bin:/home/alex/CodeSourcery/Sourcery_G++_Lite/bi n:/home/alex/CodeSourcery/Sourcery_G++_Lite/bin:/usr/lib64/qt- 3.3/bin:/home/alex/perl5/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbi n:/home/alex/.local/bin:/home/alex/bin Embedded Electronics Page 8 Verify development toolchain $ echo $CC output should be like that powerpc-fsl-linux-gnuspe-gcc -m32 -mcpu=8548 -mabi=spe -mspe -mfloat- gprs=double –sysroot=/opt/fsl-qoriq/1.9/sysroots/ppce500v2-fsl-linux-gnuspe That is a proof the development tools are installed and you are ready for Hello, World! Application development! When you compiled your first Hello,World! Application, copy your executable on the target for execution. Embedded Electronics Page 9 .
Load more

Recommended publications
  • Downloads." the Open Information Security Foundation
    Performance Testing Suricata The Effect of Configuration Variables On Offline Suricata Performance A Project Completed for CS 6266 Under Jonathon T. Giffin, Assistant Professor, Georgia Institute of Technology by Winston H Messer Project Advisor: Matt Jonkman, President, Open Information Security Foundation December 2011 Messer ii Abstract The Suricata IDS/IPS engine, a viable alternative to Snort, has a multitude of potential configurations. A simplified automated testing system was devised for the purpose of performance testing Suricata in an offline environment. Of the available configuration variables, seventeen were analyzed independently by testing in fifty-six configurations. Of these, three variables were found to have a statistically significant effect on performance: Detect Engine Profile, Multi Pattern Algorithm, and CPU affinity. Acknowledgements In writing the final report on this endeavor, I would like to start by thanking four people who made this project possible: Matt Jonkman, President, Open Information Security Foundation: For allowing me the opportunity to carry out this project under his supervision. Victor Julien, Lead Programmer, Open Information Security Foundation and Anne-Fleur Koolstra, Documentation Specialist, Open Information Security Foundation: For their willingness to share their wisdom and experience of Suricata via email for the past four months. John M. Weathersby, Jr., Executive Director, Open Source Software Institute: For allowing me the use of Institute equipment for the creation of a suitable testing
    [Show full text]
  • GNU Wget 1.10 the Non-Interactive Download Utility Updated for Wget 1.10, Apr 2005
    GNU Wget 1.10 The non-interactive download utility Updated for Wget 1.10, Apr 2005 by Hrvoje Nikˇsi´cand the developers Copyright c 1996–2005, Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being “GNU General Public License” and “GNU Free Documentation License”, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”. Chapter 1: Overview 1 1 Overview GNU Wget is a free utility for non-interactive download of files from the Web. It supports http, https, and ftp protocols, as well as retrieval through http proxies. This chapter is a partial overview of Wget’s features. • Wget is non-interactive, meaning that it can work in the background, while the user is not logged on. This allows you to start a retrieval and disconnect from the system, letting Wget finish the work. By contrast, most of the Web browsers require constant user’s presence, which can be a great hindrance when transferring a lot of data. • Wget can follow links in html and xhtml pages and create local versions of remote web sites, fully recreating the directory structure of the original site. This is sometimes referred to as “recursive downloading.” While doing that, Wget respects the Robot Exclusion Standard (‘/robots.txt’). Wget can be instructed to convert the links in downloaded html files to the local files for offline viewing.
    [Show full text]
  • Name Synopsis Description Options
    GPGTAR(1) GNU Privacy Guard 2.2 GPGTAR(1) NAME gpgtar −Encrypt or sign files into an archive SYNOPSIS gpgtar [options] filename1 [ filename2, ... ] directory1 [ directory2, ... ] DESCRIPTION gpgtar encrypts or signs files into an archive.Itisangpg-ized tar using the same format as used by PGP’s PGP Zip. OPTIONS gpgtar understands these options: --create Put givenfiles and directories into a vanilla ‘‘ustar’’archive. --extract Extract all files from a vanilla ‘‘ustar’’archive. --encrypt -e Encrypt givenfiles and directories into an archive.This option may be combined with option --symmetric for an archive that may be decrypted via a secret key orapassphrase. --decrypt -d Extract all files from an encrypted archive. --sign -s Makeasigned archive from the givenfiles and directories. This can be combined with option --encrypt to create a signed and then encrypted archive. --list-archive -t List the contents of the specified archive. --symmetric -c Encrypt with a symmetric cipher using a passphrase. The default symmetric cipher used is AES-128, but may be chosen with the --cipher-algo option to gpg. --recipient user -r user Encrypt for user id user.For details see gpg. --local-user user -u user Use user as the key tosign with. Fordetails see gpg. --output file -o file Write the archive tothe specified file file. --verbose -v Enable extra informational output. GnuPG 2.2.12 2018-12-11 1 GPGTAR(1) GNU Privacy Guard 2.2 GPGTAR(1) --quiet -q Trytobeasquiet as possible. --skip-crypto Skip all crypto operations and create or extract vanilla ‘‘ustar’’archives. --dry-run Do not actually output the extracted files.
    [Show full text]
  • With Yocto/Openembedded
    PORTING NEW CODE TO RISC-V WITH YOCTO/OPENEMBEDDED Martin Maas ([email protected]) 1st RISC-V Workshop, January 15, 2015 Monterey, CA WHY WE NEED A LINUX DISTRIBUTION • To build an application for RISC-V, you need to: – Download and build the RISC-V toolchain + Linux – Download, patch and build application + dependencies – Create an image and run it in QEMU or on hardware • Problems with this approach: – Error-prone: Easy to corrupt FS or get a step wrong – Reproducibility: Others can’t easily reuse your work – Rigidity: If a dependency changes, need to do it all over • We need a Linux distribution! – Automatic build process with dependency tracking – Ability to distribute binary packages and SDKs 2 RISCV-POKY: A PORT OF THE YOCTO PROJECT • We ported the Yocto Project – Official Linux Foundation Workgroup, supported by a large number of industry partners – Part I: Collection of hundreds of recipes (scripts that describe how to build packages for different platforms), shared with OpenEmbedded project – Part II: Bitbake, a parallel build system that takes recipes and fetches, patches, cross-compiles and produces packages (RPM/DEB), images, SDKs, etc. • Focus on build process and customizability 3 GETTING STARTED WITH RISCV-POKY • Let’s build a full Linux system including the GCC toolchain, Linux, QEMU + a large set of packages (including bash, ssh, python, perl, apt, wget,…) • Step I: Clone riscv-poky: git clone [email protected]:ucb-bar/riscv-poky.git • Step II: Set up the build system: source oe-init-build-env • Step III: Build an image (may
    [Show full text]
  • Replacing PGP 2.X with Gnupg
    Replacing PGP 2.x with GnuPG This article is based on an earlier PGP 2.x/GnuPG compatability guide (http://www.toehold.com/~kyle/pgp- compat.html) written by Kyle Hasselbacher (<[email protected]>). Mike Ashley (<[email protected]>) edited and expanded it. Michael Fischer v. Mollard (<[email protected]>) transformed the HTML source to Doc- Book SGML and also expanded it further. Some of the details described here came from the gnupg-devel and gnupg-user mailing lists. The workaround for both signing with and encrypting to an RSA key were taken from Gero Treuner’s compatability script (http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/changes.html). Please direct questions, bug reports, or suggesstions to the maintainer, Mike Ashley. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". Introduction This document describes how to communicate with people still using old versions of PGP 2.x GnuPG can be used as a nearly complete replacement for PGP 2.x. You may encrypt and decrypt PGP 2.x messages using imported old keys, but you cannot generate PGP 2.x keys. This document demonstrates how to extend the standard distribution of GnuPG to support PGP 2.x keys as well as what options must be used to ensure inter- operation with PGP 2.x users.
    [Show full text]
  • GNU Texinfo Font Subsystem I
    GNU Texinfo font subsystem i Table of Contents 1 Font management::::::::::::::::::::::::::::::: 1 1.1 Introduction ::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.1.1 Font features and attributes ::::::::::::::::::::::::::::::: 1 1.1.2 Current font attribute set ::::::::::::::::::::::::::::::::: 1 1.1.3 Font substitution :::::::::::::::::::::::::::::::::::::::::: 2 1.1.4 Other ::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 1.2 Font definition macros:::::::::::::::::::::::::::::::::::::::::: 3 1.3 Font selection macros :::::::::::::::::::::::::::::::::::::::::: 4 1.3.1 Relative font scaling ::::::::::::::::::::::::::::::::::::::: 4 1.4 Font substitution macros ::::::::::::::::::::::::::::::::::::::: 5 1.5 Font collections :::::::::::::::::::::::::::::::::::::::::::::::: 5 1.5.1 Font styles :::::::::::::::::::::::::::::::::::::::::::::::: 5 1.5.2 Font style selection :::::::::::::::::::::::::::::::::::::::: 5 1.5.3 Font styles for document elements ::::::::::::::::::::::::: 5 1.6 Input encodings :::::::::::::::::::::::::::::::::::::::::::::::: 8 1.7 Font encodings ::::::::::::::::::::::::::::::::::::::::::::::::: 8 Index :::::::::::::::::::::::::::::::::::::::::::::::: 9 Chapter 1: Font management 1 1 Font management Texinfo's font management macros allow customization of fonts used in the printed docu- ment. 1.1 Introduction In this chapter we introduce the basic concepts of font management in Texinfo. 1.1.1 Font features and attributes Each font can be characterized by a number of features. For example, a font can be char-
    [Show full text]
  • GNU Texinfo Reference Card @Contents Print a Complete Table of Contents
    GNU Texinfo Reference Card @contents Print a complete table of contents. Has no effect in Cross references (for Texinfo version 6.8) Info, which uses menus instead. Within the Info system http://www.gnu.org/software/texinfo/ Nodes @xref {node, [entry] , [node-title] , [info-file] , [manual] } Makes @node name Begin a new node. a reference that starts with ‘See’ in a printed manual. Follow Texinfo document skeleton command with punctuation. Only the first argument is @top title Mark the topmost @node in the file, which must be mandatory. Texinfo source files are plain text; standard extensions are defined on the line immediately preceding @top. The title is @pxref {node, [entry] , [node-title] , [info-file] , [manual] } Like ‘.texinfo’, ‘.texi’, and ‘.txi’. A Texinfo file must begin with formatted as a chapter-level heading. The entire top node, @xref, but starts with ‘see’ instead of ‘See’, and must be used lines like this: including the @node and @top lines, are normally enclosed with @ifnottex ... @end ifnottex. inside parentheses. \input texinfo @ref {node, [entry] , [node-title] , [info-file] , [manual] } Like @xref, @settitle name-of-manual @anchor {name} Define name as the current location, for use as a cross-reference target. but produces only the bare reference without ‘See’ or ‘see’; must ... be followed by a punctuation mark. the contents of the Texinfo document, ending with: @novalidate Suppress validation of node references and omit @bye creation of auxiliary files with T X. Use before @setfilename. @xrefautomaticsectiontitle on|off By default, use the section E title instead of the node name in cross references. Texinfo @-commands Chapter structuring Outside of Info Beginning a Texinfo document @lowersections Change subsequent chapters to sections, sections @url {url, [displayed-text] , [replacement] } Make a hyperlink to subsections, and so on.
    [Show full text]
  • This Book Doesn't Tell You How to Write Faster Code, Or How to Write Code with Fewer Memory Leaks, Or Even How to Debug Code at All
    Practical Development Environments By Matthew B. Doar ............................................... Publisher: O'Reilly Pub Date: September 2005 ISBN: 0-596-00796-5 Pages: 328 Table of Contents | Index This book doesn't tell you how to write faster code, or how to write code with fewer memory leaks, or even how to debug code at all. What it does tell you is how to build your product in better ways, how to keep track of the code that you write, and how to track the bugs in your code. Plus some more things you'll wish you had known before starting a project. Practical Development Environments is a guide, a collection of advice about real development environments for small to medium-sized projects and groups. Each of the chapters considers a different kind of tool - tools for tracking versions of files, build tools, testing tools, bug-tracking tools, tools for creating documentation, and tools for creating packaged releases. Each chapter discusses what you should look for in that kind of tool and what to avoid, and also describes some good ideas, bad ideas, and annoying experiences for each area. Specific instances of each type of tool are described in enough detail so that you can decide which ones you want to investigate further. Developers want to write code, not maintain makefiles. Writers want to write content instead of manage templates. IT provides machines, but doesn't have time to maintain all the different tools. Managers want the product to move smoothly from development to release, and are interested in tools to help this happen more often.
    [Show full text]
  • Latexsample-Thesis
    INTEGRAL ESTIMATION IN QUANTUM PHYSICS by Jane Doe A dissertation submitted to the faculty of The University of Utah in partial fulfillment of the requirements for the degree of Doctor of Philosophy Department of Mathematics The University of Utah May 2016 Copyright c Jane Doe 2016 All Rights Reserved The University of Utah Graduate School STATEMENT OF DISSERTATION APPROVAL The dissertation of Jane Doe has been approved by the following supervisory committee members: Cornelius L´anczos , Chair(s) 17 Feb 2016 Date Approved Hans Bethe , Member 17 Feb 2016 Date Approved Niels Bohr , Member 17 Feb 2016 Date Approved Max Born , Member 17 Feb 2016 Date Approved Paul A. M. Dirac , Member 17 Feb 2016 Date Approved by Petrus Marcus Aurelius Featherstone-Hough , Chair/Dean of the Department/College/School of Mathematics and by Alice B. Toklas , Dean of The Graduate School. ABSTRACT Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah.
    [Show full text]
  • The GNU Privacy Handbook the GNU Privacy Handbook Copyright © 1999 by the Free Software Foundation
    The GNU Privacy Handbook The GNU Privacy Handbook Copyright © 1999 by The Free Software Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front- Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". Please direct questions, bug reports, or suggestions concerning this manual to the maintainer, Mike Ashley (<jash- [email protected]>). When referring to the manual please specify which version of the manual you have by using this version string: $Name: v1_1 $. Contributors to this manual include Matthew Copeland, Joergen Grahn, and David A. Wheeler. J Horacio MG has translated the manual to Spanish. Table of Contents 1. Getting Started................................................................................................................................................ 6 Generating a new keypair............................................................................................................................ 6 Generating a revocation certificate .................................................................................................... 8 Exchanging keys ......................................................................................................................................... 8 Exporting a public key......................................................................................................................
    [Show full text]
  • PDF File (244K Characters)
    Information For Maintainers of GNU Software Richard Stallman last updated September 26, 2006 Information for maintainers of GNU software, last updated September 26, 2006. Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this entire document without royalty provided the copyright notice and this permission notice are preserved. i Table of Contents 1 About This Document ......................... 1 2 Stepping Down.................................. 1 3 Recruiting Developers .......................... 2 4 Legal Matters ................................... 2 4.1 Copyright Papers .............................................. 2 4.2 Legally Significant Changes .................................... 4 4.3 Recording Contributors ........................................ 5 4.4 Copyright Notices .............................................. 6 4.5 License Notices................................................. 7 4.6 External Libraries .............................................. 9 5 Cleaning Up Changes .......................... 9 6 Platforms to Support ......................... 10 7 Dealing With Mail ............................ 11 8 Recording Old Versions ....................... 12 9 Distributions ................................... 12 9.1 Distribution tar Files.......................................... 12 9.2 Distribution Patches .......................................... 13 9.3 Distribution on ftp.gnu.org.................................
    [Show full text]
  • Integral Estimation in Quantum Physics
    INTEGRAL ESTIMATION IN QUANTUM PHYSICS by Jane Doe A dissertation submitted to the faculty of The University of Utah in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Mathematical Physics Department of Mathematics The University of Utah May 2016 Copyright c Jane Doe 2016 All Rights Reserved The University of Utah Graduate School STATEMENT OF DISSERTATION APPROVAL The dissertation of Jane Doe has been approved by the following supervisory committee members: Cornelius L´anczos , Chair(s) 17 Feb 2016 Date Approved Hans Bethe , Member 17 Feb 2016 Date Approved Niels Bohr , Member 17 Feb 2016 Date Approved Max Born , Member 17 Feb 2016 Date Approved Paul A. M. Dirac , Member 17 Feb 2016 Date Approved by Petrus Marcus Aurelius Featherstone-Hough , Chair/Dean of the Department/College/School of Mathematics and by Alice B. Toklas , Dean of The Graduate School. ABSTRACT Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah.
    [Show full text]