DOCSLIB.ORG

I.MX Linux Reference Manual NXP Semiconductors

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
I.MX Linux Reference Manual NXP Semiconductors NXP Semiconductors Document identifier: IMXLXRM Reference Manual Rev. LF5.10.35_2.0.0, 30 June 2021 i.MX Linux Reference Manual NXP Semiconductors Contents Chapter 1 Introduction......................................................................................... 21 1.1 Overview..................................................................................................................................21 1.1.1 Software Base...........................................................................................................................21 1.1.2 Features.................................................................................................................................... 21 1.2 Audience..................................................................................................................................25 1.2.1 Conventions.............................................................................................................................. 25 1.2.2 Definitions, Acronyms, and Abbreviations.................................................................................25 1.3 References.............................................................................................................................. 29 Chapter 2 System................................................................................................ 31 2.1 Machine-Specific Layer (MSL)................................................................................................ 31 2.1.1 Introduction............................................................................................................................... 31 2.1.2 Interrupts (Operation)................................................................................................................31 2.1.2.1 Interrupt Hardware Operation...................................................................................................... 31 2.1.2.2 Interrupt Software Operation........................................................................................................31 2.1.2.3 Interrupt Features........................................................................................................................ 32 2.1.2.4 Interrupt Source Code Structure.................................................................................................. 32 2.1.2.5 Interrupt Programming Interface.................................................................................................. 32 2.1.3 Timer......................................................................................................................................... 32 2.1.3.1 Timer Software Operation............................................................................................................33 2.1.3.2 Timer Features.............................................................................................................................33 2.1.3.3 Timer Source Code Structure...................................................................................................... 33 2.1.3.4 Timer Programming Interface...................................................................................................... 33 2.1.4 Memory Map............................................................................................................................. 34 2.1.4.1 Memory Map Hardware Operation...............................................................................................34 2.1.4.2 Memory Map Features.................................................................................................................34 2.1.5 IOMUX.......................................................................................................................................34 2.1.5.1 IOMUX Hardware Operation........................................................................................................34 2.1.5.2 IOMUX Software Operation......................................................................................................... 34 2.1.5.3 IOMUX Features.......................................................................................................................... 35 2.1.5.4 IOMUX Source Code Structure....................................................................................................35 2.1.5.5 IOMUX Programming Interface....................................................................................................35 2.1.5.6 IOMUX Control Through GPIO Module....................................................................................... 36 2.1.5.6.1 GPIO Hardware Operation............................................................................................36 2.1.5.6.2 GPIO Software Operation (general)..............................................................................36 2.1.5.6.3 GPIO Implementation................................................................................................... 36 2.1.6 General Purpose Input/Output (GPIO)......................................................................................36 2.1.6.1 GPIO Software Operation............................................................................................................ 36 2.1.6.1.1 API for GPIO................................................................................................................. 37 2.1.6.2 GPIO Features.............................................................................................................................37 2.1.6.3 GPIO Module Source Code Structure..........................................................................................37 2.1.6.4 GPIO Programming Interface 2................................................................................................... 37 2.1.7 Clock......................................................................................................................................... 37 2.1.7.1 Clock Software Operation............................................................................................................ 38 2.1.7.2 Clock Features.............................................................................................................................38 2.1.7.3 Source Code Structure................................................................................................................ 38 2.1.7.4 .....................................................................................................................................................38 2.2 System Controller....................................................................................................................38 2.2.1 Introduction............................................................................................................................... 38 2.3 Boot Image.............................................................................................................................. 40 i.MX Linux Reference Manual, Rev. LF5.10.35_2.0.0, 30 June 2021 Reference Manual 2 / 275 NXP Semiconductors Contents 2.3.1 Introduction............................................................................................................................... 40 2.4 Anatop Regulator Driver..........................................................................................................41 2.4.1 Introduction............................................................................................................................... 41 2.4.2 Hardware Operation..................................................................................................................41 2.4.3 Software Operation................................................................................................................... 41 2.4.4 Driver Features......................................................................................................................... 42 2.4.5 Driver Interface Details..............................................................................................................42 2.4.6 Regulator APIs.......................................................................................................................... 42 2.4.7 Source Code Structure..............................................................................................................43 2.4.8 Menu Configuration Options..................................................................................................... 43 2.5 Power Management................................................................................................................ 43 2.5.1 Low Level Power Management (PM)........................................................................................ 43 2.5.1.1 Introduction.................................................................................................................................. 43 2.5.1.2 Software Operation...................................................................................................................... 44 2.5.1.3 Source Code Structure................................................................................................................ 45 2.5.1.4 Menu Configuration Options........................................................................................................ 46 2.5.1.5 Programming Interface...............................................................................................................
Load more

Recommended publications
  • MLNX OFED Documentation Rev 5.0-2.1.8.0
    MLNX_OFED Documentation Rev 5.0-2.1.8.0 Exported on May/21/2020 06:13 AM https://docs.mellanox.com/x/JLV-AQ Notice This document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. NVIDIA Corporation (“NVIDIA”) makes no representations or warranties, expressed or implied, as to the accuracy or completeness of the information contained in this document and assumes no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality. NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice. Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete. NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document. NVIDIA products are not designed, authorized, or warranted to be suitable for use in medical, military, aircraft, space, or life support equipment, nor in applications where failure or malfunction of the NVIDIA product can reasonably be expected to result in personal injury, death, or property or environmental damage.
    [Show full text]
  • In Defense of Rap Music: Not Just Beats, Rhymes, Sex, and Violence
    In Defense of Rap Music: Not Just Beats, Rhymes, Sex, and Violence THESIS Presented in Partial Fulfillment of the Requirements for the Master of Arts Degree in the Graduate School of The Ohio State University By Crystal Joesell Radford, BA Graduate Program in Education The Ohio State University 2011 Thesis Committee: Professor Beverly Gordon, Advisor Professor Adrienne Dixson Copyrighted by Crystal Joesell Radford 2011 Abstract This study critically analyzes rap through an interdisciplinary framework. The study explains rap‟s socio-cultural history and it examines the multi-generational, classed, racialized, and gendered identities in rap. Rap music grew out of hip-hop culture, which has – in part – earned it a garnering of criticism of being too “violent,” “sexist,” and “noisy.” This criticism became especially pronounced with the emergence of the rap subgenre dubbed “gangsta rap” in the 1990s, which is particularly known for its sexist and violent content. Rap music, which captures the spirit of hip-hop culture, evolved in American inner cities in the early 1970s in the South Bronx at the wake of the Civil Rights, Black Nationalist, and Women‟s Liberation movements during a new technological revolution. During the 1970s and 80s, a series of sociopolitical conscious raps were launched, as young people of color found a cathartic means of expression by which to describe the conditions of the inner-city – a space largely constructed by those in power. Rap thrived under poverty, police repression, social policy, class, and gender relations (Baker, 1993; Boyd, 1997; Keyes, 2000, 2002; Perkins, 1996; Potter, 1995; Rose, 1994, 2008; Watkins, 1998).
    [Show full text]
  • ELASTIC SEARCH – MAGENTO 2 COPYRIGHT 2018 MAGEDELIGHT.COM Page 2 of 6
    Elasticsearch - Magento 2 INSTALLATION GUIDE MAGEDELIGHT.COM Installation: Before installing the extension, please make below notes complete: Backup your web directory and store database. Elasticsearch – M2 Installation: Install elasticsearch on your webserver, here is the reference link http://blog.magedelight.com/how-to- install-elasticsearch-on-centos-7-ubuntu-14-10-linux-mint-17-1/ Unzip the extension package file into the root folder of your Magento 2 installation. Install elastic search library o Back up your current composer.json cp composer.json composer.json.bk o Edit composer.json file and add below code to required clause. “elasticsearch/elasticsearch” : “~5.0” o Update dependencies composer update Connect to SSH console of your server: o Navigate to root folder of your Magento 2 setup o Run command php -f bin/magento module:enable Magedelight_Elasticsearch o Run command php -f bin/magento setup:upgrade o Run command php -f bin/magento setup:static-content:deploy Flush store cache; log out from the backend and log in again ELASTIC SEARCH – MAGENTO 2 COPYRIGHT 2018 MAGEDELIGHT.COM Page 2 of 6 License Activation: Note: This section is not applicable for extension purchased from Magento Marketplace How to activate the extension? Step 1: Go to Admin Control Panel >Stores > Configuration > Magedelight > Elasticsearch > License Configuration, you will see Serial Key and Activation key fields in License Configuration. Please enter the keys you received on purchase of the product and save configuration. Step 2: Expand “General Configuration” tab, you will find list of domains for which license is purchased and configured, now select the domain you are going to use, you can select multiple domain by clicking “Ctrl + Select”.
    [Show full text]
  • PHP: Composer Orchestrating PHP Applications
    PHP: Composer Orchestrating PHP Applications Dayle Rees This book is for sale at http://leanpub.com/composer-php This version was published on 2016-05-16 This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. © 2016 Dayle Rees Tweet This Book! Please help Dayle Rees by spreading the word about this book on Twitter! The suggested tweet for this book is: I’m reading Composer: Orchestrating PHP Applications by @daylerees - https://leanpub.com/composer-php #composer The suggested hashtag for this book is #composer. Find out what other people are saying about the book by clicking on this link to search for this hashtag on Twitter: https://twitter.com/search?q=#composer Contents Acknowledgements ..................................... i Errata ............................................. ii Feedback ............................................ iii Translations ......................................... iv 1. Introduction ....................................... 1 2. Concept .......................................... 2 Dependency Management ............................... 2 Class Autoloading .................................... 3 Team Collaboration ................................... 3 3. Packages ......................................... 5 Application Packages .................................. 5 Dependency
    [Show full text]
  • UG1046 Ultrafast Embedded Design Methodology Guide
    UltraFast Embedded Design Methodology Guide UG1046 (v2.3) April 20, 2018 Revision History The following table shows the revision history for this document. Date Version Revision 04/20/2018 2.3 • Added a note in the Overview section of Chapter 5. • Replaced BFM terminology with VIP across the user guide. 07/27/2017 2.2 • Vivado IDE updates and minor editorial changes. 04/22/2015 2.1 • Added Embedded Design Methodology Checklist. • Added Accessing Documentation and Training. 03/26/2015 2.0 • Added SDSoC Environment. • Added Related Design Hubs. 10/20/2014 1.1 • Removed outdated information. •In System Level Considerations, added information to the following sections: ° Performance ° Clocking and Reset 10/08/2014 1.0 Initial Release of document. UltraFast Embedded Design Methodology Guide Send Feedback 2 UG1046 (v2.3) April 20, 2018 www.xilinx.com Table of Contents Chapter 1: Introduction Embedded Design Methodology Checklist. 9 Accessing Documentation and Training . 10 Chapter 2: System Level Considerations Performance. 13 Power Consumption . 18 Clocking and Reset. 36 Interrupts . 41 Embedded Device Security . 45 Profiling and Partitioning . 51 Chapter 3: Hardware Design Considerations Configuration and Boot Devices . 63 Memory Interfaces . 69 Peripherals . 76 Designing IP Blocks . 94 Hardware Performance Considerations . 102 Dataflow . 108 PL Clocking Methodology . 112 ACP and Cache Coherency. 116 PL High-Performance Port Access. 120 System Management Hardware Assistance. 124 Managing Hardware Reconfiguration . 127 GPs and Direct PL Access from APU . 133 Chapter 4: Software Design Considerations Processor Configuration . 137 OS and RTOS Choices . 142 Libraries and Middleware . 152 Boot Loaders . 156 Software Development Tools . 162 UltraFast Embedded Design Methodology GuideSend Feedback 3 UG1046 (v2.3) April 20, 2018 www.xilinx.com Chapter 5: Hardware Design Flow Overview .
    [Show full text]
  • RZ/G Verified Linux Package for 64Bit Kernel V1.0.5-RT Release Note For
    Release Note RZ/G Verified Linux Package for 64bit kernel Version 1.0.5-RT R01TU0311EJ0102 Rev. 1.02 Release Note for HTML5 Sep 7, 2020 Introduction This release note describes the contents, building procedures for HTML5 (Gecko) and important points of the RZ/G Verified Linux Package for 64bit kernel (hereinafter referred to as “VLP64”). In this release, Linux packages for HTML5 is preliminary and provided AS IS with no warranty. If you need information to build Linux BSPs without a GUI Framework of HTML5, please refer to “RZ/G Verified Linux Package for 64bit kernel Version 1.0.5-RT Release Note”. Contents 1. Release Items ................................................................................................................. 2 2. Build environment .......................................................................................................... 4 3. Building Instructions ...................................................................................................... 6 3.1 Setup the Linux Host PC to build images ................................................................................. 6 3.2 Building images to run on the board ........................................................................................ 8 3.3 Building SDK ............................................................................................................................. 12 4. Components ................................................................................................................. 13 5. Restrictions
    [Show full text]
  • Embedded Linux Systems with the Yocto Project™
    OPEN SOURCE SOFTWARE DEVELOPMENT SERIES Embedded Linux Systems with the Yocto Project" FREE SAMPLE CHAPTER SHARE WITH OTHERS �f, � � � � Embedded Linux Systems with the Yocto ProjectTM This page intentionally left blank Embedded Linux Systems with the Yocto ProjectTM Rudolf J. Streif Boston • Columbus • Indianapolis • New York • San Francisco • Amsterdam • Cape Town Dubai • London • Madrid • Milan • Munich • Paris • Montreal • Toronto • Delhi • Mexico City São Paulo • Sidney • Hong Kong • Seoul • Singapore • Taipei • Tokyo Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. For information about buying this title in bulk quantities, or for special sales opportunities (which may include electronic versions; custom cover designs; and content particular to your business, training goals, marketing focus, or branding interests), please contact our corporate sales depart- ment at [email protected] or (800) 382-3419. For government sales inquiries, please contact [email protected]. For questions about sales outside the U.S., please contact [email protected]. Visit us on the Web: informit.com Cataloging-in-Publication Data is on file with the Library of Congress.
    [Show full text]
  • ECE 598 – Advanced Operating Systems Lecture 19
    ECE 598 { Advanced Operating Systems Lecture 19 Vince Weaver http://web.eece.maine.edu/~vweaver [email protected] 7 April 2016 Announcements • Homework #7 was due • Homework #8 will be posted 1 Why use FAT over ext2? • FAT simpler, easy to code • FAT supported on all major OSes • ext2 faster, more robust filename and permissions 2 btrfs • B-tree fs (similar to a binary tree, but with pages full of leaves) • overwrite filesystem (overwite on modify) vs CoW • Copy on write. When write to a file, old data not overwritten. Since old data not over-written, crash recovery better Eventually old data garbage collected • Data in extents 3 • Copy-on-write • Forest of trees: { sub-volumes { extent-allocation { checksum tree { chunk device { reloc • On-line defragmentation • On-line volume growth 4 • Built-in RAID • Transparent compression • Snapshots • Checksums on data and meta-data • De-duplication • Cloning { can make an exact snapshot of file, copy-on- write different than link, different inodles but same blocks 5 Embedded • Designed to be small, simple, read-only? • romfs { 32 byte header (magic, size, checksum,name) { Repeating files (pointer to next [0 if none]), info, size, checksum, file name, file data • cramfs 6 ZFS Advanced OS from Sun/Oracle. Similar in idea to btrfs indirect still, not extent based? 7 ReFS Resilient FS, Microsoft's answer to brtfs and zfs 8 Networked File Systems • Allow a centralized file server to export a filesystem to multiple clients. • Provide file level access, not just raw blocks (NBD) • Clustered filesystems also exist, where multiple servers work in conjunction.
    [Show full text]
  • BATJ Class and Recital Information with Waiver
    Ballet & All That Jazz Ranelle W. Flurie, Director 18703 Crestwood Drive Hagerstown, MD 21742 301-797-2100 Fall 2020 BTJ is pleased to announce that we are returning to in-person and/or virtual classes coupled with a 2020 Fall Recital. Although it will be a bit different this year, we want to ensure that we showcase the talents and hard work of our dancers. We are working very hard to ensure safety first while providing class and recital instruction. Please remember to social distance, wear masks, and wash hands to keep our children safe. With that said, class instruction will begin on Monday, August 31st, and the three recitals will be held on Sunday, October 18th, and October 25th (details below). Please ensure your returning dancer is registered for fall classes via the Ballet and All That Jazz website (https://balletandallthatjazz.com/registration/), in- person, or by phone. We encourage new students to register in person. Registration is Tuesday, August 25th and Wednesday, August 26th from 5pm- 8pm at the Ballet and All That Jazz studio, located at 18703 Crestwood Drive, Hagerstown, Maryland 21742. For additional questions, contact us at 301-797-2100. Class Information: To ensure successful class instructions, please review the information below and reach out with any questions. • Classes will occur virtual/or in person. • Please ensure you have signed the waiver prior to class attendance (see form below). • Virtual class links will be sent at the beginning of the year for those who sign up for virtual instruction, and the same link will be use weekly.
    [Show full text]
  • The Robust Beauty of Improper Linear Models in Decision Making
    The Robust Beauty of Improper Linear Models in Decision Making ROBYN M. DAWES University of Oregon ABSTRACT: Proper linear models are those in which A proper linear model is one in which the predictor variables are given weights in such a way weights given to the predictor variables are chosen that the resulting linear composite optimally predicts in such a way as to optimize the relationship be- some criterion of interest; examples of proper linear tween the prediction and the criterion. Simple models are standard regression analysis, discriminant regression analysis is the most common example function analysis, and ridge regression analysis. Re- of a proper linear model; the predictor variables search summarized in Paul Meehl's book on clinical are weighted in such a way as to maximize the versus statistical prediction—and a plethora of re- search stimulated in part by that book—all indicates correlation between the subsequent weighted com- that when a numerical criterion variable (e.g., graduate posite and the actual criterion. Discriminant grade point average) is to be predicted from numerical function analysis is another example of a proper predictor variables, proper linear models outperform linear model; weights are given to the predictor clinical intuition. Improper linear models are those in variables in such a way that the resulting linear which the weights of the predictor variables are ob- composites maximize the discrepancy between two tained by some nonoptimal method; for example, they or more groups. Ridge regression analysis, an- may be obtained on the basis of intuition, derived other example (Darlington, 1978; Marquardt & from simulating a clinical judge's predictions, or set to Snee, 1975), attempts to assign weights in such be equal.
    [Show full text]
  • The Trevor Project’S Coming Out: a Handbook Are At
    COMING OUT A Handbook for LGBTQ Young People CONTENTS IDENTITY 4 HEALTHY RELATIONSHIPS 17 THE BASICS 4 SELF-CARE 18 What Is Sex Assigned at Birth? 5 Checking in on Your Mental Health 19 What Is Gender? 5 Warning Signs 19 Gender Identity 6 RESOURCES 20 Gender Expression 7 Transitioning 8 TREVOR PROGRAMS 21 What Is Sexual Orientation? 9 Map Your Own Identity 21 Sexual Orientation 10 Sexual/Physical Attraction 11 Romantic Attraction 12 Emotional Attraction 13 COMING OUT 14 Planning Ahead 14 Testing The Waters 15 Environment 15 Timing 15 Location 15 School 16 Support 16 Safety Around Coming Out 16 2 Exploring your sexual orientation Some people may share their identity with a few trusted friends online, some may choose to share and/or gender identity can bring up a lot with a counselor or a trusted family member, and of feelings and questions. Inside this handbook, others may want everyone in their life to know we will work together to explore your identity, about their identity. An important thing to know what it might be like to share your identity with is that for a lot of people, coming out doesn’t just others, and provide you with tools and guiding happen once. A lot of folks find themselves com- questions to help you think about what coming ing out at different times to different people. out means to you. It is all about what works for you, wherever you The Trevor Project’s Coming Out: A Handbook are at. The things you hear about coming out for LGBTQ Young People is here to help you nav- may make you feel pressured to take steps that igate questions around your identity.
    [Show full text]
  • Keane, for Allowing Us to Come and Visit with You Today
    BIL KEANE June 28, 1999 Joan Horne and myself, Ann Townsend, interviewers for the Town of Paradise Valley Historical Committee are privileged to interview Bil Keane. Mr. Keane has been a long time resident of the Town of Paradise Valley, but is best known and loved for his cartoon, The Family Circus. Thank you, Mr. Keane, for allowing us to come and visit with you today. May we have your permission to quote you in part or all of our conversation today? Bil Keane: Absolutely, anything you want to quote from it, if it's worthwhile quoting of course, I'm happy to do it. Ann Townsend: Thank you very much. Tell us a little bit about yourself and what brought you to hot Arizona? Bil Keane: Well, it was a TWA plane. I worked on the Philadelphia Bulletin for 15 years after I got out of the army in 1945. It was just before then end of 1958 that I had been bothered each year with allergies. I would sneeze in the summertime and mainly in the spring. Then it got in to be in the fall, then spring, summer and fall. The doctor would always prescribe at that time something that would alleviate it. At the Bulletin I was doing a regular comic and I was editor of their Fun Book. I had a nine to five job there and we lived in Roslyn which was outside Philadelphia and it was one hour and a half commute on the train and subway. I was selling a feature to the newspapers called Channel Chuckles, which was the little cartoon about television which I enjoyed doing.
    [Show full text]